[manet] RFC 8703 on Dynamic Link Exchange Protocol (DLEP) Link Identifier Extension

rfc-editor@rfc-editor.org Wed, 12 February 2020 05:37 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C1C29120864; Tue, 11 Feb 2020 21:37:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id liYSQHodO53u; Tue, 11 Feb 2020 21:37:01 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5262F120844; Tue, 11 Feb 2020 21:37:01 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A35E9F406F7; Tue, 11 Feb 2020 21:36:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, manet@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200212053637.A35E9F406F7@rfc-editor.org>
Date: Tue, 11 Feb 2020 21:36:37 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/guvW4LIDqVHJ1U9G4XRFpLL8d9s>
Subject: [manet] =?utf-8?q?RFC_8703_on_Dynamic_Link_Exchange_Protocol_=28?= =?utf-8?q?DLEP=29_Link_Identifier_Extension?=
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2020 05:37:04 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8703

        Title:      Dynamic Link Exchange Protocol (DLEP) 
                    Link Identifier Extension 
        Author:     R. Taylor,
                    S. Ratliff
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    rick.taylor@airbus.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-manet-dlep-lid-extension-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8703

        DOI:        10.17487/RFC8703

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.

This document is a product of the Mobile Ad-hoc Networks Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC