1 / 11

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

This draft provides guidelines on the implementation of node-admin tags in IS-IS, including their semantics and applications for routing purposes. It also introduces a new TLV for node admin tags.

tfine
Télécharger la présentation

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

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-03 PushpasisSarkarpsarkar@juniper.net ShraddhaHegdeshraddha@juniper.net Harish Raghuveerharish.r.prabhu@gmail.com Hannes Gredler hannes@juniper.net StephaneLitkowskistephane.litkowski@orange.com Bruno Decraenebruno.decraene@orange.com

  2. Summary of Updates • Node-admin tags • Guidelines on Implementation • Applications

  3. Node Admin Tags Semantics • Meaning of a node-admin tag is • Local to the network operator. • But unique across all the nodes in the same administrative domain. • Independent of the order the nodes are tagged with. • Facilitate any routing applications, that • Require advertisement of any node characteristics within the network deployment. • No need to define well-known values for each new characteristic required to be advertised.

  4. Implementations Guidelines • TLV 242 [RFC 4971] has 2 flooding scopes • Global (across Level 1 and Level 2, S-bit = 1) • Per-level (one per level, S-bit = 0) • MUST allow configuring tag values per flooding scope. • If already configured under global scope • MUST NOT allow configuring same tag value in any of Per-level scope. • If already configured under per-level scope for specific level • MAY allow configuring same value under per-level scope for the other level. • MUST NOT allow configuring same tag value in the global scope. • For MT deployments[RFC5120], MUST NOT allow configuring same tag value under different topologies.

  5. Applications • Auto-Discovery of Services. • Policy-based Path Selection. • Including/excluding specific sets of node characteristics. • Selection of Primary paths (using route-policies) • Selection of FRR Backup paths (draft-ietf-rtgwg-lfa-mageability) • TE path computations using • Node-preference constraints • Node-exclusion constraints. • Policy-based Explicit routing.

  6. Next Steps • Questions ? • Adoption as a WG draft.

  7. Background Slides

  8. Prior Art • Link colors [RFC5305] • Does not really represent a node characteristic. • Even if used to represent node characteristic, all incoming links need to be colored (one per node characteristic type).

  9. Prior Art • Prefix tags [RFC5130] • If the router-ID is considered the prefix representing the node • Router-ID encoded in TLV134 or TLV242. • Corresponding tag encoded in TLVs 135, 235, 236 and 237. • Additional implementation complexity • No prefix tagging mechanism for OSPF yet • Looking for consistency across protocols • draft-ietf-ospf-node-admin-tag-00 • Most Traffic Engineering Database (TED) schema support • Nodes • Links • But not Prefixes

  10. Basic Concepts • Per-Node Admin Tags • 32-bit unsigned integer value. • Represents a specific node characteristic exhibited by one or more nodes in the network • One per type of node characteristic. • Facilitates logical grouping of nodes in network, that suites deployment needs. • One tag per group (per node characteristic type). • Multiple nodes exhibiting same characteristics • Belong to a group, • Tagged with same tag value. • Single node exhibiting multiple characteristics • Belongs to multiple groups. • Tagged with multiple tag values(one per group or node characteristics).

  11. 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • SubTLV of Router-Cap TLV #242 (RFC 4971) • Unbound List of 32-Bit node colors (TLV-max-size costraints still applies)

More Related