idnits 2.17.1 draft-tuexen-tsvwg-sctp-chunk-flags-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC4960, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4960, updated by this document, for RFC5378 checks: 2006-02-17) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 1, 2010) is 5162 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4960 (Obsoleted by RFC 9260) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Tuexen 3 Internet-Draft Muenster Univ. of Applied Sciences 4 Updates: 4960 (if approved) R. Stewart 5 Intended status: Standards Track Huawei 6 Expires: September 2, 2010 March 1, 2010 8 Stream Control Transmission Protocol Chunk Flags Registration 9 draft-tuexen-tsvwg-sctp-chunk-flags-00.txt 11 Abstract 13 The current definition of the Stream Control Transmission Protocol 14 (SCTP) is missing a procedure for registering chunk flags for already 15 defined chunk types. This document defines this procedure. It does 16 not change SCTP in any other way. 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 This Internet-Draft will expire on September 2, 2010. 41 Copyright Notice 43 Copyright (c) 2010 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 61 3.1. Updated IETF Chunk Extension . . . . . . . . . . . . . . . 3 62 3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4 63 3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4 64 3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4 65 3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 4 66 3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5 67 3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5 68 3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5 69 3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5 70 3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5 71 3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5 72 3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 5 73 3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6 74 3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6 75 3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6 76 3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6 77 3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6 78 3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6 79 3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 6 80 3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7 81 3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7 82 3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7 83 3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7 84 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 85 5. Normative References . . . . . . . . . . . . . . . . . . . . . 7 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 88 1. Introduction 90 [RFC4960], which currently defines the Stream Control Transmission 91 Protocol (SCTP), provides a procedure to define new chunk types. 92 However, several protocol extensions currently being discussed need 93 to define new chunk flags for existing chunks. The only way to do 94 this is to obsolete [RFC4960], which is not appropriate. 96 This document overcomes this limitation and provides the procedure to 97 register chunk flags for existing chunk types. The protocol is not 98 changed in any other way. Therefore only Section 14.1 of [RFC4960] 99 is affected. 101 2. Conventions 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in [RFC2119]. 107 3. IANA Considerations 109 Section 3.1 describes the updated procedure for chunk type 110 registration and replaces Section 14.1 of [RFC4960]. Section 3.2 111 defines the new procedure for chunk flag registration. 113 The initial values of the tables for the chunk flags for already 114 defined chunk types is given in Section 3.3. 116 3.1. Updated IETF Chunk Extension 118 The assignment of new chunk parameter type codes is done through an 119 IETF Review action, as defined in [RFC5226]. Documentation of a new 120 chunk MUST contain the following information: 122 a) A long and short name for the new chunk type; 124 b) A detailed description of the structure of the chunk, which MUST 125 conform to the basic structure defined in section 3.2 of 126 [RFC4960]; 128 c) A detailed definition and description of intended use of each 129 field within the chunk, including the chunk flags if any. 130 Defined chunk flags will be used as initial entries in the chunk 131 flags table for the new chunk type; 133 d) A detailed procedural description of the use of the new chunk 134 type within the operation of the protocol. 136 The last chunk type (255) is reserved for future extension if 137 necessary. 139 IANA creates for each new chunk type a registration table for the 140 chunk flags for this type. The procedure for registering particular 141 chunk flags is described in the following Section 3.2. 143 3.2. New IETF Chunk Flags Registration 145 The assignment of new chunk flags is done through an RFC required 146 action, as defined in [RFC5226]. Documentation of the chunk flags 147 MUST contain the following information: 149 a) A name for the new chunk flag; 151 b) A detailed procedural description of the use of the new chunk 152 flag within the operation of the protocol. It MUST be considered 153 that implementations not supporting the flag will just ignore it. 155 IANA selects a chunk flags value, exactly one of 0x01, 0x02, 0x04, 156 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within the 157 chunk flag values for the specific chunk type. 159 3.3. Initial Registrations 161 This section describes the initially defined chunk flag tables, one 162 table per chunk. Most of the tables are currently empty. 164 3.3.1. DATA Chunk Flags 166 +------------------+-----------------+-----------+ 167 | Chunk Flag Value | Chunk Flag Name | Reference | 168 +------------------+-----------------+-----------+ 169 | 0x01 | E bit | [RFC4960] | 170 | 0x02 | B bit | [RFC4960] | 171 | 0x04 | U bit | [RFC4960] | 172 +------------------+-----------------+-----------+ 174 3.3.2. INIT Chunk Flags 176 +------------------+-----------------+-----------+ 177 | Chunk Flag Value | Chunk Flag Name | Reference | 178 +------------------+-----------------+-----------+ 180 3.3.3. INIT ACK Chunk Flags 182 +------------------+-----------------+-----------+ 183 | Chunk Flag Value | Chunk Flag Name | Reference | 184 +------------------+-----------------+-----------+ 186 3.3.4. SACK Chunk Flags 188 +------------------+-----------------+-----------+ 189 | Chunk Flag Value | Chunk Flag Name | Reference | 190 +------------------+-----------------+-----------+ 192 3.3.5. HEARTBEAT Chunk Flags 194 +------------------+-----------------+-----------+ 195 | Chunk Flag Value | Chunk Flag Name | Reference | 196 +------------------+-----------------+-----------+ 198 3.3.6. HEARTBEAT ACK Chunk Flags 200 +------------------+-----------------+-----------+ 201 | Chunk Flag Value | Chunk Flag Name | Reference | 202 +------------------+-----------------+-----------+ 204 3.3.7. ABORT Chunk Flags 206 +------------------+-----------------+-----------+ 207 | Chunk Flag Value | Chunk Flag Name | Reference | 208 +------------------+-----------------+-----------+ 209 | 0x01 | T bit | [RFC4960] | 210 +------------------+-----------------+-----------+ 212 3.3.8. SHUTDOWN Chunk Flags 214 +------------------+-----------------+-----------+ 215 | Chunk Flag Value | Chunk Flag Name | Reference | 216 +------------------+-----------------+-----------+ 218 3.3.9. SHUTDOWN ACK Chunk Flags 220 +------------------+-----------------+-----------+ 221 | Chunk Flag Value | Chunk Flag Name | Reference | 222 +------------------+-----------------+-----------+ 224 3.3.10. ERROR Chunk Flags 226 +------------------+-----------------+-----------+ 227 | Chunk Flag Value | Chunk Flag Name | Reference | 228 +------------------+-----------------+-----------+ 230 3.3.11. COOKIE ECHO Chunk Flags 232 +------------------+-----------------+-----------+ 233 | Chunk Flag Value | Chunk Flag Name | Reference | 234 +------------------+-----------------+-----------+ 236 3.3.12. COOKIE ACK Chunk Flags 238 +------------------+-----------------+-----------+ 239 | Chunk Flag Value | Chunk Flag Name | Reference | 240 +------------------+-----------------+-----------+ 242 3.3.13. ECNE Chunk Flags 244 +------------------+-----------------+-----------+ 245 | Chunk Flag Value | Chunk Flag Name | Reference | 246 +------------------+-----------------+-----------+ 248 3.3.14. CWR Chunk Flags 250 +------------------+-----------------+-----------+ 251 | Chunk Flag Value | Chunk Flag Name | Reference | 252 +------------------+-----------------+-----------+ 254 3.3.15. SHUTDOWN COMPLETE Chunk Flags 256 +------------------+-----------------+-----------+ 257 | Chunk Flag Value | Chunk Flag Name | Reference | 258 +------------------+-----------------+-----------+ 259 | 0x01 | T bit | [RFC4960] | 260 +------------------+-----------------+-----------+ 262 3.3.16. AUTH Chunk Flags 264 +------------------+-----------------+-----------+ 265 | Chunk Flag Value | Chunk Flag Name | Reference | 266 +------------------+-----------------+-----------+ 268 3.3.17. ASCONF ACK Chunk Flags 270 +------------------+-----------------+-----------+ 271 | Chunk Flag Value | Chunk Flag Name | Reference | 272 +------------------+-----------------+-----------+ 274 3.3.18. PAD Chunk Flags 276 +------------------+-----------------+-----------+ 277 | Chunk Flag Value | Chunk Flag Name | Reference | 278 +------------------+-----------------+-----------+ 280 3.3.19. FORWARD TSN Chunk Flags 282 +------------------+-----------------+-----------+ 283 | Chunk Flag Value | Chunk Flag Name | Reference | 284 +------------------+-----------------+-----------+ 286 3.3.20. ASCONF Chunk Flags 288 +------------------+-----------------+-----------+ 289 | Chunk Flag Value | Chunk Flag Name | Reference | 290 +------------------+-----------------+-----------+ 292 4. Security Considerations 294 This document does not add any additional security considerations in 295 addition to the ones given in [RFC4960]. 297 5. Normative References 299 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 300 Requirement Levels", BCP 14, RFC 2119, March 1997. 302 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 303 RFC 4960, September 2007. 305 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 306 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 307 May 2008. 309 Authors' Addresses 311 Michael Tuexen 312 Muenster Univ. of Applied Sciences 313 Stegerwaldstr. 39 314 48565 Steinfurt 315 Germany 317 Email: tuexen@fh-muenster.de 319 Randall R. Stewart 320 Huawei 321 Chapin, SC 29036 322 USA 324 Email: rstewart@huawei.com