DLEP Link Identifier Extension
draft-ietf-manet-dlep-lid-extension-06

Document Type Active Internet-Draft (manet WG)
Last updated 2019-09-26 (latest revision 2019-09-10)
Replaces draft-dlep-lid
Stream IETF
Intended RFC status Proposed Standard
Formats plain text 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 Ed Queue
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
RFC Editor RFC Editor state EDIT
Mobile Ad hoc Networks Working Group                           R. Taylor
Internet-Draft                                    Airbus Defence & Space
Intended status: Standards Track                              S. Ratliff
Expires: March 13, 2020                                       VT iDirect
                                                      September 10, 2019

                     DLEP Link Identifier Extension
                 draft-ietf-manet-dlep-lid-extension-06

Abstract

   The Dynamic Link Exchange Protocol, RFC 8175, 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 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 allowing 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 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 March 13, 2020.

Taylor & Ratliff         Expires March 13, 2020                 [Page 1]
Internet-Draft       DLEP Link Identifier Extension       September 2019

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
   (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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Applicability . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Identifier Restrictions . . . . . . . . . . . . . . . . .   5
     2.2.  Negotiation . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  New Data Items  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Link Identifier Length Data Item  . . . . . . . . . . . .   6
     3.2.  Link Identifier Data Item . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The Dynamic Link Exchange Protocol (DLEP), RFC 8175, 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 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 allowing 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.

Taylor & Ratliff         Expires March 13, 2020                 [Page 2]
Internet-Draft       DLEP Link Identifier Extension       September 2019

   As with core DLEP, 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.
Show full document text