Internet Draft Udo Neustadter Document: draft-udo-ospf-vendatt-00.txt Tropic Networks Expires: November 2003 May 2003 OSPF TE LSA Extensions in Support of Vendor/Organization Specific Attributes Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of [RFC-2026]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract Type-length-value structures have made their way into the messages distributed opaquely by OSPF. This document specifies an interoperable method to add vendor specific extensions to existing message structures. Conventions used in this document 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]. Table of Contents 1. Introduction...................................................2 2. Vendor Attributes TLV format...................................2 Neustadter Expires - November 2003 [Page 1] Internet Draft draft-udo-ospf-vendatt-00.txt May 2003 2.1 Vendor Attributes in the Router Address TLV................3 2.2 Vendor Attributes in the TE Link TLV.......................3 3. Compatibility issues...........................................3 Security Considerations...........................................4 IANA Considerations...............................................4 References........................................................4 Author's Addresses................................................4 1. Introduction OSPF can build a Traffic Engineering database for a node using the mechanisms defined in [OSPF-TE] and [OSPF-G]. The TE LSAs that make up the database are encoded in a Type-Length-Value, TLV, format. This encoding scheme is very flexible and allows for a wide range of extensions. Organizations at the forefront of the TE and GMPLS technology are able, within the framework, to define their own set of (sub-)TLVs for specific extensions that only they can/want to support. This document defines an encoding for a vendor TLV that uniquely identifies the organization, so that there is no risk of collision in picking a value from the type range reserved for vendor specific extensions. The unique identifier specified to distinguish a particular vendor is the vendors/organizations SMI Network management enterprise code. This encoding method for vendor specific data simplifies the process of defining the vendor TLV by eliminating the need of an Expert Review and the redundant registration of the vendor with IANA. 2. Vendor Attributes TLV format The vendor attribute TLV, or in short the vendatt TLV, has a sub-TLV type defined in the scope of the parent TLV. The sections below define the values in the scope of the TE LSA Router Address and Link top level TLVs. The length in the vendatt TLV represents the total length of the value field. The length must be at least 4. The value field MUST contain the SMI Network management enterprise code for the vendor or organization, encoded as a 32 bit value in network byte order. The enterprise code MAY be followed by an arbitrary set of bytes encoded in a TLV or other choice of format, as the organization decides. The vendatt TLV format is defined below: Neustadter Expires - November 2003 [Page 2] Internet Draft draft-udo-ospf-vendatt-00.txt May 2003 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | vendatt sub-TLV type | length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | enterprise code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | enterprise specific data | | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2.1 Vendor Attributes in the Router Address TLV The vendatt TLV can be used as a sub-TLV in the Router Address TLV. The sub-TLV type 1(TBD-IANA)is assigned for this purpose. In tabular form the sub-TLVs defined in this memo for use in the Router Address TLV are: Sub-TLV Type Length Name (TBD)1 variable Vendor Attributes 2.2 Vendor Attributes in the TE Link TLV The vendatt TLV can be used as a sub-TLV in the Link TLV. The sub-TLV type 17(TBD-IANA)is assigned for this purpose. In tabular form the sub-TLVs defined in this memo for use in the Link TLV are: Sub-TLV Type Length Name (TBD)17 variable Vendor Attributes 3. Compatibility issues The mechanism introduced in this memo makes it possible for: - a vendorĘs equipment to identify their sub-TLVs as assigned to it - a vendorĘs equipment to ignore other-vendorĘs sub-TLVs - a network operator to avoid unintended side-effects of multi- vendor TE networks Routers that do not implement these extensions are expected to silently ignore the unknown TLVs. Neustadter Expires - November 2003 [Page 3] Internet Draft draft-udo-ospf-vendatt-00.txt May 2003 Security Considerations The extensions proposed in this document do not raise any new security concerns. However, as the content of the vendor specific data is opaque to the mechanism, it is left the specific vendor or organization to consider their security requirements and solutions. Some usages would prefer for the data to be in the clear, for others security through obscurity might be enough, and yet other applications might require the use of more powerful security concepts. IANA Considerations This memo introduces one new sub-TLV of the Router Address TLV in the TE Opaque LSA for OSPFv2. This memo also introduces one new sub-TLV of the TE Link TLV in the TE Opaque LSA for OSPFv2. [OSPF-TE] says that the sub-TLVs of the TE link TLV in the range of 10-32767 must be assigned by Expert Review and must be registered with IANA. References [RFC-2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [OSPF-TE] Katz, D., Yeung, D., "Traffic Engineering Extensions to OSPF", work in progress. [OSPF-G] Kompella, K., Rekhter, Y., et al, "OSPF Extensions in Support of Generalized MPLS," work in progress. Author's Addresses Udo Neustadter Tropic Networks Inc. 135 Michael Cowpland Drive Kanata, Ontario, Canada, K2M 2E9 Email: udo.neustadter@tropicnetworks.com Neustadter Expires - November 2003 [Page 4]