The IESG has approved the following document:
- 'Advertisement of Remote Interface Identifiers for Layer 2 Bundle
   Members'
  (draft-ietf-lsr-l2-bundle-member-remote-id-12.txt) as Proposed Standard

This document is the product of the Link State Routing Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and Ketan
Talaulikar.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lsr-l2-bundle-member-remote-id/




Technical Summary

   In networks where Layer 2 (L2) interface bundles (such as a Link
   Aggregation Group (LAG) as defined in IEEE 802.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 Open Shortest Path First (OSPF) and
   Intermediate System to Intermediate System (IS-IS) would advertise
   the remote interface identifiers for L2 bundle members.  The
   corresponding extension of BGP Link State (BGP-LS) is also specified.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

There has been considerable support for this document in support of a
co-routed associated bidirectional path. 

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

There is one implementation supported in H3C Comware (V9R1B99D001 or later).

Personnel

   The Document Shepherd for this document is Acee Lindem. The Responsible
   Area Director is Gunter Van de Velde.

IANA Note

  v11 had IANA OK, and v12 did not have any changed IANA sections

_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to