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

Document Type Active Internet-Draft (6lo WG)
Last updated 2017-01-11
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                        January 11, 2017
Expires: July 15, 2017

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

Abstract

   This specification proposes an update to IPv6 Neighbor Discovery, to
   enhance the operation of IPv6 over wireless links that exhibit lossy
   multicast support, and enable a large degree of scalability by
   splitting the broadcast domains.  A higher speed backbone federates
   multiple wireless links to form a large MultiLink Subnet.  Backbone
   Routers acting as Layer-3 Access Point route packets to registered
   nodes, where an classical Layer-2 Access Point would bridge.
   Conversely, wireless nodes register or are proxy-registered to the
   Backbone Router to setup routing services in a fashion that is
   essentially similar to a classical Layer-2 association.

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 http://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 July 15, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Thubert                   Expires July 15, 2017                 [Page 1]
Internet-Draft            IPv6 Backbone Router              January 2017

   carefully, as they describe your rights and restrictions with respect
   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 . . . . . . . . . . . .   5
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Backbone Router Routing Operations  . . . . . . . . . . . . .  10
     5.1.  Over the Backbone Link  . . . . . . . . . . . . . . . . .  10
     5.2.  Over the LLN Link . . . . . . . . . . . . . . . . . . . .  12
   6.  BackBone Router Proxy Operations  . . . . . . . . . . . . . .  13
     6.1.  Registration and Binding State Creation . . . . . . . . .  16
     6.2.  Defending Addresses . . . . . . . . . . . . . . . . . . .  17
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   8.  Protocol Constants  . . . . . . . . . . . . . . . . . . . . .  18
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  19
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  19
     11.2.  Informative References . . . . . . . . . . . . . . . . .  20
     11.3.  External Informative References  . . . . . . . . . . . .  24
   Appendix A.  Requirements . . . . . . . . . . . . . . . . . . . .  24
     A.1.  Requirements Related to Mobility  . . . . . . . . . . . .  24
     A.2.  Requirements Related to Routing Protocols . . . . . . . .  25
     A.3.  Requirements Related to the Variety of Low-Power Link
           types . . . . . . . . . . . . . . . . . . . . . . . . . .  26
     A.4.  Requirements Related to Proxy Operations  . . . . . . . .  26
     A.5.  Requirements Related to Security  . . . . . . . . . . . .  27
     A.6.  Requirements Related to Scalability . . . . . . . . . . .  28
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  28

1.  Introduction

   Classical IPv6 Neighbor Discovery [RFC4862] operations are reactive
   and rely heavily on multicast operations to locate a correspondent.
   When this was designed, it was a natural match for the transparent
Show full document text