idnits 2.17.1 draft-lapukhov-bgp-ila-afi-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 : ---------------------------------------------------------------------------- ** There are 15 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([I-D.herbert-nvo3-ila], [RFC4760]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 12, 2016) is 2959 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) == Unused Reference: 'RFC4271' is defined on line 213, but no explicit reference was found in the text == Outdated reference: A later version (-04) exists of draft-herbert-nvo3-ila-01 ** Downref: Normative reference to an Informational draft: draft-herbert-nvo3-ila (ref. 'I-D.herbert-nvo3-ila') Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing P. Lapukhov 3 Internet-Draft Facebook 4 Intended status: Standards Track March 12, 2016 5 Expires: September 13, 2016 7 Use of BGP for dissemination of ILA mapping information 8 draft-lapukhov-bgp-ila-afi-00 10 Abstract 12 Identifier-Locator Addressing [I-D.herbert-nvo3-ila] relies on 13 splitting the 128-bit IPv6 address into identifier and locator parts 14 to implement identifier mobility, and network virtualization. This 15 document proposes a method for distributing the identifier to locator 16 mapping information using Multiprotocol Extensions for BGP-4 17 [RFC4760]. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in RFC 2119 [RFC2119]. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on September 13, 2016. 42 Copyright Notice 44 Copyright (c) 2016 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. BGP ILA AFI . . . . . . . . . . . . . . . . . . . . . . . . . 2 61 3. Capability Advertisement . . . . . . . . . . . . . . . . . . 3 62 4. Disseminating Identifier-Locator mapping information . . . . 3 63 4.1. Advertising ILA mapping information . . . . . . . . . . . 3 64 4.2. Withdrawing ILA mapping information . . . . . . . . . . . 3 65 5. Interpreting the mapping information . . . . . . . . . . . . 4 66 5.1. Unicast SAFI . . . . . . . . . . . . . . . . . . . . . . 4 67 5.2. Multicast SAFI . . . . . . . . . . . . . . . . . . . . . 4 68 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 69 7. Manageability Considerations . . . . . . . . . . . . . . . . 5 70 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 71 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 72 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 73 10.1. Normative References . . . . . . . . . . . . . . . . . . 5 74 10.2. Informative References . . . . . . . . . . . . . . . . . 5 75 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 77 1. Introduction 79 Under the ILA proposal, the IPv6 address is split in 64-bit 80 identifier (lower address bits) and locator (higher address bits) 81 portions. The locator part is determined from a mapping table that 82 maintains associations between the location-independent identifiers 83 and topologically significant locators. The hosts that collectively 84 implement and maintain such mappings are referred to as "ILA domain" 85 in this document. This document proposes a new address family 86 identifier (AFI) for the purpose of disseminating the locator- 87 identifier mappings among the nodes participating in the ILA domain. 89 2. BGP ILA AFI 91 This document introduces a new AFI known as a "Identifier-Locator 92 AFI" with the actual value to be assigned by IANA. The purpose of 93 this AFI is disseminating the mapping information between identifiers 94 and locators in ILA domain. This document defines the use of SAFI 95 values of "1" (unicast) and "2" (multicast) only. 97 3. Capability Advertisement 99 A BGP speaker that wishes to exchange ILA mapping information MUST 100 use the Multiprotocol Extensions Capability Code, as defined in 101 [RFC4760], to advertise the corresponding AFI/SAFI pair. 103 4. Disseminating Identifier-Locator mapping information 105 4.1. Advertising ILA mapping information 107 For the purpose of ILA mapping encoding, the 8-octet locator field 108 SHALL be encoded in the "next-hop address" field. The "length of the 109 next-hop address" MUST be set to "8" (64-bit). The identifiers bound 110 to the locator SHALL be encoded within the NLRI portion of 111 MP_REACH_NLRI attribute. The NLRI portion of MP_REACH_NLRI starts 112 with the two-octet "Length of identifiers" field. The rest of the 113 NLRI is a collection of 8-octet (64-bit) identifiers that are bound 114 to the locator specified in the "next-hop address" field. 116 +---------------------------------------------------------+ 117 | Address Family Identifier (2 octets) | 118 +---------------------------------------------------------+ 119 | Subsequent Address Family Identifier (1 octet) | 120 +---------------------------------------------------------+ 121 | Length of Next Hop Address (1 octet, set to "8") | 122 +---------------------------------------------------------+ 123 | Locator value (8 octets) | 124 +---------------------------------------------------------+ 125 | Reserved (1 octet), must be zero | 126 +---------------------------------------------------------+ 127 | Length of identifiers field (2 octets, multiple of 8) | 128 +---------------------------------------------------------+ 129 | Identifiers (variable, 8 octets each) | 130 +---------------------------------------------------------+ 132 Figure 1: MP_REACH_NLRI Layout 134 4.2. Withdrawing ILA mapping information 136 Withdrawal of ILA mapping information is performed via an 137 MP_UNREACH_NLRI attribute advertisement organized as following: 139 +---------------------------------------------------------+ 140 | Address Family Identifier (2 octets) | 141 +---------------------------------------------------------+ 142 | Subsequent Address Family Identifier (1 octet) | 143 +---------------------------------------------------------+ 144 | Length of witdrawn identifiers (2 octets) | 145 +---------------------------------------------------------+ 146 | Identifiers (variable, 8 octets each) | 147 +---------------------------------------------------------+ 149 Figure 2: MP_UNREACH_NLRI Layout 151 5. Interpreting the mapping information 153 5.1. Unicast SAFI 155 Only the locator part of ILA address is used for packet routing, and 156 every node that hosts an identifier MUST have a unique routable /64 157 prefix within the scope of the ILA domain. The identifiers 158 advertised under the ILA AFI are expected to be used by the data- 159 plane implementation to perform match on a full IPv6 address and 160 decide whether the locator portion of the address needs a re-write. 161 It is up to the implementation to decide which full 128-bit IPv6 162 addresses need a rewrite, e.g. by matching on a Standard Identifier 163 Representation (SIR) prefix as defined in [I-D.herbert-nvo3-ila]. 165 The locator rewrite information comes from the next-hop "address" 166 associated with the identifier. The next-hop field of MP_REACH_NLRI 167 attribute MUST NOT be used for any routing resolutions/lookups by the 168 BGP process itself. It should be used purely to create a rewrite 169 rule in the data-plane forwarding table. The actual forwarding 170 decision is then based on subsequent lookup in the forwarding table 171 to find the next hop to send the packet to. 173 5.2. Multicast SAFI 175 For multicast packets, the RPF check process SHALL be modified for 176 use with ILA source addresses. Specifically, source ILA IPv6 177 addresses with the identifier portion matching the mapping table 178 SHALL be mapped to proper locator, prior to performing the RPF check. 179 The ILA source addresses need to be identified by some means specific 180 to ILA implementation, e.g. by matching on configured SIR prefixes. 181 The ILA addresses that do not match any mapping entry SHALL be 182 considered as failing the RPF check. 184 6. IANA Considerations 186 For the purpose of this work, IANA would be asked to allocate values 187 for the new AFI. 189 7. Manageability Considerations 191 TBD 193 8. Security Considerations 195 This document does not introduce any changes in terms of BGP 196 security. Defining ILA security model is outside of scope of this 197 document. 199 9. Acknowledgements 201 The author would like to thank Doug Porter for the initial idea 202 suggestion and discussion of this proposal. 204 10. References 206 10.1. Normative References 208 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 209 Requirement Levels", BCP 14, RFC 2119, 210 DOI 10.17487/RFC2119, March 1997, 211 . 213 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 214 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 215 DOI 10.17487/RFC4271, January 2006, 216 . 218 [I-D.herbert-nvo3-ila] 219 Herbert, T., "Identifier-locator addressing for network 220 virtualization", draft-herbert-nvo3-ila-01 (work in 221 progress), October 2015. 223 10.2. Informative References 225 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 226 "Multiprotocol Extensions for BGP-4", RFC 4760, 227 DOI 10.17487/RFC4760, January 2007, 228 . 230 Author's Address 232 Petr Lapukhov 233 Facebook 234 1 Hacker Way 235 Menlo Park, CA 94025 236 US 238 Email: petr@fb.com