Network Working Group Acee Lindem Internet Draft Naiming Shen Expiration Date: February 2005 Redback Networks Rahul Aggarwal Juniper Networks Scott Shaffer Level 3 Communications JP Vasseur Cisco Systems, Inc Extensions to OSPF for Advertising Optional Router Capabilities draft-ietf-ospf-cap-03.txt Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 It is useful for routers in an OSPF routing domain to know the capabilities of their neighbors and other routers in the OSPF routing domain. This draft proposes extensions to OSPF for advertising optional router capabilities. A new Router Information (RI) opaque LSA is proposed for this purpose. 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 [3]. draft-ietf-ospf-cap-03.txt [Page 1] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 1. Motivation It is useful for routers in an OSPF routing domain to know the capabilities of their neighbors and other routers in the OSPF routing domain. This can be useful for various applications: o In MPLS Traffic Engineering (TE), it can be used as a discovery mechanism [7, 8] to announce a LSR's TE capabilities like Path Computation Server capability (Capability of an LSR to be a Path Computation Server for TE LSP path computation) or the intention of an LSR to be part of a particular MPLS TE mesh group. o For network management and troubleshooting. It gives operators a network wide view of OSPF capabilities on different routers. The presence of a capability on a given router implies that the software version supports the capability and the router is configured to support it. On the other hand, the absence of an expected capability on a particular router can imply either misconfiguration or an incorrect software version. Hence, this capability information can be used to track problems resulting from misconfiguration or an incorrect software version. OSPF uses the options field in the hello packet to advertise optional router capabilities [1]. However, all the bits in this field have been allocated and there is no way to advertise new optional or MPLS TE capabilities. This document proposes extensions to OSPF to advertise these optional capabilities. For existing OSPF capabilities, this advertisement will be used primarily for informational purposes. For MPLS TE features, it is used for advertisement and discovery. Future OSPF features could also use this mechanism for advertisement and discovery. draft-ietf-ospf-cap-03.txt [Page 2] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 2. OSPF Router Information (RI) Opaque LSA OSPF routers will optionally advertise their optional capabilities in an area-scoped, local scope, or AS-scoped Opaque-LSA [2]. If a router does not advertise this LSA, it does not imply that the router does not support one or more of the defined capabilities. For existing OSPF capabilities, this advertisement will be used primarily for informational purposes. For MPLS TE features, it is used for advertisement and discovery. Future OSPF features could also use this mechanism for advertisement and discovery. The RI opaque LSA will be originated when one of the advertised capabilities is configured or changed. The Router Information LSA will have an Opaque type of 4 and Opaque ID of 0. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LS age | Options | 9, 10 or 11 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 4 | 0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Advertising Router | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LS sequence number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LS checksum | length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | +- TLV's -+ | ... | Figure 2. OSPF Router Information LSA draft-ietf-ospf-cap-03.txt [Page 3] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 The format of the TLV's within the body of a router information LSA is the same as the format used by the Traffic Engineering Extensions to OSPF [4]. The LSA payload consists of one or more nested Type/Length/Value (TLV) triplets. The format of each TLV is: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Value... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3. TLV Format The Length field defines the length of the value portion in octets (thus a TLV with no value portion would have a length of zero). The TLV is padded to four-octet alignment; padding is not included in the length field (so a three octet value would have a length of three, but the total size of the TLV would be eight octets). Nested TLV's are also 32-bit aligned. For example, a one byte value would have the length field set to 1, and three bytes of padding would be added to the end of the value portion of the TLV. Unrecognized types are ignored. 2.1 OSPF Router Capabilities TLV The first defined TLV in the body of an RI opaque LSA is the Router Capabilities TLV. A router advertising an RI opaque LSA SHOULD include the Router Capabilities TLV and SHOULD correctly identify the status of the capabilities defined in section 2.2. The format of the Router Capabilities TLV is as follows: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Capabilities | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 4. OSPF Router Capabilities TLV draft-ietf-ospf-cap-03.txt [Page 4] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 Type A 16 bit field set to 1. Length A 16 bit field that indicates the length of the value portion in bytes. Its set to N x 4 octets. N starts from 1 and can be increased when there is a need. Each 4 octets are referred to as a capability flag. Value This comprises one or more capability flags. For each 4 octets, the bits are indexed from the most significant to the least significant, where each bit represents one router capability. When the first 32 capabilities are defined, a new capability flag will be used to accommodate the next capability. The Router Capabilities TLV MAY be followed by optional TLV's that further specify a capability. 2.2 Reserved OSPF Router Capability Bits The following bits in the first capability flag have been assigned: Bit Capabilities 0-3 Reserved 4 OSPF graceful restart capable [5] 5 OSPF graceful restart helper [5] 6 Stub Router support [6] 7 Traffic Engineering support [4] 8 OSPF point-to-point over LAN [9] 9 OSPF Path Computation Server discovery [7, 8] 10-31 Future assignments draft-ietf-ospf-cap-03.txt [Page 5] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 2.3 Flooding Scope of the Router Information LSA The flooding scope for a Router Information opaque LSA is determined by the LSA type. A type 9 (link-scope), type 10 (area-scoped), or a type 11 (AS-scoped) opaque LSA may be flooded. If a type 11 opaque LSA is chosen, the originating router should also advertise type 10 LSA(s) into any attached NSSA/stub area(s). An OSPF router MAY advertise different capabilities when both NSSA/stub area type 10 LSA(s) and an AS scoped type 11 opaque LSA is advertised. The choice of flooding scope is made by the advertising router and is a matter of local policy. The originating router MAY advertise multiple RI opaque LSAs as long as the flooding scopes differ. TLV flooding scope rules will be specified on a per-TLV basis. 3. Security Consideration This memo does not create any new security issues for the OSPF protocol. Security considerations for the base OSPF protocol are covered in [1]. 4. Acknowledgments The idea for this work grew out of a conversation with Andrew Partan and we would like to thank him for his contribution. The authors would like to thanks Peter Psenak for his review and helpful comments early versions of the draft. draft-ietf-ospf-cap-03.txt [Page 6] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 5. IANA Considerations A new opaque LSA type will need to be assigned by IANA. Additionally, IANA will need to have registries for the Router Information opaque LSA TLV's. The TLV assignee will be responsible for allocation of any sub-TLV's for the IANA assigned TLV. All TLV's and sub-TLV's will be subject to OSPF WG review. 6. References Normative References [1] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, July 1998. [2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement Level", BCP 14, RFC 2119, March 1997. Informative References [4] Katz, D., D. Yeung and K. Kompella, "Traffic Engineering Extensions to OSPF", RFC 3630, September 2003. [5] Moy, J., P. Pillay-Esnault and A. Lindem, "OSPF Graceful OSPF Restart", RFC 3623, November 2003. [6] Retana, A., et al, "OSPF Stub Router Advertisement", RFC 3137, June 2001. [7] Vasseur, J., P. Psenak, "Traffic Engineering Capability TLV for OSPF", Internet Draft, work in progress. [8] Vasseur, J., et al, "RSVP Path computation request and reply messages", draft-vasseur-mpls-computation-rsvp-te-03.txt, work in progress [9] N. Shen, et al, "Point-to-point operation over LAN in link-state-routing protocols", Internet Draft, work in progress. draft-ietf-ospf-cap-03.txt [Page 7] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 7. Author Information Acee Lindem Redback Networks 350 Holger Way San Jose, CA 95134 e-mail: acee@redback.com Naiming Shen Redback Networks 350 Holger Way San Jose, CA 95134 e-mail: naiming@redback.com Rahul Aggarwal Juniper Networks 1194 N. Mathilda Ave. Sunnyvale, CA 94089 USA e-mail: rahul@juniper.net Scott Shaffer Level 3 Communications e-mail: scott.shaffer@level3.com JP Vasseur Cisco Systems, Inc. 300 Apollo Drive Chelmsford, MA 01824 e-mail: jpv@cisco.com draft-ietf-ospf-cap-03.txt [Page 8] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 8. Full Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78 and except as set forth therein, the authors retain all their rights. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. draft-ietf-ospf-cap-03.txt [Page 9] Internet Draft draft-ietf-ospf-cap-03.txt Jul 2004 9. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. 10. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. draft-ietf-ospf-cap-03.txt [Page 10]