The Babel Routing Protocol
draft-ietf-babel-rfc6126bis-05
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8966.
|
|
|---|---|---|---|
| Authors | Juliusz Chroboczek , David Schinazi | ||
| Last updated | 2018-05-29 | ||
| Replaces | draft-chroboczek-babel-rfc6126bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
GENART Last Call review
(of
-10)
by Russ Housley
Ready w/nits
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | In WG Last Call | |
| Document shepherd | Donald E. Eastlake 3rd | ||
| IESG | IESG state | Became RFC 8966 (Proposed Standard) | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | Donald Eastlake <d3e3e3@gmail.com> |
draft-ietf-babel-rfc6126bis-05
#x27;t reannounce any routes that it has learnt from its neighbours. It may either maintain a full routing table, or simply select a default gateway amongst any one of its neighbours that announces a default route. Since a stub implementation never forwards packets except from or to directly attached links, it cannot possibly participate in a routing loop, and hence it need not evaluate the feasibility condition or maintain a source table. No matter how primitive, a stub implementation MUST parse sub-TLVs attached to any TLVs that it understands and check the mandatory bit. It MUST answer acknowledgment requests and MUST participate in the Hello/IHU protocol. It MUST also be able to reply to seqno requests for routes that it announces and SHOULD be able to reply to route requests. Experience shows that an IPv6-only stub implementation of Babel can be written in less than 1000 lines of C code and compile to 13 kB of text on 32-bit CISC architecture. Appendix E. Software Availability The sample implementation of Babel is available from <https://www.irif.fr/~jch/software/babel/>. Chroboczek & Schinazi Expires November 30, 2018 [Page 56] Internet-Draft The Babel Routing Protocol May 2018 Appendix F. Changes from previous versions F.1. Changes since RFC 6126 o Changed UDP port number to 6696. o Consistently use router-id rather than id. o Clarified that the source garbage collection timer is reset after sending an update even if the entry was not modified. o In section "Seqno Requests", fixed an erroneous "route request". o In the description of the Seqno Request TLV, added the description of the Router-Id field. o Made router-ids all-0 and all-1 forbidden. F.2. Changes since draft-ietf-babel-rfc6126bis-00 o Added security considerations. F.3. Changes since draft-ietf-babel-rfc6126bis-01 o Integrated the format of sub-TLVs. o Mentioned for each TLV whether it supports sub-TLVs. o Added Appendix C. o Added a mandatory bit in sub-TLVs. o Changed compression state to be per-AF rather than per-AE. o Added implementation hint for the routing table. o Clarified how router-ids are computed when bit 0x40 is set in Updates. o Relaxed the conditions for sending requests, and tightened the conditions for forwarding requests. o Clarified that neighbours should be acquired at some point, but it doesn't matter when. Chroboczek & Schinazi Expires November 30, 2018 [Page 57] Internet-Draft The Babel Routing Protocol May 2018 F.4. Changes since draft-ietf-babel-rfc6126bis-02 o Added Unicast Hellos. o Added unscheduled (interval-less) Hellos. o Changed Appendix A to consider Unicast and unscheduled Hellos. o Changed Appendix B to agree with the reference implementation. o Added optional algorithm to avoid the hold time. o Changed the table of pending seqno requests to be indexed by router-id in addition to prefixes. o Relaxed the route acquisition algorithm. o Replaced minimal implementations by stub implementations. o Added acknowledgments section. F.5. Changes since draft-ietf-babel-rfc6126bis-03 o Clarified that all the data structures are conceptual. o Made sending and receiving Multicast Hellos a SHOULD, avoids expressing any opinion about Unicast Hellos. o Removed opinion about Multicast vs. Unicast Hellos (Appendix A.4). o Made hold-time into a SHOULD rather than MUST. o Clarified that Seqno Requests are for a finite-metric Update. o Clarified that sub-TLVs Pad1 and PadN are allowed within any TLV that allows sub-TLVs. o Updated IANA Considerations. o Updated Security Considerations. o Renamed routing table back to route table. o Made buffering outgoing updates a SHOULD. o Weakened advice to use modified EUI-64 in router-ids. o Added information about sending requests to Appendix B. Chroboczek & Schinazi Expires November 30, 2018 [Page 58] Internet-Draft The Babel Routing Protocol May 2018 o A number of minor wording changes and clarifications. F.6. Changes since draft-ietf-babel-rfc6126bis-03 Minor editorial changes. F.7. Changes since draft-ietf-babel-rfc6126bis-04 o Renamed isotonicity to left-distributivity. o Minor clarifications to unicast hellos. o Updated requirements boilerplate to RFC 8174. o Minor editorial changes. Authors' Addresses Juliusz Chroboczek IRIF, University of Paris-Diderot Case 7014 75205 Paris Cedex 13 France Email: jch@irif.fr David Schinazi Apple Inc. 1 Infinite Loop Cupertino, California 95014 US Email: dschinazi@apple.com Chroboczek & Schinazi Expires November 30, 2018 [Page 59]