draft-ietf-tsvwg-addip-sctp-19.txt   draft-ietf-tsvwg-addip-sctp-20.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track Q. Xie Intended status: Standards Track Q. Xie
Expires: September 21, 2007 Motorola, Inc. Expires: October 7, 2007 Motorola, Inc.
M. Tuexen M. Tuexen
Univ. of Applied Sciences Muenster Univ. of Applied Sciences Muenster
S. Maruyama S. Maruyama
M. Kozuka M. Kozuka
Kyoto University Kyoto University
March 20, 2007 April 5, 2007
Stream Control Transmission Protocol (SCTP) Dynamic Address Stream Control Transmission Protocol (SCTP) Dynamic Address
Reconfiguration Reconfiguration
draft-ietf-tsvwg-addip-sctp-19.txt draft-ietf-tsvwg-addip-sctp-20.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 41 skipping to change at page 1, line 41
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 21, 2007. This Internet-Draft will expire on October 7, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes extensions to the Stream Control Transmission This document describes extensions to the Stream Control Transmission
Protocol (SCTP) [RFC2960] that provides a method to reconfigure IP Protocol (SCTP) [RFC2960] that provides a method to reconfigure IP
address information on an existing association. address information on an existing association.
skipping to change at page 2, line 24 skipping to change at page 2, line 24
4.1.1. Address Configuration Change Chunk (ASCONF) . . . . . 6 4.1.1. Address Configuration Change Chunk (ASCONF) . . . . . 6
4.1.2. Address Configuration Acknowledgment Chunk 4.1.2. Address Configuration Acknowledgment Chunk
(ASCONF-ACK) . . . . . . . . . . . . . . . . . . . . . 7 (ASCONF-ACK) . . . . . . . . . . . . . . . . . . . . . 7
4.2. New Parameter Types . . . . . . . . . . . . . . . . . . . 8 4.2. New Parameter Types . . . . . . . . . . . . . . . . . . . 8
4.2.1. Add IP Address . . . . . . . . . . . . . . . . . . . . 9 4.2.1. Add IP Address . . . . . . . . . . . . . . . . . . . . 9
4.2.2. Delete IP Address . . . . . . . . . . . . . . . . . . 10 4.2.2. Delete IP Address . . . . . . . . . . . . . . . . . . 10
4.2.3. Error Cause Indication . . . . . . . . . . . . . . . . 11 4.2.3. Error Cause Indication . . . . . . . . . . . . . . . . 11
4.2.4. Set Primary IP Address . . . . . . . . . . . . . . . . 12 4.2.4. Set Primary IP Address . . . . . . . . . . . . . . . . 12
4.2.5. Success Indication . . . . . . . . . . . . . . . . . . 13 4.2.5. Success Indication . . . . . . . . . . . . . . . . . . 13
4.2.6. Adaptation Layer Indication . . . . . . . . . . . . . 14 4.2.6. Adaptation Layer Indication . . . . . . . . . . . . . 14
4.3. New Error Causes . . . . . . . . . . . . . . . . . . . . . 14 4.2.7. Supported Extensions Parameter . . . . . . . . . . . . 14
4.3. New Error Causes . . . . . . . . . . . . . . . . . . . . . 15
4.3.1. Error Cause: Request to Delete Last Remaining IP 4.3.1. Error Cause: Request to Delete Last Remaining IP
Address . . . . . . . . . . . . . . . . . . . . . . . 15 Address . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.2. Error Cause: Operation Refused Due to Resource 4.3.2. Error Cause: Operation Refused Due to Resource
Shortage . . . . . . . . . . . . . . . . . . . . . . . 15 Shortage . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.3. Error Cause: Request to Delete Source IP Address . . . 16 4.3.3. Error Cause: Request to Delete Source IP Address . . . 17
4.3.4. Error Cause: Association Aborted due to illegal 4.3.4. Error Cause: Association Aborted due to illegal
ASCONF-ACK . . . . . . . . . . . . . . . . . . . . . . 17 ASCONF-ACK . . . . . . . . . . . . . . . . . . . . . . 18
4.3.5. Error Cause: Request refused - no authorization. . . . 17 4.3.5. Error Cause: Request refused - no authorization. . . . 18
5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1. ASCONF Chunk Procedures . . . . . . . . . . . . . . . . . 18 5.1. ASCONF Chunk Procedures . . . . . . . . . . . . . . . . . 19
5.1.1. Congestion Control of ASCONF Chunks . . . . . . . . . 20 5.1.1. Congestion Control of ASCONF Chunks . . . . . . . . . 21
5.2. Upon reception of an ASCONF Chunk. . . . . . . . . . . . . 21 5.2. Upon reception of an ASCONF Chunk. . . . . . . . . . . . . 22
5.3. General rules for address manipulation . . . . . . . . . . 23 5.3. General rules for address manipulation . . . . . . . . . . 24
5.3.1. A special case for OOTB ABORT Chunks . . . . . . . . . 27 5.3.1. A special case for OOTB ABORT Chunks . . . . . . . . . 28
5.3.2. A special case for changing an address. . . . . . . . 27 5.3.2. A special case for changing an address. . . . . . . . 28
5.4. Setting of the primary address . . . . . . . . . . . . . . 28 5.4. Setting of the primary address . . . . . . . . . . . . . . 29
5.5. Bundling of multiple ASCONFs . . . . . . . . . . . . . . . 28 5.5. Bundling of multiple ASCONFs . . . . . . . . . . . . . . . 29
6. Security Considerations . . . . . . . . . . . . . . . . . . . 29 6. Security Considerations . . . . . . . . . . . . . . . . . . . 30
7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 30 7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 31
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32
9. Normative References . . . . . . . . . . . . . . . . . . . . . 31 9. Normative References . . . . . . . . . . . . . . . . . . . . . 32
Appendix A. Abstract Address Handling . . . . . . . . . . . . . . 32 Appendix A. Abstract Address Handling . . . . . . . . . . . . . . 33
A.1. General remarks . . . . . . . . . . . . . . . . . . . . . 32 A.1. General remarks . . . . . . . . . . . . . . . . . . . . . 33
A.2. Generalized endpoints . . . . . . . . . . . . . . . . . . 32 A.2. Generalized endpoints . . . . . . . . . . . . . . . . . . 33
A.3. Associations . . . . . . . . . . . . . . . . . . . . . . . 33 A.3. Associations . . . . . . . . . . . . . . . . . . . . . . . 34
A.4. Relationship with RFC 2960 . . . . . . . . . . . . . . . . 34 A.4. Relationship with RFC 2960 . . . . . . . . . . . . . . . . 35
A.5. Rules for address manipulation . . . . . . . . . . . . . . 34 A.5. Rules for address manipulation . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 35 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36
Intellectual Property and Copyright Statements . . . . . . . . . . 37 Intellectual Property and Copyright Statements . . . . . . . . . . 38
1. Introduction 1. Introduction
A local host may have multiple points of attachment to the Internet, A local host may have multiple points of attachment to the Internet,
giving it a degree of fault tolerance from hardware failures. SCTP giving it a degree of fault tolerance from hardware failures. SCTP
was developed to take full advantage of such a multi-homed host to was developed to take full advantage of such a multi-homed host to
provide a fast failover and association survivability in the face of provide a fast failover and association survivability in the face of
such hardware failures. However, many modern computers allow for the such hardware failures. However, many modern computers allow for the
dynamic addition and deletion of network cards (sometimes termed a dynamic addition and deletion of network cards (sometimes termed a
hot-pluggable interface). Complicate this with the ability of a hot-pluggable interface). Complicate this with the ability of a
skipping to change at page 8, line 46 skipping to change at page 8, line 46
4.2. New Parameter Types 4.2. New Parameter Types
The seven new parameters added follow the format defined in section The seven new parameters added follow the format defined in section
3.2.1 of RFC2960 [RFC2960]. Table 2, 3 and 4 describe the 3.2.1 of RFC2960 [RFC2960]. Table 2, 3 and 4 describe the
parameters. parameters.
Address Configuration Parameters Parameter Type Address Configuration Parameters Parameter Type
------------------------------------------------- -------------------------------------------------
Set Primary Address 0xC004 Set Primary Address 0xC004
Adaptation Layer Indication 0xC006 Adaptation Layer Indication 0xC006
Supported Extensions 0x8008
Table 2: Parameters that can be used in INIT/INIT-ACK chunk Table 2: Parameters that can be used in INIT/INIT-ACK chunk
Address Configuration Parameters Parameter Type Address Configuration Parameters Parameter Type
------------------------------------------------- -------------------------------------------------
Add IP Address 0xC001 Add IP Address 0xC001
Delete IP Address 0xC002 Delete IP Address 0xC002
Set Primary Address 0xC004 Set Primary Address 0xC004
Table 3: Parameters used in ASCONF Parameter Table 3: Parameters used in ASCONF Parameter
skipping to change at page 14, line 38 skipping to change at page 14, line 38
documents. documents.
Valid Chunk Appearance Valid Chunk Appearance
The Adaptation Layer Indication parameter may appear in INIT or INIT- The Adaptation Layer Indication parameter may appear in INIT or INIT-
ACK chunk and SHOULD be passed to the receivers upper layer protocol ACK chunk and SHOULD be passed to the receivers upper layer protocol
based upon the upper layer protocol configuration of the SCTP stack. based upon the upper layer protocol configuration of the SCTP stack.
This parameter MUST NOT be sent in any other chunks and if it is This parameter MUST NOT be sent in any other chunks and if it is
received in another chunk it MUST be ignored. received in another chunk it MUST be ignored.
4.2.7. Supported Extensions Parameter
This parameter is used at startup to identify any additional
extensions that the sender supports. The sender MUST support both
the sending and the receiving of any chunk types listed within the
Supported Extensions Parameter. An implementation supporting this
extension MUST list the ASCONF and the ASCONF-ACK chunks in its INIT
and INIT-ACK parameters.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 0x8008 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CHUNK TYPE 1 | CHUNK TYPE 2 | CHUNK TYPE 3 | CHUNK TYPE 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CHUNK TYPE N | PAD | PAD | PAD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type This field holds the IANA defined parameter type for
Supported Extensions Parameter. The suggested value of this field
for IANA is 0x8008.
Parameter Type Length This field holds the length of the parameter,
including the Parameter Type, Parameter Length and any addition
supported extensions. Note: the length MUST NOT include any padding.
CHUNK TYPE X This field(s) hold the chunk type of any SCTP
extension(s) that are currently supported by the sending SCTP.
Multiple chunk types may be defined listing each additional feature
that the sender supports. The sender MUST NOT include multiple
Supported Extensions Parameter within any chunk.
Parameter Appearance This parameter may appear in the INIT or INIT-
ACK chunk. This parameter MUST NOT appear in any other chunk.
4.3. New Error Causes 4.3. New Error Causes
Five new Error Causes are added to the SCTP Operational Errors, Five new Error Causes are added to the SCTP Operational Errors,
primarily for use in the ASCONF-ACK Chunk. primarily for use in the ASCONF-ACK Chunk.
Cause Code Cause Code
Value Cause Code Value Cause Code
--------- ---------------- --------- ----------------
0x0100 Request to Delete Last Remaining IP Address. 0x0100 Request to Delete Last Remaining IP Address.
0x0101 Operation Refused Due to Resource Shortage. 0x0101 Operation Refused Due to Resource Shortage.
skipping to change at page 30, line 27 skipping to change at page 31, line 27
acceptable. The second chunk type must come from the range where acceptable. The second chunk type must come from the range where
only the upper bit is set to one. We recommend 0x80 but any other only the upper bit is set to one. We recommend 0x80 but any other
available code point with the upper bit set is also acceptable. The available code point with the upper bit set is also acceptable. The
chunk types with there suggested values are shown below. chunk types with there suggested values are shown below.
Chunk Type Chunk Name Chunk Type Chunk Name
-------------------------------------------------------------- --------------------------------------------------------------
0xC1 Address Configuration Change Chunk (ASCONF) 0xC1 Address Configuration Change Chunk (ASCONF)
0x80 Address Configuration Acknowledgment (ASCONF-ACK) 0x80 Address Configuration Acknowledgment (ASCONF-ACK)
All of the parameter types must come from the range of types where All of the parameter types, with the exception of the supported
the upper two bits are set, we recommend 0xC001 - 0xC006, as shown parameters extension, must come from the range of types where the
below. Note: that for any of these values a different unique upper two bits are set, we recommend 0xC001 - 0xC006, as shown below.
parameter type may be assigned by IANA as long as the upper bits The supported parameters type extension must come from the range
correspond to the ones specified in this document. The suggested where only the upper bit is set, we recommend 0x8008. Note: that for
parameter types are listed below: any of these values a different unique parameter type may be assigned
by IANA as long as the upper bits correspond to the ones specified in
this document. The suggested parameter types are listed below:
Parameter Type Parameter Name Parameter Type Parameter Name
------------------------------------------------- -------------------------------------------------
0x8008 Supported Extensions
0xC001 Add IP Address 0xC001 Add IP Address
0xC002 Delete IP Address 0xC002 Delete IP Address
0xC003 Error Cause Indication 0xC003 Error Cause Indication
0xC004 Set Primary Address 0xC004 Set Primary Address
0xC005 Success Indication 0xC005 Success Indication
0xC006 Adaptation Layer Indication 0xC006 Adaptation Layer Indication
The five new error causes can be any value, in this document we have The five new error causes can be any value, in this document we have
used 0x0100-0x0104 in an attempt to separate these from the common used 0x0100-0x0104 in an attempt to separate these from the common
ranges of error codes. Any other unassigned values are also ranges of error codes. Any other unassigned values are also
skipping to change at page 31, line 26 skipping to change at page 32, line 27
IETF Consensus action as defined in RFC2434 [RFC2434]. For this new IETF Consensus action as defined in RFC2434 [RFC2434]. For this new
registry no initial values are being added by this document, however registry no initial values are being added by this document, however
draft-ietf-rddp-sctp will add the first entry. draft-ietf-rddp-sctp will add the first entry.
8. Acknowledgments 8. Acknowledgments
The authors would like to express a special note of thanks to Michael The authors would like to express a special note of thanks to Michael
Ramahlo and Phillip Conrad for there extreme efforts in the early Ramahlo and Phillip Conrad for there extreme efforts in the early
formation of this draft. formation of this draft.
The authors wish to thank Jon Berger, Greg Kendall, Seok Koh, Peter The authors wish to thank Jon Berger, Mark Butler, Lars Eggert,
Janardhan Iyengar, Greg Kendall, Seok Koh, Salvatore Loreto, Peter
Lei, John Loughney, Ivan Arias Rodriguez, Renee Revis, Marshall Rose, Lei, John Loughney, Ivan Arias Rodriguez, Renee Revis, Marshall Rose,
Chip Sharp, and Irene Ruengeler for their invaluable comments. Ronnie Sellars, Chip Sharp, and Irene Ruengeler for their invaluable
comments.
The authors would also like to give special mention to Maria-Carmen The authors would also like to give special mention to Maria-Carmen
Belinchon and Ian Rytina for there early contributions to this Belinchon and Ian Rytina for there early contributions to this
document and their thoughtful comments. document and their thoughtful comments.
9. Normative References 9. Normative References
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122, October 1989.
 End of changes. 14 change blocks. 
39 lines changed or deleted 84 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/