Link Identifier Extension to DLEP
draft-dlep-lid-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Rick Taylor 
Last updated 2017-05-30
Replaces draft-taylor-manet-l3-dlep
Replaced by RFC 8703, RFC 8703
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)
Mobile Ad hoc Networks Working Group                           R. Taylor
Internet-Draft                                    Airbus Defence & Space
Intended status: Standards Track                            May 30, 2017
Expires: December 1, 2017

                   Link Identifier Extension to DLEP
                           draft-dlep-lid-00

Abstract

   There exists a class of modems that wish to support the Dynamic Link
   Exchange Protocol (DLEP) [I-D.ietf-manet-dlep] but do not present a
   single Layer 2 network domain as required by DLEP.  Such devices may
   be:

   o  Modems that maintain a varying link to some upstream backbone
      network infrastructure, where the ability to announce link state
      and DLEP metrics is desired, but the concept of a DLEP destination
      router for the backbone does not apply.  Examples of such devices
      can include LTE modems, IEEE 802.11 stations not in ad-hoc mode,
      and some satellite terminals.

   o  Modems that provide Layer 3 wide area network connectivity between
      devices, where individual DLEP destinations do exist, but are not
      directly reachable by MAC address.

   This document introduces an optional extension to the core DLEP
   specification, allowing DLEP to be used between routers and modems
   that operate in this way.

   Note:

   o  This document is intended as an extension to the core DLEP
      specification, and readers are expected to be fully conversant
      with the operation of core DLEP.

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/.

Taylor                  Expires December 1, 2017                [Page 1]
Internet-Draft      Link Identifier Extension to DLEP           May 2017

   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 December 1, 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
   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
     1.1.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Identifier Restrictions . . . . . . . . . . . . . . . . .   4
     2.2.  Link Identifier Data Item . . . . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  DLEP Link Identifier Flag . . . . . . . . . . . . . . . .   5
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Dynamic Link Exchange Protocol (DLEP) [I-D.ietf-manet-dlep]
   describes a protocol for modems to advertise the status of wireless
   links between reachable destinations to attached routers.  The core
   specification of the protocol assumes that every modem in the radio
   network has an attached DLEP router, and the MAC address of the DLEP
   interface on the router is used to identify the destination in the
   network for purposes of reporting the state and quality of the link
   to that destination.

Taylor                  Expires December 1, 2017                [Page 2]
Internet-Draft      Link Identifier Extension to DLEP           May 2017

   This document describes a DLEP Extension allowing modems that do not
   meet the strict requirement that DLEP must be implemented on a single
   Layer 2 domain to use DLEP to describe link state and quality to one
   or more destinations reachable only at Layer 3.

   To enable routers to take advantage of the DLEP protocol this
Show full document text