RFC 9089 on Signaling Entropy Label Capability and Entropy Readable Label Depth Using OSPF
rfc-editor@rfc-editor.org Sat, 14 August 2021 13:38 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 A59E93A1DB0; Sat, 14 Aug 2021 06:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 gI6GUOZAH0yv; Sat, 14 Aug 2021 06:38:05 -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 6BF333A1D9D; Sat, 14 Aug 2021 06:38:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3C99CF407FB; Sat, 14 Aug 2021 06:37:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9089 on Signaling Entropy Label Capability and Entropy Readable Label Depth Using OSPF
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, lsr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210814133728.3C99CF407FB@rfc-editor.org>
Date: Sat, 14 Aug 2021 06:37:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dcL_ZBephJ2XLByhy-GImym5dmE>
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: Sat, 14 Aug 2021 13:38:22 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9089
Title: Signaling Entropy Label Capability and
Entropy Readable Label Depth Using OSPF
Author: X. Xu,
S. Kini,
P. Psenak,
C. Filsfils,
S. Litkowski,
M. Bocci
Status: Standards Track
Stream: IETF
Date: August 2021
Mailbox: xiaohu.xu@capitalonline.net,
sriganeshkini@gmail.com,
ppsenak@cisco.com,
cfilsfil@cisco.com,
slitkows@cisco.com,
matthew.bocci@nokia.com
Pages: 8
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ospf-mpls-elc-15.txt
URL: https://www.rfc-editor.org/info/rfc9089
DOI: 10.17487/RFC9089
Multiprotocol Label Switching (MPLS) has defined a mechanism to
load-balance traffic flows using Entropy Labels (EL). An ingress
Label Switching Router (LSR) cannot insert ELs for packets going into
a given Label Switched Path (LSP) unless an egress LSR has indicated
via signaling that it has the capability to process ELs, referred to
as the Entropy Label Capability (ELC), on that LSP. In addition, it
would be useful for ingress LSRs to know each LSR's capability for
reading the maximum label stack depth and performing EL-based
load-balancing, referred to as Entropy Readable Label Depth (ERLD).
This document defines a mechanism to signal these two capabilities
using OSPFv2 and OSPFv3, and Border Gateway Protocol - Link State
(BGP-LS).
This document is a product of the Link State Routing 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