advertising per node admin tags in is is draft psarkar isis node admin tag 01
Download
Skip this Video
Download Presentation
Advertising Per- node Admin Tags in IS-IS draft-psarkar-isis-node-admin-tag- 01

Loading in 2 Seconds...

play fullscreen
1 / 6

Advertising Per- node Admin Tags in IS-IS draft-psarkar-isis-node-admin-tag- 01 - PowerPoint PPT Presentation


  • 119 Views
  • Uploaded on

Advertising Per- node Admin Tags in IS-IS draft-psarkar-isis-node-admin-tag- 01. Pushpasis Sarkar psarkar @ juniper.net Shraddha Hegde shraddha @ juniper.net Harish Raghuveer hraghuveer @ juniper.net Hannes Gredler [email protected] Stephane Litkowski stephane.litkowski @ orange.com

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Advertising Per- node Admin Tags in IS-IS draft-psarkar-isis-node-admin-tag- 01' - denise


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
rationale
Rationale
  • Node color is used for describing path constraints
    • IP paths
    • MPLS paths
  • there is a category of path constraints which requires that a certain path should or should not be routed over a node with specific properties.
    • go over the packet-optical super-core
    • don't go over any other PE router
    • don't go over any other ASBR (hot potato)
    • don't go over equipment from vendor X
    • don’t go over nodes with limited hardware capabilities (e.g. LB)
    • don't go over equipment which is running software version x.y.z
    • de-prefer nodes which have not good hardware based latency measurements
re using existing protocols 1
Re-using existing protocols ? (1)
  • Link colors as per RFC5305 ?
  • One has to tag all incoming links (=touching N nodes) to color a specific node
re using existing protocols 2
Re-using existing protocols ? (2)
  • Prefix tags as per RFC5130 ?
    • No bijectionbetween a node (router-ID) and some prefix (which carries the tags)
      • In fact those are different name-spaces
    • What about L1L2 case for Prefix leaking ?
      • How to differentiate leaked prefixes vs. self-originated prefixes ?
    • No prefix tagging mechanism for OSPF yet
      • Looking for consistency across protocols
      • draft-hegde-ospf-node-admin-tag-01
    • For MPLS/TE paths most implementations of Traffic Engineering Database (TED) schema support
      • Nodes
      • Links
      • But not Prefixes
per node admin tag sub tlv
Per-Node Admin Tag subTLV

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

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Type | Length |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Administrative Tag #1 |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Administrative Tag #2 |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

// //

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Administrative Tag #N |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  • subTLVof Router-Cap TLV #242 (RFC 4971)
    • Unbound List of 32-Bit node colors
next steps
Next Steps
  • Questions ?
  • Adoption as a WG item ?
ad