draft-ietf-bess-orf-covering-prefixes-02.txt   draft-ietf-bess-orf-covering-prefixes-03.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Expires: August 7, 2015 Verizon Expires: August 7, 2015 Verizon
R. Bonica R. Bonica
Juniper Networks Juniper Networks
K. Patel K. Patel
Cisco Systems Cisco Systems
L. Yong L. Yong
Huawei Technologies Huawei Technologies
February 3, 2015 February 3, 2015
Covering Prefixes Outbound Route Filter for BGP-4 Covering Prefixes Outbound Route Filter for BGP-4
draft-ietf-bess-orf-covering-prefixes-02 draft-ietf-bess-orf-covering-prefixes-03
Abstract Abstract
This document defines a new Outbound Route Filter (ORF) type, called This document defines a new Outbound Route Filter (ORF) type, called
the "Covering Prefixes ORF (CP-ORF)". CP-ORF is applicable in the "Covering Prefixes ORF (CP-ORF)". CP-ORF is applicable in
Virtual Hub-and-Spoke VPNs. It also is applicable in BGP/MPLS Virtual Hub-and-Spoke VPNs. It also is applicable in BGP/MPLS
Ethernet VPN (EVPN) networks. Ethernet VPN (EVPN) networks.
Requirements Language Requirements Language
skipping to change at page 2, line 37 skipping to change at page 2, line 37
4.1. Multicast Considerations . . . . . . . . . . . . . . . . 12 4.1. Multicast Considerations . . . . . . . . . . . . . . . . 12
5. Applicability In BGP/MPLS Ethernet VPN (EVPN) . . . . . . . . 12 5. Applicability In BGP/MPLS Ethernet VPN (EVPN) . . . . . . . . 12
6. Clean-up . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6. Clean-up . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 17 8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
11.1. Normative References . . . . . . . . . . . . . . . . . . 17 11.1. Normative References . . . . . . . . . . . . . . . . . . 17
11.2. Informative References . . . . . . . . . . . . . . . . . 18 11.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
A BGP [RFC4271] speaker can send Outbound Route Filters (ORF) A BGP [RFC4271] speaker can send Outbound Route Filters (ORF)
[RFC5291] to a peer. The peer uses ORFs to filter routing updates [RFC5291] to a peer. The peer uses ORFs to filter routing updates
that it sends to the BGP speaker. Using ORF, a BGP speaker can that it sends to the BGP speaker. Using ORF, a BGP speaker can
realize a "route pull" paradigm, in which the BGP speaker, on demand, realize a "route pull" paradigm, in which the BGP speaker, on demand,
pulls certain routes from the peer. pulls certain routes from the peer.
This document defines a new ORF-type, called the "Covering Prefixes This document defines a new ORF-type, called the "Covering Prefixes
skipping to change at page 17, line 22 skipping to change at page 17, line 22
receive the CP-ORF only to known, trusted iBGP peers receive the CP-ORF only to known, trusted iBGP peers
o Enforce a per-peer limit on the number of CP-ORFs that can be o Enforce a per-peer limit on the number of CP-ORFs that can be
installed at any given time. Ignore all requests to add CP-ORFs installed at any given time. Ignore all requests to add CP-ORFs
beyond that limit beyond that limit
Section 5 of RFC 5291 describes how BGP speakers use the Outbound Section 5 of RFC 5291 describes how BGP speakers use the Outbound
Route Filtering Capability to advertise their intention to send CP- Route Filtering Capability to advertise their intention to send CP-
ORFs and their willingness to accept CP-ORFs. ORFs and their willingness to accept CP-ORFs.
Security considerations for BGP are presented in RFC4271 while
further security analysis of BGP is found in [RFC6952].
9. Contributors 9. Contributors
The following individuals contributed to the development of this The following individuals contributed to the development of this
document: document:
o Yakov Rekhter o Yakov Rekhter
o Xiaohu Xu o Xiaohu Xu
10. Acknowledgements 10. Acknowledgements
skipping to change at page 18, line 44 skipping to change at page 18, line 47
[IANA.AFI] [IANA.AFI]
IANA, "Address Family Numbers", IANA, "Address Family Numbers",
<http://www.iana.org/assignments/address-family-numbers/ <http://www.iana.org/assignments/address-family-numbers/
address-family-numbers.xhtml>. address-family-numbers.xhtml>.
[IANA.SAFI] [IANA.SAFI]
IANA, "Subsequent Address Family Identifiers (SAFI) IANA, "Subsequent Address Family Identifiers (SAFI)
Parameters", <http://www.iana.org/assignments/safi- Parameters", <http://www.iana.org/assignments/safi-
namespace/safi-namespace.xhtml#safi-namespace-2>. namespace/safi-namespace.xhtml#safi-namespace-2>.
[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
BGP, LDP, PCEP, and MSDP Issues According to the Keying
and Authentication for Routing Protocols (KARP) Design
Guide", RFC 6952, May 2013.
Authors' Addresses Authors' Addresses
Huajin Jeng Huajin Jeng
AT&T AT&T
Email: hj2387@att.com Email: hj2387@att.com
Luay Jalil Luay Jalil
Verizon Verizon
Email: luay.jalil@verizon.com Email: luay.jalil@verizon.com
Ron Bonica Ron Bonica
Juniper Networks Juniper Networks
2251 Corporate Park Drive 2251 Corporate Park Drive
Herndon, Virginia 20170 Herndon, Virginia 20170
USA USA
 End of changes. 5 change blocks. 
2 lines changed or deleted 11 lines changed or added

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