Network Working Group X. Xu Internet-Draft Huawei Intended status: Standards Track U. Chunduri Expires: December 6, 2014 Ericsson M. Bhatia Alcatel-Lucent June 4, 2014 Carrying Routable IP Addresses in OSPF RI LSA draft-xu-ospf-routable-ip-address-00 Abstract This document proposes two new TLVs within the body of the OSPF Router Information (RI) Opaque LSA, called Routable IPv4 Address TLV and Routable IPv6 Address TLV. Here the OSPF means boths OSPFv2 and OSPFv3. 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 December 6, 2014. Copyright Notice Copyright (c) 2014 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 Xu, et al. Expires December 6, 2014 [Page 1] Internet-Draft June 2014 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Routable IPv4 Address TLV . . . . . . . . . . . . . . . . . . 3 4. Routable IPv6 Address TLV . . . . . . . . . . . . . . . . . . 3 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 7. Security Considerations . . . . . . . . . . . . . . . . . . . 3 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 8.2. Informative References . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction There are several situations where it is required for OSPF routers in one area to find correlations between routable IP addresses and capabilities of OSPF routers in another area. One example is the Entropy Label Capability (ELC) advertisement [I-D.xu-ospf-mpls-elc] across the OSPF domain. In this example, assume the ELC TLV orginated by a router in one area is propagated to another area, those routers in the latter area need to find routable IP addresses of the router originating that ELC TLV before inserting the Entropy Label (EL) for packets going to the Label Switch Path (LSP) tunnel towards one of the above routable IP addresses. Another example is the S-BFD discriminator distribution [I-D.bhatia-ospf-sbfd-discriminator] across the OSPF domain. In this example, assume the S-BFD Discriminator TLV orginated by a router in one area is propagated to another area, those routers in the latter area need to find routable IP addresses of the router originating that S-BFD Discriminator TLV so as to set up S-BDF seesions with that originating router. However, in the OSPF Router Information (RI) Opaque LSA as defined in [RFC4970], which is used by OSPF routers to announce their capabilities, there is no such field for containing routable IP addresses of the originating router. Therefore, this document propose two new TLVs within the body of OSPF RI LSA, called Routable IPv4 Address TLV and Routable IPv6 Address TLV, which are used to carry routable IPv4 and IPv6 addresses respectively. Here the OSPF means boths OSPFv2 and OSPFv3. Xu, et al. Expires December 6, 2014 [Page 2] Internet-Draft June 2014 1.1. Requirements Language 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 [RFC2119]. 2. Terminology This memo makes use of the terms defined in [RFC4970]. 3. Routable IPv4 Address TLV A new TLV within the body of the OSPFv2 RI Opaque LSA, called Routable IPv4 Address TLV is defined to carry one or more routable IPv4 addresses of the router originating the RI LSA. The Type of this TLV is TBD, the Length is variable (multiple of 4), and the Value field contains one or more routable IPv4 addresses of the router originating the RI LSA. This TLV is only applicable to OSPFv2. The scope of the advertisement depends on the application but it is recommended that it SHOULD be domain-wide. 4. Routable IPv6 Address TLV A new TLV within the body of the OSPFv3 RI Opaque LSA, called Routable IPv6 Address TLV is defined to carry one or more routable IPv6 global addresses of the router originating the RI LSA. The Type of this TLV is TBD, the Length is variable (multiple of 16), and the Value field contains one or more routable IPv6 global addresses of the router originating the RI LSA. This TLV is only applicable to OSPFv3. The scope of the advertisement depends on the application but it is recommended that it SHOULD be domain-wide. 5. Acknowledgements Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel M. Halpern, Wes George, Les Ginsberg and Acee Lindem for their valuable comments on the initial idea of this draft. 6. IANA Considerations This document includes a request to IANA to allocate two TLV type codes for the new RI LSA TLVs proposed in this document respectively. 7. Security Considerations This document does not introduce any new security risk. Xu, et al. Expires December 6, 2014 [Page 3] Internet-Draft June 2014 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S. Shaffer, "Extensions to OSPF for Advertising Optional Router Capabilities", RFC 4970, July 2007. 8.2. Informative References [I-D.bhatia-ospf-sbfd-discriminator] Bhatia, M., Ranganath, T., Pignataro, C., and S. Aldrin, "OSPF extensions to advertise S-BFD Target Discriminator", draft-bhatia-ospf-sbfd-discriminator-00 (work in progress), May 2014. [I-D.xu-ospf-mpls-elc] Xu, X., Kini, S., Sivabalan, S., and C. Filsfils, "Signaling Entropy Label Capability Using OSPF", draft-xu- ospf-mpls-elc-00 (work in progress), December 2013. Authors' Addresses Xiaohu Xu Huawei Email: xuxiaohu@huawei.com Uma Chunduri Ericsson Email: uma.chunduri@ericsson.com Manav Bhatia Alcatel-Lucent Email: manav.bhatia@alcatel-lucent.com Xu, et al. Expires December 6, 2014 [Page 4]