idnits 2.17.00 (12 Aug 2021) /tmp/idnits14619/draft-acee-ospf-bgp-rr-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 (March 13, 2017) is 1895 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Lindem 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track K. Patel 5 Expires: September 14, 2017 Arrcus 6 S. Zandi 7 LinkedIn 8 March 13, 2017 10 OSPF Extensions for Advertising/Signaling BGP Route Reflector 11 Information 12 draft-acee-ospf-bgp-rr-00.txt 14 Abstract 16 This document specifies an OSPF Router Information (RI) TLV to 17 advertise the BGP Router Reflector capability and peering 18 information. This information can be used by BGP Router Reflector 19 clients to dynamically learn and establish sessions with BGP Router 20 Reflectors in the routing domain. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on September 14, 2017. 39 Copyright Notice 41 Copyright (c) 2017 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 2 58 2. OSPF BGP Route Reflector TLV . . . . . . . . . . . . . . . . 2 59 3. OSPF Router Information (RI) Opaque LSAs . . . . . . . . . . 4 60 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 61 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 62 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 6.2. Informative References . . . . . . . . . . . . . . . . . 5 65 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 5 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 68 1. Introduction 70 This document specifies an OSPF Router Information (RI) TLV [OSPF-RI] 71 to advertise the BGP Router Reflector [BGP-RR] capability and peering 72 information. This information can be used by BGP Router Reflector 73 clients to dynamically learn and establish sessions with BGP Router 74 Reflectors in the routing domain. 76 1.1. Requirements Notation 78 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 79 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 80 document are to be interpreted as described in [RFC-KEYWORDS]. 82 2. OSPF BGP Route Reflector TLV 84 The BGP Router Reflector TLV can be used to advertise the route 85 reflector capability, local AS number, BGP peering address, and 86 supported AFI/SAFI pairs using an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] 87 router using the OSPF Router Information LSA [OSPF-RI]. The OSPF 88 Router Information LSA can be advertised in either area or AS scoped 89 RI LSAs. The BGP Router Reflector TLV consists of the following 90 fields: 92 0 1 2 3 93 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 94 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 95 | Local AS | 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 | Address Family| Reserved | 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | IPv4/IPv6 Address | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 | IPv6 Address | 102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 103 | IPv6 Address | 104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 105 | IPv6 Address | 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | AFI | SAFI | AFI | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | AFI | SAFI | o o o 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 Length The length will be 12 for IPv4 peering addresses or 113 24 for IPv6 peering addresses plus 3 * the number 114 of AFI/SAFI pairs. 116 Local AS The Router-Reflector's local AS number. This can 117 either be used for AS match checking or certain 118 situations where the client's AS doesn't match the 119 route reflectors. 121 Address IANA Address family (1 for IPv4 or 2 for IPv6) 122 Family 124 Address Local IPv4 or IPv6 Address used for BGP peering. 126 AFI/SAFI Address Family Identifier (AFI)/ Subsequent 127 Address Family Identifier 129 OSPF BGP Route-Reflector TLV 131 o The BGP Route Reflector (RR) TLV MAY be advertised multiple times 132 with different peering addresses and AFI/SAFI pairs and MAY be 133 advertised in multiple OSPF RI LSAs. 135 o If different peering addresses are advertised for the same AFI/ 136 SAFI pair, the decision of whether a BGP client establishes 137 sessions with one or more of the advertised peering addresses is 138 beyond the scope of this document. 140 o If the BGP Router Reflector (RR) TLV has an invalid length or is 141 otherwise malformed, it will not be used for BGP client session 142 establishment. The occurrence of a malformed TLV SHOULD be 143 logged. 145 3. OSPF Router Information (RI) Opaque LSAs 147 The OSPF BGP TLV may optionally be advertised in an area-scoped or 148 AS-scoped OSPFv2 Router Information (RI) opaque LSA or OSPFv3 Router 149 Information (RI) LSA [OSPF-RI]. BGP clients may then use the peering 150 address to establish BGP sessions with the advertising route- 151 reflector. 153 4. Security Considerations 155 Security considerations for the base OSPF protocol are covered in 156 [OSPF] and [OSPFV3]. 158 5. IANA Considerations 160 The document will require the following IANA actions: 162 1. A Router Information TLV type for the BGP Router Reflector TLV 163 will be allocated from the OSPF Router Information (RI) TLVs 164 registry. 166 6. References 168 6.1. Normative References 170 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 172 [OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 173 Shaffer, "Extensions to OSPF for Advertising Optional 174 Router Capabilities", RFC 7770, January 2016. 176 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 177 for IPv6", RFC 5340, July 2008. 179 [RFC-KEYWORDS] 180 Bradner, S., "Key words for use in RFC's to Indicate 181 Requirement Levels", BCP 14, RFC 2119, March 1997. 183 6.2. Informative References 185 [BGP-RR] Bates, T., Chen, E., and R. Chandra, "BGP Route 186 Reflection: An Alternative to Full Mesh Internal BGP 187 (IBGP)", RFC 4456, April 2006. 189 Appendix A. Acknowledgments 191 The RFC text was produced using Marshall Rose's xml2rfc tool. 193 Authors' Addresses 195 Acee Lindem 196 Cisco Systems 197 301 Midenhall Way 198 Cary, NC 27513 199 USA 201 Email: acee@cisco.com 203 Keyur Patel 204 Arrcus 206 Email: keyur@arrcus.com 208 Shawn Zandi 209 LinkedIn 211 Email: szandi@linkedin.com