idnits 2.17.1 draft-ietf-tsvwg-sctp-chunk-flags-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 : ---------------------------------------------------------------------------- No issues found here. 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 (September 7, 2010) is 4952 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: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 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: March 11, 2011 September 7, 2010 8 Stream Control Transmission Protocol (SCTP) Chunk Flags Registration 9 draft-ietf-tsvwg-sctp-chunk-flags-01.txt 11 Abstract 13 This document defines the procedure for registering chunk flags with 14 the Internet Assigned Numbers Authority (IANA) for the Stream Control 15 Transmission Protocol (SCTP). It updates RFC 4960, and also defines 16 the IANA registry for contents for currently defined chunk types. It 17 does not change SCTP in any other way. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on March 11, 2011. 36 Copyright Notice 38 Copyright (c) 2010 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 56 3.1. Updated IETF-Defined Chunk Extension . . . . . . . . . . . 3 57 3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4 58 3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4 59 3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4 60 3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 5 61 3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5 62 3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5 63 3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5 64 3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5 65 3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5 66 3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5 67 3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 6 68 3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6 69 3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6 70 3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6 71 3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6 72 3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6 73 3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6 74 3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 7 75 3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7 76 3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7 77 3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7 78 3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7 79 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 80 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 81 6. Normative References . . . . . . . . . . . . . . . . . . . . . 7 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 84 1. Introduction 86 [RFC4960], which currently defines the Stream Control Transmission 87 Protocol (SCTP), provides a procedure to define new chunk types. 88 However, several protocol extensions currently being discussed need 89 to define new chunk flags for existing chunks. Without publication 90 of this document, the only way to have done this would have been to 91 obsolete [RFC4960], which is not appropriate. 93 This document updates RFC 4960 to overcome this limitation. It 94 defines the procedure to register chunk flags, and specifies the 95 registry entries for for existing chunk types. The protocol is not 96 changed in any other way. Therefore only Section 14.1 of [RFC4960] 97 is affected. 99 2. Conventions 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 103 document are to be interpreted as described in [RFC2119]. 105 3. IANA Considerations 107 Section 3.1 describes the updated procedure for chunk type 108 registration and replaces Section 14.1 of [RFC4960]. Section 3.2 109 adds a new procedure for chunk flag registration to the updated 110 section 14.1 of [RFC4960]. 112 IANA is requested to create an SCTP Chunk Flag registry. The initial 113 contents of the registry should be assigned using the values 114 specified in Section 3.3. 116 3.1. Updated IETF-Defined 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. This must be one of 0x01, 0x02, 156 0x04, 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within 157 the chunk flag values for the specific chunk type. 159 3.3. Initial Registrations 161 This section describes the initial values of the chunk flag tables, 162 one table for each chunk. Most tables are currently empty. IANA is 163 to use these value to create the new registry. 165 3.3.1. DATA Chunk Flags 167 +------------------+-----------------+-----------+ 168 | Chunk Flag Value | Chunk Flag Name | Reference | 169 +------------------+-----------------+-----------+ 170 | 0x01 | E bit | [RFC4960] | 171 | 0x02 | B bit | [RFC4960] | 172 | 0x04 | U bit | [RFC4960] | 173 +------------------+-----------------+-----------+ 175 3.3.2. INIT Chunk Flags 177 +------------------+-----------------+-----------+ 178 | Chunk Flag Value | Chunk Flag Name | Reference | 179 +------------------+-----------------+-----------+ 181 3.3.3. INIT ACK Chunk Flags 183 +------------------+-----------------+-----------+ 184 | Chunk Flag Value | Chunk Flag Name | Reference | 185 +------------------+-----------------+-----------+ 187 3.3.4. SACK Chunk Flags 189 +------------------+-----------------+-----------+ 190 | Chunk Flag Value | Chunk Flag Name | Reference | 191 +------------------+-----------------+-----------+ 193 3.3.5. HEARTBEAT Chunk Flags 195 +------------------+-----------------+-----------+ 196 | Chunk Flag Value | Chunk Flag Name | Reference | 197 +------------------+-----------------+-----------+ 199 3.3.6. HEARTBEAT ACK Chunk Flags 201 +------------------+-----------------+-----------+ 202 | Chunk Flag Value | Chunk Flag Name | Reference | 203 +------------------+-----------------+-----------+ 205 3.3.7. ABORT Chunk Flags 207 +------------------+-----------------+-----------+ 208 | Chunk Flag Value | Chunk Flag Name | Reference | 209 +------------------+-----------------+-----------+ 210 | 0x01 | T bit | [RFC4960] | 211 +------------------+-----------------+-----------+ 213 3.3.8. SHUTDOWN Chunk Flags 215 +------------------+-----------------+-----------+ 216 | Chunk Flag Value | Chunk Flag Name | Reference | 217 +------------------+-----------------+-----------+ 219 3.3.9. SHUTDOWN ACK Chunk Flags 221 +------------------+-----------------+-----------+ 222 | Chunk Flag Value | Chunk Flag Name | Reference | 223 +------------------+-----------------+-----------+ 225 3.3.10. ERROR Chunk Flags 227 +------------------+-----------------+-----------+ 228 | Chunk Flag Value | Chunk Flag Name | Reference | 229 +------------------+-----------------+-----------+ 231 3.3.11. COOKIE ECHO Chunk Flags 233 +------------------+-----------------+-----------+ 234 | Chunk Flag Value | Chunk Flag Name | Reference | 235 +------------------+-----------------+-----------+ 237 3.3.12. COOKIE ACK Chunk Flags 239 +------------------+-----------------+-----------+ 240 | Chunk Flag Value | Chunk Flag Name | Reference | 241 +------------------+-----------------+-----------+ 243 3.3.13. ECNE Chunk Flags 245 +------------------+-----------------+-----------+ 246 | Chunk Flag Value | Chunk Flag Name | Reference | 247 +------------------+-----------------+-----------+ 249 3.3.14. CWR Chunk Flags 251 +------------------+-----------------+-----------+ 252 | Chunk Flag Value | Chunk Flag Name | Reference | 253 +------------------+-----------------+-----------+ 255 3.3.15. SHUTDOWN COMPLETE Chunk Flags 257 +------------------+-----------------+-----------+ 258 | Chunk Flag Value | Chunk Flag Name | Reference | 259 +------------------+-----------------+-----------+ 260 | 0x01 | T bit | [RFC4960] | 261 +------------------+-----------------+-----------+ 263 3.3.16. AUTH Chunk Flags 265 +------------------+-----------------+-----------+ 266 | Chunk Flag Value | Chunk Flag Name | Reference | 267 +------------------+-----------------+-----------+ 269 3.3.17. ASCONF ACK Chunk Flags 271 +------------------+-----------------+-----------+ 272 | Chunk Flag Value | Chunk Flag Name | Reference | 273 +------------------+-----------------+-----------+ 275 3.3.18. PAD Chunk Flags 277 +------------------+-----------------+-----------+ 278 | Chunk Flag Value | Chunk Flag Name | Reference | 279 +------------------+-----------------+-----------+ 281 3.3.19. FORWARD TSN Chunk Flags 283 +------------------+-----------------+-----------+ 284 | Chunk Flag Value | Chunk Flag Name | Reference | 285 +------------------+-----------------+-----------+ 287 3.3.20. ASCONF Chunk Flags 289 +------------------+-----------------+-----------+ 290 | Chunk Flag Value | Chunk Flag Name | Reference | 291 +------------------+-----------------+-----------+ 293 4. Security Considerations 295 This document does not add any additional security considerations in 296 addition to the ones given in [RFC4960]. 298 5. Acknowledgments 300 The authors wish to thank Gorry Fairhurst, and Anna Brunstroem for 301 their invaluable comments. 303 6. Normative References 305 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 306 Requirement Levels", BCP 14, RFC 2119, March 1997. 308 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 309 RFC 4960, September 2007. 311 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 312 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 313 May 2008. 315 Authors' Addresses 317 Michael Tuexen 318 Muenster University of Applied Sciences 319 Stegerwaldstr. 39 320 48565 Steinfurt 321 DE 323 Email: tuexen@fh-muenster.de 325 Randall R. Stewart 326 Huawei 327 Chapin, SC 29036 328 US 330 Email: rstewart@huawei.com