Skip to main content

Advertisement of Remote Interface Identifiers for Layer 2 Bundle Members
draft-glctgp-lsr-l2-bundle-member-remote-id-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Liyan Gong , Changwang Lin , Mengxiao Chen , Ketan Talaulikar , Les Ginsberg , Peter Psenak
Last updated 2025-02-17
Replaces draft-gong-lsr-lldp-interface-id
Replaced by draft-ietf-lsr-l2-bundle-member-remote-id
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-lsr-l2-bundle-member-remote-id
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

In networks where Layer 2 (L2) interface bundles (such as a Link Aggregation Group (LAG) [IEEE802.1AX]) are deployed, a controller may need to collect the connectivity relationships between bundle members for traffic engineering (TE) purposes. For example, when performing topology management and bidirectional path computation for TE, it is essential to know the connectivity relationships among bundle members. This document describes how OSPF and IS-IS would advertise the remote interface identifiers for Layer 2 bundle members. The corresponding extension of BGP-LS is also specified.

Authors

Liyan Gong
Changwang Lin
Mengxiao Chen
Ketan Talaulikar
Les Ginsberg
Peter Psenak

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)