First v3 RFC is published - RFC 8651 on Dynamic Link Exchange Protocol (DLEP) Control-Plane-Based Pause Extension

Heather Flanagan <rse@rfc-editor.org> Mon, 07 October 2019 20:00 UTC

Return-Path: <rse@rfc-editor.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51C49120154 for <ietf@ietfa.amsl.com>; Mon, 7 Oct 2019 13:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 zj3LGtHYMVei for <ietf@ietfa.amsl.com>; Mon, 7 Oct 2019 13:00:33 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF4AC12010C for <ietf@ietf.org>; Mon, 7 Oct 2019 13:00:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 1BAFF2033D5; Mon, 7 Oct 2019 12:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8QUAwKzTyslQ; Mon, 7 Oct 2019 12:59:22 -0700 (PDT)
Received: from [64.170.98.190] (unknown [64.170.98.190]) by c8a.amsl.com (Postfix) with ESMTPSA id CDA6C2033D4; Mon, 7 Oct 2019 12:59:22 -0700 (PDT)
From: Heather Flanagan <rse@rfc-editor.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8A06E775-9252-4011-AE9D-F546EBBAE188"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: First v3 RFC is published - RFC 8651 on Dynamic Link Exchange Protocol (DLEP) Control-Plane-Based Pause Extension
Date: Mon, 07 Oct 2019 13:00:25 -0700
References: <20191007195852.11BD7B800CB@rfc-editor.org>
Cc: RSOC <rsoc@iab.org>, Internet Architecture Board <iab@iab.org>
To: IETF discussion list <ietf@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
Message-Id: <EF2AB36B-F839-422F-AB3A-8D22F1A7FFDD@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RfRz0Cy-z6AjLS1mO8H5PT1V1FQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2019 20:00:36 -0000

Wow, everyone. We did it!

Thank you all for years and years of effort in getting us to this point. RFC 8651 is now the first RFC to be published in the v3 format.

As those of you on the xml2rfc list know, there are still heated discussions underway about some aspects of the XML vocabulary. Getting the -bis documents out to capture the reality of the v3 format is critically important. That is in the top 3 priorities for me as I wrap up my time as RSE (the other two are operational transition items and the RFC Model process discussion).

I particularly want to thank the RPC staff. They have worked incredibly hard to fill the roles of expert copyeditors, quality assurance engineers, and key stakeholders throughout the seven years (and counting) of the RFC format project. This is an amazing team. Thank you.

Heather Flanagan, RSE

> Begin forwarded message:
> 
> From: rfc-editor@rfc-editor.org
> Subject: RFC 8651 on Dynamic Link Exchange Protocol (DLEP) Control-Plane-Based Pause Extension
> Date: October 7, 2019 at 12:58:52 PM PDT
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, manet@ietf.org
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 8651
> 
>        Title:      Dynamic Link Exchange Protocol (DLEP) 
>                    Control-Plane-Based Pause Extension 
>        Author:     B. Cheng, 
>                    D. Wiggins,
>                    L. Berger, Ed.
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       October 2019
>        Mailbox:    bcheng@ll.mit.edu, 
>                    david.wiggins@ll.mit.edu, 
>                    lberger@labn.net
>        Pages:      12
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-ietf-manet-dlep-pause-extension-08.txt
> 
>        URL:        https://www.rfc-editor.org/info/rfc8651
> 
>        DOI:        10.17487/RFC8651
> 
> This document defines an extension to the Dynamic Link Exchange
> Protocol (DLEP) that enables a modem to use DLEP messages to pause
> and resume data traffic coming from its peer router.
> 
> 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
> 
>