Extension to Purge Initiator Identification TLV for ISIS in TRILL
Author(s): Gang Chen
This memo specified an extension of ISIS TLV for identifying purge initiator in TRILL environments. With the extension, it's beneficial for operators to nail down the root cause when there is a corrupted Link State Protocol (LSP) data...
Network Working Group G. Chen Internet-Draft China Mobile Intended status: Standards Track July 15, 2013 Expires: January 16, 2014 Extension to Purge Initiator Identification TLV for ISIS in TRILL draft-chen-trill-isis-purge-01 Abstract This memo specified an extension of ISIS TLV for identifying purge initiator in TRILL environments. With the extension, it's beneficial for operators to nail down the root cause when there is a corrupted Link State Protocol (LSP) data unit spread within a layer-2 network. The defined TLV is expected to record Nickname and impacted VLAN information. RBridge should propagate the TLV information without changes in order to flood the information. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 16, 2014. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Chen Expires January 16, 2014 [Page 1] Internet-Draft trill-isis-purge July 2013 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 3. The Purge Initiator Identification TLV . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction It's a increasing demand to build a flexible layer 2 network within a data center network. TRILL(Transparent Interconnection of Lots of Links) was created to provide optimum point-to-point forwarding automatically by performing layer 2 customer bridging with ISIS link state routing. Multi-pathing has been supported for both unicast and multi-destination traffic through extension of ISIS in TRILL contexts. It's required that TRILL implements a separate IS-IS instance from any used by Layer 3, that is, different from the one used by routers.[RFC6325]. Layer 3 IS-IS frames must be distinguished from TRILL IS-IS frames even when those Layer 3 IS-IS frames are transiting an RBridge campus. [RFC6232]specified Purge Originator Identification(POI) TLV for Layer 3 IS-IS frames, which could provide significant signals to facilitate trouble-shooting. Some of TRILL specific extension of TLV have been defined in[RFC6165] [RFC6326].It's desirable to make Layer 2 IS-IS to be able to identify the purge initiator with a distinct indicator compared to POI. In addition, several identification information has been introduced in TRILL protocol, e.g. nickname of RBridge and VLAN. Those information is likely useful to identify the corrupted source in a large layer 2 network. It's worthwhile to map those Layer 3 feature into Layer 2. This memo specified the extension of ISIS TLV for identifying purge initiator in TRILL environments. With the extension, it's beneficial for operators to nail down the root cause when there is a corrupted LSP(Link State Protocol) data unit spread within a layer-2 network. The defined TLV is expected to record the Nickname and impacted VLAN information. RBridge should propagate the TLV information without changes in order to flood the information. 2. Requirements Language Chen Expires January 16, 2014 [Page 2] Internet-Draft trill-isis-purge July 2013 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC 2119]. 3. The Purge Initiator Identification TLV In order to trace the source of purge, the document defined the Purge Initiator Identification(PII) TLV for Layer 2 ISIS system. If an RBridge receives a corrupted LSP and generates purge message, it SHOULD include this TLV with its own nickname and optional VLAN information. If an RBridge receives a purge that does not include this TLV, then it SHOULD add this TLV with its own nickname, optional VLAN and the nickname of the RBridge that it received the purge from. This allows RBridges receiving purges to log the identification of the initiator. This makes it much easier for the network administrator to locate the origin of the purge and thus the cause of the purge. The PII TLV is ISIS TLV and has the following format: +-+-+-+-+-+-+-+-+ | Code | (1 byte) +-+-+-+-+-+-+-+-+ | Length | (1 byte) +-+-+-+-+-+-+-+-+ | Value | (1 bytes) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Nickname | (2 bytes) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VLAN-ID | RESV | (2 bytes) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ o Code: TLV Type, it's to be assigned for the PII type. o Length: It indicates the total length of the value field. o Value: Number of entity information carried in this TLV (1 octet) -- only the values 1 and 2 are defined. o Nickname: If Value is set to 1, Nickname of the Intermediate System that inserted this TLV has been included. If Value is set to 2, Nickname of the Intermediate System from which the purge was received have also been included o VLAN-ID: This carries a 12-bit VLAN identifier that is to idenfity PII is relevant to a specific VLAN.(optional) Chen Expires January 16, 2014 [Page 3] Internet-Draft trill-isis-purge July 2013 o RESV: (4 bits) MUST be sent as zero and ignored on receipt.(optional) 4. Security Considerations For general TRILL protocol security considerations, see the TRILL base protocol standard [RFC6325]. IS-IS security may be used to secure the IS-IS messages discussed here. In that case, some of considerations could be found in [RFC6232] 5. IANA Considerations IANA is asked to assign code point for the 'Trill Purge Initiator Identification' TLV from the IS-IS 'TLV Codepoints' registry. The additional values for this TLV should be IIH:n, LSP:y, SNP:n. 6. Normative References [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC6165] Banerjee, A. and D. Ward, "Extensions to IS-IS for Layer-2 Systems", RFC6165, April 2011. [RFC6232] Wei, F., Qin, Y., Li, Z., Li, T., and J. Dong, "Purge Originator Identification TLV for IS-IS", RFC6232, May 2011. [RFC6325] Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. Ghanwani, "Routing Bridges (RBridges): Base Protocol Specification", RFC6325, July 2011. [RFC6326] Eastlake, D., Banerjee, A., Dutt, D., Perlman, R., and A. Ghanwani, "Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS", RFC6326, July 2011. Author's Address Gang Chen China Mobile 53A,Xibianmennei Ave., Xuanwu District, Beijing 100053 China Email: email@example.com Chen Expires January 16, 2014 [Page 4]