draft-ietf-homenet-babel-profile-04.txt   draft-ietf-homenet-babel-profile-05.txt 
Network Working Group J. Chroboczek Network Working Group J. Chroboczek
Internet-Draft IRIF, University of Paris-Diderot Internet-Draft IRIF, University of Paris-Diderot
Intended status: Standards Track January 3, 2018 Intended status: Standards Track January 16, 2018
Expires: July 7, 2018 Expires: July 20, 2018
Homenet profile of the Babel routing protocol Homenet profile of the Babel routing protocol
draft-ietf-homenet-babel-profile-04 draft-ietf-homenet-babel-profile-05
Abstract Abstract
This document defines the subset of the Babel routing protocol This document defines the subset of the Babel routing protocol and
[RFC6126bis] and its extensions that a Homenet router must implement, its extensions that a Homenet router must implement, as well as the
as well as the interactions between HNCP [RFC7788] and Babel. interactions between HNCP and Babel.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 7, 2018. This Internet-Draft will expire on July 20, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirement Language . . . . . . . . . . . . . . . . . . 2
1.2. Background . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Homenet profile of Babel . . . . . . . . . . . . . . . . 3 2. The Homenet profile of Babel . . . . . . . . . . . . . . . . 3
2.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Non-requirements . . . . . . . . . . . . . . . . . . . . 4 2.2. Non-requirements . . . . . . . . . . . . . . . . . . . . 5
3. Interactions between HNCP and Babel . . . . . . . . . . . . . 5 3. Interactions between HNCP and Babel . . . . . . . . . . . . . 5
3.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Non-requirements . . . . . . . . . . . . . . . . . . . . 6 3.2. Non-requirements . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Normative References . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2. Informative References . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
The core of the Homenet protocol suite consists of HNCP [RFC7788], a The core of the Homenet protocol suite consists of HNCP [RFC7788], a
protocol used for flooding configuration information and assigning protocol used for flooding configuration information and assigning
prefixes to links, combined with the Babel routing protocol prefixes to links, combined with the Babel routing protocol
[RFC6126bis]. Babel is an extensible, flexible and modular protocol: [RFC6126bis]. Babel is an extensible, flexible and modular protocol:
minimal implementations of Babel have been demonstrated that consist minimal implementations of Babel have been demonstrated that consist
of a few hundred lines of code, while the "large" implementation of a few hundred lines of code, while the "large" implementation
includes support for a number of extensions and consists of over ten includes support for a number of extensions and consists of over ten
thousand lines of C code. thousand lines of C code.
This document consists of two parts. The first specifies the exact This document consists of two parts. The first specifies the exact
subset of the Babel protocol and its extensions that is required by subset of the Babel protocol and its extensions that is required by
an implementation of the Homenet protocol suite. The second an implementation of the Homenet protocol suite. The second
specifies how HNCP interacts with Babel. specifies how HNCP interacts with Babel.
1.1. Background 1.1. Requirement Language
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 RFC
2119 [RFC2119].
1.2. Background
The Babel routing protocol and its extensions are defined in a number The Babel routing protocol and its extensions are defined in a number
of documents: of documents:
o RFC 6126bis [RFC6126bis] defines the Babel routing protocol. It o RFC 6126bis [RFC6126bis] defines the Babel routing protocol. It
allows Babel's control data to be carried over either link-local allows Babel's control data to be carried over either link-local
IPv6 or IPv4, and in either case allows announcing both IPv4 and IPv6 or IPv4, and in either case allows announcing both IPv4 and
IPv6 routes. It leaves link cost estimation, metric computation IPv6 routes. It leaves link cost estimation, metric computation
and route selection to the implementation. Distinct and route selection to the implementation. Distinct
implementations of RFC 6126bis Babel will interoperate, in the implementations of RFC 6126bis Babel will interoperate, in the
skipping to change at page 7, line 6 skipping to change at page 7, line 20
4. Security Considerations 4. Security Considerations
Both HNCP and Babel carry their control data in IPv6 packets with a Both HNCP and Babel carry their control data in IPv6 packets with a
link-local source address, and implementations are required to drop link-local source address, and implementations are required to drop
packets sent from a global address. Hence, they are only susceptible packets sent from a global address. Hence, they are only susceptible
to attacks from a directly connected link on which the HNCP and Babel to attacks from a directly connected link on which the HNCP and Babel
implementations are listening. implementations are listening.
The security of a Homenet network relies on having a set of The security of a Homenet network relies on having a set of
"Internal" and "Ad Hoc" interfaces (Section 5.1 of [RFC7788]) that "Internal", "Ad Hoc" and "Hybrid" interfaces (Section 5.1 of
are assumed to be connected to links that are secured at a lower [RFC7788]) that are assumed to be connected to links that are secured
layer. HNCP and Babel packets are only accepted when they originate at a lower layer. HNCP and Babel packets are only accepted when they
on these trusted links. "External" and "Guest" interfaces are originate on these trusted links. "External" and "Guest" interfaces
connected to links that are not trusted, and any HNCP or Babel are connected to links that are not trusted, and any HNCP or Babel
packets that are received on such interfaces are ignored. ("Leaf" packets that are received on such interfaces are ignored. ("Leaf"
interfaces are a special case, since they are connected to trusted interfaces are a special case, since they are connected to trusted
links but HNCP and Babel traffic received on such interfaces is links but HNCP and Babel traffic received on such interfaces is
ignored.) ignored.) This implies that the security of a Homenet network
depends on the reliability of the border discovery procedure
described in Section 5.3 of [RFC7788].
If untrusted links are used for transit, which is NOT RECOMMENDED, If untrusted links are used for transit, which is NOT RECOMMENDED,
then any HNCP and Babel traffic that is carried over such links MUST then any HNCP and Babel traffic that is carried over such links MUST
be secured using an upper-layer security protocol. While both HNCP be secured using an upper-layer security protocol. While both HNCP
and Babel support cryptographic authentication, at the time of and Babel support cryptographic authentication, at the time of
writing no protocol for autonomous configuration of HNCP and Babel writing no protocol for autonomous configuration of HNCP and Babel
security has been defined. security has been defined.
5. Acknowledgments 5. IANA Considerations
This document requires no actions from IANA.
6. Acknowledgments
A number of people have helped with defining the requirements listed A number of people have helped with defining the requirements listed
in this document. I am especially indebted to Barbara Stark, Markus in this document. I am especially indebted to Barbara Stark, Markus
Stenberg, and Stephen Farrell. Stenberg, and Stephen Farrell.
6. References 7. References
6.1. Normative References 7.1. Normative References
[BABEL-SS] [BABEL-SS]
Boutier, M. and J. Chroboczek, "Source-Specific Routing in Boutier, M. and J. Chroboczek, "Source-Specific Routing in
Babel", draft-ietf-babel-source-specific-01 (work in Babel", draft-ietf-babel-source-specific-01 (work in
progress), August 2017. progress), August 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997.
[RFC6126bis] [RFC6126bis]
Chroboczek, J. and D. Schinazi, "The Babel Routing Chroboczek, J. and D. Schinazi, "The Babel Routing
Protocol", Internet Draft draft-ietf-babel-rfc6126bis-04, Protocol", Internet Draft draft-ietf-babel-rfc6126bis-04,
October 2017. October 2017.
[RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking [RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking
Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April
2016. 2016.
6.2. Informative References 7.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", draft-jonglez- Extension for the Babel Routing Protocol", draft-jonglez-
babel-rtt-extension-01 (work in progress), May 2015. babel-rtt-extension-01 (work in progress), May 2015.
[BABEL-Z] Chroboczek, J., "Diversity Routing for the Babel Routing [BABEL-Z] Chroboczek, J., "Diversity Routing for the Babel Routing
Protocol", draft-chroboczek-babel-diversity-routing-01 Protocol", draft-chroboczek-babel-diversity-routing-01
(work in progress), February 2016. (work in progress), February 2016.
 End of changes. 16 change blocks. 
27 lines changed or deleted 46 lines changed or added

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