Advertising L2 Bundle Member Link Attributes in OSPF
draft-ketant-lsr-ospf-l2bundles-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Ketan Talaulikar , Peter Psenak | ||
Last updated | 2020-01-05 (Latest revision 2019-07-04) | ||
Replaced by | draft-ietf-lsr-ospf-l2bundles, draft-ietf-lsr-ospf-l2bundles, RFC 9356 | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
There are deployments where the Layer 3 interface on which OSPF operates is a Layer 2 interface bundle. Existing OSPF advertisements only support advertising link attributes of the Layer 3 interface. If entities external to OSPF wish to control traffic flows on the individual physical links which comprise the Layer 2 interface bundle link attribute information about the bundle members is required. This document introduces the ability for OSPF to advertise the link attributes of layer 2 (L2) Bundle members.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)