1 / 9

LDP End-of-LIB

LDP End-of-LIB. draft-asati-mpls-ldp-end-of-lib-01.txt IETF 70. Bob Thomas Pradosh Mohapatra Emily Chen Rajiv Asati. Agenda. Motivation Overview Changes since -00 version Next step. Motivation.

jovita
Download Presentation

LDP End-of-LIB

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. LDP End-of-LIB draft-asati-mpls-ldp-end-of-lib-01.txt IETF 70 Bob Thomas Pradosh Mohapatra Emily Chen Rajiv Asati draft-asati-mpls-ldp-end-of-lib-01.txt

  2. Agenda • Motivation • Overview • Changes since -00 version • Next step draft-asati-mpls-ldp-end-of-lib-01.txt

  3. Motivation • There are scenarios where it would be useful for an LDP speaker to know when a peer had finished advertising all labels for a given FEC Type. • Scenarios such as • LDP-IGP Sync • LDP Graceful Restart • Label Request with a typed Wildcard FEC • The LDP Specification [RFC5036] specifies no mechanism for an LDP speaker to achieve the above. draft-asati-mpls-ldp-end-of-lib-01.txt

  4. Overview • The draftspecifies use of LDP Notification message with (new) ‘End-of-LIB’ status code by an LDP speaker to signal its completion of label advertisements (for a FEC type) following the LDP session establishment. • The draft also specifies use of a new LDP capability* to convey that the speaker is capable of handling (received) Notification message that may carry Unrecognized Status codes. * draft-ietf-mpls-ldp-capabilities draft-asati-mpls-ldp-end-of-lib-01.txt

  5. Overview • A Notification messages signaling End-of-LIB Status code carries: • Status TLV with End-of-LIB Status Code • FEC TLV with a Typed Wildcard FEC element draft-asati-mpls-ldp-end-of-lib-01.txt

  6. . . . . . . . . . . . . R1 R2 Keepalive Keepalive LabelMapping(FEC1(ipv4), Label11) LabelMapping(FEC1(ipv4), Label21) LabelMapping(FECn(ipv4), Label1n) LabelMapping(FECn(ipv4), Label2n) Example Scenario Initialization(CommonSessParams, ..., Unrecognized Notification Capability TLV) Initialization(CommonSessParams, ..., Unrecognized Notification Capability TLV) Session Up Notification(End-of-LIB, FEC(TypedWildcard, ipv4) Notification(End-of-LIB, FEC(TypedWildcard, ipv4) draft-asati-mpls-ldp-end-of-lib-01.txt

  7. Changes since -00 version • Incorporated all the comments received at/since the last (Chicago) IETF • Thanks to Ina Minei, Alia Atlas, Yakov Rekhter and Luyuan Fang. • See Next slide. • Two new authors - • Pradosh Mohapatra • Emily Chen draft-asati-mpls-ldp-end-of-lib-01.txt

  8. Changes since -00 version • Renamed ‘End-of-LIB’ capability (section 3) to ‘Unrecognized Notification’ capability to generalize its usage beyond just End-of-LIB, and updated its format. • The LDP speaker ignores any notification with unrecognized status code. • Further verbiage added in section 3 for clarification. • Added a section (5) on Usage guideline • Clarifies how End-of-LIB signaling would help in each of 3 scenarios (listed in slide#4) • Includes Timeout Consideration (section 5.4) if the notification was missed. draft-asati-mpls-ldp-end-of-lib-01.txt

  9. Next Steps • Should this be a WG item? draft-asati-mpls-ldp-end-of-lib-01.txt

More Related