idnits 2.17.1 draft-ietf-ospf-routable-ip-address-00.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 (September 25, 2014) is 3502 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) == Outdated reference: A later version (-01) exists of draft-xu-ospf-mpls-elc-00 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group X. Xu 2 Internet-Draft Huawei 3 Intended status: Standards Track U. Chunduri 4 Expires: March 29, 2015 Ericsson 5 M. Bhatia 6 Ionos Networks 7 September 25, 2014 9 Carrying Routable IP Addresses in OSPF RI LSA 10 draft-ietf-ospf-routable-ip-address-00 12 Abstract 14 This document proposes two new TLVs within the body of the OSPF 15 Router Information (RI) Opaque LSA, called Routable IPv4 Address TLV 16 and Routable IPv6 Address TLV. Here the OSPF means both OSPFv2 and 17 OSPFv3. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on March 29, 2015. 36 Copyright Notice 38 Copyright (c) 2014 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Routable IPv4 Address TLV . . . . . . . . . . . . . . . . . . 3 57 4. Routable IPv6 Address TLV . . . . . . . . . . . . . . . . . . 3 58 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . 3 61 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 63 8.2. Informative References . . . . . . . . . . . . . . . . . 4 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 66 1. Introduction 68 There are several situations where it is required for OSPF routers in 69 one area to find correlations between routable IP addresses and 70 capabilities of OSPF routers in another area. One example is the 71 Entropy Label Capability (ELC) advertisement [I-D.xu-ospf-mpls-elc] 72 across the OSPF domain. In this example, assume the ELC TLV 73 originated by a router in one area is propagated to another area, 74 those routers in the latter area need to find routable IP addresses 75 of the router originating that ELC TLV before inserting the Entropy 76 Label (EL) for packets going to the Label Switch Path (LSP) tunnel 77 towards one of the above routable IP addresses. Another example is 78 the S-BFD discriminator distribution 79 [I-D.bhatia-ospf-sbfd-discriminator] across the OSPF domain. In this 80 example, assume the S-BFD Discriminator TLV originated by a router in 81 one area is propagated to another area, those routers in the latter 82 area need to find routable IP addresses of the router originating 83 that S-BFD Discriminator TLV so as to set up S-BDF sessions with that 84 originating router. 86 However, in the OSPF Router Information (RI) Opaque LSA as defined in 87 [RFC4970], which is used by OSPF routers to announce their 88 capabilities, there is no such field for containing routable IP 89 addresses of the originating router. Therefore, this document 90 propose two new TLVs within the body of OSPF RI LSA, called Routable 91 IPv4 Address TLV and Routable IPv6 Address TLV, which are used to 92 carry routable IPv4 and IPv6 addresses respectively. Here the OSPF 93 means both OSPFv2 and OSPFv3. 95 1.1. Requirements Language 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119 [RFC2119]. 101 2. Terminology 103 This memo makes use of the terms defined in [RFC4970]. 105 3. Routable IPv4 Address TLV 107 A new TLV within the body of the OSPF RI Opaque LSA, called Routable 108 IPv4 Address TLV is defined to carry one or more routable IPv4 109 addresses of the router originating the RI LSA. The Type of this TLV 110 is TBD, the Length is variable (multiple of 4), and the Value field 111 contains one or more routable IPv4 addresses of the router 112 originating the RI LSA. This TLV is applicable to OSPFv2 and for 113 IPv4 Address Families (AFs) of OSPFv3 [RFC5838] within the body of 114 the corresponding RI Opaque LSA. The scope of the advertisement MUST 115 be domain-wide. 117 4. Routable IPv6 Address TLV 119 A new TLV within the body of the OSPFv3 RI Opaque LSA, called 120 Routable IPv6 Address TLV is defined to carry one or more routable 121 IPv6 global addresses of the router originating the RI LSA. The Type 122 of this TLV is TBD, the Length is variable (multiple of 16), and the 123 Value field contains one or more routable IPv6 global addresses of 124 the router originating the RI LSA. This TLV is only applicable to 125 OSPFv3. The scope of the advertisement MUST be domain-wide. 127 5. Acknowledgements 129 Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel M. 130 Halpern, Wes George, Les Ginsberg, Abhay Roy, Mach Chen and Acee 131 Lindem for their support and valuable comments on this draft. 133 6. IANA Considerations 135 This document includes a request to IANA to allocate two TLV type 136 codes for the new RI LSA TLVs proposed in this document respectively. 138 7. Security Considerations 140 This document does not introduce any new security risk. 142 8. References 144 8.1. Normative References 146 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 147 Requirement Levels", BCP 14, RFC 2119, March 1997. 149 [RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S. 150 Shaffer, "Extensions to OSPF for Advertising Optional 151 Router Capabilities", RFC 4970, July 2007. 153 8.2. Informative References 155 [I-D.bhatia-ospf-sbfd-discriminator] 156 Bhatia, M., Ranganath, T., Pignataro, C., and S. Aldrin, 157 "OSPF extensions to advertise S-BFD Target Discriminator", 158 draft-bhatia-ospf-sbfd-discriminator-00 (work in 159 progress), May 2014. 161 [I-D.xu-ospf-mpls-elc] 162 Xu, X., Kini, S., Sivabalan, S., and C. Filsfils, 163 "Signaling Entropy Label Capability Using OSPF", draft-xu- 164 ospf-mpls-elc-00 (work in progress), December 2013. 166 [RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R. 167 Aggarwal, "Support of Address Families in OSPFv3", RFC 168 5838, April 2010. 170 Authors' Addresses 172 Xiaohu Xu 173 Huawei 175 Email: xuxiaohu@huawei.com 177 Uma Chunduri 178 Ericsson 180 Email: uma.chunduri@ericsson.com 182 Manav Bhatia 183 Ionos Networks 185 Email: manav@ionosnetworks.com