[manet] RFC 9894 on Dynamic Link Exchange Protocol (DLEP) Diffserv Aware Credit Window Extension
rfc-editor@rfc-editor.org Sat, 31 January 2026 22:07 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 29F35B00973A; Sat, 31 Jan 2026 14:07:20 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 21B2DC000CC4; Sat, 31 Jan 2026 14:07:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260131220720.21B2DC000CC4@rfcpa.rfc-editor.org>
Date: Sat, 31 Jan 2026 14:07:20 -0800
Message-ID-Hash: XSUGQNL42KO3S5YVWHGKWRH4U36WAH5Q
X-Message-ID-Hash: XSUGQNL42KO3S5YVWHGKWRH4U36WAH5Q
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-manet.ietf.org-0; header-match-manet.ietf.org-1; header-match-manet.ietf.org-2; header-match-manet.ietf.org-3; header-match-manet.ietf.org-4; header-match-manet.ietf.org-5; header-match-manet.ietf.org-6; header-match-manet.ietf.org-7; header-match-manet.ietf.org-8; header-match-manet.ietf.org-9; header-match-manet.ietf.org-10; header-match-manet.ietf.org-11; header-match-manet.ietf.org-12; header-match-manet.ietf.org-13; header-match-manet.ietf.org-14; header-match-manet.ietf.org-15; header-match-manet.ietf.org-16; header-match-manet.ietf.org-17; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, manet@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [manet] RFC 9894 on Dynamic Link Exchange Protocol (DLEP) Diffserv Aware Credit Window Extension
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/DN3sTFBfxVFkm3hFpePU5uxI1n0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Owner: <mailto:manet-owner@ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Subscribe: <mailto:manet-join@ietf.org>
List-Unsubscribe: <mailto:manet-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9894
Title: Dynamic Link Exchange Protocol (DLEP)
Diffserv Aware Credit Window Extension
Author: B. Cheng,
D. Wiggins,
L. Berger,
D. Eastlake 3rd, Ed.
Status: Standards Track
Stream: IETF
Date: January 2026
Mailbox: bcheng@ll.mit.edu,
lberger@labn.net,
d3e3e3@gmail.com
Pages: 6
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-manet-dlep-da-credit-extension-21.txt
URL: https://www.rfc-editor.org/info/rfc9894
DOI: 10.17487/RFC9894
This document defines an extension to the Dynamic Link Exchange
Protocol (DLEP) that enables a Diffserv aware credit window scheme
for destination-specific and shared flow control.
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