1 / 7

Updates on Domain Sequence Representation at IETF 82, Taipei - Key Issues and Next Steps

This draft outlines significant updates to the representation of domain sequences, as discussed in the 82nd IETF meeting in Taipei. Key points include support for 4-byte AS numbers, the encoding of domain sequences, and the proposed changes in sub-object ordering. The draft highlights open issues, such as the role of boundary nodes, the inclusion of additional constraints, and the definition of domain sequences using RBNF. Next steps involve resolving open issues and gathering comments from authors of related inter-domain identifiers.

bowen
Télécharger la présentation

Updates on Domain Sequence Representation at IETF 82, Taipei - Key Issues and Next Steps

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standard Representation Of Domain Sequence draft-dhody-pce-pcep-domain-sequence-01 Dhruv Dhody (dhruv.dhody@huawei.com) Udayasree Palle (udayasreepalle@huawei.com) Ramon Casellas (ramon.casellas@cttc.es) 82nd IETF @ Taipei

  2. Updates from -00 • Support for 4-Byte AS Number • Updates in OSPF/ISIS Sub-Objects 82nd IETF @ Taipei

  3. Open Issues • Encoding of Domain Sequence • (1) Keep the RFC5440 IRO object (Object class 10, object type 1) • Current Draft • (2) New IRO object (Object class 10, object type 2) • Better Application of Rules w.r.t domain sequence • Sub-Object Ordering • Different Scope • Mode of Operations • Strict v/s Loose • (3) New DOMAIN-SEQUENCE object • ** Authors feel Option-2 is the way to go…. 82nd IETF @ Taipei

  4. Open Issues • Boundary Nodes & Links a part of Domain-Sequence? • Should additional constraints/restrictions be part of Domain-Sequence? • ABR and ASBR • Inter-AS TE Links • Formal RBNF specification for Domain-Sequence? • Draft currently mentions multiple deployment scenarios and how the sub-objects (AS/Area) will be encoded in the IRO. • RBNF is generally used to define Messages and not Objects. • Does WG has a comment on using RBNF to define Domain-Sequence? 82nd IETF @ Taipei

  5. Next Steps • Resolve Open Issues and update new version. • Request all authors of inter-domain (P2P / P2MP / HPCE) IDs to give comments. 82nd IETF @ Taipei

  6. Questions & Comments? 82nd IETF @ Taipei

  7. Thanks! 82nd IETF @ Taipei

More Related