1 / 11

OSPF TE Extension for Area IDs draft-lu-ospf-area-tlv-00.txt

OSPF TE Extension for Area IDs draft-lu-ospf-area-tlv-00.txt. IETF 80 - Prague, Czech Republic March 27 – April 1, 2011 Wenhu Lu. Agenda. Background The Need of TE-ABRs Area-ID TLV Applications. Background. BN1. BN2. H. T. BN3. The need for inter-area LSPs

aquarius
Download Presentation

OSPF TE Extension for Area IDs draft-lu-ospf-area-tlv-00.txt

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. OSPF TE Extension for Area IDsdraft-lu-ospf-area-tlv-00.txt IETF 80 - Prague, Czech Republic March 27 – April 1, 2011 Wenhu Lu

  2. Agenda • Background • The Need of TE-ABRs • Area-ID TLV • Applications

  3. Background BN1 BN2 H T BN3 The need for inter-area LSPs BN (Border nodes) = ABR-LSRs

  4. Solutions • Global TED • Too big, negating the purpose of having multiple areas or ASes; • violates the information hiding and confidentiality requirement and is unacceptable by ISPs • Crankback • Probe a list of ABRs till a PATH is viable • But need to know ABRs – configure ? • RBPC – RFC5441 • Find an optimal path • Still need to know ABRs

  5. PCE Development • RFC 5088 – OSPF Extension for PCE Discovery • In Rtr Info LSA space; • Scopes: inter-area; inter-as • For locating PCEs, NOT LSRs

  6. RFC 3630 – OSPF TE Extension • Area scope TE database; • Opaque to OSPF • No idea of TE-ABRs • They are area exit LSRs • Good for finding intra-area LSPs

  7. The proposal • The ABR info is easily acquirable • Fig: A,B,C,D,E in backbone • A,C,D,E are ABRs West A---B---C East |\ D E South Figure 1: Sample Topology

  8. Area ID TLV 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Len | Area-ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Area-ID (Cont) | Another Area-ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Another Area-ID (Cont) | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | More Area-ID | | | // // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • To add under RFC 3630 section 2.4 • At most 1 Area ID TLV • Type – Area ID TLV (TBD: 3) • Len – 4xn, n is the number of exit areas • Eg: “D” has 1 exit area “south”, provided that its link to “south” is also TE enabled.

  9. Example • Assume router “F” connects to four areas • Area 0, 1, 2, and 3 • Assume area 2 is not TE-enabled • It advertise following Area-ID TLVs • To area 0: | 3| 8| 0 0 0 1| 0 0 0 3| • To area 1: | 3| 8| 0 0 0 0| 0 0 0 3| • To area 2: None • To area 3: | 3| 8| 0 0 0 0| 0 0 0 1|

  10. Application • Area ID TLVs give CSPF (PCE) knowledge of TE-ABR info. • It can automate the crankback process • Replacing manual configuration • Any algorithm (BRPC) that needs exit LSRs • It is backward compatible

  11. Thank You

More Related