draft-ietf-isis-purge-tlv-04.txt   draft-ietf-isis-purge-tlv-05.txt 
IS-IS Working Group F. Wei IS-IS Working Group F. Wei
Internet-Draft Y. Qin Internet-Draft Y. Qin
Updates: 5301 5304 5310 Z. Li Updates: 5301 5304 5310 Z. Li
(if approved) China Mobile (if approved) China Mobile
Intended status: Standards Track T. Li Intended status: Standards Track T. Li
Expires: March 5, 2011 Cisco Systems, Inc. Expires: April 27, 2011 Cisco Systems, Inc.
J. Dong J. Dong
Huawei Technologies Huawei Technologies
September 1, 2010 October 24, 2010
Purge Originator Identification TLV for IS-IS Purge Originator Identification TLV for IS-IS
draft-ietf-isis-purge-tlv-04 draft-ietf-isis-purge-tlv-05
Abstract Abstract
At present an IS-IS purge does not contain any information At present an IS-IS purge does not contain any information
identifying the Intermediate System (IS) that generates the purge. identifying the Intermediate System (IS) that generates the purge.
This makes it difficult to locate the source IS. This makes it difficult to locate the source IS.
To address this issue, this document defines a TLV to be added to To address this issue, this document defines a TLV to be added to
purges to record the system ID of the IS generating it. Since normal purges to record the system ID of the IS generating it. Since normal
LSP flooding does not change LSP contents, this TLV should propagate LSP flooding does not change LSP contents, this TLV should propagate
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 5, 2011. This Internet-Draft will expire on April 27, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 21 skipping to change at page 2, line 21
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
3. The Purge Originator Identification (POI) TLV . . . . . . . . . 3 3. The Purge Originator Identification (POI) TLV . . . . . . . . . 3
4. Using the Dynamic Hostname TLV in Purges . . . . . . . . . . . 4 4. Using the Dynamic Hostname TLV in Purges . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . . 5 8. Normative References . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
The IS-IS [ISO 10589] routing protocol has been widely used in large- The IS-IS [ISO 10589] routing protocol has been widely used in large-
scale IP networks because of its strong scalability and fast scale IP networks because of its strong scalability and fast
convergence. convergence.
The IS-IS protocol floods purges throughout an area, regardless of The IS-IS protocol floods purges throughout an area, regardless of
skipping to change at page 4, line 20 skipping to change at page 4, line 20
from. (optional) from. (optional)
The POI TLV SHOULD be found in all purges and MUST NOT be found in The POI TLV SHOULD be found in all purges and MUST NOT be found in
LSPs with a non-zero Remaining Lifetime. LSPs with a non-zero Remaining Lifetime.
4. Using the Dynamic Hostname TLV in Purges 4. Using the Dynamic Hostname TLV in Purges
This document also extends the use of the Dynamic hostname TLV (type This document also extends the use of the Dynamic hostname TLV (type
137) [RFC5301] to further aid in the rapid identification of the 137) [RFC5301] to further aid in the rapid identification of the
system that generated the purge. This TLV MAY be included in purges. system that generated the purge. This TLV MAY be included in purges.
Implementations SHOULD include the Dynamic hostname TLV if the POI Implementations SHOULD include one instance of Dynamic hostname TLV
TLV is included. if the POI TLV is included. Only the local hostname should be
inserted.
5. Security Considerations 5. Security Considerations
Use of the extensions defined here with authentication as defined in Use of the extensions defined here with authentication as defined in
[RFC5304] or [RFC5310] will result in the discarding of purges by [RFC5304] or [RFC5310] will result in the discarding of purges by
legacy systems which are in strict conformance with either of those legacy systems which are in strict conformance with either of those
RFCs. This may compromise the correctness/consistency of the routing RFCs. This may compromise the correctness/consistency of the routing
database unless all ISs in the network support these extensions. NEW database unless all ISs in the network support these extensions.
TEXT: Therefore, all implementations in a domain implementing Therefore, all implementations in a domain implementing
authentication MUST be upgraded to receive the POI TLV before any IS authentication MUST be upgraded to receive the POI TLV before any IS
is allowed to generate a purge with the POI TLV. is allowed to generate a purge with the POI TLV.
More interactions between the POI TLV, the Dynamic hostname TLV, and More interactions between the POI TLV, the Dynamic hostname TLV, and
the Authentication TLV are described in [I-D.li-reg-purge]. the Authentication TLV are described in [I-D.ietf-isis-reg-purge].
6. IANA Considerations 6. IANA Considerations
RFC EDITOR NOTE: This section to be removed upon publication.
This document requests that IANA assign code point 13 for the 'Purge This document requests that IANA assign code point 13 for the 'Purge
Originator Identification' TLV from the IS-IS 'TLV Codepoints Originator Identification' TLV from the IS-IS 'TLV Codepoints
Registry'. The additional values for this TLV should be: IIH:n, Registry'. The additional values for this TLV should be: IIH:n,
LSP:y, SNP:n, Purge:y. LSP:y, SNP:n, Purge:y.
7. Acknowledgments 7. Acknowledgments
Many thanks to Adrian Farrel and Daniel King for your comments to Many thanks to Adrian Farrel and Daniel King for your comments to
improve this document and move it forward. improve this document and move it forward.
The first version of this document was mainly composed by Lianyuan The first version of this document was mainly composed by Lianyuan
Li. Li.
Acknowledgments to the discussion in the mailing list. Some Acknowledgments to the discussion in the mailing list. Some
improvements of this document are based on the discussion. improvements of this document are based on the discussion.
8. Normative References 8. Normative References
[I-D.li-reg-purge] [I-D.ietf-isis-reg-purge]
Li, T., "IS-IS Registry Extension for Purges", Li, T. and L. Ginsberg, "IS-IS Registry Extension for
draft-li-reg-purge-00 (work in progress), August 2010. Purges", draft-ietf-isis-reg-purge-00 (work in progress),
October 2010.
[ISO 10589] [ISO 10589]
ISO, "Intermediate system to Intermediate system routeing ISO, "Intermediate system to Intermediate system routeing
information exchange protocol for use in conjunction with information exchange protocol for use in conjunction with
the Protocol for providing the Connectionless-mode Network the Protocol for providing the Connectionless-mode Network
Service (ISO 8473)", ISO/IEC 10589:2002. Service (ISO 8473)", ISO/IEC 10589:2002.
[ISO TC1] ISO, "Intermediate system to Intermediate system intra- [ISO TC1] ISO, "Intermediate system to Intermediate system intra-
domain routeing information exchange protocol for use in domain routeing information exchange protocol for use in
conjunction with the protocol for providing the conjunction with the protocol for providing the
 End of changes. 10 change blocks. 
15 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/