1 / 8

Entropy Labels in MPLS Forwarding draft-kompella-mpls-entropy-label- 02

Entropy Labels in MPLS Forwarding draft-kompella-mpls-entropy-label- 02. Kireeti Kompella , John Drake – Juniper Networks Shane Amante – Level 3 Communications Wim Hendrickx – Alcatel-Lucent Lucy Yong – Huawei. History. First presented back at IETF 73 IETF 78: Update from -00 to -01

miya
Download Presentation

Entropy Labels in MPLS Forwarding draft-kompella-mpls-entropy-label- 02

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. Entropy Labels in MPLS Forwardingdraft-kompella-mpls-entropy-label-02 KireetiKompella, John Drake – Juniper Networks Shane Amante – Level 3 Communications WimHendrickx – Alcatel-Lucent Lucy Yong – Huawei draft-kompella-mpls-entropy-label-02

  2. History • First presented back at IETF 73 • IETF 78: Update from -00 to -01 • Today (IETF 80): Update from -01 to -02 draft-kompella-mpls-entropy-label-02

  3. Background • LAG and ECMP are powerful tools with widespread deployment • Goal is to make them better • Ingress PE’s perform packet header key extraction and assigns an “entropy label” to incoming traffic • Typically, hash of 5-tuple of IPv4 or IPv6 header • Transit LSR’s just use label stack (incl. entropy label) as input-keys for LAG and ECMP, regardless of MPLS payload carried! • Egress PE’s discard entropy label before forwarding packet to final destination • This draft is complementary to draft-ietf-pwe3-fat-pw draft-kompella-mpls-entropy-label-02

  4. MPLS Label Stack When app. labels ARE NOT used When app. labels ARE used Tunnel Label Tunnel Label Application Label BOS = 0 Entropy Label Indicator (ELI) BOS = 0 Entropy Label value Entropy Label BOS = 1 Entropy Label BOS = 1 Data Header (e.g.: IPv4 or IPv6) Data Header (e.g.: IPv4 or IPv6) Data Data draft-kompella-mpls-entropy-label-02

  5. Changes from -01 to -02 • Substantial additions to doc • Section 5: Signaling for Entropy Labels now includes BGP and, separately, RSVP-TE P2P (unicast, unidirectional & bidirectional) LSP Signaling Procedures • LDP Signaling for Entropy Labels already in draft • Section 6: OAM + Entropy Labels • Section 7: MPLS-TP + Entropy Labels • Entropy Labels do not apply to MPLS-TP LSP’s, because MPLS-TP does not co-exist with ECMP per §3.2 of RFC 5921. • Section 8: P2MP LSP’s + Entropy Labels • Section 9: (Example) Entropy Labels & Applications • Includes Tunnel LSP’s, Inter-AS VPN’s and Multiple Simultaneous Applications on same PE draft-kompella-mpls-entropy-label-02

  6. Open Issues: 1 / 2RSVP P2MP LSP Procedures • Problem: receivers on same tree that: • Do and do not support receipt of Entropy Labels; • Join and leave P2MP LSP • Proposed Solution: • Currently define that it’s the responsibility of Ingress LSR to keep track of receiver’s EL capabilities and determine when, and when not, to send EL’s on the P2MP LSP. • Operators may decide to have two P2MP LSP’s: first with P2MP EL capable receivers + second with P2MP non-EL capable receivers. draft-kompella-mpls-entropy-label-02

  7. Open Issues: 2 / 2OAM • How will LSP ping/traceroute over LAG + ECMP work with entropy labels? • Currently, LSP traceroute based on DPI of MPLS payload for input-keys, (e.g.: IP header 5-tuple), in real world • IOW, label range option of LSP traceroute not used in practice • With EL’s, ideally would have LSR’s return label ranges to be used as input-key for load-balancing • Problems: • Not practical to globally (box-wide) disable DPI forLSPtraceroute on LSR’s, given EL capability or lack thereof on PE’s • How to coordinate, between PE’s and LSR’s, whether and how to enable/disable DPI vs. using a label range for LSP ping/traceroute between PE’s and transit LSR’s draft-kompella-mpls-entropy-label-02

  8. Next Steps • Think the draft comprehensively addresses all signaling protocols and use cases • Would like to ask to make this a WG draft, while continuing to resolve Open Issues draft-kompella-mpls-entropy-label-02

More Related