RFC 8629 on Dynamic Link Exchange Protocol (DLEP) Multi-Hop Forwarding Extension

rfc-editor@rfc-editor.org Tue, 23 July 2019 15:32 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94F0D12016D; Tue, 23 Jul 2019 08:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NwVJel4x9hoW; Tue, 23 Jul 2019 08:32:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFB1112040A; Tue, 23 Jul 2019 08:32:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9D159B80430; Tue, 23 Jul 2019 08:31:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg2Mjkgb24gRHluYW1pYyBMaW5rIEV4Y2hhbmdlIFByb3RvY29sIChETEVQKSBNdWx0aS1Ib3AgRm9yd2FyZGluZyBFeHRlbnNpb24=?=
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: <20190723153153.9D159B80430@rfc-editor.org>
Date: Tue, 23 Jul 2019 08:31:53 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nu3kcE25rfTbWqv7l2hEbHqJZL0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2019 15:32:15 -0000

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

        
        RFC 8629

        Title:      Dynamic Link Exchange Protocol (DLEP) 
                    Multi-Hop Forwarding Extension 
        Author:     B. Cheng,
                    L. Berger, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2019
        Mailbox:    bcheng@ll.mit.edu, 
                    lberger@labn.net
        Pages:      10
        Characters: 23138
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-manet-dlep-multi-hop-extension-07.txt

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

        DOI:        10.17487/RFC8629

This document defines an extension to the Dynamic Link Exchange
Protocol (DLEP) that enables the reporting and control of multi-hop
forwarding by DLEP-capable modems.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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