[rfc-dist] RFC 5061 on Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Sep 21 15:21:56 PDT 2007

A new Request for Comments is now available in online RFC libraries.

        RFC 5061

        Title:      Stream Control Transmission Protocol (SCTP) 
                    Dynamic Address Reconfiguration 
        Author:     R. Stewart, Q. Xie,
                    M. Tuexen, S. Maruyama,
                    M. Kozuka
        Status:     Standards Track
        Date:       September 2007
        Mailbox:    rrs at cisco.com, 
                    Qiaobing.Xie at motorola.com, 
                    tuexen at fh-muenster.de, mail at marushin.gr.jp, 
                    ma-kun at kozuka.jp
        Pages:      41
        Characters: 91851
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-addip-sctp-22.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5061.txt

A local host may have multiple points of attachment to the Internet,
giving it a degree of fault tolerance from hardware failures.  Stream
Control Transmission Protocol (SCTP) (RFC 4960) was developed to take
full advantage of such a multi-homed host to provide a fast failover
and association survivability in the face of such hardware failures.
This document describes an extension to SCTP that will allow an SCTP
stack to dynamically add an IP address to an SCTP association,
dynamically delete an IP address from an SCTP association, and to
request to set the primary address the peer will use when sending to
an endpoint.  [STANDARDS TRACK]

This document is a product of the Transport Area Working Group
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list