Loading in 2 Seconds...
Loading in 2 Seconds...
LDP-AII-REACHABILITY draft-delord-jounay-pwe3-ldp-aii-reachability-01.txt. Simon Delord Uecomm Frederic Jounay / Philippe Niger France Telecom Matthew Bocci / Mustapha Aissaoui Alcatel-Lucent Cao Wei Huawei Yaakov (J) Stein RAD. What is this document about?.
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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Simon Delord Uecomm
Frederic Jounay / Philippe Niger France Telecom
Matthew Bocci / Mustapha Aissaoui Alcatel-Lucent
Cao Wei Huawei
Yaakov (J) Stein RAD
Procedure for PEs to populate their Pseudowire Attachment Individual Identifiers (PW AII) routing tables via Label Distribution Protocol (LDP) when other mechanisms (MP-BGP, IGP) are not available.
Typical use case are MPLS enabled access networks.
New LDP Address Family type called AII address family is defined for the Address-List TLV carried in LDP Address and Address Withdraw messages
When a T-PE needs to advertise a new AII to an S-PE:
it sends an LDP Address Message containing the AII address to all the S-PEs with which it maintains T-LDP sessions.
When a T-PE needs to withdraw an AII:
it sends an LDP Address Withdraw Message containing the AII address to all S-PEs with which it maintains T-LDP sessions.
An S-PE that receives an Address Message with an AII address uses the Address it learns to maintain its AII routing table for this specific T-PE by installing them in its PW routing table.
The S-PE MUST NOT pass on T-LDP messages containing the address TLV to any other LSR.
This document was presented for the first time:
- it received good feedback from the WG
- it was considered as a good starting point
The authors have included feedback provided by various people during the previous presentation.
Tried to clarify the draft to remove ambiguous statements :
section 2.1 regarding loop prevention
If this mechanism is allowed, in order to avoid any routing loop,a PE MUST NOT readvertise an AII back to the PE that originated that AII.
rephrasing/clarification when using “interwork” or “autodiscovery”.
Tried to improve readability of section 4 on proposed procedures:
This document is not expected to change any LDP behavior
To reinforce this the authors have included explicit references to RFC5036:
LDP session breakup
Address List processing
The authors would like to ask the WG if this document can become a WG document?