draft-ietf-idr-flowspec-l2vpn-04.txt   draft-ietf-idr-flowspec-l2vpn-05.txt 
IDR W. Hao IDR W. Hao
Q. Liang Q. Liang
Internet Draft Huawei Internet Draft Huawei
Intended status: Standards Track Jim Uttaro Intended status: Standards Track Jim Uttaro
AT&T AT&T
S. Litkowski S. Litkowski
Orange Business Service Orange Business Service
S. Zhuang S. Zhuang
Huawei Huawei
Expires: November 2016 May 17, 2016 Expires: June 2017 December 30, 2016
Dissemination of Flow Specification Rules for L2 VPN Dissemination of Flow Specification Rules for L2 VPN
draft-ietf-idr-flowspec-l2vpn-04.txt draft-ietf-idr-flowspec-l2vpn-05.txt
Abstract Abstract
This document defines BGP flow-spec extension for Ethernet traffic This document defines BGP flow-spec extension for Ethernet traffic
filtering in L2 VPN network. SAFI=134 in [RFC5575] is redefined for filtering in L2 VPN network. SAFI=134 in [RFC5575] is redefined for
dissemination traffic filtering information in an L2VPN environment. dissemination traffic filtering information in an L2VPN environment.
A new subset of component types and extended community also are A new subset of component types and extended community also are
defined. defined.
Status of this Memo Status of this Memo
skipping to change at page 3, line 32 skipping to change at page 3, line 32
auto-discovery [6074]. auto-discovery [6074].
This draft proposes a new subset of component types and extended This draft proposes a new subset of component types and extended
community to support L2VPN flow-spec application. The flow-spec community to support L2VPN flow-spec application. The flow-spec
rules can be enforced on all border routers or on some interface rules can be enforced on all border routers or on some interface
sets of the border routers. SAFI=134 in [RFC5575] is redefined for sets of the border routers. SAFI=134 in [RFC5575] is redefined for
dissemination traffic filtering information in an L2VPN environment. dissemination traffic filtering information in an L2VPN environment.
2. Layer 2 Flow Specification encoding in BGP 2. Layer 2 Flow Specification encoding in BGP
The [RFC5575] defines SAFI 133 and SAFI 134 for ''dissemination of The [RFC5575] defines SAFI 133 and SAFI 134 for "dissemination of
IPv4 flow specification rules'' and ''dissemination of VPNv4 flow IPv4 flow specification rules" and "dissemination of VPNv4 flow
specification rules'' respectively. [draft-ietf-idr-flow-spec-v6-06] specification rules" respectively. [draft-ietf-idr-flow-spec-v6-06]
redefines the [RFC5575] SAFIs in order to make them applicable to redefines the [RFC5575] SAFIs in order to make them applicable to
both IPv4 and IPv6 applications. This document will further redefine both IPv4 and IPv6 applications. This document will further redefine
the SAFI 134 in order to make them applicable to L2VPN applications. the SAFI 134 in order to make them applicable to L2VPN applications.
The following changes are defined: The following changes are defined:
''SAFI 134 for dissemination of L3VPN flow specification rules'' to "SAFI 134 for dissemination of L3VPN flow specification rules" to
now be defined as ''SAFI 134 for dissemination of VPN flow now be defined as "SAFI 134 for dissemination of VPN flow
specification rules'' specification rules"
For SAFI 134 the indication to which address family it is referring For SAFI 134 the indication to which address family it is referring
to will be recognized by AFI value (AFI=1 for VPNv4, AFI=2 VPNv6 and to will be recognized by AFI value (AFI=1 for VPNv4, AFI=2 VPNv6 and
AFI=25 for L2VPN). Such modification is fully backwards compatible AFI=25 for L2VPN). Such modification is fully backwards compatible
with existing implementation and production deployments. with existing implementation and production deployments.
3. Ethernet Flow Specification encoding in BGP 3. Ethernet Flow Specification encoding in BGP
The NLRI format for this address family consists of a fixed-length The NLRI format for this address family consists of a fixed-length
Route Distinguisher field (8 bytes) followed by a flow specification, Route Distinguisher field (8 bytes) followed by a flow specification,
 End of changes. 4 change blocks. 
8 lines changed or deleted 8 lines changed or added

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