draft-ietf-babel-rfc6126bis-10.txt   draft-ietf-babel-rfc6126bis-11.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
Obsoletes: 6126,7557 (if approved) D. Schinazi Obsoletes: 6126,7557 (if approved) D. Schinazi
Intended status: Standards Track Google LLC Intended status: Standards Track Google LLC
Expires: December 9, 2019 June 7, 2019 Expires: December 31, 2019 June 29, 2019
The Babel Routing Protocol The Babel Routing Protocol
draft-ietf-babel-rfc6126bis-10 draft-ietf-babel-rfc6126bis-11
Abstract Abstract
Babel is a loop-avoiding distance-vector routing protocol that is Babel is a loop-avoiding distance-vector routing protocol that is
robust and efficient both in ordinary wired networks and in wireless robust and efficient both in ordinary wired networks and in wireless
mesh networks. This document describes the Babel routing protocol, mesh networks. This document describes the Babel routing protocol,
and obsoletes RFCs 6126 and 7557. and obsoletes RFCs 6126 and 7557.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 December 9, 2019. This Internet-Draft will expire on December 31, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
skipping to change at page 3, line 15 skipping to change at page 3, line 15
F.3. Changes since draft-ietf-babel-rfc6126bis-01 . . . . . . 58 F.3. Changes since draft-ietf-babel-rfc6126bis-01 . . . . . . 58
F.4. Changes since draft-ietf-babel-rfc6126bis-02 . . . . . . 59 F.4. Changes since draft-ietf-babel-rfc6126bis-02 . . . . . . 59
F.5. Changes since draft-ietf-babel-rfc6126bis-03 . . . . . . 59 F.5. Changes since draft-ietf-babel-rfc6126bis-03 . . . . . . 59
F.6. Changes since draft-ietf-babel-rfc6126bis-03 . . . . . . 60 F.6. Changes since draft-ietf-babel-rfc6126bis-03 . . . . . . 60
F.7. Changes since draft-ietf-babel-rfc6126bis-04 . . . . . . 60 F.7. Changes since draft-ietf-babel-rfc6126bis-04 . . . . . . 60
F.8. Changes since draft-ietf-babel-rfc6126bis-05 . . . . . . 60 F.8. Changes since draft-ietf-babel-rfc6126bis-05 . . . . . . 60
F.9. Changes since draft-ietf-babel-rfc6126bis-06 . . . . . . 60 F.9. Changes since draft-ietf-babel-rfc6126bis-06 . . . . . . 60
F.10. Changes since draft-ietf-babel-rfc6126bis-07 . . . . . . 60 F.10. Changes since draft-ietf-babel-rfc6126bis-07 . . . . . . 60
F.11. Changes since draft-ietf-babel-rfc6126bis-08 . . . . . . 60 F.11. Changes since draft-ietf-babel-rfc6126bis-08 . . . . . . 60
F.12. Changes since draft-ietf-babel-rfc6126bis-09 . . . . . . 61 F.12. Changes since draft-ietf-babel-rfc6126bis-09 . . . . . . 61
F.13. Changes since draft-ietf-babel-rfc6126bis-10 . . . . . . 61
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61
1. Introduction 1. Introduction
Babel is a loop-avoiding distance-vector routing protocol that is Babel is a loop-avoiding distance-vector routing protocol that is
designed to be robust and efficient both in networks using prefix- designed to be robust and efficient both in networks using prefix-
based routing and in networks using flat routing ("mesh networks"), based routing and in networks using flat routing ("mesh networks"),
and both in relatively stable wired networks and in highly dynamic and both in relatively stable wired networks and in highly dynamic
wireless networks. wireless networks.
skipping to change at page 32, line 7 skipping to change at page 32, line 7
In order to speed up convergence after a mobility event, a node MAY In order to speed up convergence after a mobility event, a node MAY
send a unicast wildcard request after acquiring a new neighbour. send a unicast wildcard request after acquiring a new neighbour.
Additionally, a node MAY send a small number of multicast wildcard Additionally, a node MAY send a small number of multicast wildcard
requests shortly after booting. Note however that doing that requests shortly after booting. Note however that doing that
carelessly can cause serious congestion when a whole network is carelessly can cause serious congestion when a whole network is
rebooted, especially on link layers with high per-packet overhead rebooted, especially on link layers with high per-packet overhead
(e.g., IEEE 802.11). (e.g., IEEE 802.11).
4. Protocol Encoding 4. Protocol Encoding
A Babel packet is sent as the body of a UDP datagram, with network- A Babel packet MUST be sent as the body of a UDP datagram, with
layer hop count set to 1, destined to a well-known multicast address network-layer hop count set to 1, destined to a well-known multicast
or to a unicast address, over IPv4 or IPv6; in the case of IPv6, address or to a unicast address, over IPv4 or IPv6; in the case of
these addresses are link-local. Both the source and destination UDP IPv6, these addresses are link-local. Both the source and
port are set to a well-known port number. A Babel packet MUST be destination UDP port are set to a well-known port number. A Babel
silently ignored unless its source address is either a link-local packet MUST be silently ignored unless its source address is either a
IPv6 address or an IPv4 address belonging to the local network, and link-local IPv6 address or an IPv4 address belonging to the local
its source port is the well-known Babel port. It MAY be silently network, and its source port is the well-known Babel port. It MAY be
ignored if its destination address is a global IPv6 address. silently ignored if its destination address is a global IPv6 address.
In order to minimise the number of packets being sent while avoiding In order to minimise the number of packets being sent while avoiding
lower-layer fragmentation, a Babel node SHOULD attempt to maximise lower-layer fragmentation, a Babel node SHOULD attempt to maximise
the size of the packets it sends, up to the outgoing interface's MTU the size of the packets it sends, up to the outgoing interface's MTU
adjusted for lower-layer headers (28 octets for UDP over IPv4, 48 adjusted for lower-layer headers (28 octets for UDP over IPv4, 48
octets for UDP over IPv6). It MUST NOT send packets larger than the octets for UDP over IPv6). It MUST NOT send packets larger than the
attached interface's MTU adjusted for lower-layer headers or 512 attached interface's MTU adjusted for lower-layer headers or 512
octets, whichever is larger, but not exceeding 2^16 - 1 adjusted for octets, whichever is larger, but not exceeding 2^16 - 1 adjusted for
lower-layer headers. Every Babel speaker MUST be able to receive lower-layer headers. Every Babel speaker MUST be able to receive
packets that are as large as any attached interface's MTU adjusted packets that are as large as any attached interface's MTU adjusted
skipping to change at page 32, line 48 skipping to change at page 32, line 48
4.1.1. Interval 4.1.1. Interval
Relative times are carried as 16-bit values specifying a number of Relative times are carried as 16-bit values specifying a number of
centiseconds (hundredths of a second). This allows times up to centiseconds (hundredths of a second). This allows times up to
roughly 11 minutes with a granularity of 10ms, which should cover all roughly 11 minutes with a granularity of 10ms, which should cover all
reasonable applications of Babel. reasonable applications of Babel.
4.1.2. Router-Id 4.1.2. Router-Id
A router-id is an arbitrary 8-octet value. A router-id MUST NOT A router-id is an arbitrary 8-octet value. A router-id MUST NOT
consist of either all zeroes or all ones. consist of either all binary zeroes (0000000000000000 hexadecimal) or
all binary ones ones (ffffffffffffffff hexadecimal).
4.1.3. Address 4.1.3. Address
Since the bulk of the protocol is taken by addresses, multiple ways Since the bulk of the protocol is taken by addresses, multiple ways
of encoding addresses are defined. Additionally, a common subnet of encoding addresses are defined. Additionally, a common subnet
prefix may be omitted when multiple addresses are sent in a single prefix may be omitted when multiple addresses are sent in a single
packet -- this is known as address compression (Section 4.6.9). packet -- this is known as address compression (Section 4.6.9).
Address encodings: Address encodings:
skipping to change at page 61, line 9 skipping to change at page 61, line 9
F.11. Changes since draft-ietf-babel-rfc6126bis-08 F.11. Changes since draft-ietf-babel-rfc6126bis-08
o Added recommendation that route selection should not take seqnos o Added recommendation that route selection should not take seqnos
into account. into account.
F.12. Changes since draft-ietf-babel-rfc6126bis-09 F.12. Changes since draft-ietf-babel-rfc6126bis-09
o Editorial changes only. o Editorial changes only.
F.13. Changes since draft-ietf-babel-rfc6126bis-10
o Editorial changes only.
Authors' Addresses Authors' Addresses
Juliusz Chroboczek Juliusz Chroboczek
IRIF, University of Paris-Diderot IRIF, University of Paris-Diderot
Case 7014 Case 7014
75205 Paris Cedex 13 75205 Paris Cedex 13
France France
Email: jch@irif.fr Email: jch@irif.fr
 End of changes. 7 change blocks. 
13 lines changed or deleted 19 lines changed or added

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