1 / 5

Tomohiro Otani otani@kddilabs.jp Satoru Okamoto okamoto.satoru@lab.ntt.co.jp

GMPLS Inter-domain routing problem statement and requirements draft-otani-ccamp-inter-domain-routing-req-00.txt. Tomohiro Otani otani@kddilabs.jp Satoru Okamoto okamoto.satoru@lab.ntt.co.jp. Summary of this requirement draft. This draft fits to the following charter item

evonne
Download Presentation

Tomohiro Otani otani@kddilabs.jp Satoru Okamoto okamoto.satoru@lab.ntt.co.jp

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. GMPLS Inter-domain routing problem statement and requirementsdraft-otani-ccamp-inter-domain-routing-req-00.txt Tomohiro Otani otani@kddilabs.jp Satoru Okamoto okamoto.satoru@lab.ntt.co.jp 64th IETF meeting, Nov. 2005

  2. Summary of this requirement draft • This draft fits to the following charter item • “defining signaling and routing mechanisms to create paths that span multiple IGP areas, multiple ASes, and multiple providers”. • This draft • describes GMPLS Inter-domain routing problems and requirements • clarifies the need for inter-domain routing functionalities between GMPLS-controlled domains, which other SDOs already considered or specify (E-NNI, DDRP). • is jointly proposed by SPs (KDDI/NTT) • Is created by reconsidering “draft-otani-ccamp-interas-gmpls-te-03.txt” by eliminating TE extensions. 64th IETF meeting, Nov. 2005

  3. GMPLS Inter domain problem statement • Why do SPs need this work ? • Effective interconnection between multiple SPs’ GMPLS networks • Policy control at a domain boundary • Abstracted topology information exchange • What are issues ? • No definition of GMPLS inter-domain routing • Difficulty and less efficiency to set up the route without knowing reachability information over domains. • Cannot apply any policy mechanisms • Other SDOs define or consider this type of routing functionality. • IETF CCAMP WG should create such a solution. 64th IETF meeting, Nov. 2005

  4. Requirement of GMPLS inter-domain routing • GMPLS inter-domain routing must support • The exchange of reachability information over domains. • Redistributed mechanism of the exchanged reachability information. • Reachability information includes: • Reachable IP address (Node ID or Interface IP address) • Interface ID (unnumbered link) • Policy mechanisms must be supported for controlling reachability information within a domain or over domains. • Aggregation/topology concealing functions should be considered. 64th IETF meeting, Nov. 2005

  5. Next Steps • We would like to propose to adopt this as a working group document at this meeting in order to newly initiate GMPLS inter-domain routing work. • Will investigate GMPLS EGP extensions. 64th IETF meeting, Nov. 2005

More Related