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
|
Capability Codes - Per [RFC2842]
As specified in this document, the Capability optional parameter
contains the Capability Code field. Capability Code value 0 is
reserved. Capability Code values 1 through 63 are to be assigned by
IANA using the "IETF Consensus" policy defined in RFC2434. Capability
Code values 64 through 127 are to be assigned by IANA, using the
"First Come First Served" policy defined in RFC2434. Capability
Code values 128 through 255 are vendor-specific, and values in this
range are not to be assigned by IANA.
Capability Codes
Value Description Reference
------- ------------------------------------------ ---------
0 Reserved [RFC2842]
1 Multiprotocol Extensions for BGP-4 [RFC2858]
2 Route Refresh Capability for BGP-4 [RFC2918]
3 Cooperative Route Filtering Capability [Rekhter]
4 Multiple routes to a destination capability [RFC3107]
5-63 Unassigned
64 Graceful Restart Capability [Chen]
65-127 Unassigned
128-255 Vendor Specific
References
----------
[RFC2842] Chandra, R., and J. Scudder, "Capabilities Advertisement
with BGP-4", RFC 2842, May 2000.
[RFC2858] Bates, T., Y. Rekhter, R. Chandra, and D. Katz,
"Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.
[RFC2918] Chen, E., "Route Refresh Capability for BGP-4", RFC 2918,
September 2000.
[RFC3107] Y. Rekhter and E. Rosen, "Carrying Label Information in
BGP-4", RFC 3107, May 2001.
People
------
[Chandra] Ravi Chandra, <rchandra@siara.com>, May 2000
[Chen] Enke Chen, <enke@redback.com>, October 2000.
[Rekhter] Yakov Rekhter, <yakov@cisco.com>, October 2000.
(last updated May 10 2001)
[]
|
