TL;DR
This paper introduces a mechanism to enhance the IS-IS routing protocol by allowing network operators to attach "administrative tags" to IP prefixes. These tags enable more granular control and easier management of how IP prefixes are distributed and handled within complex, multi-level IS-IS domains, without introducing new security vulnerabilities.
What Problem Does This Paper Address?
In large and complex network infrastructures, especially those using the IS-IS routing protocol, efficiently managing and controlling the distribution of IP prefixes can be challenging. Network operators need ways to apply specific policies to certain prefixes, such as controlling redistribution between different routing levels or areas, or influencing how prefixes are advertised. Existing IS-IS mechanisms offer limited flexibility for such fine-grained policy enforcement directly within the routing information itself. This paper addresses the need for a standardized, integrated way to carry policy-relevant information alongside IP prefix reachability data within IS-IS Link State Protocol Data Units (LSPs).
Methods
The core of this paper is the definition of two new "sub-TLVs" (Type-Length-Value fields) that can be embedded within existing IS-IS TLVs used for IP prefix reachability. These new sub-TLVs are:
- 32-bit Administrative Tag Sub-TLV (Type 1): Allows for one or more 32-bit unsigned integers to be associated with an IP prefix.
- 64-bit Administrative Tag Sub-TLV (Type 2): Allows for one or more 64-bit unsigned integers to be associated with an IP prefix.
These sub-TLVs can be added to several existing IS-IS TLVs, including the IPv4 extended IP reachability TLV (TLV 135), its multi-topology derivative (TLV 235), and their IPv6 counterparts (TLV 236 and TLV 237). The paper specifies the encoding for these tags, including their type, length, and the tag values themselves. It also defines how implementations should handle multiple tags (prioritizing the first one) and reserves a tag value of zero to indicate "no tag."
Datasets
Not discussed in the paper.
Key Insights and Ideas
- Policy as Data: The fundamental idea is to treat policy-relevant information as data that can be directly carried within the routing protocol's advertisements. This moves policy enforcement closer to the routing decision-making process.
- Flexibility through Tags: Administrative tags are designed to be autonomous identifiers. Their meaning and how they are used for policy are left to the network operator's discretion, allowing for diverse applications like BGP community mapping, controlled redistribution, or managing multiple IS-IS instances.
- Preserving Order: While tag order doesn't imply a specific operation, preserving the order of tags when propagating TLVs between IS-IS levels is recommended. This ensures a consistent view for implementations that might only recognize a single tag.
- No New Security Issues: The authors emphasize that these extensions do not introduce new security vulnerabilities, as the tags are intended to remain within the administrative control of the network operator.
Key Results
The paper defines the mechanism for adding administrative tags to IS-IS. It specifies the structure and encoding of the 32-bit and 64-bit administrative tag sub-TLVs. The key "result" is the standardization of this mechanism, enabling interoperability and providing a common framework for network operators to implement policy control within IS-IS domains. The paper outlines potential use cases, such as differentiating prefixes for controlled leaking between IS-IS levels, but does not present quantitative performance metrics or benchmark results.
Limitations and Future Work
- Implementation-Dependent Semantics: The paper explicitly states that the semantics of the tags and how they are used for policy are implementation-dependent and left to the operator. This means that while the mechanism is standardized, the actual policy enforcement logic will vary between vendors and configurations.
- Coexistence of Implementations: The document acknowledges that implementations supporting single tags and multiple tags can coexist. It recommends that implementations supporting multiple tags should place any tag that needs to be interpreted by all systems as the first tag.
- Future Work: The paper suggests that the defined sub-TLVs can be used with future, as-yet-undefined IS-IS TLVs, indicating a forward-looking design. The operational use cases are broad, and further exploration of specific policy applications would be a natural extension.
Summary updated