metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 5061: Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC5061
Published
September 2007
Authors
R. Stewart; Q. Xie; M. Tuexen; S. Maruyama; M. Kozuka
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
41
Also known as
—

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5061-stream-control-transmission-protocol-sctp-dynamic-address-reconfiguration