1 / 4

András Kern – Ericsson Attila Ta kács – Ericsson

Use Cases and Alternatives for Configuring Intermediate Nodes using RSVP-TE draft-kern-ccamp-intermediate-node-config-00 & Encoding of Attributes of LSP Intermediate Hops using RSVP-TE draft-kern-ccamp-rsvpte-hop-attributes-00. András Kern – Ericsson Attila Ta kács – Ericsson. IETF-77 Anaheim.

reavis
Download Presentation

András Kern – Ericsson Attila Ta kács – Ericsson

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. Use Cases and Alternatives for Configuring Intermediate Nodes using RSVP-TEdraft-kern-ccamp-intermediate-node-config-00& Encoding of Attributes of LSP Intermediate Hops using RSVP-TEdraft-kern-ccamp-rsvpte-hop-attributes-00 András Kern – Ericsson Attila Takács – Ericsson IETF-77 Anaheim

  2. Background, Motivation and Objectives • Multiple use-cases identified requiring specific configuration at intermediate nodes of an LSP • OAM Configuration of Non-Intrusive Monitoring Entities • OAM Configuration for Tandem Connection Monitoring • WSON Regeneration, modulation type, FEC code changes • draft-bernstein-ccamp-wson-signaling-06 • MPLS FRR • draft-dong-ccamp-rsvp-te-plr-designation-00 • LSP Attributes (RFC5420) primarily deals with attributes that are relevant to the whole LSP • Currently, it is not possible to declare and signal attributes to a specific intermediate hop of the LSP

  3. Discussion • Scalability issues raised in Hiroshima about adding a new “HOP_ATTRIBUTES” sub-object to the ERO to carry hop specified configuration • This document summarizes use cases and collects extension options • Using the LSP_ATTRIBUTES Object • Using the HOP_ATTRIBUTES Sub-Object in ERO • Combination of LSP_ATTRIBUTES and ERO • Using multiple messages • Multiple messages with semantic fragmentation • Using other signaling messages/procedures Discussed in Hiroshima

  4. Next Steps • Further discussion on alternatives… • For intermediate node configuration two methods may be needed • Support cases where path setup and intermediate node configuration need to be done congruently • For simple configurations only • Use the ERO with a new HOP_ATTRIBUTES Sub-Object draft-kern-ccamp-rsvpte-hop-attributes-00.txt • For complex configurations we may need to rely on multiple message exchanges to scale • Something along the lines of semantic fragmentation described for P2MP LSPs may be useful • Solicit feedback and comments from the WG • Other use-cases?

More Related