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
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
|
<pre>Internet Engineering Task Force (IETF) C. Dearlove
Request for Comments: 7631 BAE Systems ATC
Updates: <a href="./rfc5444">5444</a> T. Clausen
Category: Standards Track LIX, Ecole Polytechnique
ISSN: 2070-1721 September 2015
<span class="h1">TLV Naming in the Mobile Ad Hoc Network (MANET)</span>
<span class="h1">Generalized Packet/Message Format</span>
Abstract
This document reorganizes the naming of already-allocated TLV (type-
length-value) types and type extensions in the "Mobile Ad hoc NETwork
(MANET) Parameters" registries defined by <a href="./rfc5444">RFC 5444</a> to use names
appropriately. It has no consequences in terms of any protocol
implementation.
This document also updates the Expert Review guidelines in <a href="./rfc5444">RFC 5444</a>,
so as to establish a policy for consistent naming of future TLV type
and type extension allocations. It makes no other changes to
<a href="./rfc5444">RFC 5444</a>.
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/rfc7631">http://www.rfc-editor.org/info/rfc7631</a>.
<span class="grey">Dearlove & Clausen Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
Copyright Notice
Copyright (c) 2015 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.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Expert Review: Evaluation Guidelines .......................<a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Updated IANA Registries ....................................<a href="#page-6">6</a>
<a href="#section-4">4</a>. Security Considerations ........................................<a href="#page-13">13</a>
<a href="#section-5">5</a>. References .....................................................<a href="#page-13">13</a>
<a href="#section-5.1">5.1</a>. Normative References ......................................<a href="#page-13">13</a>
<a href="#section-5.2">5.2</a>. Informative References ....................................<a href="#page-14">14</a>
Acknowledgments ...................................................<a href="#page-15">15</a>
Authors' Addresses ................................................<a href="#page-15">15</a>
<span class="grey">Dearlove & Clausen Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document reorganizes and rationalizes the naming of TLVs (type-
length-value structures) defined by [<a href="./rfc5444" title=""Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format"">RFC5444</a>] and recorded by IANA in
the following subregistries of the "Mobile Ad hoc NETwork (MANET)
Parameters" registry: "Packet TLV Types", "Message TLV Types", and
"Address Block TLV Types".
This document reorganizes the naming of already-allocated Packet,
Message, and Address Block TLV types, and their corresponding type
extensions. It also updates the corresponding IANA registries.
TLVs have a type (one octet) and a type extension (one octet) that
together form a full type (of two octets). A TLV may omit the type
extension when it is zero. However, that applies only to its
representation; it still has a type extension of zero. A TLV type
defines an IANA registry of type extensions for that type.
There have been two forms of TLV allocation.
The first, but less common, form of allocation has been that
allocation of the TLV type has defined (but not necessarily
allocated) all the type extensions for that TLV type. This applies,
for example, to the Address Block TLV LINK_METRIC specified in
[<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>]. The LINK_METRIC type extensions are all available for
allocation for different definitions of link metric. It is
appropriate in this case to apply the name LINK_METRIC to the type,
and also to all the full types corresponding to that type, as has
been done. Type extensions can then be individually named or can be
simply referred to by their number.
The second, more common, form of allocation has been that allocation
of the TLV type has defined only type extension 0, and possibly type
extension 1, for that TLV type. An example is the Address Block TLV
LINK_STATUS defined in [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>], where only type extension 0 is
allocated. It is not reasonable to assume that the remaining 255
type extensions will be allocated to forms of LINK_STATUS. (Other
forms of link status are already catered to by the introduction, in
[<a href="./rfc7188" title=""Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs"">RFC7188</a>], of a registry for values of the LINK_STATUS TLV.) Thus,
the name LINK_STATUS should be attached to the specific type
extension for that type, i.e., to the full type and not to the TLV
type when used with any other type extensions. This was, however,
not done as part of the initial registration of this TLV type.
Effectively, this leaves, for the LINK_STATUS TLV type, the type
extensions 1-255 either unavailable for allocation (if applying
strictly the interpretation that they must relate to a LINK_STATUS)
or counterintuitively named for their intended function.
<span class="grey">Dearlove & Clausen Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The purpose of this document is to change how names of the second
form are applied and recorded in IANA registries, and to provide
guidelines and instructions for future TLV type allocations. This is
to facilitate the addition of new TLVs using type extensions other
than 0, but without them having inappropriate names attached. So,
for example, LINK_STATUS will become the name of the full type
(composed of the TLV type 3 and the TLV type extension 0) and will
cease being the name of the TLV type 3. This leaves the question of
how to name the type. As it is not clear what other TLVs might be
defined for other type extensions of the same type, the type is
currently left unnamed and specified only by number.
This document also updates the Expert Review guidelines from
[<a href="./rfc5444" title=""Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format"">RFC5444</a>], so as to establish a policy for consistent naming of
future TLV type and type extension allocations.
For clarity, all currently allocated TLVs in [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>], [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>],
[<a href="./rfc6621" title=""Simplified Multicast Forwarding"">RFC6621</a>], [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>], and [<a href="./rfc7182" title=""Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)"">RFC7182</a>] are listed in the IANA
Considerations section of this document, each specifying the updates
or indicating no change when that is appropriate (such as the
LINK_METRIC TLV and both TLVs defined in [<a href="./rfc6621" title=""Simplified Multicast Forwarding"">RFC6621</a>]). The only
changes are of naming.
Note that nothing in this document changes the operation of any
protocol. This naming is already used, in effect, in [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>] and
[<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>], currently the main users of allocated TLVs. For example,
the former indicates that all usage of LINK_STATUS refers to that TLV
with type extension 0.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "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>].
All references to elements such as "packet", "message", and "TLV" in
this document refer to those defined in [<a href="./rfc5444" title=""Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format"">RFC5444</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
This document updates the Expert Review evaluation guidelines for
allocations in [<a href="./rfc5444" title=""Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format"">RFC5444</a>] in the "Packet TLV Types", "Message TLV
Types", and "Address Block TLV Types" registries and updates the
already-made allocations to conform with these guidelines.
<span class="grey">Dearlove & Clausen Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Expert Review: Evaluation Guidelines</span>
For registration in the "Packet TLV Types", "Message TLV Types", and
"Address Block TLV Types" registries, the following guidelines apply,
in addition to those given in <a href="./rfc5444#section-6.1">Section 6.1 in [RFC5444]</a>:
o If the requested TLV type immediately defines (but not necessarily
allocates) all the corresponding type extensions for versions of
that type, then a common name SHOULD be assigned for the TLV type.
This case is unchanged by this specification. This currently
includes TLV types named ICV, TIMESTAMP, and LINK_METRIC; it also
includes the HELLO Message-Type-specific TLVs defined in
[<a href="./rfc6621" title=""Simplified Multicast Forwarding"">RFC6621</a>].
o Otherwise, if the requested TLV type does not immediately define
all the corresponding type extensions for versions of that type,
then a common name SHOULD NOT be assigned for that TLV type.
Instead, it is RECOMMENDED that:
* The "description" for the allocated TLV type be "Defined by
Type Extension".
* For Packet TLV Types, the type extension registry, created for
the TLV type, be named "Type XX Packet TLV Type Extensions",
with XX replaced by the numerical value of the TLV type.
* For Message TLV Types, the type extension registry, created for
the TLV type, be named "Type XX Message TLV Type Extensions",
with XX replaced by the numerical value of the TLV type.
* For Address Block TLV Types, the type extension registry,
created for the TLV type, be named "Type XX Address Block TLV
Type Extensions", with XX replaced by the numerical value of
the TLV type.
* When a new type extension is required, unless there are reasons
to the contrary, the next consecutive type extension is
allocated and given a name. (Reasons to the contrary MAY
include maintaining a correspondence between corresponding
Packet, Message, and Address Block TLVs, and reserving type
extension zero if not yet allocated.)
<span class="grey">Dearlove & Clausen Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Updated IANA Registries</span>
The following changes (including correction of some existing minor
errors) apply to the IANA registry "Mobile Ad hoc NETwork (MANET)
Parameters". For clarity, registries that are unchanged, including
those that define all type extensions of a TLV type, are listed as
unchanged.
The IANA registry "Packet TLV Types" is unchanged.
The IANA registry "ICV Packet TLV Type Extensions" is unchanged.
The IANA registry "TIMESTAMP Packet TLV Type Extensions" is
unchanged.
The IANA registry "Message TLV Types" is changed to match Table 1.
+---------+-------------------------------+-----------+
| Type | Description | Reference |
+---------+-------------------------------+-----------+
| 0 | Defined by Type Extension | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| 1 | Defined by Type Extension | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| 2-4 | Unassigned | |
| 5 | ICV | [<a href="./rfc7182" title=""Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)"">RFC7182</a>] |
| 6 | TIMESTAMP | [<a href="./rfc7182" title=""Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)"">RFC7182</a>] |
| 7 | Defined by Type Extension | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| 8 | Defined by Type Extension | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| 9-223 | Unassigned | |
| 224-255 | Reserved for Experimental Use | [<a href="./rfc5444" title=""Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format"">RFC5444</a>] |
+---------+-------------------------------+-----------+
Table 1: Message TLV Types
<span class="grey">Dearlove & Clausen Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The IANA registry "INTERVAL_TIME Message Type Extensions" has been
renamed "Type 0 Message TLV Type Extensions" and changed to match
Table 2.
+-----------+---------------+---------------------------+-----------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+---------------+---------------------------+-----------+
| 0 | INTERVAL_TIME | The maximum time before | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | another message of the | |
| | | same type as this message | |
| | | from the same originator | |
| | | should be received | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for Experimental | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | Use | |
+-----------+---------------+---------------------------+-----------+
Table 2: Type 0 Message TLV Type Extensions
The IANA registry "VALIDITY_TIME Message Type Extensions" has been
renamed "Type 1 Message TLV Type Extensions" and changed to match
Table 3.
+-----------+---------------+---------------------------+-----------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+---------------+---------------------------+-----------+
| 0 | VALIDITY_TIME | The time from receipt of | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | the message during which | |
| | | the information contained | |
| | | in the message is to be | |
| | | considered valid | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for Experimental | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | Use | |
+-----------+---------------+---------------------------+-----------+
Table 3: Type 1 Message TLV Type Extensions
The IANA registry "ICV Message TLV Type Extensions" is unchanged.
The IANA registry "TIMESTAMP Message TLV Type Extensions" is
unchanged.
<span class="grey">Dearlove & Clausen Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The IANA registry "MPR_WILLING Message Type Extensions" has been
renamed "Type 7 Message TLV Type Extensions" and changed to match
Table 4.
+-----------+-------------+-----------------------------+-----------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+-------------+-----------------------------+-----------+
| 0 | MPR_WILLING | Bits 0-3 specify the | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| | | originating router's | |
| | | willingness to act as a | |
| | | flooding MPR; bits 4-7 | |
| | | specify the originating | |
| | | router's willingness to act | |
| | | as a routing MPR | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for Experimental | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| | | Use | |
+-----------+-------------+-----------------------------+-----------+
Table 4: Type 7 Message TLV Type Extensions
The IANA registry "CONT_SEQ_NUM Message Type Extensions" has been
renamed "Type 8 Message TLV Type Extensions" and changed to match
Table 5.
+-----------+--------------+----------------------------+-----------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+--------------+----------------------------+-----------+
| 0 | CONT_SEQ_NUM | Specifies a content | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| | (COMPLETE) | sequence number for this | |
| | | complete message | |
| 1 | CONT_SEQ_NUM | Specifies a content | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| | (INCOMPLETE) | sequence number for this | |
| | | incomplete message | |
| 2-223 | | Unassigned | |
| 224-255 | | Reserved for Experimental | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| | | Use | |
+-----------+--------------+----------------------------+-----------+
Table 5: Type 8 Message TLV Type Extensions
The IANA registry "HELLO Message-Type-specific Message TLV Types" is
unchanged.
The IANA registry "SMF_TYPE Message TLV Type Extensions" is
unchanged.
<span class="grey">Dearlove & Clausen Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The IANA registry "TC Message-Type-specific Message TLV Types" is
unchanged.
The IANA registry "Address Block TLV Types" has been changed to match
Table 6.
+---------+-------------------------------+-----------+
| Type | Description | Reference |
+---------+-------------------------------+-----------+
| 0 | Defined by Type Extension | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| 1 | Defined by Type Extension | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| 2 | Defined by Type Extension | [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>] |
| 3 | Defined by Type Extension | [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>] |
| 4 | Defined by Type Extension | [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>] |
| 5 | ICV | [<a href="./rfc7182" title=""Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)"">RFC7182</a>] |
| 6 | TIMESTAMP | [<a href="./rfc7182" title=""Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)"">RFC7182</a>] |
| 7 | LINK_METRIC | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| 8 | Defined by Type Extension | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| 9 | Defined by Type Extension | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| 10 | Defined by Type Extension | [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>] |
| 11-223 | Unassigned | |
| 224-255 | Reserved for Experimental Use | [<a href="./rfc5444" title=""Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format"">RFC5444</a>] |
+---------+-------------------------------+-----------+
Table 6: Address Block TLV Types
The IANA registry "INTERVAL_TIME Address Block TLV Type Extensions"
has been renamed "Type 0 Address Block TLV Type Extensions" and
changed to match Table 7.
+-----------+---------------+---------------------------+-----------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+---------------+---------------------------+-----------+
| 0 | INTERVAL_TIME | The maximum time before | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | another message of the | |
| | | same type as this message | |
| | | from the same originator | |
| | | and containing this | |
| | | address should be | |
| | | received | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for Experimental | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | Use | |
+-----------+---------------+---------------------------+-----------+
Table 7: Type 0 Address Block TLV Type Extensions
<span class="grey">Dearlove & Clausen Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The IANA registry "VALIDITY_TIME Address Block TLV Type Extensions"
has been renamed "Type 1 Address Block TLV Type Extensions" and
changed to match Table 8.
+-----------+---------------+---------------------------+-----------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+---------------+---------------------------+-----------+
| 0 | VALIDITY_TIME | The time from receipt of | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | the address during which | |
| | | the information regarding | |
| | | this address is to be | |
| | | considered valid | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for Experimental | [<a href="./rfc5497" title=""Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)"">RFC5497</a>] |
| | | Use | |
+-----------+---------------+---------------------------+-----------+
Table 8: Type 1 Address Block TLV Type Extensions
The IANA registry "LOCAL_IF Address Block TLV Type Extensions" has
been renamed "Type 2 Address Block TLV Type Extensions" and changed
to match Table 9.
+-----------+----------+-----------------------+--------------------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+----------+-----------------------+--------------------+
| 0 | LOCAL_IF | This value is to be | [<a href="./rfc7188" title=""Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs"">RFC7188</a>][RFC6130] |
| | | interpreted according | |
| | | to the registry | |
| | | "LOCAL_IF TLV Values" | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for | [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>] |
| | | Experimental Use | |
+-----------+----------+-----------------------+--------------------+
Table 9: Type 2 Address Block TLV Type Extensions
<span class="grey">Dearlove & Clausen Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The IANA registry "LINK_STATUS Address Block TLV Type Extensions" has
been renamed "Type 3 Address Block TLV Type Extensions" and changed
to match Table 10.
+-----------+-------------+--------------------+--------------------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+-------------+--------------------+--------------------+
| 0 | LINK_STATUS | This value is to | [<a href="./rfc7188" title=""Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs"">RFC7188</a>][RFC6130] |
| | | be interpreted | |
| | | according to the | |
| | | registry | |
| | | "LINK_STATUS TLV | |
| | | Values" | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for | [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>] |
| | | Experimental Use | |
+-----------+-------------+--------------------+--------------------+
Table 10: Type 3 Address Block TLV Type Extensions
The IANA registry "OTHER_NEIGHB Address Block TLV Type Extensions"
has been renamed "Type 4 Address Block TLV Type Extensions" and
changed to match Table 11.
+-----------+--------------+-------------------+--------------------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+--------------+-------------------+--------------------+
| 0 | OTHER_NEIGHB | This value is to | [<a href="./rfc7188" title=""Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs"">RFC7188</a>][RFC6130] |
| | | be interpreted | |
| | | according to the | |
| | | registry | |
| | | "OTHER_NEIGHB TLV | |
| | | Values" | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for | [<a href="./rfc6130" title=""Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)"">RFC6130</a>] |
| | | Experimental Use | |
+-----------+--------------+-------------------+--------------------+
Table 11: Type 4 Address Block TLV Type Extensions
The IANA registry "ICV Address TLV Type Extensions" has been renamed
"ICV Address Block TLV Type Extensions" but is otherwise unchanged.
The IANA registry "TIMESTAMP Address TLV Type Extensions" has been
renamed "TIMESTAMP Address Block TLV Type Extensions" but is
otherwise unchanged.
<span class="grey">Dearlove & Clausen Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The IANA registry "LINK_METRIC Address Block TLV Type Extensions" is
unchanged.
The IANA registry "MPR Address Block TLV Type Extensions" has been
renamed "Type 8 Address Block TLV Type Extensions" and changed to
match Table 12.
+-----------+------+---------------------------+--------------------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+------+---------------------------+--------------------+
| 0 | MPR | This value is to be | [<a href="./rfc7188" title=""Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs"">RFC7188</a>][RFC7181] |
| | | interpreted according to | |
| | | the registry "MPR TLV Bit | |
| | | Values" | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for Experimental | <a href="./rfc7631">RFC 7631</a> (this |
| | | Use | document) |
+-----------+------+---------------------------+--------------------+
Table 12: Type 8 Address Block TLV Type Extensions
The IANA registry "NBR_ADDR_TYPE Address Block TLV Type Extensions"
has been renamed "Type 9 Address Block TLV Type Extensions" and
changed to match Table 13.
+-----------+---------------+------------------+--------------------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+---------------+------------------+--------------------+
| 0 | NBR_ADDR_TYPE | This value is to | [<a href="./rfc7188" title=""Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs"">RFC7188</a>][RFC7181] |
| | | be interpreted | |
| | | according to the | |
| | | registry | |
| | | "NBR_ADDR_TYPE | |
| | | Address Block | |
| | | TLV Bit Values" | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for | <a href="./rfc7631">RFC 7631</a> (this |
| | | Experimental Use | document) |
+-----------+---------------+------------------+--------------------+
Table 13: Type 9 Address Block TLV Type Extensions
<span class="grey">Dearlove & Clausen Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
The IANA registry "GATEWAY Address Block TLV Type Extensions" has
been renamed "Type 10 Address Block TLV Type Extensions" and changed
to match Table 14.
+-----------+---------+------------------------+--------------------+
| Type | Name | Description | Reference |
| Extension | | | |
+-----------+---------+------------------------+--------------------+
| 0 | GATEWAY | Specifies that a given | [<a href="./rfc7188" title=""Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVs"">RFC7188</a>][RFC7181] |
| | | network address is | |
| | | reached via a gateway | |
| | | on the originating | |
| | | router, with value | |
| | | equal to the number of | |
| | | hops | |
| 1-223 | | Unassigned | |
| 224-255 | | Reserved for | <a href="./rfc7631">RFC 7631</a> (this |
| | | Experimental Use | document) |
+-----------+---------+------------------------+--------------------+
Table 14: Type 10 Address Block TLV Type Extensions
The IANA registry "HELLO Message-Type-specific Address Block TLV
Types" is unchanged.
The IANA registry "SMF_NBR_TYPE Address Block TLV Type Extensions" is
unchanged.
The IANA registry "TC Message-Type-specific Address Block TLV Types"
is unchanged.
Note: This document adds reservations for Experimental Use [<a href="./rfc5226" title="">RFC5226</a>],
omitted in [<a href="./rfc7181" title=""The Optimized Link State Routing Protocol Version 2"">RFC7181</a>], to the last three tables.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
As this document is concerned only with how entities are named, those
names being used only in documents such as this and IANA registries,
this document has no security considerations.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</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>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
<span class="grey">Dearlove & Clausen Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
[<a id="ref-RFC5444">RFC5444</a>] Clausen, T., Dearlove, C., Dean, J., and C. Adjih,
"Generalized Mobile Ad Hoc Network (MANET) Packet/Message
Format", <a href="./rfc5444">RFC 5444</a>, DOI 10.17487/RFC5444, February 2009,
<<a href="http://www.rfc-editor.org/info/rfc5444">http://www.rfc-editor.org/info/rfc5444</a>>.
[<a id="ref-RFC5497">RFC5497</a>] Clausen, T. and C. Dearlove, "Representing Multi-Value
Time in Mobile Ad Hoc Networks (MANETs)", <a href="./rfc5497">RFC 5497</a>,
DOI 10.17487/RFC5497, March 2009,
<<a href="http://www.rfc-editor.org/info/rfc5497">http://www.rfc-editor.org/info/rfc5497</a>>.
[<a id="ref-RFC6130">RFC6130</a>] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc
Network (MANET) Neighborhood Discovery Protocol (NHDP)",
<a href="./rfc6130">RFC 6130</a>, DOI 10.17487/RFC6130, April 2011,
<<a href="http://www.rfc-editor.org/info/rfc6130">http://www.rfc-editor.org/info/rfc6130</a>>.
[<a id="ref-RFC6621">RFC6621</a>] Macker, J., Ed., "Simplified Multicast Forwarding",
<a href="./rfc6621">RFC 6621</a>, DOI 10.17487/RFC6621, May 2012,
<<a href="http://www.rfc-editor.org/info/rfc6621">http://www.rfc-editor.org/info/rfc6621</a>>.
[<a id="ref-RFC7181">RFC7181</a>] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg,
"The Optimized Link State Routing Protocol Version 2",
<a href="./rfc7181">RFC 7181</a>, DOI 10.17487/RFC7181, April 2014,
<<a href="http://www.rfc-editor.org/info/rfc7181">http://www.rfc-editor.org/info/rfc7181</a>>.
[<a id="ref-RFC7182">RFC7182</a>] Herberg, U., Clausen, T., and C. Dearlove, "Integrity
Check Value and Timestamp TLV Definitions for Mobile Ad
Hoc Networks (MANETs)", <a href="./rfc7182">RFC 7182</a>, DOI 10.17487/RFC7182,
April 2014, <<a href="http://www.rfc-editor.org/info/rfc7182">http://www.rfc-editor.org/info/rfc7182</a>>.
[<a id="ref-RFC7188">RFC7188</a>] Dearlove, C. and T. Clausen, "Optimized Link State Routing
Protocol Version 2 (OLSRv2) and MANET Neighborhood
Discovery Protocol (NHDP) Extension TLVs", <a href="./rfc7188">RFC 7188</a>,
DOI 10.17487/RFC7188, April 2014,
<<a href="http://www.rfc-editor.org/info/rfc7188">http://www.rfc-editor.org/info/rfc7188</a>>.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<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>,
DOI 10.17487/RFC5226, May 2008,
<<a href="http://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>>.
<span class="grey">Dearlove & Clausen Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7631">RFC 7631</a> TLV Naming September 2015</span>
Acknowledgments
The authors would like to thank Adrian Farrel for pointing out the
need to reorganize and rationalize the naming of the TLVs defined by
[<a href="./rfc5444" title=""Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format"">RFC5444</a>] and Tom Taylor and the RFC Editor for pointing out some
omissions and errors.
Authors' Addresses
Christopher Dearlove
BAE Systems Advanced Technology Centre
West Hanningfield Road
Great Baddow, Chelmsford
United Kingdom
Phone: +44 1245 242194
Email: chris.dearlove@baesystems.com
URI: <a href="http://www.baesystems.com/">http://www.baesystems.com/</a>
Thomas Heide Clausen
LIX, Ecole Polytechnique
Phone: +33 6 6058 9349
Email: T.Clausen@computer.org
URI: <a href="http://www.ThomasClausen.org/">http://www.ThomasClausen.org/</a>
Dearlove & Clausen Standards Track [Page 15]
</pre>
|
