IPv6 Backbone Router
draft-ietf-6lo-backbone-router-07

Document Type Active Internet-Draft (6lo WG)
Last updated 2018-09-03
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd Samita Chakrabarti
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Samita Chakrabarti" <samitac.ietf@gmail.com>
6lo                                                      P. Thubert, Ed.
Internet-Draft                                                     cisco
Intended status: Standards Track                              C. Perkins
Expires: March 7, 2019                                         Futurewei
                                                       September 3, 2018

                          IPv6 Backbone Router
                   draft-ietf-6lo-backbone-router-07

Abstract

   Backbone Routers placed at the wireless edge of a backbone link
   interconnect multiple wireless links at Layer-3 to form a large
   MultiLink Subnet, so that the broadcast domain of the backbone does
   not extend to the wireless links.  Wireless nodes register or are
   proxy-registered to a Backbone Router to establish IPv6 Neighbor
   Discovery proxy services, and the Backbone Router takes care of the
   ND operation on behalf of registered nodes and ensures and routes
   towards the registered addresses over the wireless interface.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 7, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Thubert & Perkins         Expires March 7, 2019                 [Page 1]
Internet-Draft            IPv6 Backbone Router            September 2018

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Applicability and Requirements Served . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Backbone Router Routing Operations  . . . . . . . . . . . . .   8
     5.1.  Over the Backbone Link  . . . . . . . . . . . . . . . . .   9
     5.2.  Over the LLN Link . . . . . . . . . . . . . . . . . . . .  10
   6.  Backbone Router Proxy Operations  . . . . . . . . . . . . . .  11
     6.1.  Registration and Binding State Creation . . . . . . . . .  14
     6.2.  Defending Addresses . . . . . . . . . . . . . . . . . . .  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   8.  Protocol Constants  . . . . . . . . . . . . . . . . . . . . .  16
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  17
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  17
     11.2.  Informative References . . . . . . . . . . . . . . . . .  18
     11.3.  External Informative References  . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   One of the key services provided by IEEE STD. 802.1 [IEEEstd8021]
   Ethernet Bridging is an efficient and reliable broadcast service, and
   multiple applications and protocols have been built that heavily
   depend on that feature for their core operation.  Unfortunately, a
   wide range of wireless networks do not provide economical broadcast
   capabilities of Ethernet Bridging; protocols designed for bridged
   networks that rely on broadcast often exhibit disappointing
   behaviours when applied unmodified to a wireless medium.

   Wi-Fi [IEEEstd80211] Access Points (APs) deployed in an Extended
   Service Set (ESS) act as bridges.  However, in order to ensure a
   solid connectivity to the devices and protect the medium against
   harmful broadcasts, they refrain from relying on broadcast-intensive
   protocols such as Transparent Bridging on the wireless side.
   Instead, an association process is used to register proactively the
   MAC addresses of the wireless device (STA) to the AP.  Then, the APs
Show full document text