1 / 7

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

Entropy Labels in MPLS Forwarding draft-kompella-mpls-entropy-label-01. Kireeti Kompella Juniper Networks Shane Amante Level 3 Communications. History. First presented back at IETF 73 Valuable input (& kick) from John Drake Today: Update from -00 to -01. Background.

signa
Download Presentation

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

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-01 KireetiKompella Juniper Networks Shane Amante Level 3 Communications

  2. History • First presented back at IETF 73 • Valuable input (& kick) from John Drake • Today: Update from -00 to -01

  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 entropy labels as input-keys for LAG and ECMP • Egress PE’s discard entropy label before forwarding to final destination

  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

  5. Changes from -00 to -01 • Removed reqm’t that allowed an LSR to signal it MUST receive entropy labels. • Simplified approach to “Entropy Label Indicator” • If application labels are used no ELI necessary; • If no application label is used, (e.g.: IPv4/MPLS), then ELI MUST always be used for FEC • Latter makes signaling more straightforward, particularly if/when applications are added to egress PE’s. • Security Considerations • IANA Considerations, (see next slide)

  6. Changes from -00 to -01, (cont’d) • LDP Signaling • Entropy Label sub-TLV • Label Mapping Msg sub-TLV • Indicates that egress PE can handle entropy-labels • Indicates label value to use in ELI field 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |U|F| Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ELI Label | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Entropy Label sub-TLV

  7. To Do / Next Steps • RSVP-TE and BGP signaled entropy labels TBD • Adopt as WG draft?

More Related