| < draft-ietf-isis-admin-tags-00.txt | draft-ietf-isis-admin-tags-01.txt > | |||
|---|---|---|---|---|
| Network Working Group Christian Martin | Network Working Group Christian Martin | |||
| INTERNET DRAFT Verizon Internet Services | INTERNET DRAFT Verizon Internet Services | |||
| Expiration Date: January 2003 Brad Neal | Expiration Date: January 2003 Brad Neal | |||
| Broadwing Communications | Broadwing Communications | |||
| Stefano Previdi | Stefano Previdi | |||
| August 2002 Cisco Systems | August 2002 Cisco Systems | |||
| A Policy Control Mechanism is IS-IS Using Administrative Tags | A Policy Control Mechanism in IS-IS Using Administrative Tags | |||
| <draft-ietf-isis-admin-tags-00.txt> | <draft-ietf-isis-admin-tags-01.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 4, line 40 ¶ | skipping to change at page 4, line 40 ¶ | |||
| Consider the network in figure 1. We wish to "leak" L1 prefixes [5] | Consider the network in figure 1. We wish to "leak" L1 prefixes [5] | |||
| with some property, A, from L2 to the L1 router R1. Without policy- | with some property, A, from L2 to the L1 router R1. Without policy- | |||
| groups, there is no way for R2 to know property A prefixes from | groups, there is no way for R2 to know property A prefixes from | |||
| property B prefixes. | property B prefixes. | |||
| R2--------R3--------R4 | R2--------R3--------R4 | |||
| L2 / \ | L2 / \ | |||
| - - - /- - - - - - - - - - - - - - | - - - /- - - - - - - - - - - - - - | |||
| L1 / \ | L1 / \ | |||
| R5----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.1.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." | |||
| End of changes. 2 change blocks. | ||||
| 3 lines changed or deleted | 3 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/ | ||||