draft-ietf-isis-purge-tlv-02.txt   draft-ietf-isis-purge-tlv-03.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: December 9, 2010 Cisco Systems, Inc. Expires: December 17, 2010 Cisco Systems, Inc.
J. Dong J. Dong
Huawei Technologies Huawei Technologies
June 7, 2010 June 15, 2010
Purge Originator Identification TLV for IS-IS Purge Originator Identification TLV for IS-IS
draft-ietf-isis-purge-tlv-02 draft-ietf-isis-purge-tlv-03
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 December 9, 2010. This Internet-Draft will expire on December 17, 2010.
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 3, line 32 skipping to change at page 3, line 32
purge when they receive a corrupted LSP. purge when they receive a corrupted LSP.
2. Requirements Language 2. Requirements Language
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
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. The Purge Originator Identification TLV 3. The Purge Originator Identification TLV
This document defines a TLV to be included in purges. This TLV This document defines a TLV to be included in purges. If an IS
carries the system ID of the IS generating the purge, or, in a proxy generates a purge, it SHOULD include this TLV in the purge with its
mode, carries the system ID of the IS that first saw the purge and own system ID. If an IS receives a purge that does not include this
inserted this TLV, as well as the system ID of the system that it TLV, then it SHOULD add this TLV with both its own system ID and the
received the purge from. system ID of the IS that it received the purge from.
This allows ISs receiving purges to log the system ID of the This allows ISs receiving purges to log the system ID of the
originator, or the upstream source of the purge. This makes it much originator, or the upstream source of the purge. This makes it much
easier for the network administrator to locate the origin of the easier for the network administrator to locate the origin of the
purge and thus the cause of the purge. Similarly, this TLV is purge and thus the cause of the purge. Similarly, this TLV is
helpful to developers in lab situations. helpful to developers in lab situations.
The Purge Originator Identification TLV is defined as: The Purge Originator Identification TLV is defined as:
CODE - 13 CODE - 13
LENGTH - total length of the value field. LENGTH - total length of the value field.
VALUE - VALUE -
Number of system IDs carried in this TLV (1 octet) -- Only the Number of system IDs carried in this TLV (1 octet) -- Only the
values 1 and 2 are defined. values 1 and 2 are defined.
System ID of the Intermediate System that inserted this TLV. System ID of the Intermediate System that inserted this TLV.
The system ID of the Intermediate System that the purge was System ID of the Intermediate System that the purge was received
received from. (optional) from. (optional)
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]. This TLV MAY also be included in purges. This will 137) [RFC5301]. This TLV MAY also be included in purges. This will
further aid in the rapid identification of the system that generated further aid in the rapid identification of the system that generated
the purge. the purge.
Implementations SHOULD include the Purge Originator Identification Implementations SHOULD include the Purge Originator Identification
TLV in addition to the Dynamic hostname TLV. TLV in addition to the Dynamic hostname TLV.
5. Security Considerations 5. Security Considerations
If the proposed TLV or the Dynamic hostname TLV is used in If the Purge Originator Identification TLV or the Dynamic hostname
conjunction with IS-IS authentication mechanisms [RFC5304][RFC5310], TLV is used in conjunction with IS-IS authentication mechanisms
the purge LSP is constructed as follows. First, the original [RFC5304][RFC5310], the purge LSP is constructed or modified as
contents of the LSP are removed, leaving only the LSP header, then follows. First, the original contents of the LSP are removed,
the Purge Originator Identification TLV and/or the Dynamic hostname leaving only the LSP header, then the Purge Originator Identification
TLV are added, and then the IS-IS authentication TLV is added. TLV and/or the Dynamic hostname TLV are added, and then the IS-IS
authentication TLV is added.
Legacy systems that implement [RFC5304] or [RFC5310] MUST discard Legacy systems that implement [RFC5304] or [RFC5310] MUST discard
purges with these additional TLVs. This is not thought to be a purges with these additional TLVs. This is not thought to be a
significant operational issue as the loss of purges is typically not significant operational issue as the loss of purges is typically not
critical. critical.
6. Functional Changes 6. Functional Changes
This document amends the behavior specified in [RFC5301], [RFC5304] This document amends the behavior specified in [RFC5301], [RFC5304]
and [RFC5310]. ISs that receive purges with the Purge Originator and [RFC5310]. ISs that receive purges with the Purge Originator
Identification TLV or the Dynamic hostname TLV with valid Identification TLV or the Dynamic hostname TLV with valid
authentication MUST NOT discard the PDU and SHOULD process it authentication MUST NOT discard the PDU and SHOULD process it
normally. ISs that receive purges with the Purge Originator normally. The Purge Originator Identification TLV or Dynamic
Identification TLV or the Dynamic hostname TLV MUST be accepted and hostname TLV MUST NOT be removed from the purge prior to propagation.
processed as a normal purge. The Purge Originator Identification TLV If multiple purges are received for the same LSP fragment, then the
or Dynamic hostname TLV MUST NOT be removed from the purge prior to implementation MAY propagate any one of the purges.
propagation. If multiple purges are received for the same LSP
fragment, then the implementation MAY propagate any one of the
purges.
7. IANA Considerations 7. IANA Considerations
RFC EDITOR NOTE: This section to be removed upon publication. RFC EDITOR NOTE: This section to be removed upon publication.
This document requests that IANA assign a code point for this TLV This document requests that IANA assign a code point for this TLV
from the IS-IS 'TLV Codepoints Registry'. from the IS-IS 'TLV Codepoints Registry'.
8. Acknowledgments 8. Acknowledgments
 End of changes. 8 change blocks. 
24 lines changed or deleted 22 lines changed or added

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