idnits 2.17.00 (12 Aug 2021) /tmp/idnits44703/draft-ietf-ospf-routable-ip-address-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 15, 2014) is 2774 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4970 (Obsoleted by RFC 7770) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Xu 3 Internet-Draft Huawei 4 Intended status: Standards Track U. Chunduri 5 Expires: April 18, 2015 Ericsson 6 M. Bhatia 7 Ionos Networks 8 October 15, 2014 10 Carrying Routable IP Addresses in OSPF RI LSA 11 draft-ietf-ospf-routable-ip-address-01 13 Abstract 15 This document proposes two new TLVs within the body of the OSPF 16 Router Information (RI) Opaque LSA, called Routable IPv4 Address TLV 17 and Routable IPv6 Address TLV. Here the term OSPF means both OSPFv2 18 and OSPFv3. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on April 18, 2015. 37 Copyright Notice 39 Copyright (c) 2014 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Routable IPv4 Address TLV . . . . . . . . . . . . . . . . . . 3 58 4. Routable IPv6 Address TLV . . . . . . . . . . . . . . . . . . 3 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 61 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 62 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 8.2. Informative References . . . . . . . . . . . . . . . . . 4 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 There are several situations where it is required for OSPF routers in 70 one area to find correlations between routable IP addresses and 71 capabilities of OSPF routers in another area. One example is the 72 Entropy Label Capability (ELC) advertisement [I-D.xu-ospf-mpls-elc] 73 across the OSPF domain. In this example, assume the ELC TLV 74 originated by a router in one area is propagated to another area. 75 Those routers in the latter area need to find routable IP addresses 76 of the router originating that ELC TLV before inserting the Entropy 77 Label (EL) for packets going to the Label Switch Path (LSP) tunnel 78 towards one of the above routable IP addresses. Another example is 79 the S-BFD discriminator distribution 80 [I-D.bhatia-ospf-sbfd-discriminator] across the OSPF domain. In this 81 example, assume the S-BFD Discriminator TLV originated by a router in 82 one area is propagated to another area. Those routers in the latter 83 area need to find routable IP addresses of the router originating 84 that S-BFD Discriminator TLV so as to set up S-BDF sessions with that 85 originating router. 87 However, in the OSPF Router Information (RI) Opaque LSA as defined in 88 [RFC4970], which is used by OSPF routers to announce their 89 capabilities, there is no such field for containing routable IP 90 addresses of the originating router. Therefore, this document 91 propose two new TLVs within the body of OSPF RI LSA, called Routable 92 IPv4 Address TLV and Routable IPv6 Address TLV, which are used to 93 carry routable IPv4 and IPv6 addresses respectively. Here the term 94 OSPF means both OSPFv2 and OSPFv3. 96 1.1. Requirements Language 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in RFC 2119 [RFC2119]. 102 2. Terminology 104 This memo makes use of the terms defined in [RFC4970]. 106 3. Routable IPv4 Address TLV 108 A new TLV within the body of the OSPF RI Opaque LSA, called Routable 109 IPv4 Address TLV is defined to carry one or more routable IPv4 110 addresses of the router originating the RI LSA. The Type of this TLV 111 is TBD, the Length is variable (multiple of 4), and the Value field 112 contains one or more routable IPv4 addresses of the router 113 originating the RI LSA. This TLV is applicable to OSPFv2 and for 114 IPv4 Address Families (AFs) of OSPFv3 [RFC5838]. The scope of the 115 advertisement MUST be domain-wide as mapping between the originator 116 and advertised address is required only when crossing the area 117 boundaries. 119 4. Routable IPv6 Address TLV 121 A new TLV within the body of the OSPFv3 RI Opaque LSA, called 122 Routable IPv6 Address TLV is defined to carry one or more routable 123 IPv6 global addresses of the router originating the RI LSA. The Type 124 of this TLV is TBD, the Length is variable (multiple of 16), and the 125 Value field contains one or more routable IPv6 global addresses of 126 the router originating the RI LSA. This TLV is only applicable to 127 OSPFv3. The scope of the advertisement MUST be domain-wide as 128 mapping between the originator and advertised address is required 129 only when crossing the area boundaries. 131 5. Acknowledgements 133 Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel M. 134 Halpern, Wes George, Les Ginsberg, Abhay Roy, Mach Chen, Peter Psenak 135 and Acee Lindem for their support and valuable comments on this 136 draft. 138 6. IANA Considerations 140 This document includes a request to IANA to allocate two TLV type 141 codes for the new TLVs proposed in Section 3 and Section 4 of this 142 document from OSPF Router Information (RI) TLVs Registry defined by 143 [RFC4970]. 145 7. Security Considerations 147 This document describes a mechanism for advertising routable IP 148 address information through OSPF Router Information Opaque LSA and 149 does not introduce any new security issues other than what is 150 specified by [RFC4970]. 152 8. References 154 8.1. Normative References 156 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 157 Requirement Levels", BCP 14, RFC 2119, March 1997. 159 [RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S. 160 Shaffer, "Extensions to OSPF for Advertising Optional 161 Router Capabilities", RFC 4970, July 2007. 163 8.2. Informative References 165 [I-D.bhatia-ospf-sbfd-discriminator] 166 Bhatia, M., Ranganath, T., Pignataro, C., and S. Aldrin, 167 "OSPF extensions to advertise S-BFD Target Discriminator", 168 draft-bhatia-ospf-sbfd-discriminator-00 (work in 169 progress), May 2014. 171 [I-D.xu-ospf-mpls-elc] 172 Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S. 173 Litkowski, "Signaling Entropy Label Capability Using 174 OSPF", draft-xu-ospf-mpls-elc-01 (work in progress), 175 October 2014. 177 [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 178 Aggarwal, "Support of Address Families in OSPFv3", RFC 179 5838, April 2010. 181 Authors' Addresses 183 Xiaohu Xu 184 Huawei 186 Email: xuxiaohu@huawei.com 188 Uma Chunduri 189 Ericsson 191 Email: uma.chunduri@ericsson.com 192 Manav Bhatia 193 Ionos Networks 195 Email: manav@ionosnetworks.com