RFC 9356 on Advertising Layer 2 Bundle Member Link Attributes in OSPF
rfc-editor@rfc-editor.org Wed, 25 January 2023 19:39 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 B1E6FC15153D; Wed, 25 Jan 2023 11:39:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 9wUMzEqdHl72; Wed, 25 Jan 2023 11:39:21 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [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 BD270C3B8E08; Wed, 25 Jan 2023 11:38:40 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id B1581194CBAF; Wed, 25 Jan 2023 11:38:40 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9356 on Advertising Layer 2 Bundle Member Link Attributes in OSPF
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: <20230125193840.B1581194CBAF@rfcpa.amsl.com>
Date: Wed, 25 Jan 2023 11:38:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/4Esmr0ycRtrjBb8kp2ChEz1BV4A>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 25 Jan 2023 19:39:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9356
Title: Advertising Layer 2 Bundle Member
Link Attributes in OSPF
Author: K. Talaulikar, Ed.,
P. Psenak
Status: Standards Track
Stream: IETF
Date: January 2023
Mailbox: ketant.ietf@gmail.com,
ppsenak@cisco.com
Pages: 12
Updates: RFC 9085
I-D Tag: draft-ietf-lsr-ospf-l2bundles-10.txt
URL: https://www.rfc-editor.org/info/rfc9356
DOI: 10.17487/RFC9356
There are deployments where the Layer 3 (L3) interface on which OSPF
operates is a Layer 2 (L2) interface bundle. Existing OSPF
advertisements only support advertising link attributes of the L3
interface. If entities external to OSPF wish to control traffic flows
on the individual physical links that comprise the L2 interface
bundle, link attribute information for the bundle members is
required.
This document defines the protocol extensions for OSPF to advertise
the link attributes of L2 bundle members. The document also specifies
the advertisement of these OSPF extensions via the Border Gateway
Protocol - Link State (BGP-LS) and thereby updates RFC 9085.
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