Hi Alia, I have reviewed the document and had several conversations with the authors. I believe the encodings are adaptable to the OSPF Segment Routing extensions. Of course, we’ll use a different identifier than System ID (Used to identify LAN-Adj-SID neighors). One comment I have is that it would be nice to have ASCII art graphically depicting the format of the new Sub-TLVs.
Thanks, Acee From: OSPF <ospf-boun...@ietf.org<mailto:ospf-boun...@ietf.org>> on behalf of Alia Atlas <akat...@gmail.com<mailto:akat...@gmail.com>> Date: Wednesday, May 3, 2017 at 2:30 PM To: OSPF WG List <o...@ietf.org<mailto:o...@ietf.org>>, Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>, IDR List <i...@ietf.org<mailto:i...@ietf.org>> Subject: [OSPF] Fwd: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard Dear RTGWG, OSPF WG & IDR WG, I'd like to bring this IETF Last Call to your attention. The method for advertising L2 bundle information via IS-IS described in this draft may be of interest for other protocols (OSPF, BGP-LS) that may use it as precedent for how to advertise such information if there is need in the future and consistency is desired at that point. Regards, Alia ---------- Forwarded message ---------- From: The IESG <iesg-secret...@ietf.org<mailto:iesg-secret...@ietf.org>> Date: Wed, May 3, 2017 at 1:52 PM Subject: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard To: IETF-Announce <ietf-annou...@ietf.org<mailto:ietf-annou...@ietf.org>> Cc: han...@gredler.at<mailto:han...@gredler.at>, isis-cha...@ietf.org<mailto:isis-cha...@ietf.org>, isis...@ietf.org<mailto:isis...@ietf.org>, draft-ietf-isis-l2bund...@ietf.org<mailto:draft-ietf-isis-l2bund...@ietf.org>, akat...@gmail.com<mailto:akat...@gmail.com> The IESG has received a request from the IS-IS for IP Internets WG (isis) to consider the following document: - 'Advertising L2 Bundle Member Link Attributes in IS-IS' <draft-ietf-isis-l2bundles-04.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org<mailto:i...@ietf.org> mailing lists by 2017-05-17. Exceptionally, comments may be sent to i...@ietf.org<mailto:i...@ietf.org> instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract There are deployments where the Layer 3 interface on which IS-IS operates is a Layer 2 interface bundle. Existing IS-IS advertisements only support advertising link attributes of the Layer 3 interface. If entities external to IS-IS 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 IS-IS to advertise the link attributes of layer 2 (L2) bundle members. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-isis-l2bundles/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-isis-l2bundles/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/2793/
_______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg
