draft-ietf-bess-orf-covering-prefixes-03.txt   draft-ietf-bess-orf-covering-prefixes-04.txt 
BESS Routing Working Group H. Jeng BESS Routing Working Group H. Jeng
Internet-Draft AT&T Internet-Draft AT&T
Intended status: Standards Track L. Jalil Intended status: Standards Track L. Jalil
Expires: August 7, 2015 Verizon Expires: August 24, 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 20, 2015
Covering Prefixes Outbound Route Filter for BGP-4 Covering Prefixes Outbound Route Filter for BGP-4
draft-ietf-bess-orf-covering-prefixes-03 draft-ietf-bess-orf-covering-prefixes-04
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 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 7, 2015. This Internet-Draft will expire on August 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 9 skipping to change at page 3, line 9
This document defines a new ORF-type, called the "Covering Prefixes This document defines a new ORF-type, called the "Covering Prefixes
ORF (CP-ORF)". CP-ORF is applicable in Virtual Hub-and-Spoke VPNs ORF (CP-ORF)". CP-ORF is applicable in Virtual Hub-and-Spoke VPNs
[RFC7024] [RFC4364]. It also is applicable BGP/MPLS Ethernet VPN [RFC7024] [RFC4364]. It also is applicable BGP/MPLS Ethernet VPN
(EVPN) [I-D.ietf-l2vpn-evpn] networks. (EVPN) [I-D.ietf-l2vpn-evpn] networks.
1.1. Terminology 1.1. Terminology
This document uses the following terms: This document uses the following terms:
o Address Family Indicator (AFI) - defined in [RFC4760] o Address Family Identifier (AFI) - defined in [RFC4760]
o Subsequent Address Family Indicator (SAFI) - defined in [RFC4760] o Subsequent Address Family Identifier (SAFI) - defined in [RFC4760]
o VPN IP Default Route - defined in [RFC7024]. o VPN IP Default Route - defined in [RFC7024].
o V-Hub - defined in [RFC7024]. o V-Hub - defined in [RFC7024].
o V-Spoke - defined in [RFC7024]. o V-Spoke - defined in [RFC7024].
o BGP/MPLS Ethernet VPN (EVPN) - defined in [I-D.ietf-l2vpn-evpn] o BGP/MPLS Ethernet VPN (EVPN) - defined in [I-D.ietf-l2vpn-evpn]
o EVPN Instance (EVI) - defined in [I-D.ietf-l2vpn-evpn] o EVPN Instance (EVI) - defined in [I-D.ietf-l2vpn-evpn]
skipping to change at page 5, line 27 skipping to change at page 5, line 27
If the ROUTE-REFRESH AFI is equal to IPv4: If the ROUTE-REFRESH AFI is equal to IPv4:
o The value of Minlen MUST be less than or equal to 32 o The value of Minlen MUST be less than or equal to 32
o The value of Maxlen MUST be less than or equal to 32 o The value of Maxlen MUST be less than or equal to 32
o The value of Minlen MUST be less than or equal to the value of o The value of Minlen MUST be less than or equal to the value of
Maxlen Maxlen
o The value of Route Type MUST be 0 (i.e., undefined) o The value of Route Type MUST be 0 (i.e., RESERVED)
o The Host Address MUST contain exactly 32 bits o The Host Address MUST contain exactly 32 bits
If the ROUTE-REFRESH AFI is equal to IPv6: If the ROUTE-REFRESH AFI is equal to IPv6:
o The value of Minlen MUST be less than or equal to 128 o The value of Minlen MUST be less than or equal to 128
o The value of Maxlen MUST be less than or equal to 128 o The value of Maxlen MUST be less than or equal to 128
o The value of Minlen MUST be less than or equal to the value of o The value of Minlen MUST be less than or equal to the value of
Maxlen Maxlen
o The value of Route Type MUST be 0 (i.e., undefined) o The value of Route Type MUST be 0 (i.e., RESERVED)
o The Host Address MUST contain exactly 128 bits o The Host Address MUST contain exactly 128 bits
If the ROUTE-REFRESH AFI is equal to L2VPN, the value of Route Type If the ROUTE-REFRESH AFI is equal to L2VPN, the value of Route Type
MUST be one of the following: MUST be one of the following values, taken from IANA EVPN Registry
[IANA.EVPN]:
o 1 - Ethernet Autodiscovery Route o 1 - Ethernet Autodiscovery Route
o 2 - MAC/IP Advertisement Route o 2 - MAC/IP Advertisement Route
o 3 - Inclusive Multicast Route o 3 - Inclusive Multicast Route
o 4 - Ethernet Segment Route o 4 - Ethernet Segment Route
If the ROUTE-REFRESH AFI is equal to L2VPN and the value of Route If the ROUTE-REFRESH AFI is equal to L2VPN and the value of Route
Type is equal to Ethernet Autodiscovery Route, Inclusive Multicast Type is equal to Ethernet Autodiscovery Route, Inclusive Multicast
Route, or Ethernet Segment Route: Route, or Ethernet Segment Route:
o The value of Minlen MUST be equal to 0 o The value of Minlen MUST be equal to 0
o The value of Maxlen MUST be equal to 0 o The value of Maxlen MUST be equal to 0
skipping to change at page 18, line 42 skipping to change at page 18, line 42
Y., and R. Aggarwal, "Virtual Hub-and-Spoke in BGP/MPLS Y., and R. Aggarwal, "Virtual Hub-and-Spoke in BGP/MPLS
VPNs", RFC 7024, October 2013. VPNs", RFC 7024, October 2013.
11.2. Informative References 11.2. Informative References
[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.EVPN]
IANA, "Ethernet VPN (EVPN)",
<http://www.iana.org/assignments/evpn/evpn.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 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
BGP, LDP, PCEP, and MSDP Issues According to the Keying BGP, LDP, PCEP, and MSDP Issues According to the Keying
and Authentication for Routing Protocols (KARP) Design and Authentication for Routing Protocols (KARP) Design
Guide", RFC 6952, May 2013. Guide", RFC 6952, May 2013.
 End of changes. 12 change blocks. 
10 lines changed or deleted 15 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/