draft-ietf-tsvwg-sctp-chunk-flags-02.txt   rfc6096.txt 
Network Working Group M. Tuexen Internet Engineering Task Force (IETF) M. Tuexen
Internet-Draft Muenster Univ. of Applied Sciences Request for Comments: 6096 Muenster Univ. of Applied Sciences
Updates: 4960 (if approved) R. Stewart Updates: 4960 R. Stewart
Intended status: Standards Track Huawei Category: Standards Track Huawei
Expires: April 11, 2011 October 8, 2010 ISSN: 2070-1721 January 2011
Stream Control Transmission Protocol (SCTP) Chunk Flags Registration Stream Control Transmission Protocol (SCTP) Chunk Flags Registration
draft-ietf-tsvwg-sctp-chunk-flags-02.txt
Abstract Abstract
This document defines the procedure for registering chunk flags with This document defines the procedure for registering chunk flags with
the Internet Assigned Numbers Authority (IANA) for the Stream Control the Internet Assigned Numbers Authority (IANA) for the Stream Control
Transmission Protocol (SCTP). It updates RFC 4960, and also defines Transmission Protocol (SCTP). It updates RFC 4960 and also defines
the IANA registry for contents for currently defined chunk types. It the IANA registry for contents for currently defined chunk types. It
does not change SCTP in any other way. does not change SCTP in any other way.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on April 11, 2011. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6096.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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 2, line 36 skipping to change at page 2, line 35
3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6 3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6
3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6 3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6
3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6 3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6
3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 7 3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 7
3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7 3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7
3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7 3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7
3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7 3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7
3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7 3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Normative References . . . . . . . . . . . . . . . . . . . . . 7 6. Normative References . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
[RFC4960], which currently defines the Stream Control Transmission [RFC4960], which currently defines the Stream Control Transmission
Protocol (SCTP), provides a procedure to define new chunk types. Protocol (SCTP), provides a procedure to define new chunk types.
However, several protocol extensions currently being discussed need However, several protocol extensions currently being discussed need
to define new chunk flags for existing chunks. to define new chunk flags for existing chunks.
This document updates RFC 4960 to overcome this limitation. It This document updates RFC 4960 to overcome this limitation. It
defines the procedure to register chunk flags, and specifies the defines the procedure to register chunk flags and specifies the
registry entries for existing chunk types. The protocol is not registry entries for existing chunk types. The protocol is not
changed in any other way. Therefore only Section 14.1 of [RFC4960] changed in any other way. Therefore, only Section 14.1 of [RFC4960]
is affected. is affected.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. IANA Considerations 3. IANA Considerations
skipping to change at page 3, line 39 skipping to change at page 3, line 39
Section 3.2 provides a new procedure for SCTP Chunk Flag Section 3.2 provides a new procedure for SCTP Chunk Flag
registration. A registry entry must be created for each SCTP Chunk registration. A registry entry must be created for each SCTP Chunk
Type. Type.
Section 3.3 provides the SCTP Chunk Flag registry values for the SCTP Section 3.3 provides the SCTP Chunk Flag registry values for the SCTP
Chunk Types specified in [RFC3758], [RFC4820], [RFC4960], [RFC4895], Chunk Types specified in [RFC3758], [RFC4820], [RFC4960], [RFC4895],
and [RFC5061]. and [RFC5061].
3.1. Updated IETF-Defined Chunk Extension 3.1. Updated IETF-Defined Chunk Extension
The assignment of new chunk parameter type codes is done through an The assignment of new chunk type codes is done through an IETF Review
IETF Review action, as defined in [RFC5226]. Documentation of a new action, as defined in [RFC5226]. Documentation of a new chunk MUST
chunk MUST contain the following information: contain the following information:
a) A long and short name for the new chunk type; a) A long and short name for the new chunk type;
b) A detailed description of the structure of the chunk, which MUST b) A detailed description of the structure of the chunk, which MUST
conform to the basic structure defined in section 3.2 of conform to the basic structure defined in Section 3.2 of
[RFC4960]; [RFC4960];
c) A detailed definition and description of intended use of each c) A detailed definition and description of intended use of each
field within the chunk, including the chunk flags if any. field within the chunk, including the chunk flags if any.
Defined chunk flags will be used as initial entries in the chunk Defined chunk flags will be used as initial entries in the chunk
flags table for the new chunk type; flags table for the new chunk type;
d) A detailed procedural description of the use of the new chunk d) A detailed procedural description of the use of the new chunk
type within the operation of the protocol. type within the operation of the protocol.
The last chunk type (255) is reserved for future extension if The last chunk type (255) is reserved for future extension if
necessary. necessary.
IANA creates for each new chunk type a registration table for the For each new chunk type, IANA creates a registration table for the
chunk flags for this type. The procedure for registering particular chunk flags of that type. The procedure for registering particular
chunk flags is described in the following Section 3.2. chunk flags is described in the following Section 3.2.
3.2. New IETF Chunk Flags Registration 3.2. New IETF Chunk Flags Registration
The assignment of new chunk flags is done through an RFC required The assignment of new chunk flags is done through an RFC required
action, as defined in [RFC5226]. Documentation of the chunk flags action, as defined in [RFC5226]. Documentation of the chunk flags
MUST contain the following information: MUST contain the following information:
a) A name for the new chunk flag; a) A name for the new chunk flag;
skipping to change at page 4, line 40 skipping to change at page 4, line 35
that implementations not supporting the flag will send '0' on that implementations not supporting the flag will send '0' on
transmit and just ignore it on receipt. transmit and just ignore it on receipt.
IANA selects a chunk flags value. This must be one of 0x01, 0x02, IANA selects a chunk flags value. This must be one of 0x01, 0x02,
0x04, 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within 0x04, 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within
the chunk flag values for the specific chunk type. the chunk flag values for the specific chunk type.
3.3. Initial Registrations 3.3. Initial Registrations
This section describes the initial values of the chunk flag tables, This section describes the initial values of the chunk flag tables,
one table for each chunk. Most tables are currently empty. IANA is one table for each chunk. Most tables are currently empty. IANA
to use these values to create the new registry. used these values to create the new registry.
3.3.1. DATA Chunk Flags 3.3.1. DATA Chunk Flags
+------------------+-----------------+-----------+ +------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference | | Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+ +------------------+-----------------+-----------+
| 0x01 | E bit | [RFC4960] | | 0x01 | E bit | [RFC4960] |
| 0x02 | B bit | [RFC4960] | | 0x02 | B bit | [RFC4960] |
| 0x04 | U bit | [RFC4960] | | 0x04 | U bit | [RFC4960] |
+------------------+-----------------+-----------+ +------------------+-----------------+-----------+
skipping to change at page 8, line 13 skipping to change at page 8, line 18
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
Conrad, "Stream Control Transmission Protocol (SCTP) Conrad, "Stream Control Transmission Protocol (SCTP)
Partial Reliability Extension", RFC 3758, May 2004. Partial Reliability Extension", RFC 3758, May 2004.
[RFC4820] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and [RFC4820] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and
Parameter for the Stream Control Transmission Protocol Parameter for the Stream Control Transmission Protocol
(SCTP)", RFC 4820, March 2007. (SCTP)", RFC 4820, March 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007.
[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, [RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla,
"Authenticated Chunks for the Stream Control Transmission "Authenticated Chunks for the Stream Control Transmission
Protocol (SCTP)", RFC 4895, August 2007. Protocol (SCTP)", RFC 4895, August 2007.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007.
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. [RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
Kozuka, "Stream Control Transmission Protocol (SCTP) Kozuka, "Stream Control Transmission Protocol (SCTP)
Dynamic Address Reconfiguration", RFC 5061, Dynamic Address Reconfiguration", RFC 5061,
September 2007. September 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
Authors' Addresses Authors' Addresses
Michael Tuexen Michael Tuexen
Muenster University of Applied Sciences Muenster University of Applied Sciences
Stegerwaldstr. 39 Stegerwaldstr. 39
48565 Steinfurt 48565 Steinfurt
DE DE
Email: tuexen@fh-muenster.de EMail: tuexen@fh-muenster.de
Randall R. Stewart Randall R. Stewart
Huawei Huawei
Chapin, SC 29036 Chapin, SC 29036
US US
Email: rstewart@huawei.com EMail: randall@lakerest.net
 End of changes. 19 change blocks. 
37 lines changed or deleted 32 lines changed or added

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