idnits 2.17.1 draft-ietf-grow-large-communities-usage-04.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 2602 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: '1' on line 583 -- Looks like a reference, but probably isn't: '2' on line 585 -- Looks like a reference, but probably isn't: '3' on line 587 -- Looks like a reference, but probably isn't: '4' on line 589 Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Global Routing Operations J. Snijders 3 Internet-Draft J. Heasley 4 Intended status: Informational NTT 5 Expires: September 14, 2017 M. Schmidt 6 i3D.net 7 March 13, 2017 9 Use of BGP Large Communities 10 draft-ietf-grow-large-communities-usage-04 12 Abstract 14 Examples and inspiration for operators to use BGP Large Communities. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on September 14, 2017. 33 Copyright Notice 35 Copyright (c) 2017 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. The Design Overview . . . . . . . . . . . . . . . . . . . . . 2 52 2.1. Informational Communities . . . . . . . . . . . . . . . . 4 53 2.2. Action Communities . . . . . . . . . . . . . . . . . . . 4 54 3. Examples of Informational Communities . . . . . . . . . . . . 5 55 3.1. Location . . . . . . . . . . . . . . . . . . . . . . . . 5 56 3.1.1. An ISO 3166-1 Numeric Function . . . . . . . . . . . 5 57 3.1.2. A UN M.49 Region Function . . . . . . . . . . . . . . 5 58 3.2. Relation Function . . . . . . . . . . . . . . . . . . . . 6 59 3.3. Combining Informational Communities . . . . . . . . . . . 6 60 4. Examples of Action Communities . . . . . . . . . . . . . . . 7 61 4.1. Selective NO_EXPORT . . . . . . . . . . . . . . . . . . . 7 62 4.1.1. ASN Based Selective NO_EXPORT . . . . . . . . . . . . 7 63 4.1.2. Location Based Selective NO_EXPORT . . . . . . . . . 7 64 4.2. Selective AS_PATH Prepending . . . . . . . . . . . . . . 8 65 4.2.1. ASN Based Selective AS_PATH Prepending . . . . . . . 8 66 4.2.2. Location Based Selective AS_PATH Prepending . . . . . 9 67 4.3. Manipulation of the LOCAL_PREF Attribute . . . . . . . . 9 68 4.3.1. Global Manipulation of LOCAL_PREF . . . . . . . . . . 10 69 4.3.2. Location Based Manipulation of LOCAL_PREF . . . . . . 10 70 4.3.3. Note of Caution for LOCAL_PREF Functions . . . . . . 11 71 4.4. Route Server Prefix Distribution Control . . . . . . . . 11 72 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 73 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 74 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 75 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 76 8.1. Normative References . . . . . . . . . . . . . . . . . . 13 77 8.2. Informative References . . . . . . . . . . . . . . . . . 13 78 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 81 1. Introduction 83 BGP Large Communities [RFC8092] provide a mechanism to signal opaque 84 information between Autonomous Systems (ASs). This document presents 85 examples of how operators might utilize BGP Large Communities to 86 achieve various goals. This document draws on the experience of 87 operator communities such as NANOG [1] and NLNOG [2]. 89 2. The Design Overview 91 BGP Large Communities are composed of three 4-octet fields. The 92 first is the Global Administrator (GA) field, whose value is the 93 Autonomous System Number (ASN) of the AS that has defined the meaning 94 of the remaining two 4-octet fields, known as "Local Data Part 1" and 95 "Local Data Part 2". This document describes an approach where the 96 "Local Data Part 1" field contains a function identifier and the 97 "Local Data Part 2" contains a parameter value. Using the canonical 98 notation this format can be summarized as "ASN:Function:Parameter". 100 +----------------------+---------------+ 101 | RFC 8092 | this document | 102 +----------------------+---------------+ 103 | Global Administrator | ASN | 104 | Local Data Part 1 | Function | 105 | Local Data Part 2 | Parameter | 106 +----------------------+---------------+ 108 A mapping table on the use of fields in BGP Large Communities between 109 [RFC8092] and this document. 111 Table 1: Field Mapping 113 In contemporary deployments of both BGP Communities [RFC1997] and BGP 114 Large Communities, the function of a community can be divided into 115 two categories: 117 o Informational Communities 119 o Action Communities 121 Throughout the document a topology of four ASs is used to illustrate 122 the use of communities in the following configuration: 124 AS 65551 125 | 126 ^ 127 | 128 AS 64497 129 / \ 130 ^ \ 131 / ^ 132 AS 64498 \ 133 | | 134 `<->- AS 64499 136 AS 64497 obtains transit services from (is a customer of) AS 65551, a 137 4-octet ASN. AS 64497 provides transit services to both AS 64498 and 138 AS 64499. AS 64498 and AS 64499 maintain a peering relationship in 139 which they only exchange their customer routes. 141 The opaque nature of BGP Large Communities allows for rapid 142 deployment of new features or changes to their routing policy that 143 perform an action. Operators are encouraged to publicly publish and 144 maintain documentation on the purpose of each BGP Large Community, 145 both informational and action, that they support or are visible in 146 BGP RIBs. 148 2.1. Informational Communities 150 Informational Communities are labels for attributes such as the 151 origin of the route announcement, the nature of the relation with an 152 EBGP neighbor or the intended propagation audience. Informational 153 Communities can also assist in providing valuable information for 154 day-to-day network operations such as debugging or capacity planning. 156 The Global Administrator field is set to the ASN which labels the 157 routes with the Informational Communities. For example, AS 64497 158 might add a community with the GA 64497 to a route accepted from an 159 IBGP or EBGP neighbor as a means of signaling that it was imported in 160 a certain geographical region. 162 In general, the intended audiences of Informational Communities are 163 downstream networks and the Global Administrator itself, but any AS 164 could benefit from receiving these communities. 166 2.2. Action Communities 168 Action Communities are added as a label to request that a route be 169 treated in a particular way within an AS. The operator of the AS 170 defines a routing policy that adjusts path attributes based on the 171 community. For example, the route's propagation characteristics, the 172 LOCAL_PREF (local preference), the next-hop, or the number of AS_PATH 173 prepends to be added when it is received or propagated can be 174 changed. 176 The Global Administrator field is set to the ASN which has defined 177 the functionality of that BGP Large Community and is the ASN that is 178 expected to perform the action. For example, AS 64499 might label a 179 route with a BGP Large Community containing GA 64497 to request that 180 AS 64497 perform a pre-defined action on that route. 182 In general, the intended audience of Action Communities are transit 183 providers taking action on behalf of a customer or the Global 184 Administrator itself, but any AS could take action if they choose and 185 any AS could add an Action Community with the GA of a non-adjacent 186 ASN. However, note that an Action Community could also be 187 informational. Its presence is an indicator that the GA may have 188 performed the action and that an AS in the AS_PATH requested it. 190 Operators are recommended to publish the relative order in which 191 Action Communities (both BGP Communities and BGP Large Communities) 192 are processed in their routing policy. 194 3. Examples of Informational Communities 196 3.1. Location 198 An AS, AS 64497 in these examples, may inform other networks about 199 the geographical region where AS 64497 imported a route by labeling 200 it with BGP Large Communities following one of the following schemes 201 or a combination of them. 203 3.1.1. An ISO 3166-1 Numeric Function 205 AS 64497 could assign a value of 1 to the Function field to designate 206 the content of the Parameter field as an ISO-3166-1 [3] numeric 207 country identifier. 209 +---------------------+---------------------------------------------+ 210 | BGP Large Community | Description | 211 +---------------------+---------------------------------------------+ 212 | 64497:1:528 | Route learned in the Netherlands | 213 | 64497:1:392 | Route learned in Japan | 214 | 64497:1:840 | Route learned in the United States of | 215 | | America | 216 +---------------------+---------------------------------------------+ 218 Example documentation for Informational Communities deployed by AS 219 64497 to describe the location where a route was imported using ISO 220 3166-1 numeric identifiers. 222 Table 2: Information: ISO 3166-1 224 3.1.2. A UN M.49 Region Function 226 AS 64497 could assign a value of 2 to the Function field to designate 227 the content of the Parameter field as the M.49 numeric code published 228 by the United Nations Statistics Division (UNSD) [4] for macro 229 geographical (continental) regions, geographical sub-regions, or 230 selected economic and other groupings. 232 +---------------------+-------------------------------+ 233 | BGP Large Community | Description | 234 +---------------------+-------------------------------+ 235 | 64497:2:2 | Route learned in Africa | 236 | 64497:2:9 | Route learned in Oceania | 237 | 64497:2:145 | Route learned in Western Asia | 238 | 64497:2:150 | Route learned in Europe | 239 +---------------------+-------------------------------+ 241 Example documentation for Informational Communities deployed by AS 242 64497 to describe the location where a route was imported using M.49 243 numeric codes published by the United Nations Statistics Division. 245 Table 3: Information: UNSD Regions 247 3.2. Relation Function 249 An AS, AS 64497 in this example, could assign a value of 3 to the 250 Function field to designate the content of the Parameter field as a 251 number indicating whether the route originated inside its own network 252 or was learned externally, and if learned externally, it might 253 simultaneously characterize the nature of the relation with that 254 specific EBGP neighbor. 256 +---------------------+---------------------------------------+ 257 | BGP Large Community | Description | 258 +---------------------+---------------------------------------+ 259 | 64497:3:1 | Route originated internally | 260 | 64497:3:2 | Route learned from a customer | 261 | 64497:3:3 | Route learned from a peering partner | 262 | 64497:3:4 | Route learned from a transit provider | 263 +---------------------+---------------------------------------+ 265 Example documentation for Informational Communities deployed by AS 266 64497 to describe the relation to the ASN from which the route was 267 learned. 269 Table 4: Information: Relation 271 3.3. Combining Informational Communities 273 A route may be labeled with multiple Informational Communities. For 274 example, a route learned in the Netherlands from a customer might be 275 labeled with communities 64497:1:528, 64497:2:150 and 64497:3:2 at 276 the same time. 278 4. Examples of Action Communities 280 4.1. Selective NO_EXPORT 282 As part of an agreement, often a commercial transit agreement, 283 between AS 64497 and AS 64498, AS 64497 might expose BGP traffic 284 engineering functions to AS 64498. One such BGP traffic engineering 285 function could be selective NO_EXPORT, which is the selective 286 filtering of a route learned from one AS, AS 64498, to certain EBGP 287 neighbors of the GA, AS 64497. 289 4.1.1. ASN Based Selective NO_EXPORT 291 AS 64497 could assign a value of 4 to the Function field to designate 292 the content of the Parameter field as a neighboring ASN to which a 293 route should not be propagated. 295 +---------------------+---------------------------------+ 296 | BGP Large Community | Description | 297 +---------------------+---------------------------------+ 298 | 64497:4:64498 | Do not export route to AS 64498 | 299 | 64497:4:64499 | Do not export route to AS 64499 | 300 | 64497:4:65551 | Do not export route to AS 65551 | 301 +---------------------+---------------------------------+ 303 Example documentation for Action Communities deployed by AS 64497 to 304 expose a BGP traffic engineering function which selectively prevents 305 the propagation of routes to the neighboring ASN specified in the 306 Parameter field. 308 Table 5: Action: ASN NO_EXPORT 310 4.1.2. Location Based Selective NO_EXPORT 312 AS 64497 could assign a value of 5 to the Function field to designate 313 the content of the Parameter field as an ISO 3166-1 numeric country 314 identifier within which a labeled route is not propagated to EBGP 315 neighbors. However, this might not prevent one of those EBGP 316 neighbors from learning that route in another country and making it 317 available in the country specified by the BGP Large Community. 319 +-----------------+-------------------------------------------------+ 320 | BGP Large | Description | 321 | Community | | 322 +-----------------+-------------------------------------------------+ 323 | 64497:5:528 | Do not export to EBGP neighbors in the | 324 | | Netherlands | 325 | 64497:5:392 | Do not export to EBGP neighbors in Japan | 326 | 64497:5:840 | Do not export to EBGP neighbors in the United | 327 | | States of America | 328 +-----------------+-------------------------------------------------+ 330 Example documentation for Action Communities deployed by AS 64497 to 331 expose a BGP traffic engineering function which selectively prevents 332 the propagation of routes to all EBGP neighbors in the geographical 333 region specified in the Parameter field. 335 Table 6: Action: NO_EXPORT in Region 337 4.2. Selective AS_PATH Prepending 339 As part of an agreement between AS 64497 and AS 64498, AS 64497 might 340 expose BGP traffic engineering functions to AS 64498. One such BGP 341 traffic engineering function could be selective prepending of the 342 AS_PATH with AS 64497 to certain certain EBGP neighbors of AS 64497. 344 4.2.1. ASN Based Selective AS_PATH Prepending 346 AS 64497 could assign a value of 6 to the Function field to designate 347 the content of the Parameter field as a neighboring ASN to which 348 prepending of the AS_PATH with AS 64497 is requested on propagation 349 of the route. Additional AS_PATH prepending functions might also be 350 defined to support multiples of prepending, that is two, three or 351 more prepends of AS 64497. 353 +---------------------+------------------------------------------+ 354 | BGP Large Community | Description | 355 +---------------------+------------------------------------------+ 356 | 64497:6:64498 | Prepend 64497 once on export to AS 64498 | 357 | 64497:6:64499 | Prepend 64497 once on export to AS 64499 | 358 | 64497:6:65551 | Prepend 64497 once on export to AS 65551 | 359 +---------------------+------------------------------------------+ 361 Example documentation for Action Communities deployed by AS 64497 to 362 expose a BGP traffic engineering function which selectively prepends 363 the AS_PATH with AS 64497 when propagating the route to the specified 364 EBGP neighbor. 366 Table 7: Action: Prepend to ASN 368 4.2.2. Location Based Selective AS_PATH Prepending 370 AS 64497 could assign a value of 7 to the Function field to designate 371 the content of the Parameter field as an ISO 3166-1 numeric country 372 identifier to which the prepending of the AS_PATH with AS 64497 is 373 requested on propagation of the route to all EBGP neighbors in that 374 region. 376 +------------------+------------------------------------------------+ 377 | BGP Large | Description | 378 | Community | | 379 +------------------+------------------------------------------------+ 380 | 64497:7:528 | Prepend once to EBGP neighbors in the | 381 | | Netherlands | 382 | 64497:7:392 | Prepend once to EBGP neighbors in Japan | 383 | 64497:7:840 | Prepend once to EBGP neighbors in United | 384 | | States of America | 385 +------------------+------------------------------------------------+ 387 Example documentation for Action Communities deployed by AS 64497 to 388 expose a BGP traffic engineering function which selectively prepends 389 the AS_PATH with AS 64497 when propagating the route to all EBGP 390 neighbors in the geographical region specified in the Parameter 391 field. 393 Table 8: Action: Prepend in Region 395 4.3. Manipulation of the LOCAL_PREF Attribute 397 As part of an agreement between AS 64497 and AS 64498, AS 64497 might 398 expose BGP traffic engineering functions to AS 64498. One such BGP 399 traffic engineering function might allow AS 64498 to manipulate the 400 value of the LOCAL_PREF attribute of routes learned from AS 64498 401 within AS 64497, even though the LOCAL_PREF attribute is non- 402 transitive and is not propagated to EBGP neighbors. 404 The LOCAL_PREF value of routes are locally significant within each AS 405 and are impossible to list in this document. Instead, the typical 406 LOCAL_PREF values could be classified as a hierarchy and a BGP Large 407 Community function exposed allowing an EBGP neighbor to affect the 408 LOCAL_PREF value within the specified GA. The following example list 409 defines the classes of routes in the order of descending LOCAL_PREF 410 value and assigns a function identifier which could be used in the 411 Function field of a BGP Large Community. 413 +----------+--------------------------------------------------------+ 414 | Function | Preference Class | 415 +----------+--------------------------------------------------------+ 416 | 8 | Normal customer route | 417 | 9 | Backup customer route | 418 | 10 | Peering route | 419 | 11 | Upstream transit route | 420 | 12 | Fallback route, to be installed if no other path is | 421 | | available | 422 +----------+--------------------------------------------------------+ 424 Table 9: Action: Preference Function Identifiers 426 4.3.1. Global Manipulation of LOCAL_PREF 428 AS 64497 could place one of the previously defined Preference 429 Function Identifiers in the Function field and set the value 0 in the 430 Parameter field to designate that the LOCAL_PREF associated with that 431 function identifier should be applied for that route throughout the 432 whole AS. 434 +---------------------+---------------------------------------------+ 435 | BGP Large Community | Description | 436 +---------------------+---------------------------------------------+ 437 | 64497:9:0 | Assign LOCAL_PREF for a customer backup | 438 | | route | 439 | 64497:10:0 | Assign LOCAL_PREF for a peering route | 440 | 64497:12:0 | Assign LOCAL_PREF for a fallback route | 441 +---------------------+---------------------------------------------+ 443 Example documentation for Action Communities deployed by AS 64497 to 444 expose a BGP traffic engineering function which allows a BGP neighbor 445 to globally manipulate the LOCAL_PREF attribute for the route within 446 AS 64497. 448 Table 10: Action: Global LOCAL_PREF Manipulation 450 4.3.2. Location Based Manipulation of LOCAL_PREF 452 AS 64497 could place one of the previously defined Preference 453 Function Identifiers in the Function field and use an ISO 3166-1 454 numeric country identifier in the Parameter field to designate the 455 geographical region within which the non-default LOCAL_PREF 456 associated with that function identifier should be applied to the 457 route. The value of the LOCAL_PREF attribute should not deviate from 458 the default for that route class in any region not specified by one 459 or more of these Action Communities. 461 +--------------+----------------------------------------------------+ 462 | BGP Large | Description | 463 | Community | | 464 +--------------+----------------------------------------------------+ 465 | 64497:9:528 | Assign LOCAL_PREF for a customer backup route on | 466 | | BGP speakers in the Netherlands | 467 | 64497:10:392 | Assign LOCAL_PREF for a peering route on BGP | 468 | | speakers in Japan | 469 | 64497:12:840 | Assign LOCAL_PREF for a fallback route on BGP | 470 | | speakers in United States of America | 471 +--------------+----------------------------------------------------+ 473 Example documentation for Action Communities deployed by AS 64497 to 474 expose a BGP traffic engineering function which allows a BGP neighbor 475 to selectively manipulate the LOCAL_PREF attribute within AS 64497 in 476 the geographical region specified in the Parameter field. 478 Table 11: Action: Regional LOCAL_PREF Manipulation 480 4.3.3. Note of Caution for LOCAL_PREF Functions 482 The LOCAL_PREF attribute strongly influences the BGP Decision 483 Process, which in turn affects the scope of route propagation. 484 Operators should take special care when using Action Communities that 485 decrease the LOCAL_PREF value, and the degree of preference, to a 486 value below that of another route class. Some of the unintended BGP 487 states that might arise as a result of these traffic engineering 488 decisions are described as "BGP Wedgies" in [RFC4264]. 490 4.4. Route Server Prefix Distribution Control 492 Route Servers [RFC7947] use BGP to broker network reachability 493 information among their clients. As not all route server clients may 494 wish to interconnect with each other, the route server operator will 495 usually implement a mechanism to allow each client to control the 496 route server's export routing policy, as described in Section 4.6 of 497 [RFC7948]. One widely-used mechanism is a route server specific 498 adaption of "ASN Based Selective NO_EXPORT" (Section 4.1.1). 500 An example BGP Large Communities policy which enables client- 501 controlled prefix distribution for a route server operating as AS 502 64497, is outlined as follows: 504 +-------------------+-----------------------------------------------+ 505 | BGP Large | Description | 506 | Community | | 507 +-------------------+-----------------------------------------------+ 508 | 64497:0:peer-as | Explicitly prevent announcement of route to | 509 | | peer-as | 510 | 64497:1:peer-as | Explicitly announce route to peer-as | 511 | 64497:0:0 | Do not announce route to any peers by default | 512 | 64497:1:0 | Announce route to all peers by default | 513 +-------------------+-----------------------------------------------+ 515 Table 12: Action: Route Server Prefix Distribution Control 517 Multiple BGP Large Community values can be used together to implement 518 fine-grained route distribution control. For example, route server 519 client AS 64500 might wish to use a route server for interconnecting 520 to all other clients except AS 64510. In this case, they would label 521 all their outbound routes to the route server with 64497:1:0 (to 522 announce to all clients by default) and 64497:1:64510 (to prevent 523 announcement to AS 64510). 525 Alternatively, route server client AS 64501 may have a selective 526 routing policy and may wish to interconnect with only AS 64505 and AS 527 64506. This could be implemented by announcing routes labeled with 528 64497:0:0 (blocking all distribution by default) and 64497:1:64505, 529 64497:1:64506 to instruct the route server to force announcement to 530 those two ASNs. 532 5. Security Considerations 534 Operators should note the recommendations in Section 11 of BGP 535 Operations and Security [RFC7454]. 537 6. IANA Considerations 539 None. 541 7. Acknowledgments 543 The authors would like to gratefully acknowledge the insightful 544 comments, contributions, critique and support from Adam Chappell, 545 Jonathan Stewart, Greg Hankins, Nick Hilliard, Will Hargrave, and 546 Randy Bush. 548 8. References 550 8.1. Normative References 552 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 553 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 554 . 556 [RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations 557 and Security", BCP 194, RFC 7454, DOI 10.17487/RFC7454, 558 February 2015, . 560 [RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas, 561 I., and N. Hilliard, "BGP Large Communities Attribute", 562 RFC 8092, DOI 10.17487/RFC8092, February 2017, 563 . 565 8.2. Informative References 567 [RFC4264] Griffin, T. and G. Huston, "BGP Wedgies", RFC 4264, 568 DOI 10.17487/RFC4264, November 2005, 569 . 571 [RFC7947] Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker, 572 "Internet Exchange BGP Route Server", RFC 7947, 573 DOI 10.17487/RFC7947, September 2016, 574 . 576 [RFC7948] Hilliard, N., Jasinska, E., Raszuk, R., and N. Bakker, 577 "Internet Exchange BGP Route Server Operations", RFC 7948, 578 DOI 10.17487/RFC7948, September 2016, 579 . 581 8.3. URIs 583 [1] https://www.nanog.org 585 [2] https://nlnog.net 587 [3] https://www.iso.org/iso-3166-country-codes.html 589 [4] https://unstats.un.org/unsd/methodology/m49/ 591 Authors' Addresses 592 Job Snijders 593 NTT Communications 594 Theodorus Majofskistraat 100 595 Amsterdam 1065 SZ 596 The Netherlands 598 Email: job@ntt.net 600 John Heasley 601 NTT Communications 602 1111 NW 53rd Drive 603 Portland, OR 97210 604 United States of America 606 Email: heas@shrubbery.net 608 Martijn Schmidt 609 i3D.net 610 Rivium 1e Straat 1 611 Capelle aan den IJssel 2909 LE 612 NL 614 Email: martijnschmidt@i3d.net