draft-ietf-tsvwg-addip-sctp-03.txt   draft-ietf-tsvwg-addip-sctp-04.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Cisco Systems Cisco Systems
Q. Xie Q. Xie
Motorola Motorola
M. Tuexen M. Tuexen
Siemens AG Siemens AG
I. Rytina I. Rytina
Ericsson Ericsson
P. Conrad P. Conrad
Temple University Temple University
expires in six months Novmeber 19, 2001 expires in six months January 29, 2002
SCTP Extensions for Dynamic Reconfiguration of IP Addresses SCTP Extensions for Dynamic Reconfiguration of IP Addresses
<draft-ietf-tsvwg-addip-sctp-03.txt> <draft-ietf-tsvwg-addip-sctp-04.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026 [RFC2026]. Internet-Drafts all provisions of Section 10 of RFC 2026 [RFC2026]. Internet-Drafts
are working documents of the Internet Engineering Task Force (IETF), are working documents of the Internet Engineering Task Force (IETF),
its areas, and its working groups. Note that other groups may also its areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
skipping to change at page 2, line 4 skipping to change at page 2, line 4
TABLE OF CONTENTS TABLE OF CONTENTS
1. Introduction............................................... 2 1. Introduction............................................... 2
2. Conventions................................................ 2 2. Conventions................................................ 2
3. Additional Chunks and Parameters........................... 3 3. Additional Chunks and Parameters........................... 3
3.1 New Chunk Types........................................... 3 3.1 New Chunk Types........................................... 3
3.1.1 Address/Stream Configuration Change Chunk (ASCONF)...... 3 3.1.1 Address/Stream Configuration Change Chunk (ASCONF)...... 3
3.1.2 Address/Stream Configuration Acknowledgment Chunk 3.1.2 Address/Stream Configuration Acknowledgment Chunk
(ASCONF-ACK)............................................ 5 (ASCONF-ACK)............................................ 5
3.2 New Parameter Types....................................... 6 3.2 New Parameter Types....................................... 6
3.2.1 Add IP Address.......................................... 6 3.2.1 Add IP Address.......................................... 6
3.2.2 Delete IP Address....................................... 7 3.2.2 Delete IP Address....................................... 6
3.2.3 Error Cause Indication.................................. 7 3.2.3 Error Cause Indication.................................. 7
3.2.4 Set Primary IP Address.................................. 8 3.2.4 Set Primary IP Address.................................. 8
3.2.5 Success Indication...................................... 8 3.2.5 Success Indication...................................... 8
3.2.6 Adaption Layer Indication............................... 9 3.2.6 Adaption Layer Indication............................... 9
3.3 New Error Causes.......................................... 9 3.3 New Error Causes.......................................... 9
3.3.1 Error Cause: Request to Delete Last Remaining IP Address 9 3.3.1 Error Cause: Request to Delete Last Remaining IP Address 9
3.3.2 Error Cause: Operation Refused Due to Resource Shortage.10 3.3.2 Error Cause: Operation Refused Due to Resource Shortage.10
3.3.3 Error Cause: Request to Delete Source IP Address........11 3.3.3 Error Cause: Request to Delete Source IP Address........11
4. Procedures.................................................11 4. Procedures.................................................11
4.1 ASCONF Chunk Procedures...................................11 4.1 ASCONF Chunk Procedures...................................11
4.1.1 Congestion Control of ASCONF Chunks.....................13 4.1.1 Congestion Control of ASCONF Chunks.....................13
4.2 Upon reception of an ASCONF Chunk.........................14 4.2 Upon reception of an ASCONF Chunk.........................14
4.3 General rules for address manipulation....................15 4.3 General rules for address manipulation....................15
4.3.1 A special case for OOTB ABORT chunks....................18 4.3.1 A special case for OOTB ABORT chunks....................18
4.3.2 A special case for changing an address..................19 4.3.2 A special case for changing an address..................19
4.4 Setting of the primary address............................19 4.4 Setting of the primary address............................19
5. Security Considerations....................................19 5. Security Considerations....................................20
6. IANA considerations........................................20 6. IANA considerations........................................20
7. Authors' Addresses.........................................20 7. Authors' Addresses.........................................20
8. References.................................................21 8. References.................................................21
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 reconfigure IP address information on an existing ability to reconfigure IP address information on an existing
association. association.
skipping to change at page 6, line 10 skipping to change at page 6, line 10
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 eight new parameters added follow the format defined in section The six new parameters added follow the format defined in section
3.2.1 of [RFC2960]. Table 2 describes the parameters. 3.2.1 of [RFC2960]. Table 2 describes the parameters.
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
Error Cause Indication 0xC004 Error Cause Indication 0xC003
Set Primary Address 0xC005 Set Primary Address 0xC004
Success report 0xC006 Success report 0xC005
Adaption Layer Indication 0xC006
Table 2: Address Configuration Parameters Table 2: Address Configuration Parameters
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 9, line 46 skipping to change at page 9, line 48
protocol. protocol.
3.3 New Error Causes 3.3 New Error Causes
Three new Error Causes are added to the SCTP Operational Errors, Three 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
--------- ---------------- --------- ----------------
0xC Request to Delete Last Remaining IP Address. 0xB Request to Delete Last Remaining IP Address.
0xD Operation Refused Due to Resource Shortage. 0xC Operation Refused Due to Resource Shortage.
0xE Request to Delete Source IP Address. 0xD Request to Delete Source IP Address.
Table 3: New Error Causes Table 3: 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code=0x000C | Cause Length=Variable | | Cause Code=0x000B | Cause Length=Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ TLV-Copied-From-ASCONF / \ TLV-Copied-From-ASCONF /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
An example of a failed delete in an Error Cause TLV would look as An example of a failed delete in an Error Cause TLV would look as
follows in the response ASCONF-ACK message: follows in the response ASCONF-ACK message:
+--------------------------------+ +--------------------------------+
| Type = 0xC004 | Length = 20 | | Type = 0xC003 | Length = 20 |
+--------------------------------+ +--------------------------------+
| Cause=0x000C | Length = 16 | | Cause=0x000B | Length = 16 |
+----------------+---------------+ +----------------+---------------+
| Type= 0xC002 | Length = 12 | | Type= 0xC002 | Length = 12 |
+----------------+---------------+ +----------------+---------------+
| 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-REQ into the entire TLV that is refused is copied from the ASCONF-REQ into the
error cause. error 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code=0x000D | Cause Length=Variable | | Cause Code=0x000C | Cause Length=Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ TLV-Copied-From-ASCONF / \ TLV-Copied-From-ASCONF /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
An example of a failed addition in an Error Cause TLV would look as An example of a failed addition in an Error Cause TLV would look as
follows in the response ASCONF-ACK message: follows in the response ASCONF-ACK message:
+--------------------------------+ +--------------------------------+
| Type = 0xC004 | Length = 20 | | Type = 0xC003 | Length = 20 |
+--------------------------------+ +--------------------------------+
| Cause=0x000D | Length = 16 | | Cause=0x000C | Length = 16 |
+----------------+---------------+ +----------------+---------------+
| Type=0xC001 | Length = 12 | | Type=0xC001 | Length = 12 |
+--------------------------------+ +--------------------------------+
| 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 a request to delete the source IP address of the ASCONF
message. This error indicates that the request is rejected. message. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code=0x000E | Cause Length=Variable | | Cause Code=0x000D | Cause Length=Variable |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ TLV-Copied-From-ASCONF / \ TLV-Copied-From-ASCONF /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
An example of a failed delete in an Error Cause TLV would look as An example of a failed delete in an Error Cause TLV would look as
follows in the response ASCONF-ACK message: follows in the response ASCONF-ACK message:
+--------------------------------+ +--------------------------------+
| Type = 0xC004 | Length = 20 | | Type = 0xC003 | Length = 20 |
+--------------------------------+ +--------------------------------+
| Cause=0x000E | Length = 16 | | Cause=0x000D | Length = 16 |
+----------------+---------------+ +----------------+---------------+
| Type=0xC002 | Length = 12 | | Type=0xC002 | Length = 12 |
+----------------+---------------+ +----------------+---------------+
| Type=0x0005 | Length = 8 | | Type=0x0005 | Length = 8 |
+----------------+---------------+ +----------------+---------------+
| Value=0x0A010101 | | Value=0x0A010101 |
+----------------+---------------+ +----------------+---------------+
IMPLEMENTATION NOTE: It is unlikely that an endpoint would source IMPLEMENTATION NOTE: It is unlikely that an endpoint would source
a packet from the address being deleted, unless the endpoint a packet from the address being deleted, unless the endpoint
skipping to change at page 15, line 9 skipping to change at page 15, line 11
endpoint may also use the response to carry rejections for other endpoint may also use the response to carry rejections for other
reasons such as resource shortages etc using the Error Cause TLV and reasons such as resource shortages etc using the Error Cause TLV and
an appropriate error condition. an appropriate error condition.
Note: a positive response is implied if no error is indicated by the Note: a positive response is implied if no error is indicated by the
sender. sender.
V3) All error responses MUST copy the ASCONF-Request Correlation ID V3) All error responses MUST copy the ASCONF-Request Correlation ID
field received in the ASCONF, from the TLV being responded to, into field received in the ASCONF, from the TLV being responded to, into
the ASCONF-Request Correlation ID field. The ASCONF-Request the ASCONF-Request Correlation ID field. The ASCONF-Request
Correlation ID always precedes the request TLV. Correlation ID always precedes the request TLV. Note that a
TLV sent in a ASCONF-ACK MUST be accompanied by a Correlation ID
and a Correlation ID MUST NOT be sent without a TLV i.e. the two
are atomic.
V4) After processing the entire Chunk, it MUST send all TLVs for V4) After processing the entire Chunk, it MUST send all TLVs for
both unrecognized parameters and any other status TLVs inside the both unrecognized parameters and any other status TLVs inside the
ASCONF-ACK chunk that acknowledges the arrival and processing of the ASCONF-ACK chunk that acknowledges the arrival and processing of the
ASCONF Chunk. ASCONF Chunk.
V5) Update the 'Peer-Serial-Number' to the value found in the serial V5) Update the 'Peer-Serial-Number' to the value found in the serial
number field. number field.
C3) If the value found in the serial number is equal to the value C3) If the value found in the serial number is equal to the value
 End of changes. 

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