S2L Name Identification for Point-to-Multipoint TE LSPs draft-ali-mpls-rsvp-te-s2l-name-01.txt - PowerPoint PPT Presentation

View by Category
About This Presentation
Title:

S2L Name Identification for Point-to-Multipoint TE LSPs draft-ali-mpls-rsvp-te-s2l-name-01.txt

Description:

Working with destination IP address to identify/ filter a given S2L is not user ... Session name attribute cannot be used to identify an S2L by name. ... – PowerPoint PPT presentation

Number of Views:72
Avg rating:3.0/5.0
Slides: 6
Provided by: cis957
Learn more at: http://www.ietf.org
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: S2L Name Identification for Point-to-Multipoint TE LSPs draft-ali-mpls-rsvp-te-s2l-name-01.txt


1
S2L Name Identification for Point-to-Multipoint
TE LSPs draft-ali-mpls-rsvp-te-s2l-name-01.txt

Zafar Ali (zali_at_cisco.com) Robert Sawaya
(rsawaya_at_cisco.com)
2
Agenda
  • Requirement.
  • Proposed Solution.
  • Next Steps.

3
Requirement
  • Requirements for signaling S2L name are similar
    to reasons for defining Session name for LSP.
  • Service providers would like to use meaningful
    names not only at the LSP level, but also at the
    S2L level.
  • E.g., West-Distribution-tree as P2MP LSP name,
    and LA-to-San-Francisco as S2L name, in the above
    example.
  • Working with destination IP address to identify/
    filter a given S2L is not user friendly,
    especially when a destination is terminating
    multiple S2Ls.

4
Proposed Solution
  • A Path message can be used to signal one or more
    S2L sub-LSPs.
  • Session name attribute cannot be used to
    identify an S2L by name. E.g., S2L sub-lsp names
    like LA-to-San-Francisco in the previous example
    cannot be specified.
  • This document proposes to add an optional
    object called S2L_ATTRIBUTE object to the sub-LSP
    descriptor tuple defined in RFC4875. i.e., it
    proposes to use the lt ltS2L_SUB_LSPgt, ltP2MP
    SECONDARY_EXPLICIT_ROUTEgt, ltS2L_ATTRIBUTEgt gt
    tuple to represent the S2L sub-LSP being signaled
    in the Path message (in the sub-LSP descriptor
    list).
  • The document defines "S2L sub-LSP name" as an
    attribute of S2L_ATTRIBUTE object.
  • If needed, the S2L_ATTRIBUTE object can be
    extended to include other S2L sub-LSP scoped
    attributes in future.
  • An excellent comment from Adrian prompted us to
    encode S2L_ATTRIBUTE object using RFC4420-style
    encoding.
  • Recommends Session Name in the SESSION_ATTRIBUTE
    object to carry P2MP LSP name (Distribution tree
    name), and S2L sub-LSP Name in the S2L_ATTRIBUTE
    object to carry S2L sub-LSP name.

5
Next Steps
  • We would like to request WG to accept this ID as
    a WG document.

Thank You
About PowerShow.com