draft-ietf-tsvwg-addip-sctp-12.txt   draft-ietf-tsvwg-addip-sctp-13.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft M. Ramalho Internet-Draft M. Ramalho
Expires: December 9, 2005 Cisco Systems, Inc. Expires: May 26, 2006 Cisco Systems, Inc.
Q. Xie Q. Xie
Motorola, Inc. Motorola, Inc.
M. Tuexen M. Tuexen
Univ. of Applied Sciences Muenster Univ. of Applied Sciences Muenster
P. Conrad P. Conrad
University of Delaware University of Delaware
June 7, 2005 November 22, 2005
Stream Control Transmission Protocol (SCTP) Dynamic Address Stream Control Transmission Protocol (SCTP) Dynamic Address
Reconfiguration Reconfiguration
draft-ietf-tsvwg-addip-sctp-12.txt draft-ietf-tsvwg-addip-sctp-13.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of Section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims have been or will be disclosed, and any of which he or she becomes
of which he or she is aware have been or will be disclosed, and aware will be disclosed, in accordance with Section 6 of BCP 79.
any of which he or she becomes 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 December 9, 2005. This Internet-Draft will expire on May 26, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Additional Chunks and Parameters . . . . . . . . . . . . . . . 6 3. Additional Chunks and Parameters . . . . . . . . . . . . . . . 6
3.1 New Chunk Types . . . . . . . . . . . . . . . . . . . . . 6 3.1. New Chunk Types . . . . . . . . . . . . . . . . . . . . . 6
3.1.1 Address Configuration Change Chunk (ASCONF) . . . . . 6 3.1.1. Address Configuration Change Chunk (ASCONF) . . . . . 6
3.1.2 Address Configuration Acknowledgment Chunk 3.1.2. Address Configuration Acknowledgment Chunk
(ASCONF-ACK) . . . . . . . . . . . . . . . . . . . . . 7 (ASCONF-ACK) . . . . . . . . . . . . . . . . . . . . . 7
3.2 New Parameter Types . . . . . . . . . . . . . . . . . . . 8 3.2. New Parameter Types . . . . . . . . . . . . . . . . . . . 8
3.2.1 Add IP Address . . . . . . . . . . . . . . . . . . . . 9 3.2.1. Add IP Address . . . . . . . . . . . . . . . . . . . . 9
3.2.2 Delete IP Address . . . . . . . . . . . . . . . . . . 10 3.2.2. Delete IP Address . . . . . . . . . . . . . . . . . . 10
3.2.3 Error Cause Indication . . . . . . . . . . . . . . . . 11 3.2.3. Error Cause Indication . . . . . . . . . . . . . . . . 11
3.2.4 Set Primary IP Address . . . . . . . . . . . . . . . . 12 3.2.4. Set Primary IP Address . . . . . . . . . . . . . . . . 12
3.2.5 Success Indication . . . . . . . . . . . . . . . . . . 13 3.2.5. Success Indication . . . . . . . . . . . . . . . . . . 13
3.2.6 Adaptation Layer Indication . . . . . . . . . . . . . 13 3.2.6. Adaptation Layer Indication . . . . . . . . . . . . . 14
3.3 New Error Causes . . . . . . . . . . . . . . . . . . . . . 14 3.2.7. Supported Extensions Parameter . . . . . . . . . . . . 14
3.3.1 Error Cause: Request to Delete Last Remaining IP 3.3. New Error Causes . . . . . . . . . . . . . . . . . . . . . 15
Address . . . . . . . . . . . . . . . . . . . . . . . 14 3.3.1. Error Cause: Request to Delete Last Remaining IP
3.3.2 Error Cause: Operation Refused Due to Resource Address . . . . . . . . . . . . . . . . . . . . . . . 15
Shortage . . . . . . . . . . . . . . . . . . . . . . . 15 3.3.2. Error Cause: Operation Refused Due to Resource
3.3.3 Error Cause: Request to Delete Source IP Address . . . 16 Shortage . . . . . . . . . . . . . . . . . . . . . . . 16
3.3.4 Error Cause: Association Aborted due to illegal 3.3.3. Error Cause: Request to Delete Source IP Address . . . 17
ASCONF-ACK . . . . . . . . . . . . . . . . . . . . . . 17 3.3.4. Error Cause: Association Aborted due to illegal
3.3.5 Error Cause: Request refused - no authorization. . . . 17 ASCONF-ACK . . . . . . . . . . . . . . . . . . . . . . 18
4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.3.5. Error Cause: Request refused - no authorization. . . . 18
4.1 ASCONF Chunk Procedures . . . . . . . . . . . . . . . . . 19 4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.1.1 Congestion Control of ASCONF Chunks . . . . . . . . . 20 4.1. ASCONF Chunk Procedures . . . . . . . . . . . . . . . . . 20
4.2 Upon reception of an ASCONF Chunk. . . . . . . . . . . . . 21 4.1.1. Congestion Control of ASCONF Chunks . . . . . . . . . 21
4.3 General rules for address manipulation . . . . . . . . . . 23 4.2. Upon reception of an ASCONF Chunk. . . . . . . . . . . . . 22
4.3.1 A special case for OOTB ABORT chunks . . . . . . . . . 27 4.3. General rules for address manipulation . . . . . . . . . . 24
4.3.2 A special case for changing an address. . . . . . . . 27 4.3.1. A special case for OOTB ABORT chunks . . . . . . . . . 28
4.4 Setting of the primary address . . . . . . . . . . . . . . 28 4.3.2. A special case for changing an address. . . . . . . . 28
5. Security Considerations . . . . . . . . . . . . . . . . . . . 29 4.4. Setting of the primary address . . . . . . . . . . . . . . 29
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 30 5. Security Considerations . . . . . . . . . . . . . . . . . . . 30
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 31
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 31 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
A. Abstract Address Handling . . . . . . . . . . . . . . . . . . 34 Appendix A. Abstract Address Handling . . . . . . . . . . . . . . 33
A.1 General remarks . . . . . . . . . . . . . . . . . . . . . 34 A.1. General remarks . . . . . . . . . . . . . . . . . . . . . 33
A.2 Generalized endpoints . . . . . . . . . . . . . . . . . . 34 A.2. Generalized endpoints . . . . . . . . . . . . . . . . . . 33
A.3 Associations . . . . . . . . . . . . . . . . . . . . . . . 35 A.3. Associations . . . . . . . . . . . . . . . . . . . . . . . 34
A.4 Relationship with RFC 2960 . . . . . . . . . . . . . . . . 36 A.4. Relationship with RFC 2960 . . . . . . . . . . . . . . . . 35
A.5 Rules for address manipulation . . . . . . . . . . . . . . 36 A.5. Rules for address manipulation . . . . . . . . . . . . . . 35
Intellectual Property and Copyright Statements . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36
Intellectual Property and Copyright Statements . . . . . . . . . . 38
1. Introduction 1. Introduction
To extend the utility and application scenarios of SCTP, this To extend the utility and application scenarios of SCTP, this
document introduces optional extensions that provide SCTP with the document introduces optional extensions that provide SCTP with the
ability to: ability to:
1. reconfigure IP address information on an existing association. 1. reconfigure IP address information on an existing association.
2. set the remote primary path. 2. set the remote primary path.
skipping to change at page 6, line 7 skipping to change at page 6, line 7
2. Conventions 2. Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
they appear in this document, are to be interpreted as described in they appear in this document, are to be interpreted as described in
RFC2119 [2]. RFC2119 [2].
3. Additional Chunks and Parameters 3. Additional Chunks and Parameters
This section describes the addition of two new chunks and, six new This section describes the addition of two new chunks and, seven new
parameters to allow: parameters to allow:
o Dynamic addition of IP Addresses to an association. o Dynamic addition of IP Addresses to an association.
o Dynamic deletion of IP Addresses from an association. o Dynamic deletion of IP Addresses from an association.
o A request to set the primary address the peer will use when o A request to set the primary address the peer will use when
sending to an endpoint. sending to an endpoint.
Additionally, this section describes three new error causes that Additionally, this section describes three new error causes that
support these new chunks and parameters. support these new chunks and parameters.
3.1 New Chunk Types 3.1. New Chunk Types
This section defines two new chunk types that will be used to This section defines two new chunk types that will be used to
transfer the control information reliably. Table 1 illustrates the transfer the control information reliably. Table 1 illustrates the
two new chunk types. two new chunk types.
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)
skipping to change at page 6, line 43 skipping to change at page 6, line 43
It should be noted that the ASCONF Chunk format requires the receiver It should be noted that the ASCONF Chunk format requires the receiver
to report to the sender if it does not understand the ASCONF Chunk. to report to the sender if it does not understand the ASCONF Chunk.
This is accomplished by setting the upper bits in the chunk type as This is accomplished by setting the upper bits in the chunk type as
described in RFC2960 [6] section 3.2. Note that the upper two bits described in RFC2960 [6] section 3.2. Note that the upper two bits
in the ASCONF Chunk are set to one. As defined in RFC2960 [6] in the ASCONF Chunk are set to one. As defined in RFC2960 [6]
section 3.2, setting these upper bits in this manner will cause the section 3.2, setting these upper bits in this manner will cause the
receiver that does not understand this chunk to skip the chunk and receiver that does not understand this chunk to skip the chunk and
continue processing, but report in an Operation Error Chunk using the continue processing, but report in an Operation Error Chunk using the
'Unrecognized Chunk Type' cause of error. 'Unrecognized Chunk Type' cause of error.
3.1.1 Address Configuration Change Chunk (ASCONF) 3.1.1. Address Configuration Change Chunk (ASCONF)
This chunk is used to communicate to the remote endpoint one of the This chunk is used to communicate to the remote endpoint one of the
configuration change requests that MUST be acknowledged. The configuration change requests that MUST be acknowledged. The
information carried in the ASCONF Chunk uses the form of a Type- information carried in the ASCONF Chunk uses the form of a Type-
Length-Value (TLV), as described in "3.2.1 Optional/Variable-length Length-Value (TLV), as described in "3.2.1 Optional/Variable-length
Parameter Format" in RFC2960 [6], for all variable parameters. This Parameter Format" in RFC2960 [6], for all variable parameters. This
chunk MUST be sent in an authenticated way by using the mechanism chunk MUST be sent in an authenticated way by using the mechanism
defined in SCTP-AUTH [7]. If this chunk is received unauthenticated defined in SCTP-AUTH [7]. If this chunk is received unauthenticated
it MUST be silently discarded as described in SCTP-AUTH [7]. it MUST be silently discarded as described in SCTP-AUTH [7].
skipping to change at page 7, line 36 skipping to change at page 7, line 36
valid range of Serial Number is from 0 to 4294967295 (2**32 - 1). valid range of Serial Number is from 0 to 4294967295 (2**32 - 1).
Serial Numbers wrap back to 0 after reaching 4294967295. Serial Numbers wrap back to 0 after reaching 4294967295.
Address Parameter : 8 or 20 bytes (depending on type) Address Parameter : 8 or 20 bytes (depending on type)
This field contains an address parameter, either IPv6 or IPv4, from This field contains an address parameter, either IPv6 or IPv4, from
RFC2960 [6]. The address is an address of the sender of the ASCONF RFC2960 [6]. The address is an address of the sender of the ASCONF
chunk, the address MUST be considered part of the association by the chunk, the address MUST be considered part of the association by the
peer endpoint (the receiver of the ASCONF chunk). This field may be peer endpoint (the receiver of the ASCONF chunk). This field may be
used by the receiver of the ASCONF to help in finding the used by the receiver of the ASCONF to help in finding the
association. This parameter MUST be present in every ASCONF message association. If the address 0.0.0.0 or ::0 is provided the receiver
i.e. it is a mandatory TLV parameter. MAY lookup the association by other information provided in the
packet. This parameter MUST be present in every ASCONF message i.e.
it is a mandatory TLV parameter.
Note the host name address parameter is NOT allowed and MUST be Note the host name address parameter is NOT allowed and MUST be
ignored if received in any ASCONF message. ignored if received in any ASCONF message.
ASCONF Parameter: TLV format ASCONF Parameter: TLV format
Each Address configuration change is represented by a TLV parameter Each Address configuration change is represented by a TLV parameter
as defined in Section 3.2. One or more requests may be present in an as defined in Section 3.2. One or more requests may be present in an
ASCONF Chunk. ASCONF Chunk.
3.1.2 Address Configuration Acknowledgment Chunk (ASCONF-ACK) 3.1.2. Address Configuration Acknowledgment Chunk (ASCONF-ACK)
This chunk is used by the receiver of an ASCONF Chunk to acknowledge This chunk is used by the receiver of an ASCONF Chunk to acknowledge
the reception. It carries zero or more results for any ASCONF the reception. It carries zero or more results for any ASCONF
Parameters that were processed by the receiver. This chunk MUST be Parameters that were processed by the receiver. This chunk MUST be
sent in an authenticated way by using the mechanism defined in SCTP- sent in an authenticated way by using the mechanism defined in SCTP-
AUTH [7]. If this chunk is received unauthenticated it MUST be AUTH [7]. If this chunk is received unauthenticated it MUST be
silently discarded as described in SCTP-AUTH [7]. silently discarded as described in SCTP-AUTH [7].
0 1 2 3 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 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
skipping to change at page 8, line 39 skipping to change at page 8, line 41
ASCONF Parameter Response : TLV format ASCONF Parameter Response : TLV format
The ASCONF Parameter Response is used in the ASCONF-ACK to report The ASCONF Parameter Response is used in the ASCONF-ACK to report
status of ASCONF processing. By default, if a responding endpoint status of ASCONF processing. By default, if a responding endpoint
does not include any Error Cause, a success is indicated. Thus a does not include any Error Cause, a success is indicated. Thus a
sender of an ASCONF-ACK MAY indicate complete success of all TLVs in sender of an ASCONF-ACK MAY indicate complete success of all TLVs in
an ASCONF by returning only the Chunk Type, Chunk Flags, Chunk Length an ASCONF by returning only the Chunk Type, Chunk Flags, Chunk Length
(set to 8) and the Serial Number. (set to 8) and the Serial Number.
3.2 New Parameter Types 3.2. New Parameter Types
The six 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 [6]. Table 2 and 3 describes the parameters. 3.2.1 of RFC2960 [6]. Table 2, 3 and 4 describes the parameters.
Address Configuration Parameters Parameter Type Address Configuration Parameters Parameter Type
------------------------------------------------- -------------------------------------------------
Set Primary Address 0xC004 Set Primary Address 0xC004
Adaption Layer Indication 0xC006 Adaption 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 2: Parameters used in ASCONF Parameter Table 3: Parameters used in ASCONF Parameter
Address Configuration Parameters Parameter Type Address Configuration Parameters Parameter Type
------------------------------------------------- -------------------------------------------------
Error Cause Indication 0xC003 Error Cause Indication 0xC003
Success Indication 0xC005 Success Indication 0xC005
Table 3: Parameters used in ASCONF Parameter Response Table 4: Parameters used in ASCONF Parameter Response
Any parameter that appears where it is not allowed (for example a Any parameter that appears where it is not allowed (for example a
0xC002 parameter appearing within an INIT or INIT-ACK) MAY be 0xC002 parameter appearing within an INIT or INIT-ACK) MAY be
responded to with an ABORT by the receiver of the invalid parameter. responded to with an ABORT by the receiver of the invalid parameter.
3.2.1 Add IP Address 3.2.1. Add IP Address
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0xC001 | Length = Variable | | Type = 0xC001 | Length = Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASCONF-Request Correlation ID | | ASCONF-Request Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Parameter | | Address Parameter |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 9, line 46 skipping to change at page 10, line 4
This is an opaque integer assigned by the sender to identify each This is an opaque integer assigned by the sender to identify each
request parameter. It is in host byte order and is only meaningful request parameter. It is in host byte order and is only meaningful
to the sender. The receiver of the ASCONF Chunk will copy this 32 to the sender. The receiver of the ASCONF Chunk will copy this 32
bit value into the ASCONF Response Correlation ID field of the bit value into the ASCONF Response Correlation ID field of the
ASCONF-ACK response parameter. The sender of the ASCONF can use this ASCONF-ACK response parameter. The sender of the ASCONF can use this
same value in the ASCONF-ACK to find which request the response is same value in the ASCONF-ACK to find which request the response is
for. for.
Address Parameter: TLV Address Parameter: TLV
This field contains an IPv4 or IPv6 address parameter as described in This field contains an IPv4 or IPv6 address parameter as described in
3.3.2.1 of RFC2960 [6]. The complete TLV is wrapped within this 3.3.2.1 of RFC2960 [6]. The complete TLV is wrapped within this
parameter. It informs the receiver that the address specified is to parameter. It informs the receiver that the address specified is to
be added to the existing association. be added to the existing association. This parameter MUST NOT
contain a broadcast or multicast address. If the address 0.0.0.0 or
::0 is provided, the source address of the packet MUST be added.
An example TLV requesting that the IPv4 address 10.1.1.1 be added to An example TLV requesting that the IPv4 address 10.1.1.1 be added to
the association would look as follows: the association would look as follows:
+--------------------------------+ +--------------------------------+
| Type=0xC001 | Length = 16 | | Type=0xC001 | Length = 16 |
+--------------------------------+ +--------------------------------+
| C-ID = 0x01023474 | | C-ID = 0x01023474 |
+--------------------------------+ +--------------------------------+
| Type=5 | Length = 8 | | Type=5 | Length = 8 |
+----------------+---------------+ +----------------+---------------+
| Value=0x0a010101 | | Value=0x0a010101 |
+----------------+---------------+ +----------------+---------------+
Valid Chunk Appearance Valid Chunk Appearance
The Add IP Address parameter may only appear in the ASCONF Chunk The Add IP Address parameter may only appear in the ASCONF Chunk
type. type.
3.2.2 Delete IP Address 3.2.2. Delete IP Address
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type =0xC002 | Length = Variable | | Type =0xC002 | Length = Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASCONF-Request Correlation ID | | ASCONF-Request Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Parameter | | Address Parameter |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 47 skipping to change at page 11, line 4
This is an opaque integer assigned by the sender to identify each This is an opaque integer assigned by the sender to identify each
request parameter. It is in host byte order and is only meaningful request parameter. It is in host byte order and is only meaningful
to the sender. The receiver of the ASCONF Chunk will copy this 32 to the sender. The receiver of the ASCONF Chunk will copy this 32
bit value into the ASCONF Response Correlation ID field of the bit value into the ASCONF Response Correlation ID field of the
ASCONF-ACK response parameter. The sender of the ASCONF can use this ASCONF-ACK response parameter. The sender of the ASCONF can use this
same value in the ASCONF-ACK to find which request the response is same value in the ASCONF-ACK to find which request the response is
for. for.
Address Parameter: TLV Address Parameter: TLV
This field contains an IPv4 or IPv6 address parameter as described in This field contains an IPv4 or IPv6 address parameter as described in
3.3.2.1 of RFC2960 [6]. The complete TLV is wrapped within this 3.3.2.1 of RFC2960 [6]. The complete TLV is wrapped within this
parameter. It informs the receiver that the address specified is to parameter. It informs the receiver that the address specified is to
be removed from the existing association. be removed from the existing association. This parameter MUST NOT
contain a broadcast or multicast address. If the address 0.0.0.0 or
::0 is provided, the source address of the packet MUST be deleted.
An example TLV deleting the IPv4 address 10.1.1.1 from an existing An example TLV deleting the IPv4 address 10.1.1.1 from an existing
association would look as follows: association would look as follows:
+--------------------------------+ +--------------------------------+
| Type=0xC002 | Length = 16 | | Type=0xC002 | Length = 16 |
+--------------------------------+ +--------------------------------+
| C-ID = 0x01023476 | | C-ID = 0x01023476 |
+--------------------------------+ +--------------------------------+
| Type=5 | Length = 8 | | Type=5 | Length = 8 |
+----------------+---------------+ +----------------+---------------+
| Value=0x0a010101 | | Value=0x0a010101 |
+----------------+---------------+ +----------------+---------------+
Valid Chunk Appearance Valid Chunk Appearance
The Delete IP Address parameter may only appear in the ASCONF Chunk The Delete IP Address parameter may only appear in the ASCONF Chunk
type. type.
3.2.3 Error Cause Indication 3.2.3. Error Cause Indication
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0xC003 | Length = Variable | | Type = 0xC003 | Length = Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASCONF-Response Correlation ID | | ASCONF-Response Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Cause(s) or Return Info on Success | | Error Cause(s) or Return Info on Success |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 4 skipping to change at page 12, line 10
Error Cause(s): TLV(s) Error Cause(s): TLV(s)
When reporting an error this response parameter is used to wrap one When reporting an error this response parameter is used to wrap one
or more standard error causes normally found within an SCTP or more standard error causes normally found within an SCTP
Operational Error or SCTP Abort (as defined in RFC2960 [6]). The Operational Error or SCTP Abort (as defined in RFC2960 [6]). The
Error Cause(s) follow the format defined in section 3.3.10 of RFC2960 Error Cause(s) follow the format defined in section 3.3.10 of RFC2960
[6]. [6].
Valid Chunk Appearance Valid Chunk Appearance
The Error Cause Indication parameter may only appear in the ASCONF- The Error Cause Indication parameter may only appear in the ASCONF-
ACK chunk type. ACK chunk type.
3.2.4 Set Primary IP Address 3.2.4. Set Primary IP Address
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type =0xC004 | Length = Variable | | Type =0xC004 | Length = Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASCONF-Request Correlation ID | | ASCONF-Request Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Parameter | | Address Parameter |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 36 skipping to change at page 12, line 43
same value in the ASCONF-ACK to find which request the response is same value in the ASCONF-ACK to find which request the response is
for. for.
Address Parameter: TLV Address Parameter: TLV
This field contains an IPv4 or IPv6 address parameter as described in This field contains an IPv4 or IPv6 address parameter as described in
3.3.2.1 of RFC2960 [6]. The complete TLV is wrapped within this 3.3.2.1 of RFC2960 [6]. The complete TLV is wrapped within this
parameter. It requests the receiver to mark the specified address as parameter. It requests the receiver to mark the specified address as
the primary address to send data to (see section 5.1.2 of RFC2960 the primary address to send data to (see section 5.1.2 of RFC2960
[6]). The receiver MAY mark this as its primary upon receiving this [6]). The receiver MAY mark this as its primary upon receiving this
request. request. If the address 0.0.0.0 or ::0 is provided, the receiver MAY
mark the source address of the packet as its primary.
An example TLV requesting that the IPv4 address 10.1.1.1 be made the An example TLV requesting that the IPv4 address 10.1.1.1 be made the
primary destination address would look as follows: primary destination address would look as follows:
+--------------------------------+ +--------------------------------+
| Type=0xC004 | Length = 16 | | Type=0xC004 | Length = 16 |
+--------------------------------+ +--------------------------------+
| C-ID = 0x01023479 | | C-ID = 0x01023479 |
+--------------------------------+ +--------------------------------+
| Type=5 | Length = 8 | | Type=5 | Length = 8 |
skipping to change at page 13, line 4 skipping to change at page 13, line 16
| Type=0xC004 | Length = 16 | | Type=0xC004 | Length = 16 |
+--------------------------------+ +--------------------------------+
| C-ID = 0x01023479 | | C-ID = 0x01023479 |
+--------------------------------+ +--------------------------------+
| Type=5 | Length = 8 | | Type=5 | Length = 8 |
+----------------+---------------+ +----------------+---------------+
| Value=0x0a010101 | | Value=0x0a010101 |
+----------------+---------------+ +----------------+---------------+
Valid Chunk Appearance Valid Chunk Appearance
The Set Primary IP Address parameter may appear in the ASCONF Chunk, The Set Primary IP Address parameter may appear in the ASCONF Chunk,
the INIT, or the INIT-ACK chunk type. The inclusion of this the INIT, or the INIT-ACK chunk type. The inclusion of this
parameter in the INIT or INIT-ACK can be used to indicate an initial parameter in the INIT or INIT-ACK can be used to indicate an initial
preference of primary address. preference of primary address.
3.2.5 Success Indication 3.2.5. Success Indication
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0xC005 | Length = 8 | | Type = 0xC005 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASCONF-Response Correlation ID | | ASCONF-Response Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
By default if a responding endpoint does not report an error for any By default if a responding endpoint does not report an error for any
skipping to change at page 13, line 42 skipping to change at page 14, line 6
request parameter. The receiver of the ASCONF Chunk will copy this request parameter. The receiver of the ASCONF Chunk will copy this
32 bit value from the ASCONF-Request Correlation ID into the ASCONF 32 bit value from the ASCONF-Request Correlation ID into the ASCONF
Response Correlation ID field so the peer can easily correlate the Response Correlation ID field so the peer can easily correlate the
request to this response. request to this response.
Valid Chunk Appearance Valid Chunk Appearance
The Success Indication parameter may only appear in the ASCONF-ACK The Success Indication parameter may only appear in the ASCONF-ACK
chunk type. chunk type.
3.2.6 Adaptation Layer Indication 3.2.6. Adaptation Layer Indication
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type =0xC006 | Length = 8 | | Type =0xC006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Adaption Code point | | Adaption Code point |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This parameter is specified for the communication of peer upper layer This parameter is specified for the communication of peer upper layer
protocols. It is envisioned to be used for flow control and other protocols. It is envisioned to be used for flow control and other
adaptation layers that require an indication to be carried in the adaptation layers that require an indication to be carried in the
INIT and INIT-ACK. Each adaptation layer that is defined that wishes INIT and INIT-ACK. Each adaptation layer that is defined that wishes
to use this parameter MUST specify a an adaption code point in an to use this parameter MUST specify a an adaption code point in an
appropriate RFC defining its use and meaning. This parameter SHOULD appropriate RFC defining its use and meaning. This parameter SHOULD
NOT be examined by the receiving SCTP implementation and should be NOT be examined by the receiving SCTP implementation and should be
passed opaquely to the upper layer protocol. passed opaquely to the upper layer protocol.
Valid Chunk Appearance Valid Chunk Appearance
skipping to change at page 14, line 19 skipping to change at page 14, line 31
appropriate RFC defining its use and meaning. This parameter SHOULD appropriate RFC defining its use and meaning. This parameter SHOULD
NOT be examined by the receiving SCTP implementation and should be NOT be examined by the receiving SCTP implementation and should be
passed opaquely to the upper layer protocol. passed opaquely to the upper layer protocol.
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.
This parameter MUST NOT appear in a ASCONF chunk. This parameter MUST NOT appear in a ASCONF chunk.
3.3 New Error Causes 3.2.7. Supported Extensions Parameter
This parameter is used at startup to identify any additional
extensions that the sender supports.
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 Appearence This parameter may appear in the INIT or INIT-
ACK chunk. This parameter MUST NOT appear in any other chunk.
3.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.
0x0102 Request to Delete Source IP Address. 0x0102 Request to Delete Source IP Address.
0x0103 Association Aborted due to illegal ASCONF-ACK 0x0103 Association Aborted due to illegal ASCONF-ACK
0x0104 Request refused - no authorization. 0x0104 Request refused - no authorization.
Table 4: New Error Causes Table 4: New Error Causes
3.3.1 Error Cause: Request to Delete Last Remaining IP Address 3.3.1. Error Cause: Request to Delete Last Remaining IP Address
Cause of error Cause of error
Request to Delete Last Remaining IP address: The receiver of this Request to Delete Last Remaining IP address: The receiver of this
error sent a request to delete the last IP address from its error sent a request to delete the last IP address from its
association with its peer. This error indicates that the request is association with its peer. This error indicates that the request is
rejected. rejected.
0 1 2 3 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 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
skipping to change at page 15, line 25 skipping to change at page 16, line 33
+----------------+---------------+ +----------------+---------------+
| Type= 0xC002 | Length = 16 | | Type= 0xC002 | Length = 16 |
+----------------+---------------+ +----------------+---------------+
| C-ID = 0x01023476 | | C-ID = 0x01023476 |
+--------------------------------+ +--------------------------------+
| Type=0x0005 | Length = 8 | | Type=0x0005 | Length = 8 |
+----------------+---------------+ +----------------+---------------+
| Value=0x0A010101 | | Value=0x0A010101 |
+----------------+---------------+ +----------------+---------------+
3.3.2 Error Cause: Operation Refused Due to Resource Shortage 3.3.2. Error Cause: Operation Refused Due to Resource Shortage
Cause of error Cause of error
This error cause is used to report a failure by the receiver to This error cause is used to report a failure by the receiver to
perform the requested operation due to a lack of resources. The perform the requested operation due to a lack of resources. The
entire TLV that is refused is copied from the ASCONF into the error entire TLV that is refused is copied from the ASCONF into the error
cause. cause.
0 1 2 3 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 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
skipping to change at page 16, line 21 skipping to change at page 17, line 21
+----------------+---------------+ +----------------+---------------+
| Type=0xC001 | Length = 16 | | Type=0xC001 | Length = 16 |
+--------------------------------+ +--------------------------------+
| C-ID = 0x01023474 | | C-ID = 0x01023474 |
+--------------------------------+ +--------------------------------+
| Type=0x0005 | Length = 8 | | Type=0x0005 | Length = 8 |
+----------------+---------------+ +----------------+---------------+
| Value=0x0A010101 | | Value=0x0A010101 |
+----------------+---------------+ +----------------+---------------+
3.3.3 Error Cause: Request to Delete Source IP Address 3.3.3. Error Cause: Request to Delete Source IP Address
Cause of error Cause of error
Request to Delete Source IP Address: The receiver of this error sent Request to Delete Source IP Address: The receiver of this error sent
a request to delete the source IP address of the ASCONF message. a request to delete the source IP address of the ASCONF message.
This error indicates that the request is rejected. This error indicates that the request is rejected.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 17, line 25 skipping to change at page 18, line 25
+--------------------------------+ +--------------------------------+
| Type=0x0005 | Length = 8 | | Type=0x0005 | Length = 8 |
+----------------+---------------+ +----------------+---------------+
| Value=0x0A010101 | | Value=0x0A010101 |
+----------------+---------------+ +----------------+---------------+
IMPLEMENTATION NOTE: It is unlikely that an endpoint would source a IMPLEMENTATION NOTE: It is unlikely that an endpoint would source a
packet from the address being deleted, unless the endpoint does not packet from the address being deleted, unless the endpoint does not
do proper source address selection. do proper source address selection.
3.3.4 Error Cause: Association Aborted due to illegal ASCONF-ACK 3.3.4. Error Cause: Association Aborted due to illegal ASCONF-ACK
This error is to be included in an ABORT that is generated due to the This error is to be included in an ABORT that is generated due to the
reception of an ASCONF-ACK that was not expected but is larger than reception of an ASCONF-ACK that was not expected but is larger than
the current sequence number (see Section 4.3 Rule D0 ). Note that a the current sequence number (see Section 4.3 Rule D0 ). Note that a
sequence number is larger than the last acked sequence number if it sequence number is larger than the last acked sequence number if it
is either the next sequence or no more than 2^^31-1 greater than the is either the next sequence or no more than 2^^31-1 greater than the
current sequence number. current sequence number.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code=0x0103 | Cause Length=4 | | Cause Code=0x0103 | Cause Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.3.5 Error Cause: Request refused - no authorization. 3.3.5. Error Cause: Request refused - no authorization.
Cause of error Cause of error
This error cause may be included to reject a request based on local This error cause may be included to reject a request based on local
security policies. security policies.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code=0x0104 | Cause Length=Variable | | Cause Code=0x0104 | Cause Length=Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ TLV-Copied-From-ASCONF / \ TLV-Copied-From-ASCONF /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4. Procedures 4. Procedures
This section will lay out the specific procedures for address This section will lay out the specific procedures for address
configuration change chunk type and its processing. configuration change chunk type and its processing.
4.1 ASCONF Chunk Procedures 4.1. ASCONF Chunk Procedures
When an endpoint has an ASCONF signaled change to be sent to the When an endpoint has an ASCONF signaled change to be sent to the
remote endpoint it should do the following: remote endpoint it should do the following:
A1) Create an ASCONF Chunk as defined in Section 3.1.1. The chunk A1) Create an ASCONF Chunk as defined in Section 3.1.1. The chunk
should contain all of the TLV(s) of information necessary to be should contain all of the TLV(s) of information necessary to be
sent to the remote endpoint, and unique correlation identities for sent to the remote endpoint, and unique correlation identities for
each request. each request.
A2) A serial number should be assigned to the Chunk. The serial A2) A serial number should be assigned to the Chunk. The serial
skipping to change at page 20, line 44 skipping to change at page 21, line 44
sent. sent.
B5) Restart the T-4 RTO timer. Note that if a different destination B5) Restart the T-4 RTO timer. Note that if a different destination
is selected, then the RTO used will be that of the new destination is selected, then the RTO used will be that of the new destination
address. address.
Note: the total number of re-transmissions is limited by B2 above. Note: the total number of re-transmissions is limited by B2 above.
If the maximum is reached, the association will fail and enter into If the maximum is reached, the association will fail and enter into
the CLOSED state (see RFC2960 [6] section 6.4.1 for details). the CLOSED state (see RFC2960 [6] section 6.4.1 for details).
4.1.1 Congestion Control of ASCONF Chunks 4.1.1. Congestion Control of ASCONF Chunks
In defining the ASCONF Chunk transfer procedures, it is essential In defining the ASCONF Chunk transfer procedures, it is essential
that these transfers MUST NOT cause congestion within the network. that these transfers MUST NOT cause congestion within the network.
To achieve this, we place these restrictions on the transfer of To achieve this, we place these restrictions on the transfer of
ASCONF Chunks: ASCONF Chunks:
R1) One and only one ASCONF Chunk MAY be in transit and R1) One and only one ASCONF Chunk MAY be in transit and
unacknowledged at any one time. If a sender, after sending an unacknowledged at any one time. If a sender, after sending an
ASCONF chunk, decides it needs to transfer another ASCONF Chunk, ASCONF chunk, decides it needs to transfer another ASCONF Chunk,
it MUST wait until the ASCONF-ACK Chunk returns from the previous it MUST wait until the ASCONF-ACK Chunk returns from the previous
skipping to change at page 21, line 37 skipping to change at page 22, line 37
circumstances an ASCONF-ACK may exceed the path MTU and in such a circumstances an ASCONF-ACK may exceed the path MTU and in such a
case IP fragmentation should be used to transmit the chunk. case IP fragmentation should be used to transmit the chunk.
If the sender of an ASCONF Chunk receives an Operational Error If the sender of an ASCONF Chunk receives an Operational Error
indicating that the ASCONF chunk type is not understood, then the indicating that the ASCONF chunk type is not understood, then the
sender MUST NOT send subsequent ASCONF Chunks to the peer. The sender MUST NOT send subsequent ASCONF Chunks to the peer. The
endpoint should also inform the upper layer application that the peer endpoint should also inform the upper layer application that the peer
endpoint does not support any of the extensions detailed in this endpoint does not support any of the extensions detailed in this
document. document.
4.2 Upon reception of an ASCONF Chunk. 4.2. Upon reception of an ASCONF Chunk.
When an endpoint receives an ASCONF Chunk from the remote peer When an endpoint receives an ASCONF Chunk from the remote peer
special procedures MAY be needed to identify the association the special procedures MAY be needed to identify the association the
ASCONF Chunk is associated with. To properly find the association ASCONF Chunk is associated with. To properly find the association
the following procedures should be followed: the following procedures should be followed:
L1) Use the source address and port number of the sender to attempt L1) Use the source address and port number of the sender to attempt
to identify the association (i.e. use the same method defined in to identify the association (i.e. use the same method defined in
RFC2960 [6] used for all other SCTP chunks). If found proceed to RFC2960 [6] used for all other SCTP chunks). If found proceed to
rule L4. rule L4.
skipping to change at page 23, line 47 skipping to change at page 24, line 47
ASCONF-ACK. ASCONF-ACK.
C4) Otherwise, the ASCONF Chunk is discarded since it must be either C4) Otherwise, the ASCONF Chunk is discarded since it must be either
a stale packet or from an attacker. A receiver of such a packet a stale packet or from an attacker. A receiver of such a packet
MAY log the event for security purposes. MAY log the event for security purposes.
C5) In both cases C2 and C3 the ASCONF-ACK MUST be sent back to the C5) In both cases C2 and C3 the ASCONF-ACK MUST be sent back to the
source address contained in the IP header of the ASCONF being source address contained in the IP header of the ASCONF being
responded to. responded to.
4.3 General rules for address manipulation 4.3. General rules for address manipulation
When building TLV parameters for the ASCONF Chunk that will add or When building TLV parameters for the ASCONF Chunk that will add or
delete IP addresses the following rules should be applied: delete IP addresses the following rules should be applied:
D0) If an endpoint receives an ASCONF-ACK that is greater than or D0) If an endpoint receives an ASCONF-ACK that is greater than or
equal to the next serial number to be used but no ASCONF chunk is equal to the next serial number to be used but no ASCONF chunk is
outstanding the endpoint MUST ABORT the association. Note that a outstanding the endpoint MUST ABORT the association. Note that a
sequence number is greater than if it is no more than 2^^31-1 sequence number is greater than if it is no more than 2^^31-1
larger than the current sequence number (using serial arithmetic). larger than the current sequence number (using serial arithmetic).
skipping to change at page 27, line 20 skipping to change at page 28, line 16
For the DELETE case, an endpoint MAY respond to the late arriving For the DELETE case, an endpoint MAY respond to the late arriving
DATA packet as an OOTB datagram or it MAY hold the deleting IP DATA packet as an OOTB datagram or it MAY hold the deleting IP
address for a small period of time as still valid. If it treats the address for a small period of time as still valid. If it treats the
DATA packet as an OOTB the peer will silently discard the ABORT DATA packet as an OOTB the peer will silently discard the ABORT
(since by the time the ABORT is sent the peer will have removed the (since by the time the ABORT is sent the peer will have removed the
IP address from this association). If the endpoint elects to hold IP address from this association). If the endpoint elects to hold
the IP address valid for a period of time, it MUST NOT hold it valid the IP address valid for a period of time, it MUST NOT hold it valid
longer than 2 RTO intervals for the destination being removed. longer than 2 RTO intervals for the destination being removed.
4.3.1 A special case for OOTB ABORT chunks 4.3.1. A special case for OOTB ABORT chunks
Another case worth mentioning is illustrated below: Another case worth mentioning is illustrated below:
Endpoint-A Endpoint-Z Endpoint-A Endpoint-Z
---------- ---------- ---------- ----------
New DATA:------------\ New DATA:------------\
Source IP:X \ Source IP:X \
\ \
ASCONF-REQ[DEL-IP:X]----\------------------> ASCONF-REQ[DEL-IP:X]----\------------------>
skipping to change at page 27, line 42 skipping to change at page 28, line 38
\ / \ /
\----/-----------> OOTB \----/-----------> OOTB
(Ignored <---------------------/-------------ABORT (Ignored <---------------------/-------------ABORT
by rule D4) / by rule D4) /
<---------------------/ <---------------------/
For this case, during the deletion of an IP address, an Abort MUST be For this case, during the deletion of an IP address, an Abort MUST be
ignored if the destination address of the Abort message is that of a ignored if the destination address of the Abort message is that of a
destination being deleted. destination being deleted.
4.3.2 A special case for changing an address. 4.3.2. A special case for changing an address.
In some instances the sender may only have one IP address in an In some instances the sender may only have one IP address in an
association that is being renumbered. When this occurs, the sender association that is being renumbered. When this occurs, the sender
may not be able to send to the peer the appropriate ADD/DELETE pair may not be able to send to the peer the appropriate ADD/DELETE pair
and use the old address as a source in the IP header. For this and use the old address as a source in the IP header. For this
reason the sender MUST fill in the Address Parameter field with an reason the sender MUST fill in the Address Parameter field with an
address that is part of the association (in this case the one being address that is part of the association (in this case the one being
deleted). This will allow the receiver to locate the association deleted). This will allow the receiver to locate the association
without using the source address found in the IP header. without using the source address found in the IP header.
The receiver of such a chunk MUST always first use the source address The receiver of such a chunk MUST always first use the source address
found in the IP header in looking up the association. The receiver found in the IP header in looking up the association. The receiver
should attempt to use the address found in the Address Bytes field should attempt to use the address found in the Address Bytes field
only if the lookup fails using the source address from the IP header. only if the lookup fails using the source address from the IP header.
The receiver MUST reply to the source address of the packet in this The receiver MUST reply to the source address of the packet in this
case which is the new address that was added by the ASCONF (since the case which is the new address that was added by the ASCONF (since the
old address is no longer a part of the association after processing). old address is no longer a part of the association after processing).
4.4 Setting of the primary address 4.4. Setting of the primary address
A sender of this option may elect to send this combined with a A sender of this option may elect to send this combined with a
deletion or addition of an address. A sender SHOULD only send a set deletion or addition of an address. A sender SHOULD only send a set
primary request to an address that is already considered part of the primary request to an address that is already considered part of the
association. In other words if a sender combines a set primary with association. In other words if a sender combines a set primary with
an add of a new IP address the set primary will be discarded unless an add of a new IP address the set primary will be discarded unless
the add request is to be processed BEFORE the set primary (i.e. it the add request is to be processed BEFORE the set primary (i.e. it
precedes the set primary). precedes the set primary).
A request to set primary MAY also appear in an INIT or INIT-ACK A request to set primary MAY also appear in an INIT or INIT-ACK
skipping to change at page 30, line 12 skipping to change at page 31, line 12
end-point pair key is used this is not possible. For a more detailed end-point pair key is used this is not possible. For a more detailed
analysis see SCTP-AUTH [7]. analysis see SCTP-AUTH [7].
6. IANA considerations 6. IANA considerations
This document defines the following new SCTP parameters, chunks and This document defines the following new SCTP parameters, chunks and
errors: errors:
o Two new chunk types, o Two new chunk types,
o Six parameter types, and o Seven parameter types, and
o Five new SCTP error causes. o Five new SCTP error causes.
One of the two new chunk types must come from the range of chunk One of the two new chunk types must come from the range of chunk
types where the upper two bits are one, we recommend 0xC1 but any types where the upper two bits are one, we recommend 0xC1 but any
other available code point with the upper bits set is also other available code point with the upper bits set is also
acceptable. acceptable.
The second chunk type must come from the range where only the upper The second chunk type must come from the range where only the upper
bit is set to one. We recommend 0x80 but any other available code bit is set to one. We recommend 0x80 but any other available code
point with the upper bit set is also acceptable. point with the upper bit set is also acceptable.
All of the parameter types must come from the range of types where All but one of the parameter types must come from the range of types
the upper two bits are set, we recommend 0xC001 - 0xC006, as where the upper two bits are set, we recommend 0xC001 - 0xC006, as
specified in this document, but other parameter types can be used as specified in this document. The other parameter type must come from
long as the upper two bits of the type are set to one. the 0x8000 range, we recommend 0x8008. Note that for 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 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 seperate these from the common used 0x0100-0x0104 in an attempt to seperate these from the common
ranges of error codes. Any other unassigned values are also ranges of error codes. Any other unassigned values are also
acceptable. acceptable.
This document also defines a Adaption code point. The adaption code This document also defines a Adaption code point. The adaption code
point is a 32 bit integer that is assigned by IANA through an IETF point is a 32 bit integer that is assigned by IANA through an IETF
Consensus action as defined in RFC2434 [4]. Consensus action as defined in RFC2434 [4].
skipping to change at page 32, line 5 skipping to change at page 33, line 5
[6] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, [6] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer,
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Paxson, H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Paxson,
"Stream Control Transmission Protocol", RFC 2960, October 2000. "Stream Control Transmission Protocol", RFC 2960, October 2000.
[7] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, [7] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla,
"Authenticated Chunks for Stream Control Transmission Protocol "Authenticated Chunks for Stream Control Transmission Protocol
(SCTP)", draft-tuexen-sctp-auth-chunk-03 (work in progress), (SCTP)", draft-tuexen-sctp-auth-chunk-03 (work in progress),
February 2005. February 2005.
Authors' Addresses
Randall R. Stewart
Cisco Systems, Inc.
4875 Forest Drive
Suite 200
Columbia, SC 29206
USA
Phone:
Email: rrs@cisco.com
Michael A. Ramalho
Cisco Systems, Inc.
1802 Rue de la Porte
Wall Township, NJ 07719-3784
USA
Phone: +1.732.449.5762
Email: mramalho@cisco.com
Qiaobing Xie
Motorola, Inc.
1501 W. Shure Drive, #2309
Arlington Heights, IL 60004
USA
Phone: +1-847-632-3028
Email: qxie1@email.mot.com
Michael Tuexen
Univ. of Applied Sciences Muenster
Stegerwaldstr. 39
48565 Steinfurt
Germany
Email: tuexen@fh-muenster.de
Phillip T. Conrad
University of Delaware
Department of Computer and Information Sciences
Newark, DE 19716
US
Phone: +1 302 831 8622
Email: conrad@acm.org
URI: http://www.cis.udel.edu/~pconrad
Appendix A. Abstract Address Handling Appendix A. Abstract Address Handling
A.1 General remarks A.1. General remarks
The following text provides a working definition of the endpoint The following text provides a working definition of the endpoint
notion to discuss address reconfiguration. It is not intended to notion to discuss address reconfiguration. It is not intended to
restrict implementations in any way, its goal is to provide as set of restrict implementations in any way, its goal is to provide as set of
definitions only. Using these definitions should make a discussion definitions only. Using these definitions should make a discussion
about address issues easier. about address issues easier.
A.2 Generalized endpoints A.2. Generalized endpoints
A generalized endpoint is a pair of a set of IP addresses and a port A generalized endpoint is a pair of a set of IP addresses and a port
number at any given point of time. The precise definition is as number at any given point of time. The precise definition is as
follows: follows:
A generalized endpoint gE at time t is given by A generalized endpoint gE at time t is given by
gE(t) = ({IP1, ..., IPn}, Port) gE(t) = ({IP1, ..., IPn}, Port)
where {IP1, ..., IPn} is a non empty set of IP addresses. where {IP1, ..., IPn} is a non empty set of IP addresses.
skipping to change at page 35, line 5 skipping to change at page 34, line 5
if gE(t) = ({IP1, ..., IPn}, Port) holds at time t. if gE(t) = ({IP1, ..., IPn}, Port) holds at time t.
There is one fundamental rule which restricts all generalized There is one fundamental rule which restricts all generalized
endpoints: endpoints:
For two different generalized endpoints gE' and gE'' with the same For two different generalized endpoints gE' and gE'' with the same
port number Port(gE') = Port(gE'') the address sets Addr(gE')(t) and port number Port(gE') = Port(gE'') the address sets Addr(gE')(t) and
Addr(gE'')(t) must be disjoint at every point of time. Addr(gE'')(t) must be disjoint at every point of time.
A.3 Associations A.3. Associations
Associations consists of two generalized endpoints and the two Associations consists of two generalized endpoints and the two
address sets known by the peer at any time. The precise definition address sets known by the peer at any time. The precise definition
is as follows: is as follows:
An association A between to different generalized endpoints gE' and An association A between to different generalized endpoints gE' and
gE'' is given by gE'' is given by
A = (gE', S', gE'', S'') A = (gE', S', gE'', S'')
skipping to change at page 36, line 5 skipping to change at page 35, line 5
S'' from Addr(gE''). The addresses of S'' are included in the S'' from Addr(gE''). The addresses of S'' are included in the
INIT-ACK chunk. INIT-ACK chunk.
4. After the handshake the association A = (gE', S', gE'', S'') has 4. After the handshake the association A = (gE', S', gE'', S'') has
been established. been established.
5. Right after the association establishment Addr(A, gE') and 5. Right after the association establishment Addr(A, gE') and
Addr(A, gE'') are the addresses which have been seen on the wire Addr(A, gE'') are the addresses which have been seen on the wire
during the handshake. during the handshake.
A.4 Relationship with RFC 2960 A.4. Relationship with RFC 2960
RFC2960 [6] defines the notion of an endpoint. This subsection will RFC2960 [6] defines the notion of an endpoint. This subsection will
show that these endpoints are also (special) generalized endpoints. show that these endpoints are also (special) generalized endpoints.
RFC2960 [6] has no notion of address scoping or other address RFC2960 [6] has no notion of address scoping or other address
handling limitations and provides no mechanism to change the handling limitations and provides no mechanism to change the
addresses of an endpoint. addresses of an endpoint.
This means that an endpoint is simply a generalized endpoint which This means that an endpoint is simply a generalized endpoint which
does not depend on the time. Neither the Port nor the address list does not depend on the time. Neither the Port nor the address list
changes. changes.
During association setup no address scoping rules or other During association setup no address scoping rules or other
limitations will be applied. This means that for an association A limitations will be applied. This means that for an association A
between two endpoints gE' and gE'' the following is true: between two endpoints gE' and gE'' the following is true:
Addr(A, gE') = Addr(gE') and Addr(A, gE'') = Addr(gE''). Addr(A, gE') = Addr(gE') and Addr(A, gE'') = Addr(gE'').
A.5 Rules for address manipulation A.5. Rules for address manipulation
The rules for address manipulation can now be stated in a simple way: The rules for address manipulation can now be stated in a simple way:
1. An address can be added to a generalized endpoint gE only if this 1. An address can be added to a generalized endpoint gE only if this
address is not an address of a different generalized endpoint address is not an address of a different generalized endpoint
with the same port number. with the same port number.
2. An address can be added to an association A with generalized 2. An address can be added to an association A with generalized
endpoint gE if it has been added to the generalized endpoint gE endpoint gE if it has been added to the generalized endpoint gE
first. This means that the address must be an element of first. This means that the address must be an element of
skipping to change at page 37, line 5 skipping to change at page 36, line 5
3. An address can be deleted from an association A with generalized 3. An address can be deleted from an association A with generalized
endpoint gE as long as Addr(A, gE) stays non-empty. endpoint gE as long as Addr(A, gE) stays non-empty.
4. An address can be deleted from an generalized endpoint gE only if 4. An address can be deleted from an generalized endpoint gE only if
it has been removed from all associations having gE as a it has been removed from all associations having gE as a
generalized endpoint. generalized endpoint.
These rules simply make sure that the rules for the endpoints and These rules simply make sure that the rules for the endpoints and
associations given above are always fulfilled. associations given above are always fulfilled.
Authors' Addresses
Randall R. Stewart
Cisco Systems, Inc.
4875 Forest Drive
Suite 200
Columbia, SC 29206
USA
Phone:
Email: rrs@cisco.com
Michael A. Ramalho
Cisco Systems, Inc.
1802 Rue de la Porte
Wall Township, NJ 07719-3784
USA
Phone: +1.732.449.5762
Email: mramalho@cisco.com
Qiaobing Xie
Motorola, Inc.
1501 W. Shure Drive, #2309
Arlington Heights, IL 60004
USA
Phone: +1-847-632-3028
Email: qxie1@email.mot.com
Michael Tuexen
Univ. of Applied Sciences Muenster
Stegerwaldstr. 39
48565 Steinfurt
Germany
Email: tuexen@fh-muenster.de
Phillip T. Conrad
University of Delaware
Department of Computer and Information Sciences
Newark, DE 19716
US
Phone: +1 302 831 8622
Email: conrad@acm.org
URI: http://www.cis.udel.edu/~pconrad
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
 End of changes. 55 change blocks. 
142 lines changed or deleted 188 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/