Hi John,

I think the control word function is independent of the tunnel encapsulation. 
It is not very suitable to use the tunnel-encap draft extension.

Regards,
Haibo

From: John E Drake [mailto:jdr...@juniper.net]
Sent: Thursday, October 25, 2018 12:03 AM
To: Alexander Vainshtein <alexander.vainsht...@ecitele.com>; Yutianpeng (Tim) 
<yutianp...@huawei.com>
Cc: bess@ietf.org; draft-wang-bess-evpn-control-word.auth...@ietf.org; 
Wanghaibo (Rainsword) <rainsword.w...@huawei.com>
Subject: RE: A question regarding draft-wang-bess-evepn-control-word

Hi,

Comment inline

Yours Irrespectively,

John

From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> On Behalf Of 
Alexander Vainshtein
Sent: Wednesday, October 24, 2018 11:57 AM
To: Yutianpeng (Tim) <yutianp...@huawei.com<mailto:yutianp...@huawei.com>>
Cc: bess@ietf.org<mailto:bess@ietf.org>; 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>;
 Wanghaibo (Rainsword) 
<rainsword.w...@huawei.com<mailto:rainsword.w...@huawei.com>>
Subject: Re: [bess] A question regarding draft-wang-bess-evepn-control-word

Tim,
Lots of thanks for your email, it really clarifies your approach.

Regarding your proposal to “isolate” PEs that do not support the CW - I suspect 
this is not practical.

EVPN-MPLS implementations are not REQUIRED to support usage of CW. Some 
EVPN-MPLS implementations that I am aware of explicitly state that the CW usage 
can be disabled for interoperability with other vendors, so I think that there 
EVPN implementations that do not support the CW have been deployed.


draft-ietf-pals-ethernet-cw<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dpals-2Dethernet-2Dcw-2D07&d=DwMFoQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=g3IVbNU54cy6Djewd3jxs8hIBf3n6Y8tCS54HplvNNE&s=RlsyHSL6EDro6sABzjF38r6G2sDcGBosVDYDmwnPbZA&e=>
 (already in the RFC Editor queue in the AUTH48 state) says that “where both 
the ingress PE and the egress PE support the Ethernet pseudowire control word, 
then the CW MUST be used”.



Personally I think that this sets the goal that we should achieve in EVPN as 
well:

1.       All EVPN-MPLS implementations MUST support EVPN encapsulations without 
the CW

2.       An egress PE SHOULD indicate, per each L2VPN/EVPN route it advertises, 
whether it can handle received CW in the EVPN encapsulation for packets that 
are sent to it based on this route by ingress PEs, or not, and, if it can, how 
the presence of the CW is indicated.  This can be done using the CW Next-Hop 
Capability and the CWI label as explained in the draft



[JD]  I think it would be better to use this draft:    
https://tools.ietf.org/html/draft-ietf-idr-tunnel-encaps-10





3.       An ingress PE that accepts a L2VPN/EVPN route with the CW next Hop 
Capability, MUST insert the CW and indicate its presence, if it supports CWI 
and CW insertion in the appropriate EVPN encapsulation. Please note that the 
ability to insert CWI and CW may differ for different L2VPN/EVPN routes. E.g.. 
the same PE can:

a.       Support the CWI and CW insertion in the EVPN encapsulation of “known 
unicast” frames and BUM frames if their encapsulation does not require 
insertion of the ESI label

b.      Not support CWI and CW insertion in the EVPN encapsulation of BUM 
frames if this inclusion of the ESI label in their encapsulation is required.



This approach would  meet with the old IETF design principle: “Be strict in 
what you transmit and liberal in what you receive”.

Hope this helps.

My 2c,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   
alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>

From: Yutianpeng (Tim) [mailto:yutianp...@huawei.com]
Sent: Wednesday, October 24, 2018 5:32 PM
To: Alexander Vainshtein 
<alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>>
Cc: 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>;
 bess@ietf.org<mailto:bess@ietf.org>; Wanghaibo (Rainsword) 
<rainsword.w...@huawei.com<mailto:rainsword.w...@huawei.com>>
Subject: RE: A question regarding draft-wang-bess-evepn-control-word

Hi Sasha,
Thanks a lot for your advice.
I agree with you that CW is not mandatory for all traffic, mainly unicast. This 
draft focuses on CW capability advertisement and is applicable to traffic needs 
CW processing.  So far BUM should be not relevant to this draft. (Multicast 
might need CW potentially we realize recently, but we will visit this topic 
later.)
Some clarification on my proposal:
I believe we need a mechanism of negotiation on CW capabilities in EVPN ELAN. 
If you check PW or EVPN VPWS there is a clear procedure on negotiation between 
two ends.
Refer to: 
https://tools.ietf.org/html/rfc4447#section-6<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc4447-23section-2D6&d=DwMFoQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=g3IVbNU54cy6Djewd3jxs8hIBf3n6Y8tCS54HplvNNE&s=NBPHKHjAHD92xWWgTzgyFMNLRRjgyaGjNsqLclZyQYw&e=>
 and Appendix 
A<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc4447-23appendix-2DA&d=DwMFoQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=g3IVbNU54cy6Djewd3jxs8hIBf3n6Y8tCS54HplvNNE&s=O9MUigxU7UJ6prd0ZtH3-87IEYswalB2pRb1_UuKPyM&e=>
But as EVPN is MP2MP, in case of PE CW behavior can be different between PEs as 
there is no negotiation at all at the moment.
So this draft introduces CW capability which at least allows PEs within EVI 
knows the capability of each other. It also defines behavior after receiving CW 
capabilities.
What I proposed is the behavior in case CW capabilities across PEs are 
different. I mentioned a simple way of tearing down or isolate CW disabled PEs 
and raise an alarm, a bit similar to PW. The draft proposes a graceful way that 
traffic can be forwarded with a label advertised together with CW capability, 
such that egress PE can indicate CW via the label on the forwarding plane.
Happy for further discussion on this as CW of EVPN topic has been raised couple 
of times recently.
Thanks & Regards,
Tim

From: Alexander Vainshtein [mailto:alexander.vainsht...@ecitele.com]
Sent: 24 October 2018 09:39
To: Yutianpeng (Tim) <yutianp...@huawei.com<mailto:yutianp...@huawei.com>>
Cc: 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>;
 bess@ietf.org<mailto:bess@ietf.org>; Wanghaibo (Rainsword) 
<rainsword.w...@huawei.com<mailto:rainsword.w...@huawei.com>>
Subject: RE: A question regarding draft-wang-bess-evepn-control-word

Tim,
Lots of thanks for sharing your views.

Unfortunately, I doubt the approach that you propose: always use or do not use 
CW in the same EVI.

The problem, as I see it is that known unicast and BUM traffic may be handled 
differently when it comes to EVPN encapsulation:

1.       Section 18 of RFC 7432 explicitly states that “When sending 
EVPN-encapsulated packets over a P2MP LSP or P2P LSP, then the control word 
SHOULD NOT be used”

a.       This recommendation is quite reasonable because the LSPs in question 
are not affected by ECMP, so there is no need to use the CW to prevent 
ECMP-cause reordering

b.      It is quite possible to P2MP LSPs as the P-tunneling technology 
delivery of BUM traffic in EVPN while using MP2P LSPs for carrying known 
unicast traffic

c.       The bottom line: RFC 7432 defines the  scenario when the CW SHOULD be 
used in the EVPN encapsulation of the known unicast traffic but SHOULD NOT be 
used in the EVPN encapsulation of BUM traffic as valid

2.       I am aware (this information is publicly available) of at least one 
deployed EVPN implementation that:

a.       By default includes the CW in the EVPN encapsulation of known unicast 
traffic (this default behavior can be disabled by explicit configuration)

b.      Does not include the CW in the EVPN encapsulation of BUM traffic, 
presumably due to limitations imposed by the forwarding HW.

c.       The bottom line: inconsistent usage of CW in the EVPN encapsulation 
within the same EVI (with differences between known unicast and BUM traffic) is 
already a fact on the ground (at least, to some extent).

My 2c,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   
alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>

From: Yutianpeng (Tim) [mailto:yutianp...@huawei.com]
Sent: Tuesday, October 23, 2018 5:48 PM
To: Alexander Vainshtein 
<alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>>; 
Wanghaibo (Rainsword) 
<rainsword.w...@huawei..com<mailto:rainsword.w...@huawei.com>>
Cc: 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>;
 bess@ietf.org<mailto:bess@ietf.org>
Subject: RE: A question regarding draft-wang-bess-evepn-control-word

Hi Sasha,
I am also thinking of this recently but haven’t talked with author yet.
What was in my mind the solution is actually simple: directly tear down (part 
of) the mac-VRF or EVI directly if CW capabilities not consistent, considering 
behavior in one EVI should keep consistent (personally believe).
I might tend to the mechanism as below:
If router A has CW capabilities and receive type 1 or type 2 routes without CW, 
then A should drop these routes and report an alarm.
If router A does not has CW capabilities and receive type 1 or type 2 routes 
with CW, then A should drop these routes and report an alarm.
I believe the behavior within EVI or Mac-VRF should keep consistent, otherwise, 
more questions will pop out.
Considering if a service is sensitive to packet misordering and it is ELAN, I 
tend to keep behavior within this ELAN consistent.
There could also be other problems with this approach, just share an idea so 
far open the discussion.
Regards, and lots of thanks in advance,
Tim

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Alexander Vainshtein
Sent: 23 October 2018 14:42
To: Wanghaibo (Rainsword) 
<rainsword.w...@huawei.com<mailto:rainsword.w...@huawei.com>>
Cc: 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>;
 bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] A question regarding draft-wang-bess-evepn-control-word

Dear Haibo,
Again,
Lots of thanks for a prompt response.

My reading of your response is as following:

1.       All egress PEs can receive EVPN-encapsulated packets without the CW

2.       All ingress PEs can sent EVPN-encapsulated packets without the CW

3.       An egress PE that can receive EVPN-encapsulated packets with the CW in 
the EVPN encapsulation,  must add the appropriate NH Capability attribute that 
indicates the CW-indicating label value (explicitly or implicitly) to all 
relevant EVPN routes.  This includes:

a.       Per-EVI Ethernet A-D route (EVPN Route Type 1). In this case the CWI 
label would follow the label advertised in the NLRI of this route

b.      MAC/IP Advertisement route (EVPN Type 2 route). In this case the CWI 
label would follow the label advertised in the NLRI as Label1, it would not be 
relevant for packets that are encapsulated using Label2 (used with the 
Symmetric EVPN IRB).

4.       An ingress PE that has received an EVPN route with the CW capability 
attribute wand that can support usage of CW in the EVPN encapsulation, will 
insert both the CWI advertised in the CW capability attribute, and the CW in 
the EVPN packets it sends to the corresponding egress PE.  If it does not 
support usage of CW in the encapsulation, it will not insert this label.

Is this understanding correct?

If yes, I still have a couple of questions:

1.       Suppose that you use ingress replication (IR) to deliver BUM traffic 
across EVPN. The Ingress Replication label would be advertised in the PTA 
attribute of the Inclusive Multicast Ethernet Tag Route (EVPN Type 3 route); it 
will not be part of the NLRI. Do you expect the same logic to be used with 
regard to CW capabilities and CWI label advertisement applied also to these 
routes?

2.       Per-ES Ethernet A-D Routes are advertised with the ECI expended 
Community that carries within the so-called ESI label. This label is included 
the EVPN encapsulation of BUM packets sent to the PE that is attached to the 
same multi-homed ES from which the original ES packet has been received. Do you 
expect the same logic to be used with regard to CW capabilities and CWI label 
advertisement applied also to these routes with the CWI label following the ESI 
label in the EVPN encapsulation of BUM packets?

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   
alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>

From: Wanghaibo (Rainsword) [mailto:rainsword.w...@huawei.com]
Sent: Tuesday, October 23, 2018 2:34 PM
To: Alexander Vainshtein 
<alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>>
Cc: bess@ietf.org<mailto:bess@ietf.org>; 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>
Subject: RE: A question regarding draft-wang-bess-evepn-control-word

Hi Alexander,

The solution here is to carry the next hop capability attribute when the route 
is advertised. The capability carried here is the control word capability.
The specific format of the next hop capability can be referred to the draft.: 
<draft-ietf-idr-next-hop-capability>
                     +------------------------------+
                     | Capability Code (2 octets)   |
                     +------------------------------+
                     | Capability Length (2 octets) |
                     +------------------------------+
                     | Capability Value (variable)  |
                     ~                              ~
                     +------------------------------+
For the control word capability , it may encode as :
                     +------------------------------+
                     | CW Capabality Type (TBD)     |
                     +------------------------------+
                     | CW Length (0 or 3)           |
                     +------------------------------+
                     | CWI Label (may not exist)    |
                     +------------------------------+
CWI (Control word indication)

And the forwarding Packet example.
                     +------------------------------+
                     | Tunnel Label                 |
                     +------------------------------+
                     | EVI Label                    |
                     +------------------------------+
                     | CW Indicate Label            |
                     +------------------------------+
                     | Control word                 |
                     +------------------------------+

The difference between the two methods is that which value should be use for 
the control word capability indicates label.

Method 1, use reserved label, which should be assigned by IANA, (such as the 
entropy label, which is the value of 7)
If we use this method, then the control word capability attribute’s CW length 
use 0 is enough.
And the forwarding packet use the IANA specified value as the CWI (Control word 
indication) Label .(Perhaps 8 or others)

Method2, use normal value, which is assigned by router.
If we use this method, then the router must assign a label used for the CWI. 
Perhaps label. And the control word capability attribute’s CW length must be 3 
and must contain the value in the update message.
The forwarding packet must use that value as the CWI label.

Regards,
Haibo

From: Alexander Vainshtein [mailto:alexander.vainsht...@ecitele.com]
Sent: Tuesday, October 23, 2018 6:09 PM
To: Wanghaibo (Rainsword) 
<rainsword.w...@huawei.com<mailto:rainsword.w...@huawei.com>>
Cc: bess@ietf.org<mailto:bess@ietf.org>; 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>
Subject: RE: A question regarding draft-wang-bess-evepn-control-word

Dear Haibo,
Lots of thanks for an extra-prompt response to my question.

There may be some misunderstanding here.

The draft says (the important text is highlighted):

      There are two methods to specified the control word indicator label:

      The first method is to apply for a reserved label to indicate
      whether the packet contains a control word;

      The second method is to apply for a new label when the sending
      router advertises the control word capability, which is used to
      indicate whether the control word is included in the packet.

My question referred just to the 2nd method, while your response seems to deal 
with the 1st one.

Did I miss something?

Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   
alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Wanghaibo (Rainsword)
Sent: Tuesday, October 23, 2018 12:03 PM
To: Alexander Vainshtein 
<alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>>; 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: [bess] 答复: A question regarding draft-wang-bess-evepn-control-word

Hi Alexander,

The number of routes advertised by the Sender router in our solution will not 
change, but only carries a next hop capability attribute with control word 
capability
The Receiver router determines whether to carry the control word when 
forwarding packets according to its own capabilities.

The following figure is an example.:
PE1----------PE2
|-----------PE3
When PE1 advertises a route, it carries the next hop attribute of the control 
word capability. The routes received by PE2 and PE3 are the same.

If  PE2 do not support the control word, it will not carry the control word 
when forwarding packets to PE1.
PE1 cannot find the control word indication label when parsing the PE2 packet. 
PE1 will treat the packet as normal.

If  PE3 support the control word, it can add a control word when forwarding the 
packet to the PE1, and add the control word indication label specified by the 
PE1.
When the PE1 receives the packet and finds the control word indication label in 
the packet. PE1 will correctly process the control word.

Thanks
Haibo

发件人: Alexander Vainshtein [mailto:alexander.vainsht...@ecitele.com]
发送时间: 2018年10月23日 16:46
收件人: 
draft-wang-bess-evpn-control-word.auth...@ietf.org<mailto:draft-wang-bess-evpn-control-word.auth...@ietf.org>
抄送: bess@ietf.org<mailto:bess@ietf.org>
主题: A question regarding draft-wang-bess-evepn-control-word

Dear authors of 
draft-wang-bess-evpn-control-word<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dwang-2Dbess-2Devpn-2Dcontrol-2Dword-2D00&d=DwMFoQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=g3IVbNU54cy6Djewd3jxs8hIBf3n6Y8tCS54HplvNNE&s=wszxoY3qdrIHkit3qIXzuYJrQJKe-90c2fu3AJvqwlw&e=>,
I have doubts regarding at least one of the approaches for negotiating the CW 
usage in the EVPN encapsulation between egress and ingress PE that is defined 
in the draft.

In the case when the egress PE can receive EVPN-encapsulated packets both with 
and without CW, the draft seems to propose (as one of the possibilities) 
advertisement of two EVPN routes for each ES or MAC/IP pair:

-          One of these routes would use the CW Capability to indicate that it 
refers to the EVPN encapsulation that uses the CW, and would carry the 
appropriate label in its NLRI

-          The other route would not use the CW Capability to indicate that it 
refers to the EVPN encapsulation that does not use the CW, and carry a 
different label in its NLRI

The ingress PE that accepts these routes would then use one of them based on 
its own ability to use the CW (or lack thereof), and use the corresponding 
label it its EVPN encapsulation, while  the DP in the egress PW would infer 
presence or absence of the CW from the received EVPN application label.

Unfortunately, I do not think that this can work because, as per RFC 
7432<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7432&d=DwMFoQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=g3IVbNU54cy6Djewd3jxs8hIBf3n6Y8tCS54HplvNNE&s=YoT9XgzHA1XwCe6z755-DP6mPdIzYKlzA0L-uxm9pVk&e=>,
 labels in the labeled NLRI of EVPN routes are not part of the route key for 
the purpose of the BGP route key processing, while the label is treated just as 
the BGP attribute. This means that, unless some form of BGP multi-path is 
enabled in the ingress PE (and in all RRs on the way between the egress PE and 
ingress PE) for the L2VPN/EVPN  AFI/SAFI, only one of these routes will be 
selected by the BGP selection process.

Did I miss something substantial here?

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   
alexander.vainsht...@ecitele.com<mailto:alexander.vainsht...@ecitele.com>


___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information 
which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received 
this
transmission in error, please inform us by e-mail, phone or fax, and then 
delete the original
and all copies thereof.
___________________________________________________________________________

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information 
which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received 
this
transmission in error, please inform us by e-mail, phone or fax, and then 
delete the original
and all copies thereof.
___________________________________________________________________________

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information 
which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received 
this
transmission in error, please inform us by e-mail, phone or fax, and then 
delete the original
and all copies thereof.
___________________________________________________________________________

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information 
which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received 
this
transmission in error, please inform us by e-mail, phone or fax, and then 
delete the original
and all copies thereof.
___________________________________________________________________________

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information 
which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received 
this
transmission in error, please inform us by e-mail, phone or fax, and then 
delete the original
and all copies thereof.
___________________________________________________________________________
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Reply via email to