idnits 2.17.1 draft-xu-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 (June 4, 2014) is 3614 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. -------------------------------------------------------------------------------- 2 Network Working Group X. Xu 3 Internet-Draft Huawei 4 Intended status: Standards Track U. Chunduri 5 Expires: December 6, 2014 Ericsson 6 M. Bhatia 7 Alcatel-Lucent 8 June 4, 2014 10 Carrying Routable IP Addresses in OSPF RI LSA 11 draft-xu-ospf-routable-ip-address-00 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 OSPF means boths OSPFv2 and 18 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 December 6, 2014. 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 . . . . . . . . . . . . . . . . . . . 3 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 orginated 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 orginated 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 seesions 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 OSPF 94 means boths 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 OSPFv2 RI Opaque LSA, called 109 Routable IPv4 Address TLV is defined to carry one or more routable 110 IPv4 addresses of the router originating the RI LSA. The Type of 111 this TLV is TBD, the Length is variable (multiple of 4), and the 112 Value field contains one or more routable IPv4 addresses of the 113 router originating the RI LSA. This TLV is only applicable to 114 OSPFv2. The scope of the advertisement depends on the application 115 but it is recommended that it SHOULD 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 depends on the application 126 but it is recommended that it SHOULD be domain-wide. 128 5. Acknowledgements 130 Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel M. 131 Halpern, Wes George, Les Ginsberg and Acee Lindem for their valuable 132 comments on the initial idea of this draft. 134 6. IANA Considerations 136 This document includes a request to IANA to allocate two TLV type 137 codes for the new RI LSA TLVs proposed in this document respectively. 139 7. Security Considerations 141 This document does not introduce any new security risk. 143 8. References 145 8.1. Normative References 147 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 148 Requirement Levels", BCP 14, RFC 2119, March 1997. 150 [RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S. 151 Shaffer, "Extensions to OSPF for Advertising Optional 152 Router Capabilities", RFC 4970, July 2007. 154 8.2. Informative References 156 [I-D.bhatia-ospf-sbfd-discriminator] 157 Bhatia, M., Ranganath, T., Pignataro, C., and S. Aldrin, 158 "OSPF extensions to advertise S-BFD Target Discriminator", 159 draft-bhatia-ospf-sbfd-discriminator-00 (work in 160 progress), May 2014. 162 [I-D.xu-ospf-mpls-elc] 163 Xu, X., Kini, S., Sivabalan, S., and C. Filsfils, 164 "Signaling Entropy Label Capability Using OSPF", draft-xu- 165 ospf-mpls-elc-00 (work in progress), December 2013. 167 Authors' Addresses 169 Xiaohu Xu 170 Huawei 172 Email: xuxiaohu@huawei.com 174 Uma Chunduri 175 Ericsson 177 Email: uma.chunduri@ericsson.com 179 Manav Bhatia 180 Alcatel-Lucent 182 Email: manav.bhatia@alcatel-lucent.com