50 likes | 201 Views
CCAMP WG. Updates to ASON Routing for OSPFv2 Protocols (RFC 5787Bis) draft-malis-ccamp-rfc5787bis-01 Andy Malis, Verizon Communications Lyndon Ong, Ciena Remi Theillaud, Marben Products Acee Lindem, Ericsson IETF 79, Beijing. Version 01 Changes.
E N D
CCAMP WG Updates to ASON Routing for OSPFv2 Protocols (RFC 5787Bis) draft-malis-ccamp-rfc5787bis-01 Andy Malis, Verizon Communications Lyndon Ong, Ciena Remi Theillaud, Marben Products Acee Lindem, Ericsson IETF 79, Beijing
Version 01 Changes • Reviewed RFC4852 requirements are not impacted by RFC5787bis changes. • Section 2 now contains text better explaining the hierarchical relationship between RAs (taken from RFC 4258). • Section 3 has been rewritten with the description of an OSPF router advertising on behalf multiple ASON transport nodes simplified (No more Ri, Pi, and Li).
Version 01 Changes (Continued) • Section 5 - Solely editorial changes. • Section 6 has been rewritten to reflect the simplified terminology introduced in section 3. Also clarified when the rules for inclusion of the new section 6 Sub-TLVs and removed the restriction on when these new Sub-TLVs may be specified. • Section 7 includes some changes to reflect the new section 3 terminology, as well as, a couple editorial changes.
Next Steps • Updates related to ITU comments from Stephen Shew. • Clarify the reachability applies to transport plane reachability for Router Address and TE Node addresses • Investigate implications of requiring specification of TE Router IDs in the ASON context. • Above discussion begs the question of not requiring the link ID sub-TLV.
Next Steps (Continued) • Other planned updates • Clarify that the restriction on ASON hierarchy not mapping to OSPF area hierarch is an OSPF protocol restriction. • Clarify that mapping of ASON RA to OSPF area will segregate the RA. • Possibly include link attribute mapping from RFC 4652 section 5.3.1 since this RFC is informational. • Request advancement to WG document