| < draft-ietf-isis-admin-tags-01.txt | draft-ietf-isis-admin-tags-02.txt > | |||
|---|---|---|---|---|
| Network Working Group Christian Martin | Network Working Group Christian Martin | |||
| INTERNET DRAFT Verizon Internet Services | INTERNET DRAFT Verizon | |||
| Expiration Date: January 2003 Brad Neal | Expiration Date: January 2005 Brad Neal | |||
| Broadwing Communications | Broadwing Communications | |||
| Stefano Previdi | Stefano Previdi | |||
| August 2002 Cisco Systems | July 2004 Cisco Systems | |||
| A Policy Control Mechanism in IS-IS Using Administrative Tags | A Policy Control Mechanism in IS-IS Using Administrative Tags | |||
| <draft-ietf-isis-admin-tags-01.txt> | <draft-ietf-isis-admin-tags-02.txt> | |||
| 1. Status of this Memo | 1. Status of this Memo | |||
| This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
| all provisions of Section 10 of RFC 2026. | all provisions of Section 10 of RFC 2026. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
| Drafts. | Drafts. | |||
| skipping to change at page 1, line 38 ¶ | skipping to change at page 1, line 37 ¶ | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt | http://www.ietf.org/ietf/1id-abstracts.txt | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| 2. Abstract | 2. Abstract | |||
| This document describes an extension to the IS-IS protocol to add | This document describes an extension to the IS-IS protocol to add | |||
| operational capabilities that allow for ease of management and | operational capabilities that allow for ease of management and | |||
| control over IP prefix distribution within an IS-IS domain. The IS- | control over IP prefix distribution within an IS-IS domain. | |||
| IS protocol is specified in [1], with extensions for supporting IPv4 | ||||
| specified in [2] and further enhancements for Traffic Engineering [4] | ||||
| in [3] and [6]. | ||||
| This document enhances the IS-IS protocol by extending the | This document enhances the IS-IS protocol by extending the | |||
| information that a Intermediate System (IS) [router] can place in | information that a Intermediate System (IS) [router] can place in | |||
| Link State Protocol Data Units (LSPs) as specified in [2]. This | Link State Protocol Data Units (LSPs) for policy use. This | |||
| extension will provide operators with a mechanism to control IP | extension will provide operators with a mechanism to control IP | |||
| prefix distribution throughout multi-level IS-IS domains. | prefix distribution throughout multi-level IS-IS domains. | |||
| Additionally, the information can be placed in LSPs that have TLVs as | Additionally, the information can be placed in LSPs that have TLVs as | |||
| yet undefined, if this information is used to convey the same meaning | yet undefined, if this information is used to convey the same meaning | |||
| in these future TLVs as it is used in the currently defined TLVs. | in these future TLVs as it is used in the currently defined TLVs. | |||
| 3. Specification of Requirements | 3. Specification of Requirements | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| skipping to change at page 5, line 7 ¶ | skipping to change at page 5, line 7 ¶ | |||
| L1 / \ | L1 / \ | |||
| R1----1.1.1.0/24 (A) R5 | R1----1.1.1.0/24 (A) R5 | |||
| | | | | |||
| | | | | |||
| 1.1.2.0/24 (B) | 1.1.2.0/24 (B) | |||
| Figure 1 | Figure 1 | |||
| We associate Administrative Tag 100 with property A, and have R5 | We associate Administrative Tag 100 with property A, and have R5 | |||
| attach that value to the IP extended reachability information TLV for | attach that value to the IP extended reachability information TLV for | |||
| prefix 1.1.1.0/24. R2 has a policy in place to "match prefixes with | prefix 1.1.2.0/24. R2 has a policy in place to "match prefixes with | |||
| Administrative Tag 100, and leak to L1." | Administrative Tag 100, and leak to L1." | |||
| The previous example is rather simplistic; it seems that it would be | The previous example is rather simplistic; it seems that it would be | |||
| just as easy for R2 simply to match the prefix 1.1.1.0/24. However, | just as easy for R2 simply to match the prefix 1.1.2.0/24. However, | |||
| if there are a large number of routers that need to apply some policy | if there are a large number of routers that need to apply some policy | |||
| according to property A and large number of "A" prefixes, this | according to property A and large number of "A" prefixes, this | |||
| mechanism can be quite helpful. | mechanism can be quite helpful. | |||
| 9. Security Considerations | 9. Security Considerations | |||
| This document raises no new security issues for IS-IS, as any | This document raises no new security issues for IS-IS, as any | |||
| annotations to IP prefixes should not pass outside the administrative | annotations to IP prefixes should not pass outside the administrative | |||
| control of the network operator of the IS-IS domain. Such an | control of the network operator of the IS-IS domain. Such an | |||
| allowance would violate the spirit of Interior Gateway Protocols in | allowance would violate the spirit of Interior Gateway Protocols in | |||
| skipping to change at page 6, line 32 ¶ | skipping to change at page 6, line 32 ¶ | |||
| [5] Li,T., Przygienda, T., Smit, H., "Domain-wide Prefix Distribution | [5] Li,T., Przygienda, T., Smit, H., "Domain-wide Prefix Distribution | |||
| with Two-Level IS-IS" RFC 2966, October 2000 | with Two-Level IS-IS" RFC 2966, October 2000 | |||
| [6] Przygienda, T., Shen, N., Sheth, N., "M-ISIS: Multi Topology | [6] Przygienda, T., Shen, N., Sheth, N., "M-ISIS: Multi Topology | |||
| Routing in IS-IS", draft-ietf-isis-wg-multi-topology-03.txt, April | Routing in IS-IS", draft-ietf-isis-wg-multi-topology-03.txt, April | |||
| 2002. | 2002. | |||
| 13. Authors' Address | 13. Authors' Address | |||
| Christian Martin | Christian Martin | |||
| Verizon Internet Services | Verizon | |||
| 1880 Campus Commons Dr | 1880 Campus Commons Dr | |||
| Reston, VA 20191 | Reston, VA 20191 | |||
| Email: cmartin@gnilink.net | Email: cmartin@verizon.com | |||
| Brad Neal | Brad Neal | |||
| Broadwing Communications | Broadwing Communications | |||
| 1835 Kramer Lane - Suite 100 | 1835 Kramer Lane - Suite 100 | |||
| Austin, TX 78758 | Austin, TX 78758 | |||
| USA | USA | |||
| Email: bneal@broadwing.com | Email: bneal@broadwing.com | |||
| Stefano Previdi | Stefano Previdi | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| End of changes. 10 change blocks. | ||||
| 15 lines changed or deleted | 10 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||