1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Internet Engineering Task Force (IETF) M. Tuexen
Request for Comments: 6096 Muenster Univ. of Applied Sciences
Updates: <a href="./rfc4960">4960</a> R. Stewart
Category: Standards Track Huawei
ISSN: 2070-1721 January 2011
<span class="h1">Stream Control Transmission Protocol (SCTP) Chunk Flags Registration</span>
Abstract
This document defines the procedure for registering chunk flags with
the Internet Assigned Numbers Authority (IANA) for the Stream Control
Transmission Protocol (SCTP). It updates <a href="./rfc4960">RFC 4960</a> and also defines
the IANA registry for contents for currently defined chunk types. It
does not change SCTP in any other way.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6096">http://www.rfc-editor.org/info/rfc6096</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Tuexen & Stewart Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6096">RFC 6096</a> SCTP Chunk Flags Registration January 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Updated IETF-Defined Chunk Extension . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. New IETF Chunk Flags Registration . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.3">3.3</a>. Initial Registrations . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.3.1">3.3.1</a>. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.3.2">3.3.2</a>. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3.3">3.3.3</a>. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3.4">3.3.4</a>. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3.5">3.3.5</a>. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3.6">3.3.6</a>. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3.7">3.3.7</a>. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3.8">3.3.8</a>. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.3.9">3.3.9</a>. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3.10">3.3.10</a>. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3.11">3.3.11</a>. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3.12">3.3.12</a>. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3.13">3.3.13</a>. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3.14">3.3.14</a>. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3.15">3.3.15</a>. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3.16">3.3.16</a>. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.3.17">3.3.17</a>. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.3.18">3.3.18</a>. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.3.19">3.3.19</a>. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.3.20">3.3.20</a>. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5">5</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<span class="grey">Tuexen & Stewart Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6096">RFC 6096</a> SCTP Chunk Flags Registration January 2011</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
[<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>], which currently defines the Stream Control Transmission
Protocol (SCTP), provides a procedure to define new chunk types.
However, several protocol extensions currently being discussed need
to define new chunk flags for existing chunks.
This document updates <a href="./rfc4960">RFC 4960</a> to overcome this limitation. It
defines the procedure to register chunk flags and specifies the
registry entries for existing chunk types. The protocol is not
changed in any other way. Therefore, only <a href="./rfc4960#section-14.1">Section 14.1 of [RFC4960]</a>
is affected.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
<a href="#section-3.1">Section 3.1</a> provides the updated procedure for SCTP Chunk Type
registration; it replaces <a href="./rfc4960#section-14.1">Section 14.1 of [RFC4960]</a>.
<a href="#section-3.2">Section 3.2</a> provides a new procedure for SCTP Chunk Flag
registration. A registry entry must be created for each SCTP Chunk
Type.
<a href="#section-3.3">Section 3.3</a> provides the SCTP Chunk Flag registry values for the SCTP
Chunk Types specified in [<a href="./rfc3758" title=""Stream Control Transmission Protocol (SCTP) Partial Reliability Extension"">RFC3758</a>], [<a href="./rfc4820" title=""Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)"">RFC4820</a>], [<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>], [<a href="./rfc4895" title=""Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)"">RFC4895</a>],
and [<a href="./rfc5061" title=""Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration"">RFC5061</a>].
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Updated IETF-Defined Chunk Extension</span>
The assignment of new chunk type codes is done through an IETF Review
action, as defined in [<a href="./rfc5226" title="">RFC5226</a>]. Documentation of a new chunk MUST
contain the following information:
a) A long and short name for the new chunk type;
b) A detailed description of the structure of the chunk, which MUST
conform to the basic structure defined in <a href="./rfc4960#section-3.2">Section 3.2 of
[RFC4960]</a>;
c) A detailed definition and description of intended use of each
field within the chunk, including the chunk flags if any.
Defined chunk flags will be used as initial entries in the chunk
flags table for the new chunk type;
<span class="grey">Tuexen & Stewart Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6096">RFC 6096</a> SCTP Chunk Flags Registration January 2011</span>
d) A detailed procedural description of the use of the new chunk
type within the operation of the protocol.
The last chunk type (255) is reserved for future extension if
necessary.
For each new chunk type, IANA creates a registration table for the
chunk flags of that type. The procedure for registering particular
chunk flags is described in the following <a href="#section-3.2">Section 3.2</a>.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. New IETF Chunk Flags Registration</span>
The assignment of new chunk flags is done through an RFC required
action, as defined in [<a href="./rfc5226" title="">RFC5226</a>]. Documentation of the chunk flags
MUST contain the following information:
a) A name for the new chunk flag;
b) A detailed procedural description of the use of the new chunk
flag within the operation of the protocol. It MUST be considered
that implementations not supporting the flag will send '0' on
transmit and just ignore it on receipt.
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
the chunk flag values for the specific chunk type.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Initial Registrations</span>
This section describes the initial values of the chunk flag tables,
one table for each chunk. Most tables are currently empty. IANA
used these values to create the new registry.
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. DATA Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | E bit | [<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>] |
| 0x02 | B bit | [<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>] |
| 0x04 | U bit | [<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>] |
+------------------+-----------------+-----------+
<span class="grey">Tuexen & Stewart Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6096">RFC 6096</a> SCTP Chunk Flags Registration January 2011</span>
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. INIT Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. INIT ACK Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.4" href="#section-3.3.4">3.3.4</a>. SACK Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.5" href="#section-3.3.5">3.3.5</a>. HEARTBEAT Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.6" href="#section-3.3.6">3.3.6</a>. HEARTBEAT ACK Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.7" href="#section-3.3.7">3.3.7</a>. ABORT Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | T bit | [<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>] |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.8" href="#section-3.3.8">3.3.8</a>. SHUTDOWN Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="grey">Tuexen & Stewart Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6096">RFC 6096</a> SCTP Chunk Flags Registration January 2011</span>
<span class="h4"><a class="selflink" id="section-3.3.9" href="#section-3.3.9">3.3.9</a>. SHUTDOWN ACK Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.10" href="#section-3.3.10">3.3.10</a>. ERROR Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.11" href="#section-3.3.11">3.3.11</a>. COOKIE ECHO Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.12" href="#section-3.3.12">3.3.12</a>. COOKIE ACK Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.13" href="#section-3.3.13">3.3.13</a>. ECNE Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.14" href="#section-3.3.14">3.3.14</a>. CWR Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.15" href="#section-3.3.15">3.3.15</a>. SHUTDOWN COMPLETE Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | T bit | [<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>] |
+------------------+-----------------+-----------+
<span class="grey">Tuexen & Stewart Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6096">RFC 6096</a> SCTP Chunk Flags Registration January 2011</span>
<span class="h4"><a class="selflink" id="section-3.3.16" href="#section-3.3.16">3.3.16</a>. AUTH Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.17" href="#section-3.3.17">3.3.17</a>. ASCONF ACK Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.18" href="#section-3.3.18">3.3.18</a>. PAD Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.19" href="#section-3.3.19">3.3.19</a>. FORWARD TSN Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h4"><a class="selflink" id="section-3.3.20" href="#section-3.3.20">3.3.20</a>. ASCONF Chunk Flags</span>
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document does not add any additional security considerations in
addition to the ones given in [<a href="./rfc4960" title=""Stream Control Transmission Protocol"">RFC4960</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
The authors wish to thank Anna Brunstroem, Gorry Fairhurst, Russ
Housley, Suresh Krishnan, and Dan Romascanu for their invaluable
comments.
<span class="grey">Tuexen & Stewart Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6096">RFC 6096</a> SCTP Chunk Flags Registration January 2011</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3758">RFC3758</a>] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
Conrad, "Stream Control Transmission Protocol (SCTP)
Partial Reliability Extension", <a href="./rfc3758">RFC 3758</a>, May 2004.
[<a id="ref-RFC4820">RFC4820</a>] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and
Parameter for the Stream Control Transmission Protocol
(SCTP)", <a href="./rfc4820">RFC 4820</a>, March 2007.
[<a id="ref-RFC4895">RFC4895</a>] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla,
"Authenticated Chunks for the Stream Control Transmission
Protocol (SCTP)", <a href="./rfc4895">RFC 4895</a>, August 2007.
[<a id="ref-RFC4960">RFC4960</a>] Stewart, R., "Stream Control Transmission Protocol",
<a href="./rfc4960">RFC 4960</a>, September 2007.
[<a id="ref-RFC5061">RFC5061</a>] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
Kozuka, "Stream Control Transmission Protocol (SCTP)
Dynamic Address Reconfiguration", <a href="./rfc5061">RFC 5061</a>,
September 2007.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
Authors' Addresses
Michael Tuexen
Muenster University of Applied Sciences
Stegerwaldstr. 39
48565 Steinfurt
DE
EMail: tuexen@fh-muenster.de
Randall R. Stewart
Huawei
Chapin, SC 29036
US
EMail: randall@lakerest.net
Tuexen & Stewart Standards Track [Page 8]
</pre>
|
