rfc8929v5.txt   rfc8929.txt 
skipping to change at line 242 skipping to change at line 242
enables the MLSN operation over federated links that may not be enables the MLSN operation over federated links that may not be
compatible for bridging. The Routing Proxy advertises its own compatible for bridging. The Routing Proxy advertises its own
link-layer address as the Target Link-Layer Address (TLLA) in the link-layer address as the Target Link-Layer Address (TLLA) in the
proxied Neighbor Advertisements (NAs) over the backbone and routes proxied Neighbor Advertisements (NAs) over the backbone and routes
at the network layer between the federated links. at the network layer between the federated links.
Bridging Proxy: A Bridging Proxy provides IPv6 ND proxy functions Bridging Proxy: A Bridging Proxy provides IPv6 ND proxy functions
while preserving forwarding continuity at the link layer. In that while preserving forwarding continuity at the link layer. In that
case, the link-layer address and the mobility of the Registering case, the link-layer address and the mobility of the Registering
Node is visible across the bridged backbone. The Bridging Proxy Node is visible across the bridged backbone. The Bridging Proxy
advertises the link-layer address of the Registering Node as the advertises the link-layer address of the Registering Node in the
TLLA in the proxied NAs over the backbone, and it proxies ND for TLLAO in the proxied NAs over the backbone, and it proxies ND for
all unicast addresses including link-local addresses. Instead of all unicast addresses including link-local addresses. Instead of
replying on behalf of the Registering Node, a Bridging Proxy will replying on behalf of the Registering Node, a Bridging Proxy will
preferably forward the NS(Lookup) and Neighbor Unreachability preferably forward the NS(Lookup) and Neighbor Unreachability
Detection (NUD) messages that target the Registered Address to the Detection (NUD) messages that target the Registered Address to the
Registering Node as unicast frames, so it can respond in its own. Registering Node as unicast frames, so it can respond in its own.
Binding Table: The Binding Table is an abstract database that is Binding Table: The Binding Table is an abstract database that is
maintained by the 6BBR to store the state associated with its maintained by the 6BBR to store the state associated with its
registrations. registrations.
skipping to change at line 980 skipping to change at line 980
To achieve this, the Bridging Proxy intercepts the IPv6 ND messages To achieve this, the Bridging Proxy intercepts the IPv6 ND messages
and may reinject them on the other side, respond directly, or drop and may reinject them on the other side, respond directly, or drop
them. For instance, an NS(Lookup) from the backbone that matches a them. For instance, an NS(Lookup) from the backbone that matches a
Binding can be responded to directly or turned into a unicast on the Binding can be responded to directly or turned into a unicast on the
LLN side to let the 6LN respond. LLN side to let the 6LN respond.
As a Bridging Proxy, the 6BBR MUST use the Registering Node's Layer 2 As a Bridging Proxy, the 6BBR MUST use the Registering Node's Layer 2
address in the SLLAO of the NS/RS messages and the TLLAO of the NA address in the SLLAO of the NS/RS messages and the TLLAO of the NA
messages that it generates to advertise the Registered Addresses. messages that it generates to advertise the Registered Addresses.
The Registering Node's Layer 2 address is found in the SLLA of the The Registering Node's Layer 2 address is found in the SLLAO of the
registration NS(EARO) and maintained in the Binding Table. registration NS(EARO) and maintained in the Binding Table.
The MLSN prefix SHOULD NOT be advertised as on-link in RA messages The MLSN prefix SHOULD NOT be advertised as on-link in RA messages
sent towards the LLN. If a destination address is seen as on-link, sent towards the LLN. If a destination address is seen as on-link,
then a 6LN may use NS(Lookup) messages to resolve that address. In then a 6LN may use NS(Lookup) messages to resolve that address. In
that case, the 6BBR MUST either answer the NS(Lookup) message that case, the 6BBR MUST either answer the NS(Lookup) message
directly or reinject the message on the backbone, as either a Layer 2 directly or reinject the message on the backbone, as either a Layer 2
unicast or a multicast. unicast or a multicast.
If the Registering Node owns the Registered Address, meaning that the If the Registering Node owns the Registered Address, meaning that the
skipping to change at line 1620 skipping to change at line 1620
[RS-REFRESH] [RS-REFRESH]
Nordmark, E., Yourtchenko, A., and S. Krishnan, "IPv6 Nordmark, E., Yourtchenko, A., and S. Krishnan, "IPv6
Neighbor Discovery Optional RS/RA Refresh", Work in Neighbor Discovery Optional RS/RA Refresh", Work in
Progress, Internet-Draft, draft-ietf-6man-rs-refresh-02, Progress, Internet-Draft, draft-ietf-6man-rs-refresh-02,
31 October 2016, <https://tools.ietf.org/html/draft-ietf- 31 October 2016, <https://tools.ietf.org/html/draft-ietf-
6man-rs-refresh-02>. 6man-rs-refresh-02>.
[SAVI-WLAN] [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", Work in Progress, Internet-Draft, draft-bi-savi- WLAN", Work in Progress, Internet-Draft, draft-bi-savi-
wlan-19, 14 May 2020, wlan-20, 14 November 2020,
<https://tools.ietf.org/html/draft-bi-savi-wlan-19>. <https://tools.ietf.org/html/draft-bi-savi-wlan-20>.
[UNICAST-LOOKUP] [UNICAST-LOOKUP]
Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery
Unicast Lookup", Work in Progress, Internet-Draft, draft- Unicast Lookup", Work in Progress, Internet-Draft, draft-
thubert-6lo-unicast-lookup-00, 25 January 2019, thubert-6lo-unicast-lookup-00, 25 January 2019,
<https://tools.ietf.org/html/draft-thubert-6lo-unicast- <https://tools.ietf.org/html/draft-thubert-6lo-unicast-
lookup-00>. lookup-00>.
Appendix A. Possible Future Extensions Appendix A. Possible Future Extensions
skipping to change at line 1734 skipping to change at line 1734
[MCAST-PROBLEMS]. Although hosts can connect to the backbone using [MCAST-PROBLEMS]. Although hosts can connect to the backbone using
IPv6 ND operations, multicast RAs can be saved by using [RS-REFRESH], IPv6 ND operations, multicast RAs can be saved by using [RS-REFRESH],
which also requires the support of [RFC7559]. which also requires the support of [RFC7559].
Acknowledgments Acknowledgments
Many thanks to Dorothy Stanley, Thomas Watteyne, and Jerome Henry for Many thanks to Dorothy Stanley, Thomas Watteyne, and Jerome Henry for
their various contributions. Also, many thanks to Timothy Winters their various contributions. Also, many thanks to Timothy Winters
and Erik Nordmark for their help, review, and support in preparation and Erik Nordmark for their help, review, and support in preparation
for the IESG cycle and to Kyle Rose, Elwyn Davies, Barry Leiba, Mirja for the IESG cycle and to Kyle Rose, Elwyn Davies, Barry Leiba, Mirja
Kuehlewind, Alvaro Retana, Roman Danyliw, and especially Dominique KΓΌhlewind, Alvaro Retana, Roman Danyliw, and especially Dominique
Barthel and Benjamin Kaduk for their useful contributions through the Barthel and Benjamin Kaduk for their useful contributions through the
IETF Last Call and IESG process. IETF Last Call and IESG process.
Authors' Addresses Authors' Addresses
Pascal Thubert (editor) Pascal Thubert (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Building D Building D
45 Allee des Ormes - BP1200 45 Allee des Ormes - BP1200
06254 MOUGINS - Sophia Antipolis 06254 MOUGINS - Sophia Antipolis
 End of changes. 4 change blocks. 
6 lines changed or deleted 6 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/