IPv6 addressing and Stream Control Transmission Protocol
draft-stewart-tsvwg-sctpipv6-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Randall R. Stewart , Dr. Steve E. Deering | ||
| Last updated | 2002-04-11 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-stewart-tsvwg-sctpipv6-01.txt
Abstract
Stream Control Transmission Protocol [RFC2960] provides transparent multi-homing to its upper layer users. This multi-homing is accomplished through the passing of address parameters in the initial setup message used by SCTP. In an IPv4 network all addresses are passed with no consideration for their scope and routeablility. In a IPv6 network special considerations MUST be made to properly bring up associations between SCTP endpoints that have IPv6 [RFC2460] addresses bound within their association. This document defines those considerations and enumerates general rules that an SCTP endpoint MUST use in formulating both the INIT and INIT-ACK chunks.
Authors
Randall R. Stewart
Dr. Steve E. Deering
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)