1 / 4

Advertising Per- node Admin Tags in IS-IS draft-psarkar-isis-node-admin-tag-00

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

makara
Download Presentation

Advertising Per- node Admin Tags in IS-IS draft-psarkar-isis-node-admin-tag-00

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. Advertising Per-nodeAdmin Tags in IS-ISdraft-psarkar-isis-node-admin-tag-00 PushpasisSarkarpsarkar@juniper.net ShraddhaHegdeshraddha@juniper.net Harish Raghuveerhraghuveer@juniper.net Hannes Gredler hannes@juniper.net StephaneLitkowskistephane.litkowski@orange.com Bruno Decraenebruno.decraene@orange.com

  2. 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

  3. Per-Node Admin Tag TLV 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • Dedicated TLV • Unbound List of 32-Bit node colors • Received community feedback that for conserving TLV # space, this should go under Router-Cap TLV #242.

  4. What about re-using existing protocols ? • 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 • For MPLS paths most implementations of Traffic Engineering Database (TED) schema support • Nodes • Links • But not Prefixes

More Related