1 / 6

LDP End-of-LIB draft-asati-mpls-ldp-end-of-lib-00.txt Rajiv Asati Bob Thomas IETF 69 July 23, 2007

LDP End-of-LIB draft-asati-mpls-ldp-end-of-lib-00.txt Rajiv Asati Bob Thomas IETF 69 July 23, 2007. 1 draft-ietf-mpls-ldp-typed-wildcard-01. Motivation.

grant
Download Presentation

LDP End-of-LIB draft-asati-mpls-ldp-end-of-lib-00.txt Rajiv Asati Bob Thomas IETF 69 July 23, 2007

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-LIBdraft-asati-mpls-ldp-end-of-lib-00.txtRajiv AsatiBob ThomasIETF 69July 23, 2007 draft-asati-mpls-ldp-end-of-lib-00.txt

  2. 1 draft-ietf-mpls-ldp-typed-wildcard-01 Motivation There are situations where it would be useful for an LDP speaker to know when a peer had finished advertising all labels for a given FEC type; for example: • LDP-IGP Sync • LDP Graceful Restart • Following transmission of a Label Request message with a typed wildcard FEC1 draft-asati-mpls-ldp-end-of-lib-00.txt

  3. Approach Use LDP Notification message with (new) End-of-LIB Status Code to signal completion of label advertisements for a FEC type. Per RFC 3036: A Notification message carries a Status TLV and MAY include additional TLV’s as Optional Parameters, depending on the condition being signaled. A Notification message signaling End-of-LIB carries: • Status TLV with the End-of-LIB Status Code; • FEC TLV with a Typed Wildcard FEC Element which specifies the FEC Element Type of interest. draft-asati-mpls-ldp-end-of-lib-00.txt

  4. 2 draft-ietf-mpls-ldp-capabilities-00 Backward Compatibility RFC 3036: • Implicitly assumes that new Status Codes will be defined; • But fails to specify the behavior of an LDP speaker that receives a Notification message carrying a Status TLV with a Status Code it doesn't understand. This draft specifies use of the LDP capability mechanism2 by an LDP speaker to inform its peer at session establishment time that it is capable of processing Notification messages that carry the End-of-LIB status code. An LDP speaker MUST NOT send an End-of-LIB Notification to a peer unless the peer had advertised the End-of-LIB capability at session initialization. draft-asati-mpls-ldp-end-of-lib-00.txt

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

  6. Comments … draft-asati-mpls-ldp-end-of-lib-00.txt

More Related