draft-ietf-idr-flowspec-l2vpn-03.txt   draft-ietf-idr-flowspec-l2vpn-04.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: May 2016 November 16, 2015 Expires: November 2016 May 17, 2016
Dissemination of Flow Specification Rules for L2 VPN Dissemination of Flow Specification Rules for L2 VPN
draft-ietf-idr-flowspec-l2vpn-03.txt draft-ietf-idr-flowspec-l2vpn-04.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 1, line 47 skipping to change at page 1, line 47
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 5, line 33 skipping to change at page 5, line 33
Defines a list of {operation, value} pairs used to match 5-octet Defines a list of {operation, value} pairs used to match 5-octet
SNAP(Sub-Network Access Protocol) field. Values are encoded as 5- SNAP(Sub-Network Access Protocol) field. Values are encoded as 5-
byte quantities. byte quantities.
Type 21 - VLAN ID Type 21 - VLAN ID
Encoding: <type (1 octet), [op, value]+> Encoding: <type (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match VLAN ID. Defines a list of {operation, value} pairs used to match VLAN ID.
Values are encoded as 1- or 2-byte quantities. Values are encoded as 2-byte quantities, where the four most
significant bits are zero and the 12 least significant bits contain
the VLAN value.
In virtual local-area network (VLAN) stacking case, the VLAN ID is In virtual local-area network (VLAN) stacking case, the VLAN ID is
outer VLAN ID. outer VLAN ID.
Type 22 - VLAN COS Type 22 - VLAN COS
Encoding: <type (1 octet), [op, value]+> Encoding: <type (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 3-bit VLAN Defines a list of {operation, value} pairs used to match 3-bit VLAN
COS fields [802.1p]. Values are encoded using a single byte, where COS fields [802.1p]. Values are encoded using a single byte, where
skipping to change at page 6, line 4 skipping to change at page 6, line 9
Defines a list of {operation, value} pairs used to match 3-bit VLAN Defines a list of {operation, value} pairs used to match 3-bit VLAN
COS fields [802.1p]. Values are encoded using a single byte, where COS fields [802.1p]. Values are encoded using a single byte, where
the five most significant bits are zero and the three least the five most significant bits are zero and the three least
significant bits contain the VLAN COS value. significant bits contain the VLAN COS value.
In virtual local-area network (VLAN) stacking case, the VLAN COS is In virtual local-area network (VLAN) stacking case, the VLAN COS is
outer VLAN COS. outer VLAN COS.
Type 23 - Inner VLAN ID Type 23 - Inner VLAN ID
Encoding: <type (1 octet), [op, value]+> Encoding: <type (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match inner VLAN Defines a list of {operation, value} pairs used to match inner VLAN
ID using for virtual local-area network (VLAN) stacking or Q in Q ID using for virtual local-area network (VLAN) stacking or Q in Q
case. Values are encoded as 1- or 2-byte quantities. case. Values are encoded as 2-byte quantities, where the four most
significant bits are zero and the 12 least significant bits contain
the VLAN value.
In single VLAN case, the component type MUST not be used. In single VLAN case, the component type MUST not be used.
Type 24 - Inner VLAN COS Type 24 - Inner VLAN COS
Encoding: <type (1 octet), [op, value]+> Encoding: <type (1 octet), [op, value]+>
Defines a list of {operation, value} pairs used to match 3-bit inner Defines a list of {operation, value} pairs used to match 3-bit inner
VLAN COS fields [802.1p] using for virtual local-area network (VLAN) VLAN COS fields [802.1p] using for virtual local-area network (VLAN)
stacking or Q in Q case. Values are encoded using a single byte, stacking or Q in Q case. Values are encoded using a single byte,
skipping to change at page 8, line 31 skipping to change at page 8, line 31
+--------+------------------------+--------------------------+ +--------+------------------------+--------------------------+
| type | extended community | encoding | | type | extended community | encoding |
+--------+------------------------+--------------------------+ +--------+------------------------+--------------------------+
| TBD1 | VLAN-action | bitmask | | TBD1 | VLAN-action | bitmask |
| TBD2 | TPID-action | bitmask | | TBD2 | TPID-action | bitmask |
+--------+------------------------+--------------------------+ +--------+------------------------+--------------------------+
VLAN-action: The VLAN-action extended community consists of 6 bytes VLAN-action: The VLAN-action extended community consists of 6 bytes
which include the fields of action Flags, two VLAN IDs and the which include the fields of action Flags, two VLAN IDs and the
associating COS value. The action Flags fields are further divided associating COS value. The action Flags fields are further divided
into two parts which corresponds to the first action and the second into two parts which correspond to the first action and the second
action respectively, bit 0 to bit 7 belong to the first action part action respectively, bit 0 to bit 7 belong to the first action part
while bit 8 to bit 15 belong to the second part. The bits of PO, PU, while bit 8 to bit 15 belong to the second part. The bits of PO, PU,
SW, RI and RO in each part represent Pop, Push, Swap, Rewrite inner SW, RI and RO in each part represent the action of Pop, Push, Swap,
VLAN and Rewrite outer VLAN respectively. Through this method, more Rewrite inner VLAN and Rewrite outer VLAN respectively. Through this
complicated actions also can be represented in a single VLAN-action method, more complicated actions also can be represented in a single
extend community, such as SwapPop, PushSwap, etc. For example, VLAN-action extend community, such as SwapPop, PushSwap, etc. For
SwapPop action is the concatenation of two actions, the first action example, SwapPop action is the concatenation of two actions, the
is Swap and the second action is Pop. first action is Swap and the second action is Pop.
0 7 15 0 7 15
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|PO1|PU1|SW1|RI1|RO1|...|PO2|PU2|SW2|RI2|RO2|...| |PO1|PU1|SW1|RI1|RO1|...|PO2|PU2|SW2|RI2|RO2|...|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| VLAN ID1 |COS1 |R1| | VLAN ID1 |COS1 |R1|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| VLAN ID2 |COS2 |R2| | VLAN ID2 |COS2 |R2|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
 End of changes. 8 change blocks. 
12 lines changed or deleted 17 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/