draft-ietf-6lo-backbone-router-00.txt   draft-ietf-6lo-backbone-router-01.txt 
6lo P. Thubert, Ed. 6lo P. Thubert, Ed.
Internet-Draft cisco Internet-Draft cisco
Intended status: Standards Track January 5, 2016 Intended status: Standards Track March 18, 2016
Expires: July 8, 2016 Expires: September 19, 2016
IPv6 Backbone Router IPv6 Backbone Router
draft-ietf-6lo-backbone-router-00 draft-ietf-6lo-backbone-router-01
Abstract Abstract
This specification proposes an update to IPv6 Neighbor Discovery, to This specification proposes an update to IPv6 Neighbor Discovery, to
enhance the operation of IPv6 over wireless links that exhibit lossy enhance the operation of IPv6 over wireless links that exhibit lossy
multicast support, and enable a large degree of scalability by multicast support, and enable a large degree of scalability by
splitting the broadcast domains. A higher speed backbone federates splitting the broadcast domains. A higher speed backbone federates
multiple wireless links to form a large MultiLink Subnet. Backbone multiple wireless links to form a large MultiLink Subnet. Backbone
Routers acting as Layer-3 Access Point route packets to registered Routers acting as Layer-3 Access Point route packets to registered
nodes, where an classical Layer-2 Access Point would bridge. nodes, where an classical Layer-2 Access Point would bridge.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 8, 2016. This Internet-Draft will expire on September 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
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
2. Applicability and Requirements Served . . . . . . . . . . . . 5 2. Applicability and Requirements Served . . . . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. New Types And Formats . . . . . . . . . . . . . . . . . . . . 10 5. New Types And Formats . . . . . . . . . . . . . . . . . . . . 11
5.1. Transaction ID . . . . . . . . . . . . . . . . . . . . . 10 5.1. Transaction ID . . . . . . . . . . . . . . . . . . . . . 11
5.2. Owner Unique ID . . . . . . . . . . . . . . . . . . . . . 11 5.2. Owner Unique ID . . . . . . . . . . . . . . . . . . . . . 11
5.3. The Enhanced Address Registration Option (EARO) . . . . . 11 5.3. The Enhanced Address Registration Option (EARO) . . . . . 12
6. Backbone Router Routing Operations . . . . . . . . . . . . . 14 6. Backbone Router Routing Operations . . . . . . . . . . . . . 14
6.1. Over the Backbone Link . . . . . . . . . . . . . . . . . 14 6.1. Over the Backbone Link . . . . . . . . . . . . . . . . . 14
6.2. Over the LLN Link . . . . . . . . . . . . . . . . . . . . 15 6.2. Over the LLN Link . . . . . . . . . . . . . . . . . . . . 16
7. BackBone Router Proxy Operations . . . . . . . . . . . . . . 17 7. BackBone Router Proxy Operations . . . . . . . . . . . . . . 17
7.1. Registration and Binding State Creation . . . . . . . . . 19 7.1. Registration and Binding State Creation . . . . . . . . . 20
7.2. Defending Addresses . . . . . . . . . . . . . . . . . . . 21 7.2. Defending Addresses . . . . . . . . . . . . . . . . . . . 21
8. Security Considerations . . . . . . . . . . . . . . . . . . . 22 8. Security Considerations . . . . . . . . . . . . . . . . . . . 22
9. Protocol Constants . . . . . . . . . . . . . . . . . . . . . 22 9. Protocol Constants . . . . . . . . . . . . . . . . . . . . . 22
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
12.1. Normative References . . . . . . . . . . . . . . . . . . 23 12.1. Normative References . . . . . . . . . . . . . . . . . . 23
12.2. Informative References . . . . . . . . . . . . . . . . . 24 12.2. Informative References . . . . . . . . . . . . . . . . . 24
12.3. External Informative References . . . . . . . . . . . . 28 12.3. External Informative References . . . . . . . . . . . . 28
Appendix A. Requirements . . . . . . . . . . . . . . . . . . . . 28 Appendix A. Requirements . . . . . . . . . . . . . . . . . . . . 29
A.1. Requirements Related to Mobility . . . . . . . . . . . . 28 A.1. Requirements Related to Mobility . . . . . . . . . . . . 29
A.2. Requirements Related to Routing Protocols . . . . . . . . 29 A.2. Requirements Related to Routing Protocols . . . . . . . . 29
A.3. Requirements Related to the Variety of Low-Power Link A.3. Requirements Related to the Variety of Low-Power Link
types . . . . . . . . . . . . . . . . . . . . . . . . . . 30 types . . . . . . . . . . . . . . . . . . . . . . . . . . 30
A.4. Requirements Related to Proxy Operations . . . . . . . . 31 A.4. Requirements Related to Proxy Operations . . . . . . . . 31
A.5. Requirements Related to Security . . . . . . . . . . . . 31 A.5. Requirements Related to Security . . . . . . . . . . . . 31
A.6. Requirements Related to Scalability . . . . . . . . . . . 32 A.6. Requirements Related to Scalability . . . . . . . . . . . 33
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 33 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
Though in most cases, including Low-Power ones, IEEE802.11 Classical IPv6 Neighbor Discovery [RFC4862] operations are reactive
[IEEE80211] is operated as a wireless extension to an Ethernet and rely heavily on multicast operations to locate a correspondent.
bridged domain, the impact of radio broadcasts for IPv6 [RFC2460] When this was designed, it was a natural match for the transparent
multicast operations, in particular related to the power consumption bridging operation of Ethernet. IEEE 802.11 Access Points IEEE802.11
of battery-operated devices, lead the community to rethink the plain [IEEE80211] effectively act as bridges, but, in order to protect the
layer-2 approach and consider splitting the broadcast domain between medium, they do not implement transparent bridging. Instead, a so-
the wired and the wireless access links. To that effect, the current called association process is used to register proactively the MAC
IEEE802.11 specifications require the capability to perform ARP and addresses of the wireless STAs to the APs. Sadly, the IPv6 ND
ND proxy [RFC4389] functions at the Access Points (APs), but rely on operation was not adapted to match that model.
snooping for acquiring the related state, which is unsatisfactory in
a lossy and mobile environments. Though in most cases, including Low-Power ones, IEEE802.11 is
operated as a wireless extension to an Ethernet bridged domain, the
impact of radio broadcasts for IPv6 [RFC2460] multicast operations,
in particular related to the power consumption of battery-operated
devices, lead the community to rethink the plain layer-2 approach and
consider splitting the broadcast domain between the wired and the
wireless access links. To that effect, the current IEEE802.11
specifications require the capability to perform ARP and ND proxy
[RFC4389] functions at the Access Points (APs), but rely on snooping
for acquiring the related state, which is unsatisfactory in a lossy
and mobile environments.
Without a proxy, any IP multicast that circulates in the bridged Without a proxy, any IP multicast that circulates in the bridged
domain ends up broadcasted by the Access Points to all STAs, domain ends up broadcasted by the Access Points to all STAs,
including Low-Power battery-operated ones. With an incorrect or including Low-Power battery-operated ones. With an incorrect or
missing state in the proxy, a packet may not be delivered to the missing state in the proxy, a packet may not be delivered to the
destination, which may have operational impacts depending on the destination, which may have operational impacts depending on the
criticality of the packet. criticality of the packet.
Some messages are lost for the lack of retries, regardless of their Some messages are lost for the lack of retries, regardless of their
degree of criticality; it results for instance that Duplicate Address degree of criticality; it results for instance that Duplicate Address
skipping to change at page 13, line 12 skipping to change at page 13, line 26
addresses that it owns, or proxy-register addresses on behalf some addresses that it owns, or proxy-register addresses on behalf some
another node, indicating those addresses being registered in the another node, indicating those addresses being registered in the
Target Address field of the NS messages, while using one of its own, Target Address field of the NS messages, while using one of its own,
already registered, addresses as source. already registered, addresses as source.
The format of the EARO option is as follows: The format of the EARO option is as follows:
0 1 2 3 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 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 = 2 | Status | pref level | | Type | Length = 2 | Status | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |T| TID | Registration Lifetime | | Reserved |T| TID | Registration Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Owner Unique ID (EUI-64 or equivalent) + + Owner Unique ID (EUI-64 or equivalent) +
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: EARO Figure 2: EARO
skipping to change at page 13, line 40 skipping to change at page 14, line 9
Reserved: This field is unused. It MUST be initialized to zero by Reserved: This field is unused. It MUST be initialized to zero by
the sender and MUST be ignored by the receiver. the sender and MUST be ignored by the receiver.
T: One bit flag. Set if the next octet is a used as a TID. T: One bit flag. Set if the next octet is a used as a TID.
TID: 1-byte integer; a transaction id that is maintained by the node TID: 1-byte integer; a transaction id that is maintained by the node
and incremented with each transaction. it is recommended that the and incremented with each transaction. it is recommended that the
node maintains the TID in a persistent storage. node maintains the TID in a persistent storage.
Registration Lifetime: 1-byte integer; expressed in minutes. 0 Registration Lifetime: 16-bit integer; expressed in minutes. 0
means that the registration has ended and the state should be means that the registration has ended and the state should be
removed. removed.
Owner Unique Identifier: A globally unique identifier for the node Owner Unique Identifier: A globally unique identifier for the node
associated. This can be the EUI-64 derived IID of an interface, associated. This can be the EUI-64 derived IID of an interface,
or some provable ID obtained cryptographically. or some provable ID obtained cryptographically.
6. Backbone Router Routing Operations 6. Backbone Router Routing Operations
| |
skipping to change at page 24, line 44 skipping to change at page 25, line 8
6man-efficient-nd-07 (work in progress), February 2015. 6man-efficient-nd-07 (work in progress), February 2015.
[I-D.delcarpio-6lo-wlanah] [I-D.delcarpio-6lo-wlanah]
Vega, L., Robles, I., and R. Morabito, "IPv6 over Vega, L., Robles, I., and R. Morabito, "IPv6 over
802.11ah", draft-delcarpio-6lo-wlanah-01 (work in 802.11ah", draft-delcarpio-6lo-wlanah-01 (work in
progress), October 2015. progress), October 2015.
[I-D.ietf-6lo-6lobac] [I-D.ietf-6lo-6lobac]
Lynn, K., Martocci, J., Neilson, C., and S. Donaldson, Lynn, K., Martocci, J., Neilson, C., and S. Donaldson,
"Transmission of IPv6 over MS/TP Networks", draft-ietf- "Transmission of IPv6 over MS/TP Networks", draft-ietf-
6lo-6lobac-03 (work in progress), October 2015. 6lo-6lobac-04 (work in progress), February 2016.
[I-D.ietf-6lo-btle] [I-D.ietf-6lo-btle]
Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., Nieminen, J., Savolainen, T., Isomaki, M., Patil, B.,
Shelby, Z., and C. Gomez, "IPv6 over BLUETOOTH(R) Low Shelby, Z., and C. Gomez, "IPv6 over BLUETOOTH(R) Low
Energy", draft-ietf-6lo-btle-17 (work in progress), August Energy", draft-ietf-6lo-btle-17 (work in progress), August
2015. 2015.
[I-D.ietf-6lo-dect-ule] [I-D.ietf-6lo-dect-ule]
Mariager, P., Petersen, J., Shelby, Z., Logt, M., and D. Mariager, P., Petersen, J., Shelby, Z., Logt, M., and D.
Barthel, "Transmission of IPv6 Packets over DECT Ultra Low Barthel, "Transmission of IPv6 Packets over DECT Ultra Low
Energy", draft-ietf-6lo-dect-ule-03 (work in progress), Energy", draft-ietf-6lo-dect-ule-04 (work in progress),
September 2015. February 2016.
[I-D.ietf-6lo-nfc] [I-D.ietf-6lo-nfc]
Youn, J. and Y. Hong, "Transmission of IPv6 Packets over Youn, J. and Y. Hong, "Transmission of IPv6 Packets over
Near Field Communication", draft-ietf-6lo-nfc-02 (work in Near Field Communication", draft-ietf-6lo-nfc-02 (work in
progress), October 2015. progress), October 2015.
[I-D.ietf-6tisch-architecture] [I-D.ietf-6tisch-architecture]
Thubert, P., "An Architecture for IPv6 over the TSCH mode Thubert, P., "An Architecture for IPv6 over the TSCH mode
of IEEE 802.15.4", draft-ietf-6tisch-architecture-09 (work of IEEE 802.15.4", draft-ietf-6tisch-architecture-09 (work
in progress), November 2015. in progress), November 2015.
[I-D.ietf-6tisch-terminology] [I-D.ietf-6tisch-terminology]
Palattella, M., Thubert, P., Watteyne, T., and Q. Wang, Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,
"Terminology in IPv6 over the TSCH mode of IEEE "Terminology in IPv6 over the TSCH mode of IEEE
802.15.4e", draft-ietf-6tisch-terminology-06 (work in 802.15.4e", draft-ietf-6tisch-terminology-06 (work in
progress), November 2015. progress), November 2015.
[I-D.ietf-bier-architecture] [I-D.ietf-bier-architecture]
Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and Wijnands, I., Rosen, E., Dolganow, A., P, T., and S.
S. Aldrin, "Multicast using Bit Index Explicit Aldrin, "Multicast using Bit Index Explicit Replication",
Replication", draft-ietf-bier-architecture-02 (work in draft-ietf-bier-architecture-03 (work in progress),
progress), July 2015. January 2016.
[I-D.ietf-ipv6-multilink-subnets] [I-D.ietf-ipv6-multilink-subnets]
Thaler, D. and C. Huitema, "Multi-link Subnet Support in Thaler, D. and C. Huitema, "Multi-link Subnet Support in
IPv6", draft-ietf-ipv6-multilink-subnets-00 (work in IPv6", draft-ietf-ipv6-multilink-subnets-00 (work in
progress), July 2002. progress), July 2002.
[I-D.ietf-roll-terminology] [I-D.ietf-roll-terminology]
Vasseur, J., "Terms used in Routing for Low power And Vasseur, J., "Terms used in Routing for Low power And
Lossy Networks", draft-ietf-roll-terminology-13 (work in Lossy Networks", draft-ietf-roll-terminology-13 (work in
progress), October 2013. progress), October 2013.
skipping to change at page 26, line 20 skipping to change at page 26, line 31
[I-D.popa-6lo-6loplc-ipv6-over-ieee19012-networks] [I-D.popa-6lo-6loplc-ipv6-over-ieee19012-networks]
Popa, D. and J. Hui, "6LoPLC: Transmission of IPv6 Packets Popa, D. and J. Hui, "6LoPLC: Transmission of IPv6 Packets
over IEEE 1901.2 Narrowband Powerline Communication over IEEE 1901.2 Narrowband Powerline Communication
Networks", draft-popa-6lo-6loplc-ipv6-over- Networks", draft-popa-6lo-6loplc-ipv6-over-
ieee19012-networks-00 (work in progress), March 2014. ieee19012-networks-00 (work in progress), March 2014.
[I-D.sarikaya-6lo-ap-nd] [I-D.sarikaya-6lo-ap-nd]
Sarikaya, B. and P. Thubert, "Address Protected Neighbor Sarikaya, B. and P. Thubert, "Address Protected Neighbor
Discovery for Low-power and Lossy Networks", draft- Discovery for Low-power and Lossy Networks", draft-
sarikaya-6lo-ap-nd-01 (work in progress), October 2015. sarikaya-6lo-ap-nd-02 (work in progress), March 2016.
[I-D.vyncke-6man-mcast-not-efficient] [I-D.vyncke-6man-mcast-not-efficient]
Vyncke, E., Thubert, P., Levy-Abegnoli, E., and A. Vyncke, E., Thubert, P., Levy-Abegnoli, E., and A.
Yourtchenko, "Why Network-Layer Multicast is Not Always Yourtchenko, "Why Network-Layer Multicast is Not Always
Efficient At Datalink Layer", draft-vyncke-6man-mcast-not- Efficient At Datalink Layer", draft-vyncke-6man-mcast-not-
efficient-01 (work in progress), February 2014. efficient-01 (work in progress), February 2014.
[I-D.yourtchenko-6man-dad-issues] [I-D.yourtchenko-6man-dad-issues]
Yourtchenko, A. and E. Nordmark, "A survey of issues Yourtchenko, A. and E. Nordmark, "A survey of issues
related to IPv6 Duplicate Address Detection", draft- related to IPv6 Duplicate Address Detection", draft-
 End of changes. 17 change blocks. 
34 lines changed or deleted 44 lines changed or added

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