1 / 5

Ravi Singh (ravis@juniper) Yimin Shen (yshen@juniper) John Drake (jdrake@juniper)

draft-ravisingh-mpls-el-for-seamless-mpls-02 Entropy Label for Seamless MPLS. Ravi Singh (ravis@juniper.net) Yimin Shen (yshen@juniper.net) John Drake (jdrake@juniper.net). IETF-90 (Toronto) speaker: Ravi Singh. What is this draft about?.

sydnee
Download Presentation

Ravi Singh (ravis@juniper) Yimin Shen (yshen@juniper) John Drake (jdrake@juniper)

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. draft-ravisingh-mpls-el-for-seamless-mpls-02 • Entropy Label for Seamless MPLS Ravi Singh (ravis@juniper.net)Yimin Shen (yshen@juniper.net)John Drake (jdrake@juniper.net) IETF-90 (Toronto) speaker: Ravi Singh

  2. What is this draft about? • Providing benefits of entropy label (EL) for e2e MPLS data traffic when: • E2e labeled path is made from separate constituent labeled paths (that are individual portions of the e2e labeled path): • The constituent labeled paths maybe separate due to their: • using different signaling protocols, or • being setup independently • Not every constituent labeled path supports EL • Not every transit router is able to hash deep enough on label stack so as to include entropy label as a hashing input • Key concept: • Entropy Label Capability (ELC) translation rules Entropy Label for Seamless MPLS IETF-90

  3. New in “-01” • Beneficial: Central theme of the use-cases: • Carry through the same EL from e2e ingress LER to egress LER where possible: • Undesirable to insert-EL/remove-EL multiple times along e2e path • Carry through the EL even on those constituent labeled paths (of the e2e LSP) whose ingress/egress LERs are not EL-capable: • Desirable to get benefits of EL even on those constituent labeled paths that are not EL-capable • Operators will not (be able to) turn-on/deploy EL in all of their routers/networks at the same time • Use-cases: • Following use-cases for this draft are listed (see slides from IETF88 for picture-illustrations) • Inter-AS L3VPN/BGP-VPLS • CoC L3VPN Entropy Label for Seamless MPLS IETF-90

  4. New in “-02” • Clarified use of terminology: • “Concatenated LSPs” instead of “stitched LSPs” to avoid confusion with GMPLS stitching • Previously received comments have been addressed Entropy Label for Seamless MPLS IETF-90

  5. Next steps: • Summary: • All received comments have been addressed • Draft has valid deployment utility • There are other drafts citing this draft as a reference • draft-akiya-mpls-entropy-lsp-ping • draft-kini-mpls-spring-entropy-label • Requesting: • WG adoption • Assignment of a document shepherd Entropy Label for Seamless MPLS IETF-90

More Related