RFC 9356: Advertising Layer 2 Bundle Member Link Attributes in OSPF
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9356
- Published
- January 2023
- Authors
- K. Talaulikar; P. Psenak
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Updates:
- RFC 9085
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9355OSPF Bidirectional Forwarding Detection (BFD) Strict-ModeCurrent
February 2023
- RFC 9351Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm AdvertisementCurrent
February 2023
- RFC 9339OSPF Reverse MetricCurrent
December 2022
- RFC 9314YANG Data Model for Bidirectional Forwarding Detection (BFD)Current
September 2022
- RFC 9294Application-Specific Link Attributes Advertisement Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2022
- RFC 9247BGP - Link State (BGP-LS) Extensions for Seamless Bidirectional Forwarding Detection (S-BFD)Current
June 2022
- RFC 9513OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 9127YANG Data Model for Bidirectional Forwarding Detection (BFD)Updated
October 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?