[Lsr] RFC 9492 on OSPF Application-Specific Link Attributes
rfc-editor@rfc-editor.org Tue, 10 October 2023 23:37 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED7FC14CE22; Tue, 10 Oct 2023 16:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jTgzdBC3sXUc; Tue, 10 Oct 2023 16:37:17 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B99F1C14CEFA; Tue, 10 Oct 2023 16:37:17 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id A297018E4B44; Tue, 10 Oct 2023 16:37:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20231010233717.A297018E4B44@rfcpa.amsl.com>
Date: Tue, 10 Oct 2023 16:37:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/wLDmXDdYzsikuQcOZ7MEbhoDLEQ>
Subject: [Lsr] RFC 9492 on OSPF Application-Specific Link Attributes
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2023 23:37:22 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9492
Title: OSPF Application-Specific Link Attributes
Author: P. Psenak, Ed.,
L. Ginsberg,
W. Henderickx,
J. Tantsura,
J. Drake
Status: Standards Track
Stream: IETF
Date: October 2023
Mailbox: ppsenak@cisco.com,
ginsberg@cisco.com,
wim.henderickx@nokia.com,
jefftant.ietf@gmail.com,
jdrake@juniper.net
Pages: 20
Obsoletes: RFC 8920
I-D Tag: draft-ietf-lsr-rfc8920bis-06.txt
URL: https://www.rfc-editor.org/info/rfc9492
DOI: 10.17487/RFC9492
Existing traffic-engineering-related link attribute advertisements
have been defined and are used in RSVP-TE deployments. Since the
original RSVP-TE use case was defined, additional applications such
as Segment Routing (SR) Policy and Loop-Free Alternates (LFAs) that
also make use of the link attribute advertisements have been defined.
In cases where multiple applications wish to make use of these link
attributes, the current advertisements do not support
application-specific values for a given attribute, nor do they
support indication of which applications are using the advertised
value for a given link. This document introduces link attribute
advertisements in OSPFv2 and OSPFv3 that address both of these
shortcomings.
This document obsoletes RFC 8920.
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