draft-ietf-idr-route-filter-16.txt   draft-ietf-idr-route-filter-17.txt 
Network Working Group E. Chen Network Working Group E. Chen
Internet Draft Cisco Systems Internet Draft Cisco Systems
Expiration Date: March 2007 Y. Rekhter Expiration Date: January 2009 Y. Rekhter
Juniper Networks Juniper Networks
Outbound Route Filtering Capability for BGP-4 Outbound Route Filtering Capability for BGP-4
draft-ietf-idr-route-filter-16.txt draft-ietf-idr-route-filter-17.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 38
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document defines a BGP-based mechanism that allows a BGP speaker This document defines a BGP-based mechanism that allows a BGP speaker
to send to its BGP peer a set of route filters that the peer would to send to its BGP peer a set of Outbound Route Filters (ORFs) that
use to constrain/filter its outbound routing updates to the speaker. the peer would use to constrain/filter its outbound routing updates
to the speaker.
1. Specification of Requirements 1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC-2119]. document are to be interpreted as described in RFC 2119 [RFC-2119].
2. Introduction 2. Introduction
Currently it is not uncommon for a BGP speaker [BGP-4] to receive, Currently it is not uncommon for a BGP speaker [BGP-4] to receive,
skipping to change at page 3, line 5 skipping to change at page 3, line 5
The "ORF-Type" component determines the content of the ORF-value. The "ORF-Type" component determines the content of the ORF-value.
The "Action" component controls handling of the ORF Request by the The "Action" component controls handling of the ORF Request by the
remote peer. Action can be one of ADD, REMOVE, REMOVE-ALL. ADD adds remote peer. Action can be one of ADD, REMOVE, REMOVE-ALL. ADD adds
an ORF entry to the ORF on the remote peer; REMOVE deletes a an ORF entry to the ORF on the remote peer; REMOVE deletes a
previously installed ORF entry on the remote peer; REMOVE-ALL deletes previously installed ORF entry on the remote peer; REMOVE-ALL deletes
the previously installed entries in the specified ORF on the remote the previously installed entries in the specified ORF on the remote
peer. peer.
The "Match" component is used if support matching granularity on a The "Match" component is used to support matching granularity on a
per ORF entry basis is needed, in which case the "Match" component per ORF entry basis. It can be either PERMIT or DENY. The semantics
can be one of PERMIT or DENY. The semantics of PERMIT is to ask the of PERMIT is to ask the peer to pass updates for the set of routes
peer to pass updates for the set of routes that match the ORF entry. that match the ORF entry. The semantics of DENY is to ask the peer
The semantics of DENY is to ask the peer not to pass updates for the not to pass updates for the set of routes that match the ORF entry.
set of routes that match the ORF entry.
When an ORF is defined, an ORF specific matching rule MUST be
specified so that there is no ambiguity regarding which ORF entry is
considered as the matching entry in the ORF when a route is passed
through the ORF.
4. Carrying ORF Entries in BGP 4. Carrying ORF Entries in BGP
ORF entries are carried in the BGP ROUTE-REFRESH message [BGP-RR]. ORF entries are carried in the BGP ROUTE-REFRESH message [BGP-RR].
A BGP speaker can distinguish an incoming ROUTE-REFRESH message that A BGP speaker can distinguish an incoming ROUTE-REFRESH message that
carries one or more ORF entries from an incoming plain ROUTE-REFRESH carries one or more ORF entries from an incoming plain ROUTE-REFRESH
message by using the Message Length field in the BGP message header. message by using the Message Length field in the BGP message header.
A single ROUTE-REFRESH message MAY carry multiple ORF entries, as A single ROUTE-REFRESH message MAY carry multiple ORF entries in one
long as all these entries share the same AFI/SAFI. or more ORFs, as long as all these entries share the same AFI/SAFI.
From the encoding point of view each ORF entry consists of a common From the encoding point of view each ORF entry consists of a common
part and type-specific part as shown in Figure 1. part and type-specific part as shown in Figure 1 and Figure 2.
The common part consists of <AFI/SAFI, ORF-Type, Action, Match>, and The common part consists of <AFI/SAFI, ORF-Type, Action, Match>, and
is encoded as follows: is encoded as follows:
The AFI/SAFI component of an ORF entry is encoded in the AFI/SAFI The AFI/SAFI component of an ORF entry is encoded in the AFI/SAFI
field of the ROUTE-REFRESH message. field of the ROUTE-REFRESH message.
Following the AFI/SAFI component is the one-octet When-to-refresh Following the AFI/SAFI component is the one-octet When-to-refresh
field. The value of this field can be one of IMMEDIATE (0x01) or field. The value of this field can be either IMMEDIATE (0x01) or
DEFER (0x02). The semantics of IMMEDIATE and DEFER are discussed DEFER (0x02). The semantics of IMMEDIATE and DEFER are discussed
in the "Operation" section of this document. in the "Operation" section of this document.
Following the When-to-refresh field is a collection of one or more Following the When-to-refresh field is a collection of one or more
ORFs, grouped by ORF-Type. ORFs, grouped by ORF-Type.
The ORF-Type component is encoded as a one-octet field. The ORF-Type component is encoded as a one-octet field.
The Length of ORFs component is a two-octets field that contains The "Length of ORF entries" component is a two-octet field that
the length (in octets) of the ORF entries that follows. contains the total length (in octets) of the ORF entries that
follows for the specified ORF type.
+--------------------------------------------------+ +--------------------------------------------------+
| Address Family Identifier (2 octets) | | Address Family Identifier (2 octets) |
+--------------------------------------------------+ +--------------------------------------------------+
| Reserved (1 octet) | | Reserved (1 octet) |
+--------------------------------------------------+ +--------------------------------------------------+
| Subsequent Address Family Identifier (1 octet) | | Subsequent Address Family Identifier (1 octet) |
+--------------------------------------------------+ +--------------------------------------------------+
| When-to-refresh (1 octet) | | When-to-refresh (1 octet) |
+--------------------------------------------------+ +--------------------------------------------------+
| ORF Type (1 octet) | | ORF Type (1 octet) |
+--------------------------------------------------+ +--------------------------------------------------+
| Length of ORFs (2 octets) | | Length of ORF entries (2 octets) |
+--------------------------------------------------+ +--------------------------------------------------+
| First ORF entry (variable) | | First ORF entry (variable) |
+--------------------------------------------------+ +--------------------------------------------------+
| Second ORF entry (variable) | | Second ORF entry (variable) |
+--------------------------------------------------+ +--------------------------------------------------+
| ... | | ... |
+--------------------------------------------------+ +--------------------------------------------------+
| N-th ORF entry (variable) | | N-th ORF entry (variable) |
+--------------------------------------------------+ +--------------------------------------------------+
| ORF Type (1 octet) | | ORF Type (1 octet) |
+--------------------------------------------------+ +--------------------------------------------------+
| Length of ORFs (2 octets) | | Length of ORF entries (2 octets) |
+--------------------------------------------------+ +--------------------------------------------------+
| First ORF entry (variable) | | First ORF entry (variable) |
+--------------------------------------------------+ +--------------------------------------------------+
| Second ORF entry (variable) | | Second ORF entry (variable) |
+--------------------------------------------------+ +--------------------------------------------------+
| ... | | ... |
+--------------------------------------------------+ +--------------------------------------------------+
| N-th ORF entry (variable) | | N-th ORF entry (variable) |
+--------------------------------------------------+ +--------------------------------------------------+
| ... | | ... |
skipping to change at page 5, line 27 skipping to change at page 5, line 27
+---------------------------------+ +---------------------------------+
Figure 2: ORF Entry Encoding Figure 2: ORF Entry Encoding
When the Action component of an ORF entry specifies REMOVE-ALL, When the Action component of an ORF entry specifies REMOVE-ALL,
the entry consists of only the common part. the entry consists of only the common part.
5. Outbound Route Filtering Capability 5. Outbound Route Filtering Capability
A BGP speaker that is willing to receive ORF entries from its peer, A BGP speaker that is willing to receive ORF entries from its peer,
or a BGP speaker that would like to send ORF entries to its peer or a BGP speaker that would like to send ORF entries to its peer,
advertises this to the peer by using the Outbound Route Filtering advertises this to the peer by using the Outbound Route Filtering
Capability, as described below. Capability, as described below.
The Outbound Route Filtering Capability is a new BGP capability The Outbound Route Filtering Capability is a new BGP capability
[BGP-CAP] defined as follows: [BGP-CAP] defined as follows:
Capability code: 3 Capability code: 3
Capability length: variable Capability length: variable
skipping to change at page 6, line 51 skipping to change at page 6, line 51
ORF Type: ORF Type:
This field contains the value of an ORF Type. This field contains the value of an ORF Type.
Send/Receive: Send/Receive:
This field indicates whether the sender is (a) willing to This field indicates whether the sender is (a) willing to
receive ORF entries from its peer (value 1), (b) would like to receive ORF entries from its peer (value 1), (b) would like to
send ORF entries to its peer (value 2), or (c) both (value 3) send ORF entries to its peer (value 2), or (c) both (value 3)
for the ORF Type that follows. for the ORF Type.
6. Operation 6. Operation
A BGP speaker that is willing to receive ORF entries from its peer, A BGP speaker that is willing to receive ORF entries from its peer,
or would like to send ORF entries to its peer SHOULD advertise the or would like to send ORF entries to its peer SHOULD advertise the
Outbound Route Filtering Capability to the peer using BGP Outbound Route Filtering Capability to the peer using BGP
Capabilities advertisement [BGP-CAP]. Capabilities advertisement [BGP-CAP].
A BGP speaker that implements the Outbound Route Filtering Capability A BGP speaker that implements the Outbound Route Filtering Capability
MUST support the BGP ROUTE-REFRESH message, as defined in [BGP-RR]. A MUST support the BGP ROUTE-REFRESH message, as defined in [BGP-RR]. A
BGP speaker that advertises the Outbound Route Filtering Capability BGP speaker that advertises the Outbound Route Filtering Capability
to a peer using BGP Capabilities advertisement [BGP-CAP] does not to a peer using BGP Capabilities advertisement [BGP-CAP] does not
have to advertise the BGP Route Refresh capability to that peer. have to advertise the BGP Route Refresh capability to that peer.
Consider a BGP speaker that advertises the Outbound Route Filtering Consider a BGP speaker that advertises the Outbound Route Filtering
Capability indicating its willingness to receive a particular set of Capability indicating its willingness to receive a particular set of
<AFI, SAFI, ORF-Type> from its peer, and that receives the Outbound <AFI/SAFI, ORF-Type> from its peer, and that receives the Outbound
Route Filtering Capability indicating the desire of the peer to send Route Filtering Capability indicating the desire of the peer to send
a particular set <AFI, SAFI, ORF-Type> to the speaker. If for a given a particular set <AFI/SAFI, ORF-Type> to the speaker. If for a given
<AFI, SAFI> the intersection between these two sets are not-empty, AFI/SAFI the intersection between these two sets is not-empty, the
the speaker SHOULD NOT advertise to the peer any routes with that speaker SHOULD NOT advertise to the peer any routes with that
<AFI, SAFI> prior to receiving from the peer any ROUTE-REFRESH AFI/SAFI prior to receiving from the peer any ROUTE-REFRESH message
message carrying that <AFI, SAFI>, where the message could be either carrying that AFI/SAFI, where the message could be either without any
without any ORF entries, or with one or more ORF entry and When-to- ORF entries, or with one or more ORF entry and When-to-refresh field
refresh field set to IMMEDIATE. If, on the other hand, for a given set to IMMEDIATE. If, on the other hand, for a given AFI/SAFI the
<AFI, SAFI> the intersection between these two sets is empty, the intersection between these two sets is empty, the speaker MUST follow
speaker SHOULD follow normal BGP procedures. normal BGP procedures.
A BGP speaker may send a ROUTE-REFRESH message with one or more ORF A BGP speaker may send a ROUTE-REFRESH message with one or more ORF
entries to its peer only if the peer advertises to the speaker the entries to its peer only if the peer advertises to the speaker the
Outbound Route Filtering Capability indicating its willingness to Outbound Route Filtering Capability indicating its willingness to
receive ORF entries from the speaker, and the speaker advertises to receive ORF entries from the speaker, and the speaker advertises to
the peer the Outbound Route Filtering Capability indicating its the peer the Outbound Route Filtering Capability indicating its
desire to send ORF entries to the peer. The message may contain only desire to send ORF entries to the peer. The message may contain only
ORF entries of <AFI, SAFI, ORF-type> that the peer is willing to ORF entries of <AFI/SAFI, ORF-type> that the peer is willing to
receive, as advertised to the speaker in the Outbound Route Filtering receive, as advertised to the speaker in the Outbound Route Filtering
Capability. Capability.
When a BGP speaker receives a ROUTE-REFRESH message with one or more When a BGP speaker receives a ROUTE-REFRESH message with one or more
ORF entries from its peer, then the speaker performs the following ORF entries from its peer, then the speaker performs the following
actions. If the <AFI, SAFI, ORF-type> carried by the message does not actions. If an <AFI/SAFI, ORF-type> carried by the message does not
match <AFI, SAFI, ORF-type> that the speaker is willing to receive match <AFI/SAFI, ORF-type> that the speaker is willing to receive
from the peer (as advertised to the peer in the Outbound Route from the peer (as advertised to the peer in the Outbound Route
Filtering Capability), the specified ORF is ignored. Otherwise, the Filtering Capability), the specified ORF entries in the message are
speaker modifies the specified ORF, as specified in the ORF entries ignored. Otherwise, the speaker modifies the specified ORF
carried by the message. If any of the fields within an ORF entry previously received, according to the ORF entries carried in the
contain an unrecognized value, the whole specified ORF is removed. message. If any of the fields of an ORF entry in the message contains
an unrecognized value, the whole specified ORF previously received is
removed.
If the Action component of an ORF entry is REMOVE, but the ORF does If the Action component of an ORF entry is REMOVE, but the ORF
not contain the specified entry, the entry is ignored. previously received does not contain the specified entry, the ORF
entry in the message is ignored.
ORF entries with either REMOVE or REMOVE-ALL can not remove locally ORF entries with either REMOVE or REMOVE-ALL can not remove locally
configured outbound route filters. configured outbound route filters.
If the When-to-refresh indicates IMMEDIATE, then after processing all If the When-to-refresh indicates IMMEDIATE, then after processing all
the ORF entries carried in the message the speaker re-advertises to the ORF entries carried in the message the speaker re-advertises to
the peer routes from the Adj-RIB-Out associated with the peer that the peer routes from the Adj-RIB-Out associated with the peer that
have the same AFI/SAFI as what is carried in the message, and taking have the same AFI/SAFI as what is carried in the message, and taking
into account all the ORF entries for that AFI/SAFI received from the into account all the ORF entries for that AFI/SAFI received from the
peer. The speaker MUST re-advertise all the routes that have been peer. The speaker MUST re-advertise all the routes that have been
skipping to change at page 8, line 31 skipping to change at page 8, line 34
advertisement to the peer routes from the Adj-RIB-Out associated with advertisement to the peer routes from the Adj-RIB-Out associated with
the peer that have the same AFI/SAFI as what is carried in the the peer that have the same AFI/SAFI as what is carried in the
message, and taking into account all the ORF entries received from message, and taking into account all the ORF entries received from
the peer until the speaker receives a subsequent ROUTE-REFRESH the peer until the speaker receives a subsequent ROUTE-REFRESH
message for the same AFI/SAFI either without any ORF entries, or with message for the same AFI/SAFI either without any ORF entries, or with
one or more ORF entries and When-to-refresh set to IMMEDIATE. one or more ORF entries and When-to-refresh set to IMMEDIATE.
If the speaker receives from the peer a ROUTE-REFRESH message without If the speaker receives from the peer a ROUTE-REFRESH message without
any ORF entries, then the speaker sends to the peer all routes from any ORF entries, then the speaker sends to the peer all routes from
the Adj-RIB-Out associated with the peer whose AFI/SAFI is the same the Adj-RIB-Out associated with the peer whose AFI/SAFI is the same
as what is carried in the message and taking into account the ORF as what is carried in the message and taking into account the ORFs
received from the peer. (if any) previously received from the peer.
The set of ORF entries that the speaker sends to the peer expresses The set of ORF entries that the speaker sends to the peer expresses
the speaker's local preference, that the peer MAY or MAY NOT decide the speaker's local preference, that the peer may or may not decide
to honor. to honor.
During a single BGP session the speaker MAY pass multiple ORF entries During a single BGP session the speaker MAY pass multiple ORF entries
to the peer. to the peer.
After a BGP speaker makes changes to the ORF entries previously sent After a BGP speaker makes changes to the ORF entries previously sent
to a peer, the speaker SHOULD send to the peer the updated ORF to a peer, the speaker MUST send to the peer the updated ORF entries
entries with either (a) When-to-refresh set to IMMEDIATE, or (b) with either (a) When-to-refresh set to IMMEDIATE, or (b) When-to-
When-to-refresh set to DEFER followed by a ROUTE-REFRESH message. The refresh set to DEFER followed by a plain ROUTE-REFRESH message. The
latter SHALL be used by the speaker when there are other policy latter MUST be used by the speaker when there are other policy
changes (in addition to the ORF entries) that require the peer to changes (in addition to the ORF entries) that require the peer to
re-advertise all the routes. re-advertise all the routes.
The lifetime of an ORF is the duration of the BGP session during The lifetime of an ORF is the duration of the BGP session during
which the ORF is exchanged. which the ORF is exchanged.
An ORF is removed when the last ORF entry is removed (either via An ORF is removed when the last ORF entry is removed (either via
REMOVE-ALL, or via a sequence of REMOVE). REMOVE-ALL, or via a sequence of REMOVE).
If a particular route maintained by a BGP speaker does not match any If a particular route maintained by a BGP speaker does not match any
skipping to change at page 10, line 5 skipping to change at page 10, line 5
- ORF-Type values 1 through 63 are to be assigne dby IANA using - ORF-Type values 1 through 63 are to be assigne dby IANA using
either the Standards Action process defined in RFC 2434, or the either the Standards Action process defined in RFC 2434, or the
Early IANA Allocation process defined in RFC 4020. Early IANA Allocation process defined in RFC 4020.
- ORF-Type values 64 through 127 are to be assigned by IANA, using - ORF-Type values 64 through 127 are to be assigned by IANA, using
the "First Come First Served" policy defined in RFC 2434. the "First Come First Served" policy defined in RFC 2434.
- ORF-Type values 128 through 255 are vendor-specific, and values - ORF-Type values 128 through 255 are vendor-specific, and values
in this range are not to be assigned by IANA. in this range are not to be assigned by IANA.
8. Security Considerations 8. Manageability Considerations
This extension to BGP does not change the underlying security issues. The management objects for BGP ORFs will be defined separately,
outside this document. However, it is suggested that the following
management objects be defined:
9. Intellectual Property Considerations The ORF capability object, which describes the ORF capability
exchanged over a BGP session, should include the ORF types and the
Send/Receive values advertised and received for a BGP peer.
The ORF entry object should contain the ORF entries of each ORF sent
and received for a BGP peer.
9. Security Considerations
This extension to BGP does not change the underlying security issues
[BGP-4].
10. Intellectual Property Considerations
This section is taken from Section 5 of RFC 3668. This section is taken from Section 5 of RFC 3668.
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 10, line 35 skipping to change at page 11, line 5
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
10. Copyright Notice 11. Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
11. Acknowledgements 12. Acknowledgments
Some of the material in the document is adapted from a proposal for Some of the material in the document is adapted from a proposal for
selective updates by Yakov Rekhter, Kannan Varadhan, and Curtis selective updates by Yakov Rekhter, Kannan Varadhan, and Curtis
Villamizar. Villamizar.
12. Normative References 13. Normative References
[BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol [BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol
4 (BGP-4)", RFC 4271, January 2006. 4 (BGP-4)", RFC 4271, January 2006.
[BGP-MP] Bates, T., Chandra, R., Katz, D., and Rekhter, Y., [BGP-MP] Bates, T., Chandra, R., Rekhter, Y., and D. Katz,
"Multiprotocol Extensions for BGP-4", draft-ietf-idr-rfc1858bis- "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007.
10.txt.
[BGP-CAP] Chandra, R., Scudder, J., "Capabilities Advertisement with [BGP-CAP] Chandra, R., Scudder, J., "Capabilities Advertisement with
BGP-4", RFC 3392, November 2002. BGP-4", RFC 3392, November 2002.
[BGP-RR] Chen, E., "Route Refresh Capability for BGP-4", RFC 2918, [BGP-RR] Chen, E., "Route Refresh Capability for BGP-4", RFC 2918,
September 2000. September 2000.
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
13. Author Information 14. Author Information
Enke Chen Enke Chen
Cisco Systems, Inc. Cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Email: enkechen@cisco.com Email: enkechen@cisco.com
Yakov Rekhter Yakov Rekhter
Juniper Networks Juniper Networks
 End of changes. 31 change blocks. 
61 lines changed or deleted 83 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/