idnits 2.17.1 draft-acee-ospf-bgp-rr-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 (September 7, 2017) is 2423 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: March 11, 2018 Arrcus 6 S. Zandi 7 LinkedIn 8 R. Raszuk 9 Bloomberg LP 10 September 7, 2017 12 OSPF Extensions for Advertising/Signaling BGP Route Reflector 13 Information 14 draft-acee-ospf-bgp-rr-01.txt 16 Abstract 18 This document specifies an OSPF Router Information (RI) TLV to 19 advertise the BGP Router Reflector capability and peering 20 information. This information can be used by BGP Router Reflector 21 clients to dynamically learn and establish sessions with BGP Router 22 Reflectors in the routing domain. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on March 11, 2018. 41 Copyright Notice 43 Copyright (c) 2017 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 2 60 2. OSPF BGP Route Reflector TLV . . . . . . . . . . . . . . . . 2 61 3. OSPF Router Information (RI) Opaque LSAs . . . . . . . . . . 4 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 63 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 64 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 66 6.2. Informative References . . . . . . . . . . . . . . . . . 5 67 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 5 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 70 1. Introduction 72 This document specifies an OSPF Router Information (RI) TLV [OSPF-RI] 73 to advertise the BGP Router Reflector [BGP-RR] capability and peering 74 information. This information can be used by BGP Router Reflector 75 clients to dynamically learn and establish sessions with BGP Router 76 Reflectors in the routing domain. 78 1.1. Requirements Notation 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 82 document are to be interpreted as described in [RFC-KEYWORDS]. 84 2. OSPF BGP Route Reflector TLV 86 The BGP Router Reflector TLV can be used to advertise the route 87 reflector capability, local AS number, BGP peering address, and 88 supported AFI/SAFI pairs using an OSPFv2 [OSPF] or OSPFv3 [OSPFV3] 89 router using the OSPF Router Information LSA [OSPF-RI]. The OSPF 90 Router Information LSA can be advertised in either area or AS scoped 91 RI LSAs. The BGP Router Reflector TLV consists of the following 92 fields: 94 0 1 2 3 95 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 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 | Local AS | 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | Address Family| Reserved | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 | IPv4/IPv6 Address | 102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 103 | IPv6 Address | 104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 105 | IPv6 Address | 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | IPv6 Address | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | AFI | SAFI | AFI | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | AFI | SAFI | o o o 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 Length The length will be 12 for IPv4 peering addresses or 115 24 for IPv6 peering addresses plus 3 * the number 116 of AFI/SAFI pairs. 118 Local AS The Router-Reflector's local AS number. This can 119 either be used for AS match checking or certain 120 situations where the client's AS doesn't match the 121 route reflectors. 123 Address IANA Address family (1 for IPv4 or 2 for IPv6) 124 Family 126 Address Local IPv4 or IPv6 Address used for BGP peering. 128 AFI/SAFI Address Family Identifier (AFI)/ Subsequent 129 Address Family Identifier (SAFI). The AFI/SAFI tuple 130 0/0 will act as a wildcard indicating all configured 131 AFI/SAFIs. 133 OSPF BGP Route-Reflector TLV 135 o The BGP Route Reflector (RR) TLV MAY be advertised multiple times 136 with different peering addresses and AFI/SAFI pairs and MAY be 137 advertised in multiple OSPF RI LSAs. The AFI/SAFI tuple, (0,0) 138 will serve as a wildcard indicating all configured AFI/SAFI 139 tuples. This can be used in deployments where the AF deployment 140 is fairly homogeneous. 142 o If different peering addresses are advertised for the same AFI/ 143 SAFI pair, the decision of whether a BGP client establishes 144 sessions with one or more of the advertised peering addresses is 145 beyond the scope of this document. 147 o If the BGP Router Reflector (RR) TLV has an invalid length or is 148 otherwise malformed, it will not be used for BGP client session 149 establishment. The occurrence of a malformed TLV SHOULD be 150 logged. 152 3. OSPF Router Information (RI) Opaque LSAs 154 The OSPF BGP TLV may optionally be advertised in an area-scoped or 155 AS-scoped OSPFv2 Router Information (RI) opaque LSA or OSPFv3 Router 156 Information (RI) LSA [OSPF-RI]. BGP clients may then use the peering 157 address to establish BGP sessions with the advertising route- 158 reflector. 160 4. Security Considerations 162 Security considerations for the base OSPF protocol are covered in 163 [OSPF] and [OSPFV3]. 165 5. IANA Considerations 167 The document will require the following IANA actions: 169 1. A Router Information TLV type for the BGP Router Reflector TLV 170 will be allocated from the OSPF Router Information (RI) TLVs 171 registry. 173 6. References 175 6.1. Normative References 177 [OSPF] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. 179 [OSPF-RI] Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S. 180 Shaffer, "Extensions to OSPF for Advertising Optional 181 Router Capabilities", RFC 7770, January 2016. 183 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 184 for IPv6", RFC 5340, July 2008. 186 [RFC-KEYWORDS] 187 Bradner, S., "Key words for use in RFC's to Indicate 188 Requirement Levels", BCP 14, RFC 2119, March 1997. 190 6.2. Informative References 192 [BGP-RR] Bates, T., Chen, E., and R. Chandra, "BGP Route 193 Reflection: An Alternative to Full Mesh Internal BGP 194 (IBGP)", RFC 4456, April 2006. 196 Appendix A. Acknowledgments 198 The RFC text was produced using Marshall Rose's xml2rfc tool. 200 Authors' Addresses 202 Acee Lindem 203 Cisco Systems 204 301 Midenhall Way 205 Cary, NC 27513 206 USA 208 Email: acee@cisco.com 210 Keyur Patel 211 Arrcus 213 Email: keyur@arrcus.com 215 Shawn Zandi 216 LinkedIn 218 Email: szandi@linkedin.com 220 Robert Raszuk 221 Bloomberg LP 222 731 Lexington Ave 223 New York City, NY 10022 224 USA 226 Email: robert@raszuk.net