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
|
<pre>Independent Submission J. Chroboczek
Request for Comments: 7557 PPS, University of Paris-Diderot
Updates: <a href="./rfc6126">6126</a> May 2015
Category: Experimental
ISSN: 2070-1721
<span class="h1">Extension Mechanism for the Babel Routing Protocol</span>
Abstract
This document defines the encoding of extensions to the Babel routing
protocol, as specified in <a href="./rfc6126">RFC 6126</a>.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This is a contribution to the RFC Series, independently
of any other RFC stream. The RFC Editor has chosen to publish this
document at its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not a candidate for any level of Internet
Standard; see <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/rfc7557">http://www.rfc-editor.org/info/rfc7557</a>.
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.
<span class="grey">Chroboczek Experimental [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Mechanisms for Extending the Babel Protocol . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. New Versions of the Babel Protocol . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. New TLVs . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.4">2.4</a>. The Flags Field . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.5">2.5</a>. Packet Trailer . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3">3</a>. Format of Sub-TLVs . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. Sub-TLVs Specified in This Document . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Unknown Sub-TLVs . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4">4</a>. Choosing between Extension Mechanisms . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
A Babel packet [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] contains a header followed by a sequence of
TLVs, each of which is a sequence of octets having an explicit type
and length. The original Babel protocol has the following provisions
for including extension data:
o A Babel packet with a version number different from 2 MUST be
silently ignored (<a href="./rfc6126#section-4.2">[RFC6126], Section 4.2</a>).
o An unknown TLV MUST be silently ignored (<a href="./rfc6126#section-4.3">[RFC6126], Section 4.3</a>).
o Except for Pad1 and PadN, all TLVs are self-terminating, and any
extra data included in a TLV MUST be silently ignored (<a href="./rfc6126#section-4.2">[RFC6126],
Section 4.2</a>).
o The Flags field of the Update TLV contains 6 undefined bits that
MUST be silently ignored (<a href="./rfc6126#section-4.4.9">[RFC6126], Section 4.4.9</a>).
o Any data following the last TLV of a Babel packet MUST be silently
ignored (<a href="./rfc6126#section-4.2">[RFC6126], Section 4.2</a>).
Each of these provisions provides a place to store data needed by
extensions of the Babel protocol. However, in the absence of any
further conventions, independently developed extensions to the Babel
protocol might make conflicting uses of the available space, and
therefore lead to implementations that would fail to interoperate.
<span class="grey">Chroboczek Experimental [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
This document formalises a set of rules for extending the Babel
protocol that are designed to ensure that no such incompatibilities
arise, and that are currently respected by a number of deployed
extensions.
In the rest of this document, we use the term "original protocol" for
the protocol defined in [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>], and "extended protocol" for any
extension of the Babel protocol that follows the rules set out in
this document.
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-2" href="#section-2">2</a>. Mechanisms for Extending the Babel Protocol</span>
This section describes each of the mechanisms available for extending
the Babel protocol.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. New Versions of the Babel Protocol</span>
The header of a Babel packet contains an eight-bit protocol version.
The current version of the Babel protocol is version 2; any packets
containing a version number different from 2 MUST be silently
ignored.
Versions 0 and 1 were earlier experimental versions of the Babel
protocol that have seen some modest deployment; these version numbers
SHOULD NOT be reused by future versions of the Babel protocol.
Version numbers larger than 2 might be used by a future incompatible
protocol.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. New TLVs</span>
An extension may carry its data in a new TLV type. Such new TLVs
will be silently ignored by implementations of the original Babel
protocol, as well as by other extended implementations of the Babel
protocol, as long as the TLV types do not collide.
All new TLVs MUST have the format defined in <a href="./rfc6126#section-4.3">[RFC6126], Section 4.3</a>.
New TLVs SHOULD be self-terminating, in the sense defined in the next
section, and any data found after the main data section of the TLV
SHOULD be treated as a series of sub-TLVs.
TLV types 224 through 254 are reserved for Experimental Use
[<a href="./rfc3692" title=""Assigning Experimental and Testing Numbers Considered Useful"">RFC3692</a>]. TLV type 255 is reserved for expansion of the TLV type
space, in the unlikely event that eight bits turn out not to be
enough.
<span class="grey">Chroboczek Experimental [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Sub-TLVs</span>
With the exception of the Pad1 TLV, all Babel TLVs carry an explicit
length. With the exception of Pad1 and PadN, all TLVs defined by the
original protocol are self-terminating, in the sense that the length
of the meaningful data that they contain (the "natural length") can
be determined without reference to the explicitly encoded length. In
some cases, the natural length is trivial to determine: for example,
a HELLO TLV always has a natural length of 2 (4 including the Type
and Length fields). In other cases, determining the natural length
is not that easy, but this needs to be done anyway by an
implementation that interprets the given TLV. For example, the
natural length of an Update TLV depends on both the prefix length and
the amount of prefix compression being performed.
If the explicit length of a TLV defined by the original protocol is
larger than its natural length, the extra space present in the TLV is
silently ignored by an implementation of the original protocol;
extended implementations MAY use it to store arbitrary data and
SHOULD structure the additional data as a sequence of sub-TLVs.
Unlike TLVs, the sub-TLVs themselves need not be self-terminating.
An extension MAY be assigned one or more sub-TLV types. Sub-TLV
types are assigned independently from TLV types: the same numeric
type can be assigned to a TLV and a sub-TLV. Sub-TLV types are
assigned globally: once an extension is assigned a given sub-TLV
number, it MAY use this number within any TLV. However, the
interpretation of a given sub-TLV type can depend on which particular
TLV it is embedded within.
Sub-TLV types 224 through 254 are reserved for Experimental Use
[<a href="./rfc3692" title=""Assigning Experimental and Testing Numbers Considered Useful"">RFC3692</a>]. TLV type 255 is reserved for expansion of the sub-TLV
type space, in the unlikely event that eight bits turn out not to be
enough. The format of sub-TLVs is defined in <a href="#section-3">Section 3</a> below.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. The Flags Field</span>
The Flags field is an eight-bit field in the Update TLV. Bits 0 and
1 (the bits with values 80 and 40 hexadecimal) are defined by the
original protocol and MUST be recognised and used by every
implementation. The remaining six bits are not currently used and
are silently ignored by implementations of the original protocol.
Due to the small size of the Flags field, it is NOT RECOMMENDED that
one or more bits be assigned to an extension; a sub-TLV SHOULD be
assigned instead. An implementation MUST ignore any bits in the
Flags field that it does not know about and MUST send them as zero.
<span class="grey">Chroboczek Experimental [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Packet Trailer</span>
A Babel packet carries an explicit length in its header. A Babel
packet is carried by a UDP datagram, which in turn contains an
explicit length in its header. It is possible for a UDP datagram
carrying a Babel packet to be larger than the size of the Babel
packet. In that case, the extra space after the Babel packet, known
as the packet trailer, is silently ignored by an implementation of
the original protocol.
The packet trailer was originally intended to be used as a
cryptographic trailer. However, the authentication extension to
Babel [<a href="./rfc7298" title=""Babel Hashed Message Authentication Code (HMAC) Cryptographic Authentication"">RFC7298</a>] ended up using a pair of new TLVs, and no currently
deployed extension of Babel uses the packet trailer. The format and
purpose of the packet trailer is therefore currently left undefined.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Format of Sub-TLVs</span>
A sub-TLV has exactly the same structure as a TLV. Except for Pad1
(<a href="#section-3.1.1">Section 3.1.1</a>), all sub-TLVs have the following structure:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Body...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Fields:
Type The type of the sub-TLV.
Length The length of the body, in octets, exclusive of the Type
and Length fields.
Body The sub-TLV body, the interpretation of which depends on
both the type of the sub-TLV and the type of the TLV within
which it is embedded.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Sub-TLVs Specified in This Document</span>
This document defines two types of sub-TLVs, Pad1 and PadN. These
two sub-TLVs MUST be correctly parsed and ignored by any extended
implementation of the Babel protocol that uses sub-TLVs.
<span class="grey">Chroboczek Experimental [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Pad1</span>
0
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| Type = 0 |
+-+-+-+-+-+-+-+-+
Fields:
Type Set to 0 to indicate a Pad1 sub-TLV.
This sub-TLV is silently ignored on reception.
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. PadN</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 1 | Length | MBZ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Fields:
Type Set to 1 to indicate a PadN sub-TLV.
Length The length of the body, in octets, exclusive of the Type
and Length fields.
MBZ Set to 0 on transmission.
This sub-TLV is silently ignored on reception.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Unknown Sub-TLVs</span>
Any unknown sub-TLV MUST be silently ignored by an extended
implementation that uses sub-TLVs.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Choosing between Extension Mechanisms</span>
New versions of the Babel protocol should only be defined if the new
version is not backwards compatible with the original protocol.
In many cases, an extension could be implemented either by defining a
new TLV or by adding a new sub-TLV to an existing TLV. For example,
an extension whose purpose is to attach additional data to route
updates can be implemented either by creating a new "enriched" Update
TLV or by adding a sub-TLV to the Update TLV.
<span class="grey">Chroboczek Experimental [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
The two encodings are treated differently by implementations that do
not understand the extension. In the case of a new TLV, the whole
unknown TLV is ignored by an implementation of the original protocol,
while in the case of a new sub-TLV, the TLV is parsed and acted upon,
and the unknown sub-TLV is silently ignored. Therefore, a sub-TLV
should be used by extensions that extend the Update in a compatible
manner (the extension data may be silently ignored), while a new TLV
must be used by extensions that make incompatible extensions to the
meaning of the TLV (the whole TLV must be thrown away if the
extension data is not understood).
Using a new bit in the Flags field is equivalent to defining a new
sub-TLV while using less space in the Babel packet. Due to the
limited Flags space, and the doubtful space savings, we do not
recommend the use of bits in the Flags field -- a new sub-TLV should
be used instead.
We refrain from making any recommendations about the usage of the
packet trailer due to the lack of implementation experience.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has created three new registries, called "Babel TLV Types",
"Babel Sub-TLV Types", and "Babel Flags Values". The allocation
policy for each of these registries is Specification Required
[<a href="./rfc5226" title="">RFC5226</a>].
<span class="grey">Chroboczek Experimental [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
The initial values in the "Babel TLV Types" registry are as follows:
+---------+-----------------------------------------+---------------+
| Type | Name | Reference |
+---------+-----------------------------------------+---------------+
| 0 | Pad1 | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 1 | PadN | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 2 | Acknowledgment Request | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 3 | Acknowledgment | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 4 | Hello | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 5 | IHU | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 6 | Router-Id | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 7 | Next Hop | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 8 | Update | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 9 | Route Request | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 10 | Seqno Request | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 11 | TS/PC | [<a href="./rfc7298" title=""Babel Hashed Message Authentication Code (HMAC) Cryptographic Authentication"">RFC7298</a>] |
| | | |
| 12 | HMAC | [<a href="./rfc7298" title=""Babel Hashed Message Authentication Code (HMAC) Cryptographic Authentication"">RFC7298</a>] |
| | | |
| 13 | Source-specific Update | [<a href="#ref-BABEL-SS" title=""Source-Specific Routing in Babel"">BABEL-SS</a>] |
| | | |
| 14 | Source-specific Request | [<a href="#ref-BABEL-SS" title=""Source-Specific Routing in Babel"">BABEL-SS</a>] |
| | | |
| 15 | Source-specific Seqno Request | [<a href="#ref-BABEL-SS" title=""Source-Specific Routing in Babel"">BABEL-SS</a>] |
| | | |
| 224-254 | Reserved for Experimental Use | this document |
| | | |
| 255 | Reserved for expansion of the type | this document |
| | space | |
+---------+-----------------------------------------+---------------+
<span class="grey">Chroboczek Experimental [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
The initial values in the "Babel Sub-TLV Types" registry are as
follows:
+---------+-----------------------------------------+---------------+
| Type | Name | Reference |
+---------+-----------------------------------------+---------------+
| 0 | Pad1 | this document |
| | | |
| 1 | PadN | this document |
| | | |
| 2 | Diversity | [<a href="#ref-BABEL-DIV" title=""Diversity Routing for the Babel Routing Protocol"">BABEL-DIV</a>] |
| | | |
| 3 | Timestamp | [<a href="#ref-BABEL-RTT" title=""Delay-based Metric Extension for the Babel Routing Protocol"">BABEL-RTT</a>] |
| | | |
| 224-254 | Reserved for Experimental Use | this document |
| | | |
| 255 | Reserved for expansion of the type | this document |
| | space | |
+---------+-----------------------------------------+---------------+
The initial values in the "Babel Flags Values" registry are as
follows:
+-----+-------------------+-----------+
| Bit | Name | Reference |
+-----+-------------------+-----------+
| 0 | Default prefix | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 1 | Default router-id | [<a href="./rfc6126" title=""The Babel Routing Protocol"">RFC6126</a>] |
| | | |
| 2-7 | Unassigned | |
+-----+-------------------+-----------+
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
This document specifies the structure of fields that are already
present in the original Babel protocol and does not, by itself, raise
any new security considerations. Specific extensions may change the
security properties of the protocol, for example, by adding security
mechanisms [<a href="./rfc7298" title=""Babel Hashed Message Authentication Code (HMAC) Cryptographic Authentication"">RFC7298</a>] or by enabling new kinds of attack.
<span class="grey">Chroboczek Experimental [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.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>>.
[<a id="ref-RFC3692">RFC3692</a>] Narten, T., "Assigning Experimental and Testing Numbers
Considered Useful", <a href="https://www.rfc-editor.org/bcp/bcp82">BCP 82</a>, <a href="./rfc3692">RFC 3692</a>,
DOI 10.17487/RFC3692, January 2004,
<<a href="http://www.rfc-editor.org/info/rfc3692">http://www.rfc-editor.org/info/rfc3692</a>>.
[<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>>.
[<a id="ref-RFC6126">RFC6126</a>] Chroboczek, J., "The Babel Routing Protocol", <a href="./rfc6126">RFC 6126</a>,
DOI 10.17487/RFC6126, April 2011,
<<a href="http://www.rfc-editor.org/info/rfc6126">http://www.rfc-editor.org/info/rfc6126</a>>.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-BABEL-DIV">BABEL-DIV</a>] Chroboczek, J., "Diversity Routing for the Babel Routing
Protocol", Work in Progress, <a href="./draft-chroboczek-babel-diversity-routing-00">draft-chroboczek-babel-</a>
<a href="./draft-chroboczek-babel-diversity-routing-00">diversity-routing-00</a>, July 2014.
[<a id="ref-BABEL-RTT">BABEL-RTT</a>] Jonglez, B. and J. Chroboczek, "Delay-based Metric
Extension for the Babel Routing Protocol", Work in
Progress, <a href="./draft-jonglez-babel-rtt-extension-01">draft-jonglez-babel-rtt-extension-01</a>, May 2015.
[<a id="ref-BABEL-SS">BABEL-SS</a>] Boutier, M. and J. Chroboczek, "Source-Specific Routing
in Babel", Work in Progress, <a href="./draft-boutier-babel-source-specific-01">draft-boutier-babel-</a>
<a href="./draft-boutier-babel-source-specific-01">source-specific-01</a>, May 2015.
[<a id="ref-RFC7298">RFC7298</a>] Ovsienko, D., "Babel Hashed Message Authentication Code
(HMAC) Cryptographic Authentication", <a href="./rfc7298">RFC 7298</a>,
DOI 10.17487/RFC7298, July 2014,
<<a href="http://www.rfc-editor.org/info/rfc7298">http://www.rfc-editor.org/info/rfc7298</a>>.
<span class="grey">Chroboczek Experimental [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7557">RFC 7557</a> Babel Extension Mechanism May 2015</span>
Acknowledgments
I am grateful to Denis Ovsienko and Gabriel Kerneis for their
feedback on previous draft versions of this document.
Author's Address
Juliusz Chroboczek
PPS, University of Paris-Diderot
Case 7014
75205 Paris Cedex 13
France
EMail: jch@pps.univ-paris-diderot.fr
Chroboczek Experimental [Page 11]
</pre>
|
