rfc8965v3.txt   rfc8965.txt 
Internet Engineering Task Force (IETF) J. Chroboczek Internet Engineering Task Force (IETF) J. Chroboczek
Request for Comments: 8965 IRIF, University of Paris-Diderot Request for Comments: 8965 IRIF, University of Paris-Diderot
Category: Informational November 2020 Category: Informational January 2021
ISSN: 2070-1721 ISSN: 2070-1721
Applicability of the Babel Routing Protocol Applicability of the Babel Routing Protocol
Abstract Abstract
Babel is a routing protocol based on the distance-vector algorithm Babel is a routing protocol based on the distance-vector algorithm
augmented with mechanisms for loop avoidance and starvation augmented with mechanisms for loop avoidance and starvation
avoidance. This document describes a number of niches where Babel avoidance. This document describes a number of niches where Babel
has been found to be useful and that are arguably not adequately has been found to be useful and that are arguably not adequately
skipping to change at line 35 skipping to change at line 35
Internet Engineering Steering Group (IESG). Not all documents Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841. Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata, Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8965. https://www.rfc-editor.org/info/rfc8965.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at line 282 skipping to change at line 282
3. Successful Deployments of Babel 3. Successful Deployments of Babel
This section gives a few examples of environments where Babel has This section gives a few examples of environments where Babel has
been successfully deployed. been successfully deployed.
3.1. Heterogeneous Networks 3.1. Heterogeneous Networks
Babel is able to deal with both classical, prefix-based ("Internet- Babel is able to deal with both classical, prefix-based ("Internet-
style") routing and flat ("mesh-style") routing over non-transitive style") routing and flat ("mesh-style") routing over non-transitive
link technologies. Just like traditional distance-vector protocols, link technologies. Just like traditional distance-vector protocols,
Babel is able to carry prefixes of arbitrary length, to supress Babel is able to carry prefixes of arbitrary length, to suppress
redundant announcements by applying the split-horizon optimisation redundant announcements by applying the split-horizon optimisation
where applicable, and can be configured to filter out redundant where applicable, and can be configured to filter out redundant
announcements (manual aggregation). Just like specialised mesh announcements (manual aggregation). Just like specialised mesh
protocols, Babel doesn't by default assume that links are transitive protocols, Babel doesn't by default assume that links are transitive
or symmetric, can dynamically compute metrics based on an estimation or symmetric, can dynamically compute metrics based on an estimation
of link quality, and carries large numbers of host routes efficiently of link quality, and carries large numbers of host routes efficiently
by omitting common prefixes. by omitting common prefixes.
Because of these properties, Babel has seen a number of successful Because of these properties, Babel has seen a number of successful
deployments in medium-sized heterogeneous networks, networks that deployments in medium-sized heterogeneous networks, networks that
skipping to change at line 374 skipping to change at line 374
announces to the whole routing domain is often sufficient to announces to the whole routing domain is often sufficient to
determine a mobile node's physical location with reasonable determine a mobile node's physical location with reasonable
precision. This might make Babel unapplicable in scenarios where a precision. This might make Babel unapplicable in scenarios where a
node's location is considered confidential. node's location is considered confidential.
5. References 5. References
5.1. Normative References 5.1. Normative References
[RFC8966] Chroboczek, J. and D. Schinazi, "The Babel Routing [RFC8966] Chroboczek, J. and D. Schinazi, "The Babel Routing
Protocol", RFC 8966, DOI 10.17487/RFC8966, November 2020, Protocol", RFC 8966, DOI 10.17487/RFC8966, January 2021,
<https://www.rfc-editor.org/info/rfc8966>. <https://www.rfc-editor.org/info/rfc8966>.
5.2. Informative References 5.2. Informative References
[BABEL-RTT] [BABEL-RTT]
Jonglez, B. and J. Chroboczek, "Delay-based Metric Jonglez, B. and J. Chroboczek, "Delay-based Metric
Extension for the Babel Routing Protocol", Work in Extension for the Babel Routing Protocol", Work in
Progress, Internet-Draft, draft-jonglez-babel-rtt- Progress, Internet-Draft, draft-jonglez-babel-rtt-
extension-02, 11 March 2019, <https://tools.ietf.org/html/ extension-02, 11 March 2019, <https://tools.ietf.org/html/
draft-jonglez-babel-rtt-extension-02>. draft-jonglez-babel-rtt-extension-02>.
skipping to change at line 490 skipping to change at line 490
Based on Packet Sequence Numbers for Optimized Link State Based on Packet Sequence Numbers for Optimized Link State
Routing Version 2 (OLSRv2)", RFC 7779, Routing Version 2 (OLSRv2)", RFC 7779,
DOI 10.17487/RFC7779, April 2016, DOI 10.17487/RFC7779, April 2016,
<https://www.rfc-editor.org/info/rfc7779>. <https://www.rfc-editor.org/info/rfc7779>.
[RFC7868] Savage, D., Ng, J., Moore, S., Slice, D., Paluch, P., and [RFC7868] Savage, D., Ng, J., Moore, S., Slice, D., Paluch, P., and
R. White, "Cisco's Enhanced Interior Gateway Routing R. White, "Cisco's Enhanced Interior Gateway Routing
Protocol (EIGRP)", RFC 7868, DOI 10.17487/RFC7868, May Protocol (EIGRP)", RFC 7868, DOI 10.17487/RFC7868, May
2016, <https://www.rfc-editor.org/info/rfc7868>. 2016, <https://www.rfc-editor.org/info/rfc7868>.
[RFC8967] Do, C., Kolodziejak, W., and J. Chroboczek, "Message [RFC8967] Dô, C., Kolodziejak, W., and J. Chroboczek, "MAC
Authentication Code (MAC) Authentication for the Babel Authentication for the Babel Routing Protocol", RFC 8967,
Routing Protocol", RFC 8967, DOI 10.17487/RFC8967, DOI 10.17487/RFC8967, January 2021,
November 2020, <https://www.rfc-editor.org/info/rfc8967>. <https://www.rfc-editor.org/info/rfc8967>.
[RFC8968] Décimo, A., Schinazi, D., and J. Chroboczek, "Babel [RFC8968] Décimo, A., Schinazi, D., and J. Chroboczek, "Babel
Routing Protocol over Datagram Transport Layer Security", Routing Protocol over Datagram Transport Layer Security",
RFC 8968, DOI 10.17487/RFC8968, November 2020, RFC 8968, DOI 10.17487/RFC8968, January 2021,
<https://www.rfc-editor.org/info/rfc8968>. <https://www.rfc-editor.org/info/rfc8968>.
[SS-ROUTING] [SS-ROUTING]
Boutier, M. and J. Chroboczek, "Source-specific routing", Boutier, M. and J. Chroboczek, "Source-specific routing",
In Proceedings of the IFIP Networking Conference, In Proceedings of the IFIP Networking Conference,
DOI 10.1109/IFIPNetworking.2015.7145305, May 2015, DOI 10.1109/IFIPNetworking.2015.7145305, May 2015,
<http://arxiv.org/pdf/1403.0445>. <http://arxiv.org/pdf/1403.0445>.
Acknowledgments Acknowledgments
 End of changes. 6 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/