1 / 6

LDP Multipoint Opaque Value Element Types Sandeep Bishnoi Pranjal Kumar Dutta Alcatel-Lucent

LDP Multipoint Opaque Value Element Types Sandeep Bishnoi Pranjal Kumar Dutta Alcatel-Lucent IJsbrand Wijnands Cisco Systems, Inc. LDP Multipoint Opaque Value Element Types Presented at IETF 75 Multiple Generic Identifier : “Type 0” is recommended for manual/static config

kylee-mccarthy
Download Presentation

LDP Multipoint Opaque Value Element Types Sandeep Bishnoi Pranjal Kumar Dutta Alcatel-Lucent

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 Multipoint Opaque Value Element Types Sandeep Bishnoi Pranjal Kumar Dutta Alcatel-Lucent IJsbrand Wijnands Cisco Systems, Inc

  2. LDP Multipoint Opaque Value Element Types • Presented at IETF 75 • Multiple Generic Identifier : • “Type 0” is recommended for manual/static config • “Type 1” [mLDP-draft] for dynamic • “Type 2” static P2MP for MVPN • [encoding based on RFC2685]

  3. Issues with single mLDP FEC identifier • Migration • Root node reserved FEC space MAY not match across vendors. Migration between vendors would require changing configuration on all leaf nodes. • Security • Traffic leaking from VPN to public (static) tree due to misconfiguration or during network convergence. • Provisioning • Operator has to check availability of allocated ID. No control over availability of ID till a tree not provisioned on root node.

  4. Migration from Vendor A to Vendor B ROOT NODE (Vendor A) P2MP ID Range (1-1000) ROOT NODE (Vendor B) P2MP ID Range (1001-2000) PE PE3 BRANCH NODE TRANSIT NODE CE3- VPN1 LEAF NODE PE:P2MP_ID (1) PE6 BUD NODE PE:P2MP_ID (1) LEAF NODE PE:P2MP_ID (1) PE4 PE5 LEAF NODE PE:P2MP_ID (1) CE4-VPN1 CE5-VPN1 CE2-VPN2 CE6-VPN1 CE3-VPN2

  5. Type 0 – Manual/static P2MP mLDP LSP for Global instance 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= 00 | Length |LSP Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LSP Identifier (contd.) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ AII Type = 0x00 Length = length of value field in octets. The length is set to 4. LSP Identifier = A 4-octet field containing a value that is unique at a root node.

  6. Type 2 – Manual/static P2MP mLDP LSP for MVPN   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= 2       | Length                        |       OUI     |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |              OUI (contd.)       |           VPN Index         |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |       VPN Index (contd.)        |        PMSI ID              |   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+   |       PMSI ID (contd.)          | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ AII Type = 0x02 Length = length of value field in octets. The length is set to 11. OUI = Organization Unique Identifier. The length is set to 3 bytes. VPN Index = Identifying the VPN according to the OUI. The length is set to 4 bytes. PMSI ID = Mi-PMSI or S-PMSI identifier. The length is set to 4 bytes.

More Related