draft-ietf-tsvwg-sctp-strrst-02.txt   draft-ietf-tsvwg-sctp-strrst-03.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track P. Lei Intended status: Standards Track P. Lei
Expires: June 26, 2010 Cisco Systems, Inc. Expires: July 19, 2010 Cisco Systems, Inc.
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
December 23, 2009 January 15, 2010
Stream Control Transmission Protocol (SCTP) Stream Reconfiguration Stream Control Transmission Protocol (SCTP) Stream Reconfiguration
draft-ietf-tsvwg-sctp-strrst-02.txt draft-ietf-tsvwg-sctp-strrst-03.txt
Abstract Abstract
Many applications that desire to use SCTP have requested the ability Many applications that desire to use SCTP have requested the ability
to "reset" a stream. The intention of resetting a stream is to start to "reset" a stream. The intention of resetting a stream is to start
the numbering sequence of the stream back at 'zero' with a the numbering sequence of the stream back at 'zero' with a
corresponding notification to the upper layer that this act as been corresponding notification to the upper layer that this act as been
performed. The applications that have requested this feature performed. The applications that have requested this feature
normally desire it so that they can "re-use" streams for different normally desire it so that they can "re-use" streams for different
purposes but still utilize the stream sequence number for the purposes but still utilize the stream sequence number for the
skipping to change at page 2, line 5 skipping to change at page 2, line 5
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 June 26, 2010. This Internet-Draft will expire on July 19, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 43 skipping to change at page 3, line 43
Reset Request Parameter . . . . . . . . . . . . . . . 17 Reset Request Parameter . . . . . . . . . . . . . . . 17
5.2.3. Receiver Side Procedures for the Incoming SSN 5.2.3. Receiver Side Procedures for the Incoming SSN
Reset Request Parameter . . . . . . . . . . . . . . . 18 Reset Request Parameter . . . . . . . . . . . . . . . 18
5.2.4. Receiver Side Procedures for the SSN/TSN Reset 5.2.4. Receiver Side Procedures for the SSN/TSN Reset
Request Parameter . . . . . . . . . . . . . . . . . . 18 Request Parameter . . . . . . . . . . . . . . . . . . 18
5.2.5. Receiver Side Procedures for the Add Outgoing 5.2.5. Receiver Side Procedures for the Add Outgoing
Streams Request Parameter . . . . . . . . . . . . . . 19 Streams Request Parameter . . . . . . . . . . . . . . 19
5.2.6. Receiver Side Procedures for the Stream Reset 5.2.6. Receiver Side Procedures for the Stream Reset
Response Parameter . . . . . . . . . . . . . . . . . . 19 Response Parameter . . . . . . . . . . . . . . . . . . 19
5.3. Various Examples of the Stream Reset procedures . . . . . 20 5.3. Various Examples of the Stream Reset procedures . . . . . 20
6. Socket API considerations . . . . . . . . . . . . . . . . . . 20 6. Socket API considerations . . . . . . . . . . . . . . . . . . 21
6.1. Stream Reset event . . . . . . . . . . . . . . . . . . . . 20 6.1. Stream Reset event . . . . . . . . . . . . . . . . . . . . 21
6.2. Socket Options . . . . . . . . . . . . . . . . . . . . . . 22 6.2. Event Subscription . . . . . . . . . . . . . . . . . . . . 22
6.2.1. Enable/Disable Stream Reset 6.3. Socket Options . . . . . . . . . . . . . . . . . . . . . . 23
(SCTP_ENABLE_STREAM_RESET) . . . . . . . . . . . . . . 22 6.3.1. Enable/Disable Stream Reset
6.2.2. Reset Incoming and/or Outgoing Streams (SCTP_ENABLE_STREAM_RESET) . . . . . . . . . . . . . . 24
(SCTP_RESET_STREAMS) . . . . . . . . . . . . . . . . . 23 6.3.2. Reset Incoming and/or Outgoing Streams
6.2.3. Reset SSN/TSN (SCTP_RESET_SSN_TSN) . . . . . . . . . . 23 (SCTP_RESET_STREAMS) . . . . . . . . . . . . . . . . . 24
6.2.4. Add Outgoing Streams (SCTP_ADD_STREAMS) . . . . . . . 24 6.3.3. Reset SSN/TSN (SCTP_RESET_SSN_TSN) . . . . . . . . . . 25
7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 6.3.4. Add Outgoing Streams (SCTP_ADD_STREAMS) . . . . . . . 25
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
8.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 24 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26
8.2. Five New Parameter Types . . . . . . . . . . . . . . . . . 25 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 8.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 26
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8.2. Five New Parameter Types . . . . . . . . . . . . . . . . . 27
10.1. Normative References . . . . . . . . . . . . . . . . . . . 25 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27
10.2. Informative References . . . . . . . . . . . . . . . . . . 26 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 10.1. Normative References . . . . . . . . . . . . . . . . . . . 27
10.2. Informative References . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
Many applications that desire to use SCTP have requested the ability Many applications that desire to use SCTP have requested the ability
to "reset" a stream. The intention of resetting a stream is to start to "reset" a stream. The intention of resetting a stream is to start
the numbering sequence of the stream back at 'zero' with a the numbering sequence of the stream back at 'zero' with a
corresponding notification to the upper layer that this act as been corresponding notification to the upper layer that this act as been
performed. The applications that have requested this feature performed. The applications that have requested this feature
normally desire it so that they can "re-use" streams for different normally desire it so that they can "re-use" streams for different
purposes but still utilize the stream sequence number for the purposes but still utilize the stream sequence number for the
skipping to change at page 7, line 10 skipping to change at page 7, line 10
6. Stream Reset Response Parameter. 6. Stream Reset Response Parameter.
7. Stream Reset Response Parameter, Outgoing SSN Reset Request 7. Stream Reset Response Parameter, Outgoing SSN Reset Request
Parameter. Parameter.
8. Stream Reset Response Parameter, Add Outgoing Streams Request 8. Stream Reset Response Parameter, Add Outgoing Streams Request
Parameter. Parameter.
9. Stream Reset Response Parameter, Stream Reset Response Parameter. 9. Stream Reset Response Parameter, Stream Reset Response Parameter.
If a sender transmits an unsupported combination, the receiver SHOULD
send an ERROR chunk with a protocol violation cause.
4. New Parameter Types 4. New Parameter Types
This section defines the new parameter types that will be used in the This section defines the new parameter types that will be used in the
STREAM_RESET chunk. Table 2 illustrates the new parameter types. STREAM_RESET chunk. Table 2 illustrates the new parameter types.
+----------------+----------------------------------------+ +----------------+----------------------------------------+
| Parameter Type | Parameter Name | | Parameter Type | Parameter Name |
+----------------+----------------------------------------+ +----------------+----------------------------------------+
| 0x000d | Outgoing SSN Reset Request Parameter | | 0x000d | Outgoing SSN Reset Request Parameter |
| 0x000e | Incoming SSN Reset Request Parameter | | 0x000e | Incoming SSN Reset Request Parameter |
skipping to change at page 14, line 7 skipping to change at page 14, line 7
more so, a lost request might cause an out-of-sequence error in more so, a lost request might cause an out-of-sequence error in
a stream that the receiver is not yet prepared to handle. a stream that the receiver is not yet prepared to handle.
A2: The sender MUST assign the next stream reset request sequence A2: The sender MUST assign the next stream reset request sequence
number and put it into the Stream Reset Request Sequence Number number and put it into the Stream Reset Request Sequence Number
field of the Outgoing SSN Reset Request Parameter. After field of the Outgoing SSN Reset Request Parameter. After
assigning it the next stream reset request sequence number MUST assigning it the next stream reset request sequence number MUST
be incremented by '1'. be incremented by '1'.
A3: If this Outgoing SSN Reset Request Parameter is sent in response A3: If this Outgoing SSN Reset Request Parameter is sent in response
to an Incoming SSN Request Parameter the Stream Reset Request to an Incoming SSN Request Parameter, the Stream Numbers between
Sequence Number of the Incoming SSN Request Parameter is copied the Outgoing and the Incoming parameters MUST match. If the
into the Stream Reset Response Sequence Number field of the Outgoing SSN Reset Request Parameter is sent on request of the
Outgoing SSN Reset Request Parameter. If the Outgoing SSN Reset upper layer the Stream Reset Response Sequence Number is the
Request Parameter is sent on request of the upper layer the next expected Stream Reset Request Sequence Number of the peer -
Stream Reset Response Sequence Number is the next expected 3.
Stream Reset Request Sequence Number of the peer - 3.
A4: The sender fills in the TSN it has assigned last. A4: The sender fills in the TSN it has assigned last.
A5: If this Outgoing SSN Reset Request Parameter is sent in response A5: If this Outgoing SSN Reset Request Parameter is sent in response
to an Incoming SSN Request Parameter the Stream Numbers are to an Incoming SSN Request Parameter the Stream Numbers are
copied from the Incoming SSN Request Parameter to the Outgoing copied from the Incoming SSN Request Parameter to the Outgoing
SSN Reset Request Parameter. If this Outgoing SSN Reset Request SSN Reset Request Parameter. If this Outgoing SSN Reset Request
Parameter is sent on request of the upper layer and the sender Parameter is sent on request of the upper layer and the sender
wants all outgoing streams to be reset no Stream Numbers MUST be wants all outgoing streams to be reset no Stream Numbers MUST be
put into the Outgoing SSN Reset Request Parameter. If the put into the Outgoing SSN Reset Request Parameter. If the
skipping to change at page 15, line 32 skipping to change at page 15, line 32
SSN/TSN Reset Request Parameter if the Stream Reset Timer is not SSN/TSN Reset Request Parameter if the Stream Reset Timer is not
running. The following steps MUST be followed: running. The following steps MUST be followed:
C1: The sender MUST assign the next stream reset request sequence C1: The sender MUST assign the next stream reset request sequence
number and put it into the Stream Reset Request Sequence Number number and put it into the Stream Reset Request Sequence Number
field of the SSN/TSN Reset Request Parameter. After assigning field of the SSN/TSN Reset Request Parameter. After assigning
it the next stream reset request sequence number MUST be it the next stream reset request sequence number MUST be
incremented by '1'. incremented by '1'.
C2: The sender MUST queue any user data suspending any new C2: The sender MUST queue any user data suspending any new
transmissions until the reset procedure is finished by the peer transmissions and TSN assignment until the reset procedure is
either acknowledging or denying the request. finished by the peer either acknowledging or denying the
request.
C3: The SSN/TSN Reset Request Parameter is put into a STREAM RESET C3: The SSN/TSN Reset Request Parameter is put into a STREAM RESET
Chunk. There MUST NOT be any other parameter in this chunk. Chunk. There MUST NOT be any other parameter in this chunk.
C4: The STREAM RESET Chunk is sent following the rules given in C4: The STREAM RESET Chunk is sent following the rules given in
Section 5.1.1 Section 5.1.1
5.1.5. Sender Side Procedures for the Stream Reset Response Parameter 5.1.5. Sender Side Procedures for the Stream Reset Response Parameter
When an implementation receives a request parameter it MUST respond When an implementation receives a request parameter it MUST respond
skipping to change at page 16, line 41 skipping to change at page 16, line 41
Any new stream MUST number its first message to be stream sequence 0. Any new stream MUST number its first message to be stream sequence 0.
5.2. Receiver Side Procedures 5.2. Receiver Side Procedures
5.2.1. Receiver Side Procedures for the Stream Reset Chunk 5.2.1. Receiver Side Procedures for the Stream Reset Chunk
Upon reception of a Stream Reset Chunk each parameter within it Upon reception of a Stream Reset Chunk each parameter within it
should be processed. If some parameters have to be sent back, they should be processed. If some parameters have to be sent back, they
MUST all be put into one STREAM RESET chunk. If the received STREAM MUST all be put into one STREAM RESET chunk. If the received STREAM
RESET chunk contains at least one request parameter, a SACK chunk RESET chunk contains at least one request parameter, a SACK chunk
MUST be sent back and MAY be bundled with the STREAM RESET chunk. If SHOULD be sent back and MAY be bundled with the STREAM RESET chunk.
the received STREAM RESET chunk contains at least one request and If the received STREAM RESET chunk contains at least one request and
based on the analysis of the Stream Reset Request Sequence Numbers based on the analysis of the Stream Reset Request Sequence Numbers
this is the last received STREAM RESET chunk (i.e. a retransmission), this is the last received STREAM RESET chunk (i.e. a retransmission),
the same STREAM RESET chunk has to be sent back in response as the same STREAM RESET chunk has to be sent back in response as
earlier. earlier.
The decision to deny a stream reset request is an administrative The decision to deny a stream reset request is an administrative
decision and may be user configurable even after the association has decision and may be user configurable even after the association has
formed. If for whatever reason the endpoint does NOT wish to process formed. If for whatever reason the endpoint does NOT wish to process
a received request parameter it MUST send a corresponding response a received request parameter it MUST send a corresponding response
parameter as described in Section 5.1.5 with an appropriate Result parameter as described in Section 5.1.5 with an appropriate Result
field. field.
Implementation Note: A SACK is recommended to be bundled with any
stream reset response so that any retranmission processing that needs
to occur can be expidited. A SACK chunk is not required for this
feature to work, but it will in effect help minimize the delay in
completing a stream reset operation in the face of any data loss.
5.2.2. Receiver Side Procedures for the Outgoing SSN Reset Request 5.2.2. Receiver Side Procedures for the Outgoing SSN Reset Request
Parameter Parameter
In the case that the endpoint is willing to perform a stream reset In the case that the endpoint is willing to perform a stream reset
the following steps SHOULD be followed: the following steps SHOULD be followed:
E1: If the Senders Last Assigned TSN number is greater than the E1: If the Senders Last Assigned TSN number is greater than the
cumulative acknowledgment point, then the endpoint must enter cumulative acknowledgment point, then the endpoint MUST enter
"deferred reset processing". In this mode, any data arriving "deferred reset processing". In this mode, any data arriving
with a TSN number larger than the 'senders last assigned TSN' with a TSN number larger than the 'senders last assigned TSN'
for the effected stream(s) MUST be queued locally and held until for the effected stream(s) MUST be queued locally and held until
the Cumulative Acknowledgment point reaches the 'senders last the Cumulative Acknowledgment point reaches the 'senders last
assigned TSN number'. When the Cumulative Acknowledgment point assigned TSN number'. When the Cumulative Acknowledgment point
reaches the last assigned TSN number then proceed to the next reaches the last assigned TSN number then proceed to the next
step. Note that the receiver of a stream reset that causes it step. Note that the receiver of a stream reset that causes it
to entered deferred reset processing does NOT withhold the to entered deferred reset processing does NOT withhold the
stream reset acknowledgment from the peer. This also means that stream reset acknowledgment from the peer. This also means that
the receiver will need to queue up any additional stream reset the receiver will need to queue up any additional stream reset
requests received including the one that caused the receiver to requests received including the one that caused the receiver to
enter deferred reset processing. enter deferred reset processing. This is because once the
acknowledgement is recevied by the sender, the sender is free to
send a new stream reset.
E2: If the Stream Reset Timer is running for the Stream Reset E2: If the Stream Reset Timer is running for the Stream Reset
Request Sequence Number indicated in the Stream Reset Response Request Sequence Number indicated in the Stream Reset Response
Sequence Number field, mark the Stream Reset Request Sequence Sequence Number field, mark the Stream Reset Request Sequence
Number as acknowledged. If all Stream Reset Request Sequence Number as acknowledged. If all Stream Reset Request Sequence
Numbers the Stream Reset Timer is running for are acknowledged, Numbers the Stream Reset Timer is running for are acknowledged,
stop the Stream Reset Timer. stop the Stream Reset Timer.
E3: If no Stream Numbers are listed in the parameter, then all E3: If no Stream Numbers are listed in the parameter, then all
incoming streams MUST be reset to '0' as the next expected incoming streams MUST be reset to '0' as the next expected
skipping to change at page 18, line 28 skipping to change at page 18, line 34
chunk is processed completely. chunk is processed completely.
5.2.4. Receiver Side Procedures for the SSN/TSN Reset Request Parameter 5.2.4. Receiver Side Procedures for the SSN/TSN Reset Request Parameter
In the case that the endpoint is willing to perform a SSN/TSN reset In the case that the endpoint is willing to perform a SSN/TSN reset
the following steps SHOULD be followed: the following steps SHOULD be followed:
G1: Compute an appropriate value for the Receiver's next TSN, the G1: Compute an appropriate value for the Receiver's next TSN, the
TSN the peer should use to send the next DATA chunk. Note that TSN the peer should use to send the next DATA chunk. Note that
an appropriate value should be larger than the highest TSN last an appropriate value should be larger than the highest TSN last
received plus a delta of at least 500 additional TSN's. received plus a delta of at least 2^31 additional TSN's.
G2: Compute an appropriate value for the local endpoints next TSN, G2: Compute an appropriate value for the local endpoints next TSN,
i.e. the receiver of the SSN/TSN reset chunks next TSN to be i.e. the receiver of the SSN/TSN reset chunks next TSN to be
assigned. Note that an appropriate value should be larger than assigned. Note that an appropriate value should be larger than
the endpoints current next TSN to send by at least one TSN. the endpoints current next TSN to send by at least one TSN.
G3: Do the same processing as if a SACK chunk with no gap report and G3: Do the same processing as if a SACK chunk with no gap report and
a cumulative TSN ACK of Sender's next TSN - 1 was received. a cumulative TSN ACK of Sender's next TSN - 1 was received.
G4: Do the same processing as if an FWD-TSN chunk with all streams G4: Do the same processing as if an FWD-TSN chunk with all streams
skipping to change at page 22, line 14 skipping to change at page 22, line 28
strreset_length: This field is the total length of the delivered strreset_length: This field is the total length of the delivered
event, including the header. event, including the header.
strreset_assoc_id: The association id field, holds the identifier strreset_assoc_id: The association id field, holds the identifier
for the association. All notifications for a given association for the association. All notifications for a given association
have the same association identifier. For one-to-one style have the same association identifier. For one-to-one style
socket, this field is ignored. socket, this field is ignored.
strreset_stream_list: The list of stream identifiers this event strreset_stream_list: The list of stream identifiers this event
refers to. refers to. An empty list identifies ALL streams has being reset.
6.2. Socket Options 6.2. Event Subscription
There are two methods defined in the SCTP socket API to subscribe to
events. The original method defined was an events structure with the
socket option SCTP_EVENTS. Some implementations may have already
expanded their data structure for this API to include the stream
reset subscriptions. The new API is to use a setsockopt with the
SCTP_SET_EVENT socket option. This option takes a structure that
defines the association, the event type (using the same value found
in the event type field) and a on/off boolean. This newer API is the
preferred method but we define both methods for compatability.
For some implementations the structure now takes on the form:
struct sctp_event_subscribe {
uint8_t sctp_data_io_event;
uint8_t sctp_association_event;
uint8_t sctp_address_event;
uint8_t sctp_send_failure_event;
uint8_t sctp_peer_error_event;
uint8_t sctp_shutdown_event;
uint8_t sctp_partial_delivery_event;
uint8_t sctp_adaptation_layer_event;
uint8_t sctp_authentication_event;
uint8_t sctp_sender_dry_event;
uint8_t sctp_stream_reset_event;
};
For those implementations that support this method simply putting a 1
or 0 in the sctp_stream_reset_event and setting the SCTP_EVENTS
socket option will work.However not all implementations support this
method.
The prefered method is to use the SCTP_SET_EVENT socket option and
fill in the structure sctp_set_event structure.
struct sctp_set_event {
sctp_assoc_t se_assoc_id;
uint16_t se_type;
uint8_t se_on;
};
Using this method, the user fill in the se_type with the same value
found in strreset_type field i.e. SCTP_STREAM_RESET_EVENT. The user
will also fill in the se_assoc_id field with either the association
to set this event on (this field is ignored for one-to-one style
sockets) or one of the reserved contstant values defined in the
socket API document. Finally the se_on field is set with a 1 to
enable the event or a 0 to disable the event.
6.3. Socket Options
The following table describes the new socket options which make the The following table describes the new socket options which make the
SCTP stream reset features accessible to the user. They all use SCTP stream reset features accessible to the user. They all use
IPPROTO_SCTP as their level. IPPROTO_SCTP as their level.
+--------------------------+---------------------------+-----+-----+ +--------------------------+---------------------------+-----+-----+
| option name | data type | get | set | | option name | data type | get | set |
+--------------------------+---------------------------+-----+-----+ +--------------------------+---------------------------+-----+-----+
| SCTP_STREAM_RESET_EVENT | struct sctp_tlv | X | X |
| SCTP_ENABLE_STREAM_RESET | struct sctp_assoc_value | X | X | | SCTP_ENABLE_STREAM_RESET | struct sctp_assoc_value | X | X |
| SCTP_RESET_STREAMS | struct sctp_reset_streams | | X | | SCTP_RESET_STREAMS | struct sctp_reset_streams | | X |
| SCTP_RESET_SSN_TSN | sctp_assoc_t | | X | | SCTP_RESET_SSN_TSN | sctp_assoc_t | | X |
| SCTP_ADD_STREAMS | struct sctp_assoc_value | | X | | SCTP_ADD_STREAMS | struct sctp_assoc_value | | X |
+--------------------------+---------------------------+-----+-----+ +--------------------------+---------------------------+-----+-----+
Table 4 Table 4
6.2.1. Enable/Disable Stream Reset (SCTP_ENABLE_STREAM_RESET) 6.3.1. Enable/Disable Stream Reset (SCTP_ENABLE_STREAM_RESET)
This option allows a user to control whether the SCTP implementation This option allows a user to control whether the SCTP implementation
processes or denies incoming requests in STREAM_RESET chunks. processes or denies incoming requests in STREAM_RESET chunks.
The default is not to process incoming requests. The default is not to process incoming requests.
To set or get this option the user fills in the following structure: To set or get this option the user fills in the following structure:
struct sctp_assoc_value { struct sctp_assoc_value {
sctp_assoc_t assoc_id; sctp_assoc_t assoc_id;
skipping to change at page 23, line 9 skipping to change at page 24, line 39
}; };
assoc_id: This parameter is ignored for one-to-one style sockets. assoc_id: This parameter is ignored for one-to-one style sockets.
For one-to-many style sockets this parameter indicates which For one-to-many style sockets this parameter indicates which
association the user is performing an action upon. association the user is performing an action upon.
assoc_value: If this parameter is zero the processing of incoming assoc_value: If this parameter is zero the processing of incoming
requests will be denied. If it is non-zero incoming requests will requests will be denied. If it is non-zero incoming requests will
be processed. be processed.
6.2.2. Reset Incoming and/or Outgoing Streams (SCTP_RESET_STREAMS) 6.3.2. Reset Incoming and/or Outgoing Streams (SCTP_RESET_STREAMS)
This option allows the user to request the reset incoming and/or This option allows the user to request the reset incoming and/or
outgoing streams. outgoing streams.
To set or get this option the user fills in the following structure: To set or get this option the user fills in the following structure:
struct sctp_reset_streams { struct sctp_reset_streams {
sctp_assoc_t srs_assoc_id; sctp_assoc_t srs_assoc_id;
uint16_t srs_flags; uint16_t srs_flags;
uint16_t srs_number_streams; uint16_t srs_number_streams;
skipping to change at page 23, line 44 skipping to change at page 25, line 25
srs_number_streams: This parameter is the number of elements in the srs_number_streams: This parameter is the number of elements in the
srs_stream_list. If it is zero, the operation is performed on all srs_stream_list. If it is zero, the operation is performed on all
streams. streams.
srs_stream_list: This parameter contains a list of stream identifier srs_stream_list: This parameter contains a list of stream identifier
on which the operation is performed on. It contains on which the operation is performed on. It contains
srs_number_streams elements. If it is empty, the operation is srs_number_streams elements. If it is empty, the operation is
performed on all streams. performed on all streams.
6.2.3. Reset SSN/TSN (SCTP_RESET_SSN_TSN) 6.3.3. Reset SSN/TSN (SCTP_RESET_SSN_TSN)
This option allows a user to request the reset the SSN/TSN. This option allows a user to request the reset the SSN/TSN.
To set this option the user provides an option_value of type To set this option the user provides an option_value of type
sctp_assoc_t. sctp_assoc_t.
On one-to-one style sockets the option_value is ignored. For one-to- On one-to-one style sockets the option_value is ignored. For one-to-
many style sockets the option_value is the association identifier of many style sockets the option_value is the association identifier of
the association on which the action is to be performed on. the association on which the action is to be performed on.
6.2.4. Add Outgoing Streams (SCTP_ADD_STREAMS) 6.3.4. Add Outgoing Streams (SCTP_ADD_STREAMS)
This option allows a user to request the addition a number of This option allows a user to request the addition a number of
outgoing streams. outgoing streams.
To set this option the user fills in the following structure: To set this option the user fills in the following structure:
struct sctp_assoc_value { struct sctp_assoc_value {
sctp_assoc_t assoc_id; sctp_assoc_t assoc_id;
uint32_t assoc_value; uint32_t assoc_value;
}; };
 End of changes. 21 change blocks. 
43 lines changed or deleted 107 lines changed or added

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