IPv6 over Link-Local Discovery Protocol
draft-richardson-anima-ipv6-lldp-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Michael Richardson 
Last updated 2019-12-05 (latest revision 2019-12-04)
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
anima Working Group                                        M. Richardson
Internet-Draft                                  Sandelman Software Works
Intended status: Standards Track                       December 05, 2019
Expires: June 7, 2020

                IPv6 over Link-Local Discovery Protocol
                  draft-richardson-anima-ipv6-lldp-01

Abstract

   This document describes an encapsulaton of IPv6 packets using Link-
   Layer Discovery Protocol (LLDP).

   LLDP has the desireable property over standard ethernet encapsulation
   that it does not propogate through layer-switching fabric.  This
   makes creation of the autonomic control plane easier.

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 June 7, 2020.

Copyright Notice

   Copyright (c) 2019 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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Richardson                Expires June 7, 2020                  [Page 1]
Internet-Draft                   v6-LLDP                   December 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  LLDP Encapsulation  . . . . . . . . . . . . . . . . . . .   3
     2.2.  Content of Payload - option 1 - entire IPv6 packet  . . .   4
     2.3.  Content of Payload - option 2 - elided IPv6 packet  . . .   4
     2.4.  Content of Payload - option 3 - RFC8138 compressed packet   5
   3.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The IEEE802.1AB Link Layer Discovery Protocol (LLDP) is a one-hop,
   vendor-neutral link-layer protocol used by end host network Things
   for advertising their identity, capabilities, and neighbors on an
   IEEE 802 local area network.

   Its Type-Length-Value (TLV) design allows for "vendor-specific"
   extensions to be defined.  IANA has a registered IEEE 802
   organizationally unique identifier (OUI) defined as documented in
   [RFC7042].

   The creation and maintenance of the Autonomic Control Plane described
   in [I-D.ietf-anima-autonomic-control-plane] requires creation of hop-
   by-hop discovery of adjacent systems.  There are Campus L2 systems
   that are not broadcast safe until they have been connected to their
   Software Defined Networking (SDN) controller.  The use of the stable
   connectivity provided by [RFC8368] can provide the SDN connectivity
   required.

   There is a bootstrap problem: the network may be unsafe for ACP
   discovery broadcasts until configured, and it can not be
   autonomically configured until the ACP discovery (and onboarding
   process) is done.

Richardson                Expires June 7, 2020                  [Page 2]
Internet-Draft                   v6-LLDP                   December 2019

   LLDP provides an out, as it is never broadcast, and it discovers all
   compliant layer-2 devices in a network, even if they do not normally
   do layer-3 forwarding.

   Additional LLDP has the advantage that received LLDP frames are
   already configured in routing fabrics to be send up to the control
Show full document text