draft-ietf-6lo-backbone-router-11.txt   draft-ietf-6lo-backbone-router-12.txt 
6lo P. Thubert, Ed. 6lo P. Thubert, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 6775, 8505 (if approved) C. Perkins Updates: 6775, 8505 (if approved) C. Perkins
Intended status: Standards Track Futurewei Intended status: Standards Track Futurewei
Expires: August 8, 2019 E. Levy-Abegnoli Expires: March 5, 2020 E. Levy-Abegnoli
Cisco Systems Cisco Systems
February 4, 2019 September 2, 2019
IPv6 Backbone Router IPv6 Backbone Router
draft-ietf-6lo-backbone-router-11 draft-ietf-6lo-backbone-router-12
Abstract Abstract
This document updates RFC 4861 and RFC 8505 in order to enable proxy This document updates RFC 6775 and RFC 8505 in order to enable proxy
services for IPv6 Neighbor Discovery by Routing Registrars called services for IPv6 Neighbor Discovery by Routing Registrars called
Backbone Routers. Backbone Routers are placed along the wireless Backbone Routers. Backbone Routers are placed along the wireless
edge of a Backbone, and federate multiple wireless links to form a edge of a Backbone, and federate multiple wireless links to form a
single MultiLink Subnet. single MultiLink Subnet.
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 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 August 8, 2019. This Internet-Draft will expire on March 5, 2020.
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 2, line 14 skipping to change at page 2, line 14
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. New Terms . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. New Terms . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Acronym Definitions . . . . . . . . . . . . . . . . . . . 6 2.3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 6
2.4. References . . . . . . . . . . . . . . . . . . . . . . . 7 2.4. References . . . . . . . . . . . . . . . . . . . . . . . 7
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Updating RFC 6775 and RFC 8505 . . . . . . . . . . . . . 9 3.1. Updating RFC 6775 and RFC 8505 . . . . . . . . . . . . . 9
3.2. Access Link . . . . . . . . . . . . . . . . . . . . . . . 10 3.2. Access Link . . . . . . . . . . . . . . . . . . . . . . . 10
3.3. Route-Over Mesh . . . . . . . . . . . . . . . . . . . . . 11 3.3. Route-Over Mesh . . . . . . . . . . . . . . . . . . . . . 11
3.4. The Binding Table . . . . . . . . . . . . . . . . . . . . 12 3.4. The Binding Table . . . . . . . . . . . . . . . . . . . . 12
3.5. Primary and Secondary 6BBRs . . . . . . . . . . . . . . . 13 3.5. Primary and Secondary 6BBRs . . . . . . . . . . . . . . . 13
3.6. Using Optimistic DAD . . . . . . . . . . . . . . . . . . 14 3.6. Using Optimistic DAD . . . . . . . . . . . . . . . . . . 14
4. MultiLink Subnet Considerations . . . . . . . . . . . . . . . 14 4. MultiLink Subnet Considerations . . . . . . . . . . . . . . . 14
5. Optional 6LBR serving the MultiLink Subnet . . . . . . . . . 15 5. Optional 6LBR serving the MultiLink Subnet . . . . . . . . . 15
skipping to change at page 4, line 17 skipping to change at page 4, line 17
broadcast domains and routes between subnets, or even by assigning a broadcast domains and routes between subnets, or even by assigning a
/64 prefix to each wireless node (see [RFC8273]). /64 prefix to each wireless node (see [RFC8273]).
Another way is to proxy at the boundary of the wired and wireless Another way is to proxy at the boundary of the wired and wireless
domains the Layer-3 protocols that rely on MAC Layer broadcast domains the Layer-3 protocols that rely on MAC Layer broadcast
operations. For instance, IEEE 802.11 [IEEEstd80211] situates proxy- operations. For instance, IEEE 802.11 [IEEEstd80211] situates proxy-
ARP (IPv4) and proxy-ND (IPv6) functions at the Access Points (APs). ARP (IPv4) and proxy-ND (IPv6) functions at the Access Points (APs).
The 6BBR provides a proxy-ND function and can be extended for proxy- The 6BBR provides a proxy-ND function and can be extended for proxy-
ARP in a continuation specification. ARP in a continuation specification.
IPv6 proxy-ND services can be obtained by snooping the IPV6 ND Knowledge of which address to proxy for can be obtained by snooping
protocol (see [I-D.bi-savi-wlan]). Proprietary techniques for IPv6 the IPV6 ND protocol (see [I-D.bi-savi-wlan]), but it has been found
ND and DHCP snooping have been used; although snooping does eliminate to be unreliable. An IPv6 address may not be discovered immediately
undesirable broadcast transmissions, it has been found to be due to a packet loss, or if a "silent" node is not currently using
unreliable. An IPv6 address may not be discovered immediately due to one of its addresses. A change of state (e.g. due to movement) may
a packet loss, or if a "silent" node is not currently using one of be missed or misordered, leading to unreliable connectivity and
its addresses. A change of state (e.g. due to movement) may be
missed or misordered, leading to unreliable connectivity and
incomplete knowledge of the state of the network. incomplete knowledge of the state of the network.
This specification defines the 6BBR as a Routing Registrar [RFC8505] This specification defines the 6BBR as a Routing Registrar [RFC8505]
that provide proxy services for IPv6 Neighbor Discovery. Backbone that provide proxy services for IPv6 Neighbor Discovery. Backbone
Routers federate multiple LLNs over a Backbone Link to form a Routers federate multiple LLNs over a Backbone Link to form a
MultiLink Subnet (MLSN). Backbone Routers placed along the LLN edge MultiLink Subnet (MLSN). Backbone Routers placed along the LLN edge
of the Backbone handle IPv6 Neighbor Discovery, and forward packets of the Backbone handle IPv6 Neighbor Discovery, and forward packets
on behalf of registered nodes. on behalf of registered nodes.
An LLN node (6LN) registers all its IPv6 Addresses using an NS(EARO) An LLN node (6LN) registers all its IPv6 Addresses using an NS(EARO)
skipping to change at page 6, line 5 skipping to change at page 6, line 5
Binding Table Binding Table
The Binding Table is an abstract database that is maintained by The Binding Table is an abstract database that is maintained by
the 6BBR to store the state associated with its registrations. the 6BBR to store the state associated with its registrations.
Binding Binding
A Binding is an abstract state associated to one registration, A Binding is an abstract state associated to one registration,
in other words one entry in the Binding Table. in other words one entry in the Binding Table.
2.3. Acronym Definitions 2.3. Abbreviations
This document uses the following acronyms: This document uses the following abbreviations:
6BBR: 6LoWPAN Backbone Router 6BBR: 6LoWPAN Backbone Router
6LBR: 6LoWPAN Border Router 6LBR: 6LoWPAN Border Router
6LN: 6LoWPAN Node 6LN: 6LoWPAN Node
6LR: 6LoWPAN Router 6LR: 6LoWPAN Router
6CIO: Capability Indication Option 6CIO: Capability Indication Option
skipping to change at page 11, line 5 skipping to change at page 11, line 5
3.2. Access Link 3.2. Access Link
Figure 2 illustrates a flow where 6LN forms an IPv6 Address and Figure 2 illustrates a flow where 6LN forms an IPv6 Address and
registers it to a 6BBR acting as a 6LR [RFC8505]. The 6BBRs applies registers it to a 6BBR acting as a 6LR [RFC8505]. The 6BBRs applies
ODAD (see Section 3.6) to the registered address to enable ODAD (see Section 3.6) to the registered address to enable
connectivity while the message flow is still in progress. In that connectivity while the message flow is still in progress. In that
example, a 6LBR is deployed on the backbone link to serve the whole example, a 6LBR is deployed on the backbone link to serve the whole
subnet, and EDAR / EDAC messages are used in combination with DAD to subnet, and EDAR / EDAC messages are used in combination with DAD to
enable coexistence with IPv6 ND over the backbone. enable coexistence with IPv6 ND over the backbone.
6LN(STA) 6BBR(AP) 6LBR default GW 6LN(STA) 6BBR(AP) 6LBR default GW
| | | | | | | |
| LLN Access Link | IPv6 Backbone (e.g., Ethernet) | | LLN Access Link | IPv6 Backbone (e.g., Ethernet) |
| | | | | | | |
| RS(multicast) | | | | RS(multicast) | | |
|---------------->| | | |---------------->| | |
| RA(PIO, Unicast)| | | | RA(PIO, Unicast)| | |
|<----------------| | | |<----------------| | |
| NS(EARO) | | | | NS(EARO) | | |
|---------------->| | | |---------------->| | |
| | Extended DAR | | | | Extended DAR | |
| |--------------->| | | |--------------->| |
| | Extended DAC | | | | Extended DAC | |
| |<---------------| | | |<---------------| |
| | | | | |
| | NS-DAD(EARO, multicast) | | | NS-DAD(EARO, multicast) |
| |--------> | | |--------> |
| |-------------------------------->| | |----------------------------------->|
| | | | | |
| | RS(no SLLAO, for ODAD) | | | RS(no SLLAO, for ODAD) |
| |-------------------------------->| | |----------------------------------->|
| | (if no fresher Binding) NS(Lookup) | | | if (no fresher Binding) NS(Lookup) |
| | <-------------| | | <----------------|
| |<--------------------------------| | |<-----------------------------------|
| | NA(SLLAO, not(O), EARO) | | | NA(SLLAO, not(O), EARO) |
| |-------------------------------->| | |----------------------------------->|
| | RA(unicast) | | | RA(unicast) |
| |<--------------------------------| | |<-----------------------------------|
| | | | | |
| IPv6 Packets in optimistic mode | | IPv6 Packets in optimistic mode |
|<------------------------------------------------->| |<---------------------------------------------------->|
| | | | | |
| | | |
| NA(EARO) |<DAD timeout> | NA(EARO) |<DAD timeout>
|<----------------| |<----------------|
| | | |
Figure 2: Initial Registration Flow to a 6BBR acting as Routing Proxy Figure 2: Initial Registration Flow to a 6BBR acting as Routing Proxy
3.3. Route-Over Mesh 3.3. Route-Over Mesh
Figure 3 illustrates IPv6 signaling that enables a 6LN to form a Figure 3 illustrates IPv6 signaling that enables a 6LN to form a
skipping to change at page 25, line 34 skipping to change at page 25, line 34
[RFC8505] Thubert, P., Ed., Nordmark, E., Chakrabarti, S., and C. [RFC8505] Thubert, P., Ed., Nordmark, E., Chakrabarti, S., and C.
Perkins, "Registration Extensions for IPv6 over Low-Power Perkins, "Registration Extensions for IPv6 over Low-Power
Wireless Personal Area Network (6LoWPAN) Neighbor Wireless Personal Area Network (6LoWPAN) Neighbor
Discovery", RFC 8505, DOI 10.17487/RFC8505, November 2018, Discovery", RFC 8505, DOI 10.17487/RFC8505, November 2018,
<https://www.rfc-editor.org/info/rfc8505>. <https://www.rfc-editor.org/info/rfc8505>.
15.2. Informative References 15.2. Informative References
[I-D.bi-savi-wlan] [I-D.bi-savi-wlan]
Bi, J., Wu, J., Wang, Y., and T. Lin, "A SAVI Solution for Bi, J., Wu, J., Wang, Y., and T. Lin, "A SAVI Solution for
WLAN", draft-bi-savi-wlan-16 (work in progress), November WLAN", draft-bi-savi-wlan-17 (work in progress), May 2019.
2018.
[I-D.ietf-6lo-ap-nd] [I-D.ietf-6lo-ap-nd]
Thubert, P., Sethi, M., Struik, R., and B. Sarikaya, Thubert, P., Sarikaya, B., Sethi, M., and R. Struik,
"Address Protected Neighbor Discovery for Low-power and "Address Protected Neighbor Discovery for Low-power and
Lossy Networks", draft-ietf-6lo-ap-nd-09 (work in Lossy Networks", draft-ietf-6lo-ap-nd-12 (work in
progress), December 2018. progress), April 2019.
[I-D.ietf-6man-rs-refresh] [I-D.ietf-6man-rs-refresh]
Nordmark, E., Yourtchenko, A., and S. Krishnan, "IPv6 Nordmark, E., Yourtchenko, A., and S. Krishnan, "IPv6
Neighbor Discovery Optional RS/RA Refresh", draft-ietf- Neighbor Discovery Optional RS/RA Refresh", draft-ietf-
6man-rs-refresh-02 (work in progress), October 2016. 6man-rs-refresh-02 (work in progress), October 2016.
[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-19 (work of IEEE 802.15.4", draft-ietf-6tisch-architecture-26 (work
in progress), December 2018. in progress), August 2019.
[I-D.ietf-mboned-ieee802-mcast-problems] [I-D.ietf-mboned-ieee802-mcast-problems]
Perkins, C., McBride, M., Stanley, D., Kumari, W., and J. Perkins, C., McBride, M., Stanley, D., Kumari, W., and J.
Zuniga, "Multicast Considerations over IEEE 802 Wireless Zuniga, "Multicast Considerations over IEEE 802 Wireless
Media", draft-ietf-mboned-ieee802-mcast-problems-04 (work Media", draft-ietf-mboned-ieee802-mcast-problems-08 (work
in progress), November 2018. in progress), August 2019.
[I-D.nordmark-6man-dad-approaches] [I-D.nordmark-6man-dad-approaches]
Nordmark, E., "Possible approaches to make DAD more robust Nordmark, E., "Possible approaches to make DAD more robust
and/or efficient", draft-nordmark-6man-dad-approaches-02 and/or efficient", draft-nordmark-6man-dad-approaches-02
(work in progress), October 2015. (work in progress), October 2015.
[I-D.thubert-6lo-unicast-lookup] [I-D.thubert-6lo-unicast-lookup]
Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery
Unicast Lookup", draft-thubert-6lo-unicast-lookup-00 (work Unicast Lookup", draft-thubert-6lo-unicast-lookup-00 (work
in progress), January 2019. in progress), January 2019.
 End of changes. 15 change blocks. 
57 lines changed or deleted 54 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/