1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
|
<pre>Network Working Group D. Meyer
Request for Comments: 4384 February 2006
BCP: 114
Category: Best Current Practice
BGP Communities for Data Collection
Status of This Memo
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
BGP communities (<a href="./rfc1997">RFC 1997</a>) are used by service providers for many
purposes, including tagging of customer, peer, and geographically
originated routes. Such tagging is typically used to control the
scope of redistribution of routes within a provider's network and to
its peers and customers. With the advent of large-scale BGP data
collection (and associated research), it has become clear that the
information carried in such communities is essential for a deeper
understanding of the global routing system. This memo defines
standard (outbound) communities and their encodings for export to BGP
route collectors.
<span class="grey">Meyer Best Current Practice [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Definitions .....................................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Peers and Peering ..........................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Customer Routes ............................................<a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Peer Routes ................................................<a href="#page-3">3</a>
<a href="#section-2.4">2.4</a>. Internal Routes ............................................<a href="#page-4">4</a>
<a href="#section-2.5">2.5</a>. Internal More Specific Routes ..............................<a href="#page-4">4</a>
<a href="#section-2.6">2.6</a>. Special Purpose Routes .....................................<a href="#page-4">4</a>
<a href="#section-2.7">2.7</a>. Upstream Routes ............................................<a href="#page-4">4</a>
<a href="#section-2.8">2.8</a>. National Routes ............................................<a href="#page-4">4</a>
<a href="#section-2.9">2.9</a>. Regional Routes ............................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. <a href="./rfc1997">RFC 1997</a> Community Encoding and Values ..........................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Community Values for BGP Data Collection ........................<a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. Extended Communities .......................................<a href="#page-7">7</a>
<a href="#section-4.2">4.2</a>. Four-Octet AS Specific Extended Communities ................<a href="#page-9">9</a>
<a href="#section-5">5</a>. Note on BGP UPDATE Packing ......................................<a href="#page-9">9</a>
<a href="#section-6">6</a>. Acknowledgements ................................................<a href="#page-9">9</a>
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-10">10</a>
<a href="#section-7.1">7.1</a>. Total Path Attribute Length ...............................<a href="#page-10">10</a>
<a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-10">10</a>
<a href="#section-9">9</a>. References .....................................................<a href="#page-11">11</a>
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-11">11</a>
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-11">11</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
BGP communities [<a href="./rfc1997" title=""BGP Communities Attribute"">RFC1997</a>] are used by service providers for many
purposes, including tagging of customer, peer, and geographically
originated routes. Such tagging is typically used to control the
scope of redistribution of routes within a provider's network and to
its customers and peers. Communities are also used for a wide
variety of other applications, such as allowing customers to set
attributes such as LOCAL_PREF [<a href="./rfc1771" title=""A Border Gateway Protocol (BGP-4)"">RFC1771</a>] by sending appropriate
communities to their service provider. Other applications include
signaling various types of Virtual Private Networks (VPNs) (e.g.,
Virtual Private LAN Service (VPLS) [<a href="#ref-VPLS" title=""Virtual Private LAN Service"">VPLS</a>]), and carrying link
bandwidth for traffic engineering applications [<a href="./rfc4360" title=""BGP Extended Communities Attribute"">RFC4360</a>].
With the advent of large-scale BGP data collection [<a href="#ref-RV" title=""The Routeviews Project"">RV</a>] [<a href="#ref-RIS" title=""The RIPE Routing Information Service"">RIS</a>] (and
associated research), it has become clear that the geographical and
topological information, as well as the relationship the provider has
to the source of a route (e.g., transit, peer, or customer), carried
in such communities is essential for a deeper understanding of the
global routing system. This memo defines standard communities for
export to BGP route collectors. These communities represent a
significant part of information carried by service providers as of
<span class="grey">Meyer Best Current Practice [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
this writing, and as such could be useful for internal use by service
providers. However, such use is beyond the scope of this memo.
Finally, those involved in BGP data analysis are encouraged to verify
with their data sources as to which peers implement this scheme (as
there is a large amount of existing data as well as many legacy
peerings).
The remainder of this memo is organized as follows. <a href="#section-2">Section 2</a>
provides the definition of terms used as well as the semantics of the
communities used for BGP data collection, and <a href="#section-3">Section 3</a> defines the
corresponding encodings for <a href="./rfc1997">RFC 1997</a> [<a href="./rfc1997" title=""BGP Communities Attribute"">RFC1997</a>] communities. Finally,
<a href="#section-4">Section 4</a> defines the encodings for use with extended communities
[<a href="./rfc4360" title=""BGP Extended Communities Attribute"">RFC4360</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Definitions</span>
In this section, we define the terms used and the categories of
routes that may be tagged with communities. This tagging is often
referred to as coloring, and we refer to a route's "color" as its
community value. The categories defined here are loosely modeled on
those described in [<a href="#ref-WANG" title=""Inferring and Characterizing Internet Routing Policies"">WANG</a>] and [<a href="#ref-HUSTON" title=""Interconnection, Peering, and Settlements"">HUSTON</a>].
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Peers and Peering</span>
Consider two network service providers, A and B. Service providers A
and B are defined to be peers when (i) A and B exchange routes via
BGP, and (ii) traffic exchange between A and B is settlement-free.
This arrangement is also typically known as "peering". Peers
typically exchange only their respective customer routes (see
"Customer Routes" below), and hence exchange only their respective
customer traffic. See [<a href="#ref-HUSTON" title=""Interconnection, Peering, and Settlements"">HUSTON</a>] for a more in-depth discussion of the
business models surrounding peers and peering.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Customer Routes</span>
Customer routes are those routes that are heard from a customer via
BGP and are propagated to peers and other customers. Note that a
customer can be an enterprise or another network service provider.
These routes are sometimes called client routes [<a href="#ref-HUSTON" title=""Interconnection, Peering, and Settlements"">HUSTON</a>].
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Peer Routes</span>
Peer routes are those routes heard from peers via BGP, and not
propagated to other peers. In particular, these routes are only
propagated to the service provider's customers.
<span class="grey">Meyer Best Current Practice [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Internal Routes</span>
Internal routes are those routes that a service provider originates
and passes to its peers and customers. These routes are frequently
taken out of the address space allocated to a provider.
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Internal More Specific Routes</span>
Internal more specific routes are those routes that are frequently
used for circuit load balancing purposes and Interior Gateway
Protocol (IGP) route reduction. They also may correspond to customer
services that are not visible outside the service provider's network.
Internal more specific routes are not exported to any external peer.
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Special Purpose Routes</span>
Special purpose routes are those routes that do not fall into any of
the other classes described here. In those cases in which such
routes need to be distinguished, a service provider may color such
routes with a unique value. Examples of special purpose routes
include anycast routes and routes for overlay networks.
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Upstream Routes</span>
Upstream routes are typically learned from an upstream service
provider as part of a transit service contract executed with the
upstream provider.
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. National Routes</span>
These are route sets that are sourced from and/or received within a
particular country.
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Regional Routes</span>
Several global backbones implement regional policy based on their
deployed footprint and on strategic and business imperatives.
Service providers often have settlement-free interconnections with an
Autonomous System (AS) in one region, and that same AS is a customer
in another region. This mandates use of regional routing, including
community attributes set by the network in question to allow easy
discrimination among regional routes. For example, service providers
may treat a route set received from another service provider in
Europe differently than the same route set received in North America,
as it is common practice to sell transit in one region while peering
in the other.
<span class="grey">Meyer Best Current Practice [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. <a href="./rfc1997">RFC 1997</a> Community Encoding and Values</span>
In this section, we provide <a href="./rfc1997">RFC 1997</a> [<a href="./rfc1997" title=""BGP Communities Attribute"">RFC1997</a>] community values for
the categories described above. <a href="./rfc1997">RFC 1997</a> communities are encoded as
BGP Type Code 8, and are treated as 32-bit values ranging from
0x0000000 through 0xFFFFFFF. The values 0x0000000 through 0x0000FFFF
and 0xFFFF0000 through 0xFFFFFFFF are reserved.
The best current practice among service providers is to use the
high-order two octets to represent the provider's AS number, and the
low-order two octets to represent the classification of the route, as
depicted below:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| <AS> | <Value> |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where <AS> is the 16-bit AS number. For example, the encoding
0x2A7C029A would represent the AS 10876 with value 666.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Community Values for BGP Data Collection</span>
In this section, we define the <a href="./rfc1997">RFC 1997</a> community encoding for the
route types described above for use in BGP data collection. It is
anticipated that a service provider's internal community values will
be converted to these standard values for output to a route
collector.
This memo follows the best current practice of using the basic format
<AS>:<Value>. The values for the route categories are described in
the following table:
<span class="grey">Meyer Best Current Practice [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
Category Value
===============================================================
Reserved <AS>:0000000000000000
Customer Routes <AS>:0000000000000001
Peer Routes <AS>:0000000000000010
Internal Routes <AS>:0000000000000011
Internal More Specific Routes <AS>:0000000000000100
Special Purpose Routes <AS>:0000000000000101
Upstream Routes <AS>:0000000000000110
Reserved <AS>:0000000000000111-
<AS>:0000011111111111
National and Regional Routes <AS>:0000100000000000-
<AS>:1111111111111111
Encoded as <AS>:<R><X><CC>
Reserved National and Regional values <AS>:0100000000000000-
<AS>:1111111111111111
Where
<AS> is the 16-bit AS
<R> is the 5-bit Region Identifier
<X> is the 1-bit satellite link indication
X = 1 for satellite links, 0 otherwise
<CC> is the 10-bit ISO-3166-2 country code [<a href="#ref-ISO3166" title=""ISO 3166 Maintenance agency (ISO 3166/MA)"">ISO3166</a>]
and <R> takes the values:
Africa (AF) 00001
Oceania (OC) 00010
Asia (AS) 00011
Antarctica (AQ) 00100
Europe (EU) 00101
Latin America/Caribbean Islands (LAC) 00110
North America (NA) 00111
Reserved 01000-11111
<span class="grey">Meyer Best Current Practice [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
That is:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| <AS> | <R> |X| <CC> |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
For example, the encoding for a national route over a terrestrial
link in AS 10876 from the Fiji Islands would be:
<AS> = 10876 = 0x2A7C
<R> = 00010
<X> = 0
<CC> = Fiji Islands Country Code = 242 = 0011110010
In this case, the low-order 16 bits are 0001000011110010 = 0x10F2.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x2A7C | 0x10F2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note that a configuration language might allow the specification of
this community as 10876:4338 (0x10F2 == 4338 decimal).
Finally, note that these categories are not intended to be mutually
exclusive, and multiple communities can be attached where
appropriate.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Extended Communities</span>
In some cases, the values and their encoding described in <a href="#section-4">Section 4</a>
may clash with a service provider's existing community assignments.
Extended communities [<a href="./rfc4360" title=""BGP Extended Communities Attribute"">RFC4360</a>] provide a convenient mechanism that
can be used to avoid such clashes.
The Extended Communities attribute is a transitive optional BGP
attribute with the Type Code 16 and consists of a set of extended
communities of the following format:
<span class="grey">Meyer Best Current Practice [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type high | Type low(*) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
For purposes of BGP data collection, we encode the communities
described in <a href="#section-4">Section 4</a> using the two-octet AS specific extended
community type, which has the following format:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The two-octet AS specific extended community attribute encodes the
service provider's two-octet Autonomous System number (as assigned by
a Regional Internet Registry, or RIR) in the Global Administrator
field, and the Local Administrator field may encode any information.
This memo assigns Sub-Type 0x0008 for BGP data collection, and
specifies that the <Value> field, as defined in <a href="#section-3.1">Section 3.1</a>, is
carried in the low-order octets of the Local Administrator field.
The two high-order octets of the Local Administrator field are
reserved, and are set to 0x00 when sending and ignored upon receipt.
For example, the extended community encoding for 10876:4338
(representing a terrestrial national route in AS 10876 from the Fiji
Islands) would be:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 | 0x0008 | 0x2A7C |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 | 0x00 | 0x10F2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">Meyer Best Current Practice [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Four-Octet AS Specific Extended Communities</span>
The four-octet AS specific extended community is encoded as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x02 | 0x0008 | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) | 0x10F2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In this case, the four-octet Global Administrator sub-field contains
a four-octet Autonomous System number assigned by the IANA.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Note on BGP UPDATE Packing</span>
Note that data collection communities have the potential of making
the attribute set of a specific route more unique than it would be
otherwise (since each route collects data that is specific to its
path inside one or more ASes). This, in turn, can affect whether
multiple routes can be grouped in the same BGP update message, and it
may lead to increased use of bandwidth, router CPU cycles, and
memory.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
The community encoding described in this memo germinated from an
interesting suggestion from Akira Kato at WIDE. In particular, the
idea would be to use the collection community values to select paths
that would result in (hopefully) more efficient access to various
services. For example, in the case of <a href="./rfc3258">RFC 3258</a> [<a href="./rfc3258" title=""Distributing Authoritative Name Servers via Shared Unicast Addresses"">RFC3258</a>] based DNS
anycast service, BGP routers may see multiple paths to the same
prefix, and others might be coming from the same origin with
different paths, but others might be from different region/country
(with the same origin AS).
Joe Abley, Randy Bush, Sean Donelan, Xenofontas Dimitropoulos, Vijay
Gill, John Heasley, Geoff Huston, Steve Huter, Michael Patton,
Olivier Marce, Ryan McDowell, Rob Rockell, Rob Thomas, Pekka Savola,
Patrick Verkaik, and Alex Zinin all made many insightful comments on
early versions of this document. Henk Uijterwaal suggested the use
of the ISO-3166-2 country codes.
<span class="grey">Meyer Best Current Practice [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
While this memo introduces no additional security considerations into
the BGP protocol, the information contained in the communities
defined in this memo may in some cases reveal network structure that
was not previously visible outside the provider's network. As a
result, care should be taken when exporting such communities to route
collectors. Finally, routes exported to a route collector should
also be tagged with the NO_EXPORT community (0xFFFFFF01).
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Total Path Attribute Length</span>
The communities described in this memo are intended for use on egress
to a route collector. Hence an operator may choose to overwrite its
internal communities with the values specified in this memo when
exporting routes to a route collector. However, operators should in
general ensure that the behavior of their BGP implementation is
well-defined when the addition of an attribute causes a PDU to exceed
4096 octets. For example, since it is common practice to use
community attributes to implement policy (among other functionality
such as allowing customers to set attributes such as LOCAL_PREF), the
behavior of an implementation when the attribute space overflows is
crucial. Among other behaviors, an implementation might usurp the
intended attribute data or otherwise cause indeterminate failures.
These behaviors can result in unanticipated community attribute sets,
and hence result in unintended policy implications.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
This memo assigns a new Sub-Type for the AS specific extended
community type in the First Come First Served extended transitive
category. The IANA has assigned Sub-Type 0x0008 as defined in
<a href="#section-4.1">Section 4.1</a>.
In addition, the IANA has created two registries for BGP Data
Collection Communities, one for standard communities and one for
extended communities. Both of these registries will initially be
populated by the values described in <a href="#section-4">Section 4</a>. IETF Consensus, as
described in [<a href="./rfc2434" title="">RFC2434</a>], usually through the Global Routing Operations
Working Group (grow), is required for the assignment of new values in
these registries (in particular, for <Value> or <R> in the table of
values for the route categories in <a href="#section-4">Section 4</a>).
<span class="grey">Meyer Best Current Practice [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-ISO3166">ISO3166</a>] "ISO 3166 Maintenance agency (ISO 3166/MA)", Web
Page: <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html">http://www.iso.org/iso/en/prods-services/</a>
<a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html">iso3166ma/index.html</a>, 2004.
[<a id="ref-RFC1771">RFC1771</a>] Rekhter, Y. and T. Li (Editors), "A Border Gateway
Protocol (BGP-4)", <a href="./rfc1771">RFC 1771</a>, March 1995.
[<a id="ref-RFC1997">RFC1997</a>] Chandra, R. and P. Traina, "BGP Communities
Attribute", <a href="./rfc1997">RFC 1997</a>, August 1996.
[<a id="ref-RFC4360">RFC4360</a>] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", <a href="./rfc4360">RFC 4360</a>, January 2006.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-HUSTON">HUSTON</a>] Huston, G., "Interconnection, Peering, and
Settlements",
<a href="http://www.isoc.org/inet99/proceedings/1e/1e_1.htm">http://www.isoc.org/inet99/proceedings/1e/1e_1.htm</a>
[<a id="ref-RFC2434">RFC2434</a>] Narten, T., and H. Alvestrand, "Guidelines for
Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP</a>
<a href="https://www.rfc-editor.org/bcp/bcp26">26</a>, <a href="./rfc2434">RFC 2434</a>, October 1998.
[<a id="ref-RFC3258">RFC3258</a>] Hardie, T., "Distributing Authoritative Name Servers
via Shared Unicast Addresses", <a href="./rfc3258">RFC 3258</a>, April 2002.
[<a id="ref-RIS">RIS</a>] "The RIPE Routing Information Service", Web Page:
<a href="http://www.ripe.net/ris">http://www.ripe.net/ris</a>, 2004.
[<a id="ref-RV">RV</a>] Meyer, D., "The Routeviews Project", Web Page:
<a href="http://www.routeviews.org">http://www.routeviews.org</a>, 2002.
[<a id="ref-VPLS">VPLS</a>] Kompella, K., et al., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22Virtual+Private+LAN+Service%22'>"Virtual Private LAN Service"</a>,
Work in Progress, April 2005.
[<a id="ref-WANG">WANG</a>] Wang, F. and L. Gao, "Inferring and Characterizing
Internet Routing Policies", ACM SIGCOMM Internet
Measurement Conference 2003.
Author's Address
David Meyer
EMail: dmm@1-4-5.net
<span class="grey">Meyer Best Current Practice [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc4384">RFC 4384</a> BGP Communities for Data Collection February 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Meyer Best Current Practice [Page 12]
</pre>
|
