draft-ietf-tsvwg-sctp-chunk-flags-00.txt   draft-ietf-tsvwg-sctp-chunk-flags-01.txt 
Network Working Group M. Tuexen Network Working Group M. Tuexen
Internet-Draft Muenster Univ. of Applied Sciences Internet-Draft Muenster Univ. of Applied Sciences
Updates: 4960 (if approved) R. Stewart Updates: 4960 (if approved) R. Stewart
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: December 8, 2010 June 6, 2010 Expires: March 11, 2011 September 7, 2010
Stream Control Transmission Protocol (SCTP) Chunk Flags Registration Stream Control Transmission Protocol (SCTP) Chunk Flags Registration
draft-ietf-tsvwg-sctp-chunk-flags-00.txt draft-ietf-tsvwg-sctp-chunk-flags-01.txt
Abstract Abstract
The current definition of the Stream Control Transmission Protocol This document defines the procedure for registering chunk flags with
(SCTP) is missing a procedure for registering chunk flags for already the Internet Assigned Numbers Authority (IANA) for the Stream Control
defined chunk types. This document defines this procedure. It does Transmission Protocol (SCTP). It updates RFC 4960, and also defines
not change SCTP in any other way. the IANA registry for contents for currently defined chunk types. It
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 This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on December 8, 2010. This Internet-Draft will expire on March 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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
skipping to change at page 2, line 10 skipping to change at page 2, line 11
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Updated IETF Chunk Extension . . . . . . . . . . . . . . . 3 3.1. Updated IETF-Defined Chunk Extension . . . . . . . . . . . 3
3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4 3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4
3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4 3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4
3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4 3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4
3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 4 3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5 3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5 3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5 3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5 3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5
3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5 3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5 3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 5 3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 6
3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6 3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6
3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6 3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6
3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6 3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 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. The only way to do to define new chunk flags for existing chunks. Without publication
this is to obsolete [RFC4960], which is not appropriate. of this document, the only way to have done this would have been to
obsolete [RFC4960], which is not appropriate.
This document overcomes this limitation and provides the procedure to This document updates RFC 4960 to overcome this limitation. It
register chunk flags for existing chunk types. The protocol is not defines the procedure to register chunk flags, and specifies the
registry entries for 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
Section 3.1 describes the updated procedure for chunk type Section 3.1 describes the updated procedure for chunk type
registration and replaces Section 14.1 of [RFC4960]. Section 3.2 registration and replaces Section 14.1 of [RFC4960]. Section 3.2
adds a new procedure for chunk flag registration to the updated adds a new procedure for chunk flag registration to the updated
section 14.1 of [RFC4960]. section 14.1 of [RFC4960].
The IANA is requested to create a Chunk Flag registry. The initial IANA is requested to create an SCTP Chunk Flag registry. The initial
contents of the registry should be assigned using the values contents of the registry should be assigned using the values
specified in Section 3.3. specified in Section 3.3.
3.1. Updated IETF 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 parameter type codes is done through an
IETF Review action, as defined in [RFC5226]. Documentation of a new IETF Review action, as defined in [RFC5226]. Documentation of a new
chunk MUST contain the following information: chunk MUST 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];
skipping to change at page 4, line 27 skipping to change at page 4, line 32
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;
b) A detailed procedural description of the use of the new chunk b) A detailed procedural description of the use of the new chunk
flag within the operation of the protocol. It MUST be considered flag within the operation of the protocol. It MUST be considered
that implementations not supporting the flag will just ignore it. that implementations not supporting the flag will just ignore it.
IANA selects a chunk flags value, exactly one of 0x01, 0x02, 0x04, IANA selects a chunk flags value. This must be one of 0x01, 0x02,
0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within the 0x04, 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within
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 initially defined chunk flag tables, one This section describes the initial values of the chunk flag tables,
table per chunk. Most of the tables are currently empty. one table for each chunk. Most tables are currently empty. IANA is
to use these value 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 7, line 36 skipping to change at page 7, line 42
| Chunk Flag Value | Chunk Flag Name | Reference | | Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+ +------------------+-----------------+-----------+
4. Security Considerations 4. Security Considerations
This document does not add any additional security considerations in This document does not add any additional security considerations in
addition to the ones given in [RFC4960]. addition to the ones given in [RFC4960].
5. Acknowledgments 5. Acknowledgments
The authors wish to thank Gorry Fairhurst for his invaluable The authors wish to thank Gorry Fairhurst, and Anna Brunstroem for
comments. their invaluable comments.
6. Normative References 6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007. RFC 4960, 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 Univ. of Applied Sciences Muenster University of Applied Sciences
Stegerwaldstr. 39 Stegerwaldstr. 39
48565 Steinfurt 48565 Steinfurt
Germany 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
USA US
Email: rstewart@huawei.com Email: rstewart@huawei.com
 End of changes. 18 change blocks. 
27 lines changed or deleted 31 lines changed or added

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