Dynamic Link Exchange Protocol (DLEP) Link Identifier Extension
RFC 8703

Document Type RFC - Proposed Standard (February 2020; No errata)
Last updated 2020-02-11
Replaces draft-dlep-lid
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Justin Dean
Shepherd write-up Show (last changed 2018-08-22)
IESG IESG state RFC 8703 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to Justin Dean <bebemaster@gmail.com>, aretana.ietf@gmail.com
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack


Internet Engineering Task Force (IETF)                         R. Taylor
Request for Comments: 8703                        Airbus Defence & Space
Category: Standards Track                                     S. Ratliff
ISSN: 2070-1721                                            February 2020

    Dynamic Link Exchange Protocol (DLEP) Link Identifier Extension

Abstract

   The Dynamic Link Exchange Protocol (DLEP) is a protocol for modems to
   advertise the status of wireless links between reachable destinations
   to attached routers.  The core specification of the protocol (RFC
   8175) assumes that every modem in the radio network has an attached
   DLEP router and requires that the Media Access Control (MAC) address
   of the DLEP interface on the attached router be used to identify the
   destination in the network, for purposes of reporting the state and
   quality of the link to that destination.

   This document describes a DLEP extension that allows modems that do
   not meet the strict requirement above to use DLEP to describe link
   availability and quality to one or more destinations reachable beyond
   a device on the Layer 2 domain.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8703.

Copyright Notice

   Copyright (c) 2020 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
     1.1.  Terminology
     1.2.  Applicability
     1.3.  Requirements Language
   2.  Operation
     2.1.  Identifier Restrictions
     2.2.  Negotiation
   3.  New Data Items
     3.1.  Link Identifier Length Data Item
     3.2.  Link Identifier Data Item
   4.  Security Considerations
   5.  IANA Considerations
   6.  References
     6.1.  Normative References
     6.2.  Informative References
   Authors' Addresses

1.  Introduction

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

   This document describes a DLEP extension that allows modems that do
   not meet the strict requirement above to use DLEP to describe link
   availability and quality to one or more destinations reachable beyond
   a device on the Layer 2 domain.

   As with core DLEP [RFC8175], a router can use this knowledge to
   influence any routing or flow-control decisions regarding traffic to
   this destination, understanding that such traffic flows via Layer 3.

1.1.  Terminology

   Local Layer 2 domain:  The Layer 2 domain that links the router and
      modem participants of the current DLEP session.

   Layer 3 DLEP Destination:  A DLEP Destination that is not directly
      addressable within the local Layer 2 domain but is reachable via a
      node addressable within the local Layer 2 domain.

   Gateway Node:  The last device with a MAC address reachable in the
      local Layer 2 domain on the path from the DLEP router participant
      towards the Layer 3 DLEP Destination.  This device is commonly the
      DLEP peer modem but could be another DLEP Destination in the Layer
      2 domain.

1.2.  Applicability

   This extension was designed primarily to address the following use
   cases:

   1.  A radio system that does not operate in Layer 2 bridge mode but
       instead provides Layer 3 connectivity between destinations, often
       using its own embedded Layer 3 routing function.

   2.  A point-to-multipoint tunnel system, such as a software-defined
       wide-area network (SD-WAN) deployment, where the tunnel provider
Show full document text