Re: [bess] FXC draft refresh

2019-06-06 Thread Ali Sajassi (sajassi)
Done. Cheers, Ali From: "Shah, Himanshu" Date: Thursday, June 6, 2019 at 8:30 AM To: "draft-ietf-bess-evpn-vpws-...@ietf.org" , "bess@ietf.org" Subject: FXC draft refresh Resent-From: Resent-To: Cisco Employee , , , , , , Resent-Date: Thursday, June 6, 2019 at 8:30 AM Hello authors –

Re: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping

2019-05-07 Thread Ali Sajassi (sajassi)
Support as a co-author. I am not aware of any undisclosed IPR. Cheers, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Tuesday, May 7, 2019 at 12:37 AM To: "bess@ietf.org" Subject: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping Hi, This email

Re: [bess] I-D Action: draft-ietf-bess-evpn-na-flags-03.txt

2019-04-25 Thread Ali Sajassi (sajassi)
Hi Jorge, The new I-flag is to enforce one-to-one mapping between an IP address and a MAC address, right? So, if this falg is set, then it is not applicable to Extended Mobility procedures (i.e., draft-ietf-bess-evpn-irb-extended-mobility-00). Can you reference this draft as informative

Re: [bess] WG adoption and IPR poll for draft-malhotra-bess-evpn-irb-extended-mobility-04

2019-03-19 Thread Ali Sajassi (sajassi)
Support as co-author. Not aware of any undisclosed IPR. Cheers, Ali From: mitesh kanjariya Date: Monday, March 18, 2019 at 1:50 PM To: "bess@ietf.org" , "draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org" , "stephane.litkow...@orange.com" Cc: "bess-cha...@ietf.org" Subject: WG

Re: [bess] WG adoption and IPR poll for draft-malhotra-bess-evpn-irb-extended-mobility-04

2019-03-05 Thread Ali Sajassi (sajassi)
Support as a co-author. Not aware of any undisclosed IPR. Cheers, Ali From: "stephane.litkow...@orange.com" Date: Tuesday, March 5, 2019 at 12:43 AM To: "bess@ietf.org" , "draft-malhotra-bess-evpn-irb-extended-mobil...@ietf.org" Cc: "bess-cha...@ietf.org" Subject: WG adoption and IPR poll

Re: [bess] WG adoption and IPR poll for draft-salam-bess-evpn-oam-req-frmwk-01

2019-02-22 Thread Ali Sajassi (sajassi)
Support. Not aware of any undisclosed IPR. Cheers, Ali From: "Bocci, Matthew (Nokia - GB)" Date: Wednesday, February 6, 2019 at 2:23 AM To: "bess@ietf.org" Cc: "draft-salam-bess-evpn-oam-req-fr...@ietf.org" Subject: WG adoption and IPR poll for draft-salam-bess-evpn-oam-req-frmwk-01

Re: [bess] WG adoption and IPR poll for draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-02

2019-02-18 Thread Ali Sajassi (sajassi)
Support as a co-author. I am not aware of any undisclosed IPR. Cheers, Ali From: "stephane.litkow...@orange.com" Date: Monday, February 18, 2019 at 7:53 AM To: "draft-rabadan-sajassi-bess-evpn-ipvpn-interwork...@ietf.org" , "bess@ietf.org" Cc: "bess-cha...@ietf.org" Subject: WG adoption

Re: [bess] Minor comment on draft-ietf-bess-evpn-inter-subnet-forwarding

2019-02-11 Thread Ali Sajassi (sajassi)
Please see my reply inline marked by “AS>”. From: BESS on behalf of Muthu Arul Mozhi Perumal Date: Wednesday, February 6, 2019 at 11:33 PM To: "bess@ietf.org" Subject: [bess] Minor comment on draft-ietf-bess-evpn-inter-subnet-forwarding Section 6.2.1 says the following: Each NVE

Re: [bess] Mobility procedure in draft-ietf-bess-evpn-inter-subnet-forwarding

2019-02-11 Thread Ali Sajassi (sajassi)
Mobility procedures for asymmetric IRB is very similar to symmetric IRB except for ARP response handling by the source NVE. So, I added the following sentence to the sections 4.1, 4.2, and 4.3 in rev07. “In case of the asymmetric IRB, the source NVE also updates its ARP table with the

Re: [bess] handling DAD in draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-02-03 Thread Ali Sajassi (sajassi)
On 1/31/19, 1:39 AM, "Sowmini Varadhan" wrote: On Wed, Jan 30, 2019 at 9:20 PM Ali Sajassi (sajassi) saja...@cisco.com wrote: sajassi> AS> RFC 7431 has procedures for duplicate MAC address detection. rfc 7431 is the Informational RFC titled "Multic

Re: [bess] Last call comment to draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-30 Thread Ali Sajassi (sajassi)
of policy and mapping them to subnet configuration is outside of the scope of this document. Linda From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com] Sent: Wednesday, January 30, 2019 8:24 PM To: Linda Dunbar ; bess@ietf.org Subject: Re: [bess] Last call comment to draft-ietf-bess-evpn-in

Re: [bess] Last call comment to draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-30 Thread Ali Sajassi (sajassi)
Hi Linda, Please refer to my reply inline marked with “AS>” From: BESS on behalf of Linda Dunbar Date: Thursday, October 4, 2018 at 9:30 AM To: "bess@ietf.org" , "i...@ietf.org" Subject: [bess] Last call comment to draft-ietf-bess-evpn-inter-subnet-forwarding-05 Ali, et al: Sorry for the

Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-30 Thread Ali Sajassi (sajassi)
Hi Stephane, I have addressed all the comments from the people you mentioned in your email below as well as some additional comment received after WGLC ended. I will check in a new rev. shortly. Cheers, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Monday, September 3,

Re: [bess] handling DAD in draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-30 Thread Ali Sajassi (sajassi)
Please refer to my reply inline marked with "AS>" On 9/17/18, 3:47 PM, "BESS on behalf of Sowmini Varadhan" wrote: hi, I have a question about Section 4.1.1 ("Initiating an APR Request upon a Move") in draft-ietf-bess-evpn-inter-subnet-forwarding-05 which has the paragraph:

Re: [bess] Some questions regarding draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-30 Thread Ali Sajassi (sajassi)
Please refer to my reply inline marked with “AS>” From: BESS on behalf of Zhuangshunwan Date: Thursday, September 13, 2018 at 1:00 AM To: "draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org" Cc: "bess@ietf.org" Subject: [bess] Some questions regarding

Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-29 Thread Ali Sajassi (sajassi)
Please refer to my replie inline marked with “AS>” From: BESS on behalf of "Luc Andre Burdet (lburdet)" Date: Tuesday, August 21, 2018 at 10:56 AM To: "stephane.litkow...@orange.com" , "bess@ietf.org" Subject: Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05 Support.

Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-29 Thread Ali Sajassi (sajassi)
Please refer to my reply inline marked with “AS>” From: BESS on behalf of "Acee Lindem (acee)" Date: Wednesday, August 15, 2018 at 12:20 PM To: "stephane.litkow...@orange.com" , "bess@ietf.org" Subject: Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05 Hi Stephane,

Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

2019-01-29 Thread Ali Sajassi (sajassi)
Please refer to my reply inline. From: BESS on behalf of Krzysztof Szarkowicz Date: Wednesday, August 8, 2018 at 10:55 AM To: "bess@ietf.org" Cc: "stephane.litkow...@orange.com" Subject: Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05 Hello working group, I have

Re: [bess] Benjamin Kaduk's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

2019-01-24 Thread Ali Sajassi (sajassi)
Hi Benjamin, please refer to my reply inline. On 1/22/19, 9:37 AM, "Benjamin Kaduk" wrote: On Tue, Jan 22, 2019 at 07:17:05AM +, Ali Sajassi (sajassi) wrote: > > Benjamin, Thanks for your review and your comments. Please refer to my comment resolution repl

Re: [bess] Suresh Krishnan's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

2019-01-22 Thread Ali Sajassi (sajassi)
Suresh, Thanks for your review and your comments. Please refer to my replies below marked with "AS>". On 1/9/19, 8:03 PM, "Suresh Krishnan" wrote: Suresh Krishnan has entered the following ballot position for draft-ietf-bess-evpn-vpls-seamless-integ-05: No Objection When

Re: [bess] Ben Campbell's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

2019-01-22 Thread Ali Sajassi (sajassi)
Ben, Thanks for your review and your comments. Please refer to my replies below marked with "AS>". On 1/9/19, 1:28 PM, "Ben Campbell" wrote: Ben Campbell has entered the following ballot position for draft-ietf-bess-evpn-vpls-seamless-integ-05: No Objection When responding,

Re: [bess] Deborah Brungard's Yes on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

2019-01-22 Thread Ali Sajassi (sajassi)
Deborah, Thanks for your review and feedback. You are spot on. If the document was talking about only VPLS/PBB-VPLS or EVPN/PBB-EVPN, then BCP would be appropriate but this document specifies the mechanism needed for an EVPN/PBB-EVPN PEs to simultaneously interoperate with both EVPN/PBB-EVPN

Re: [bess] Genart last call review of draft-ietf-bess-evpn-vpls-seamless-integ-05

2019-01-22 Thread Ali Sajassi (sajassi)
Peter, Thanks for your review and your comments. Please refer to my replies below marked with "AS>". On 12/19/18, 8:15 AM, "Pete Resnick" wrote: Reviewer: Pete Resnick Review result: Ready with Issues I am the assigned Gen-ART reviewer for this draft. The General Area

Re: [bess] Alvaro Retana's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

2019-01-21 Thread Ali Sajassi (sajassi)
Alvaro, Thanks for your review and your comments. Please refer to my replies below marked with "AS>". On 1/7/19, 9:30 AM, "Alvaro Retana" wrote: Alvaro Retana has entered the following ballot position for draft-ietf-bess-evpn-vpls-seamless-integ-05: No Objection When

Re: [bess] Benjamin Kaduk's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

2019-01-21 Thread Ali Sajassi (sajassi)
Benjamin, Thanks for your review and your comments. Please refer to my comment resolution replies below marked with "AS>". On 1/7/19, 9:17 AM, "Benjamin Kaduk" wrote: Benjamin Kaduk has entered the following ballot position for draft-ietf-bess-evpn-vpls-seamless-integ-05: No

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2019-01-15 Thread Ali Sajassi (sajassi)
n a physical ENNI but it also applies to logical ENNI and just like physical ENNI, a type-3 ESI is used for these logical ENNIs. Cheers, Ali Tim, Next time, it would be great that you raise your comments during the WGLC or even before (the sooner, the better). Thanks, Stephane From: Ali

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2019-01-15 Thread Ali Sajassi (sajassi)
the logical ENNI and coloring vES by using MAC address of ENNI’s ESI as describe in section 5.3 Cheers, Ali Thanks for understanding. Regards, Tim 发件人: Ali Sajassi (sajassi) [mailto:saja...@cisco.com] 发送时间: 2019年1月12日 3:50 收件人: Yu Tianpeng; jorge.raba...@alcatel-lucent.com 抄送: stephane.litkow..

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2019-01-11 Thread Ali Sajassi (sajassi)
differs between vendors. Appreciate if we can use language in RFC4448 (e.g. Raw mode) OK. Cheers, Ali Thanks & Regards, Tim On Thu, 10 Jan 2019, 06:17 Ali Sajassi (sajassi) mailto:saja...@cisco.com> wrote: From: Yu Tianpeng mailto:yutianpeng.i...@gmail.com>> Date: W

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2019-01-09 Thread Ali Sajassi (sajassi)
ana Mishra (mankamis) mailto:manka...@cisco.com> wrote: Thanks ali. I took look at the diff, it looks ok to me to move forward. Thanks Mankamana From: BESS mailto:bess-boun...@ietf.org>> on behalf of "Ali Sajassi (sajassi)" mailto:saja...@cisco.com>> Date

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2019-01-08 Thread Ali Sajassi (sajassi)
Tim, Mankamana, The rev02 of the draft has the updates to address your latest comments. Cheers, Ali From: BESS on behalf of Tim Date: Monday, January 7, 2019 at 2:53 PM To: "stephane.litkow...@orange.com" , "bess@ietf.org" Subject: Re: [bess] WGLC, IPR and implementation poll for

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2019-01-06 Thread Ali Sajassi (sajassi)
Hi Stephane, I just checked in a new revision of the document that incorporates the comments from Sasha and Mankamana. Rick also responded to the IPR call, so we are good to go. Cheers, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Monday, December 17, 2018 at 4:55 AM

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates

2018-12-20 Thread Ali Sajassi (sajassi)
As a co-author, I am not aware of any undisclosed IPR on this draft. Regards, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Monday, December 17, 2018 at 4:50 AM To: "bess@ietf.org" Subject: [bess] WGLC, IPR and implementation poll for

Re: [bess] A question about RFC 8317

2018-12-20 Thread Ali Sajassi (sajassi)
Hi Sasha, The use case that you have described below is a legitimate use case and if we look at what happens in RFC 7432 baseline, there is no flooding there because MAC addresses among multi-homing PEs get synch’d up and thus even a PE in the all-active multi-homing group doesn’t receive a

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2018-12-04 Thread Ali Sajassi (sajassi)
Hi Stephane, It seems like the IPR that I was talking about has already been disclosed in April of this year. The disclosure is on draft-sajassi-bess-evpn-virtual-eth-segment-03. Since the history of its WG draft version doesn’t show the individual draft

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

2018-12-03 Thread Ali Sajassi (sajassi)
There is one IPR related to this draft that I thought it was disclosed but it wasn’t. I put request for it to be disclosed ASAP. The term for it is the same as any other Cisco IPR disclosure. Regarding implementation, this draft has been implemented in Cisco products for quite some time.

Re: [bess] PLEASE LOOK: minor change to draft-ietf-bess-evpn-df-election-framework-05 => two weeks poll to get feedback

2018-11-22 Thread Ali Sajassi (sajassi)
e to think about this change and raise your support or concerns. The poll starts now and will end on Dec 5th. This DF election framework will be an important component of EVPN and we need to ensure that we are providing the required level of flexibility to address the different use ca

[bess] minor change to draft-ietf-bess-evpn-df-election-framework-05

2018-11-20 Thread Ali Sajassi (sajassi)
Folks, The authors of the above draft are purposing a minor change to the draft and since the draft is currently under review by IESG, the chair has asked to send an email to the WG to solicit inputs and ensuring that there is no objection. The proposed change is as follow: Currently, the

Re: [bess] Proposed updates to address comments to draft-ietf-bess-mvpn-fast-failover

2018-11-06 Thread Ali Sajassi (sajassi)
Hi Greg, The changes look good. Thanks for taking care of my comments. Cheers, Ali From: Greg Mirsky Date: Tuesday, October 30, 2018 at 7:50 AM To: Cisco Employee , BESS , "bess-cha...@ietf.org" Subject: Proposed updates to address comments to draft-ietf-bess-mvpn-fast-failover Dear Ali,

Re: [bess] Comparing using the SD-WAN Overlay SAFI specified by draft-dunbar-idr-bgp-sdwan-overlay-ext with the EVPN approach described by draft-sajassi-bess-secure-evpn-00

2018-11-04 Thread Ali Sajassi (sajassi)
on Attribute [TUNNEL-ENCAP]. [Tunnel-Encap] cannot be effectively used for SD-WAN overlay network because a SD-WAN Tunnel needs to be established before data arrival. There is no routes to be associated with the SD-WAN Tunnel. How do you address those issues? Linda From: Ali Sajassi (s

Re: [bess] Comparing using the SD-WAN Overlay SAFI specified by draft-dunbar-idr-bgp-sdwan-overlay-ext with the EVPN approach described by draft-sajassi-bess-secure-evpn-00

2018-11-04 Thread Ali Sajassi (sajassi)
Just finished reading your draft and I don’t think the two drafts are complimentary. Frankly, I don’t see any advantages for using a separate SAFI for this purpose but many disadvantages such as: 1. Resurrecting the approach in RFC 5512 that is being deprecated – i.e., send a separate

Re: [bess] WG adoption poll for draft-zzhang-bess-mvpn-evpn-aggregation-label-01

2018-11-04 Thread Ali Sajassi (sajassi)
Support the adoption of this draft. About 10 years ago the suggestion of a configured network-wide MPLS label was considered sacrilegious as I suggested it then for aggregate tunnels for MP2MP to simplify operation ; however, with the advent of controller-based solutions, such usages are

Re: [bess] Comparing using the SD-WAN Overlay SAFI specified by draft-dunbar-idr-bgp-sdwan-overlay-ext with the EVPN approach described by draft-sajassi-bess-secure-evpn-00

2018-10-30 Thread Ali Sajassi (sajassi)
Hi Linda, I haven’t read your draft yet. I am traveling now but will plan to read your draft over next couple of days and respond to your questions. Cheers, Ali From: BESS on behalf of Linda Dunbar Date: Tuesday, October 30, 2018 at 9:19 AM To: "i...@ietf.org" , "bess@ietf.org" Subject:

Re: [bess] Encoding a 20 bit label in a 24 bit field.

2018-10-22 Thread Ali Sajassi (sajassi)
or RFC 7432. Opinions? Regards, Jakob. -Original Message- From: RFC Errata System mailto:rfc-edi...@rfc-editor.org>> Sent: Friday, October 12, 2018 12:37 PM To: Ali Sajassi (sajassi) mailto:saja...@cisco.com>>; raggarw...@yahoo.com<mailto:r

Re: [bess] Slot requests for BESS WG session - IETF 103 - Bangkok

2018-10-21 Thread Ali Sajassi (sajassi)
I’d like to request the following slots: 1. draft-sajassi-bess-secure-evpn, Ali Sajassi, 10 min 2) draft-sajassi-bess-evpn-mvpn-seamless-interop-02, Ali Sajassi, 5 min (review of updates) Cheers, Ali From: BESS on behalf of "Mankamana Mishra (mankamis)" Date: Saturday, October 6,

Re: [bess] Encoding a 20 bit label in a 24 bit field.

2018-10-16 Thread Ali Sajassi (sajassi)
er 12, 2018 12:37 PM To: Ali Sajassi (sajassi) ; raggarw...@yahoo.com; nabil.n.bi...@verizon.com; aisaa...@bloomberg.net; utt...@att.com; jdr...@juniper.net; wim.henderi...@alcatel-lucent.com; db3...@att.com; aretana.i...@gmail.com; martin.vigour...@nokia.com; Giles Heron (giheron) ; nabil

Re: [bess] All-Active Multi-homing and Virtual Ethernet Segments: A Question

2018-09-25 Thread Ali Sajassi (sajassi)
Hi Sasha, What Luc mentioned below can work with any of the existing model supporting static PW because the pair of EVPN PEs terminating vES (with PW termination) act and look like a single logical PE to the CE. Therefore, the CE sees its PW being terminated by a single logical PE. EVPN

Re: [bess] WG adoption poll for draft-malhotra-bess-evpn-unequal-lb-04

2018-09-05 Thread Ali Sajassi (sajassi)
Support as a co-author. not aware of any undisclosed IPR. Cheers, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Tuesday, September 4, 2018 at 12:29 AM To: "bess@ietf.org" Subject: [bess] WG adoption poll for draft-malhotra-bess-evpn-unequal-lb-04 Hi WG, This email

Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

2018-09-03 Thread Ali Sajassi (sajassi)
We’ll resolve/incorporate the comments and we’ll publish a new rev. Regards, Ali From: "stephane.litkow...@orange.com" Date: Monday, September 3, 2018 at 1:23 AM To: "bess@ietf.org" , "draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org" Subject: RE: new WGLC for

Re: [bess] WG adoption poll and IPR poll for draft-sajassi-bess-evpn-per-mcast-flow-df-election

2018-09-03 Thread Ali Sajassi (sajassi)
We’ll do. Cheers, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Monday, September 3, 2018 at 1:19 AM To: LITKOWSKI Stephane OBS/OINIS , "bess@ietf.org" Subject: Re: [bess] WG adoption poll and IPR poll for draft-sajassi-bess-evpn-per-mcast-flow-df-election Hi, The

Re: [bess] A question regarding Single-Active ES redundancy mode and DF election in RFC 7432

2018-09-03 Thread Ali Sajassi (sajassi)
Hi Sasha, I don’t see any contradiction between the two statements from RFC 7432 that you mentioned below. For All-Active, DF election is for BUM traffic of a given VLAN (or group of VLANs in case of VLAN bundling) in the egress direction toward an ES. For Single-Active, DF election is for all

Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

2018-08-21 Thread Ali Sajassi (sajassi)
Support as a co-author. Not aware of any undisclosed IPR. Cheers, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Wednesday, August 8, 2018 at 7:04 AM To: "bess@ietf.org" Subject: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05 Hello working group,

Re: [bess] WG adoption poll and IPR poll for draft-sajassi-bess-evpn-per-mcast-flow-df-election

2018-08-21 Thread Ali Sajassi (sajassi)
Support as a co-author. I am not aware of any undisclosed IPR. Cheers, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Wednesday, August 8, 2018 at 6:38 AM To: "bess@ietf.org" Subject: [bess] WG adoption poll and IPR poll for

Re: [bess] Comments on draft-sajassi-bess-evpn-mvpn-seamless-interop

2018-06-28 Thread Ali Sajassi (sajassi)
Eric, Please see my responses to your comments inline marked w/ "Ali>" On 11/9/17, 9:42 AM, "BESS on behalf of Eric C Rosen" wrote: I have a number of comments on draft-sajassi-bess-evpn-mvpn-seamless-interop. 1. It seems that the proposal does not do correct ethernet

Re: [bess] Comments on draft-sajassi-bess-evpn-mvpn-seamless-interop-01

2018-06-28 Thread Ali Sajassi (sajassi)
Hi Jingrong, Thanks for the comments. Please see my responses inline. From: BESS on behalf of Xiejingrong Date: Tuesday, June 19, 2018 at 7:38 PM To: "bess@ietf.org" , "draft-sajassi-bess-evpn-mvpn-seamless-inte...@ietf.org" Subject: [bess] Comments on

Re: [bess] Slot requests for BESS WG session - IETF 102 - Montreal

2018-06-25 Thread Ali Sajassi (sajassi)
Hi Stephane, I’d like to request the following two slots: draft-ietf-bess-evpn-igmp-mld-proxy-02 Speaker: Ali Sajassi Reason: present the changes and asking for WG LC Duration: 10 min draft-sajassi-bess-evpn-mvpn-seamless-interop-01 Speaker: Ali Sajassi Reason: present the changes and asking

Re: [bess] WG Adoption and IPR Poll for draft-sajassi-bess-evpn-virtual-eth-segment-03

2018-06-18 Thread Ali Sajassi (sajassi)
Hi Matthew, I have incorporated Sasha’s comments into the rev00 and published it. Cheers, Ali From: "Bocci, Matthew (Nokia - GB)" Date: Monday, June 11, 2018 at 2:01 AM To: "bess@ietf.org" Cc: "draft-sajassi-bess-evpn-virtual-eth-segm...@ietf.org" Subject: Re: [bess] WG Adoption and IPR

Re: [bess] WG adoption and IPR poll for draft-sajassi-bess-evpn-fast-df-recovery-02

2018-05-14 Thread Ali Sajassi (sajassi)
As a co-author, I support WG adoption of this document. I am not aware of any IPR that hasn’t already been disclosed but I will double check with other co-authors. Regards, Ali From: BESS on behalf of "stephane.litkow...@orange.com"

Re: [bess] Benjamin Kaduk's Discuss on draft-ietf-bess-evpn-prefix-advertisement-10: (with DISCUSS and COMMENT)

2018-05-09 Thread Ali Sajassi (sajassi)
Hi Alvaro, You are right, the draft-ietf-bess-evpn-inter-subnet-forwarding has passed the WGLC but I need to take care of some last min. comments before publishing the next rev. Since prefix-advertisement draft will become RFC ahead of inter-subnet-forwarding, do we need to move the reference

Re: [bess] Shepherd's review of draft-ietf-bess-df-election-framework

2018-04-30 Thread Ali Sajassi (sajassi)
Hi Eric, On 4/30/18, 7:46 AM, "Eric C Rosen" wrote: Let me add a couple of minor comments: - The draft should state the action to be taken when receiving a route that has more than one DF Election Extended Community. I think the two possible options

Re: [bess] Document shepherd's review of draft-ietf-bess-evpn-vpls-seamless-integ-03

2018-04-25 Thread Ali Sajassi (sajassi)
Hi Matthew, Thank you for your comments. I addressed them all (please refer inline for the comment resolutions) and I published a new rev04 with these resolutions. Regards, Ali From: "Bocci, Matthew (Nokia - GB)" Date: Wednesday, April 25, 2018 at 4:53 AM To:

Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

2018-04-18 Thread Ali Sajassi (sajassi)
Hi Matthew, Stephane: I have addressed all the comments during this WG LC period and have published rev03 of the draft. I believe the two-week period was ended last Wednesday. Regards, Ali From: "Bocci, Matthew (Nokia - GB)" Date: Wednesday, March 28, 2018 at 5:50 AM

Re: [bess] WG adoption and IPR poll for draft-sajassi-bess-evpn-vpws-fxc-03.txt

2018-04-09 Thread Ali Sajassi (sajassi)
As a co-author, I support WG adoption of this draft. There is an IPR related to this draft for which I have requested its disclosure to IETF. Regards, Ali From: "Bocci, Matthew (Nokia - GB)" Date: Monday, April 9, 2018 at 6:23 AM To:

Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

2018-04-02 Thread Ali Sajassi (sajassi)
hursday, March 29, 2018 11:48 AM To: Alexander Vainshtein <alexander.vainsht...@ecitele.com>; Ali Sajassi (sajassi) <saja...@cisco.com> Cc: bess-cha...@ietf.org; draft-ietf-bess-evpn-vpls-seamless-in...@ietf.org; bess@ietf.org Subject: Re: WG Last Call and IPR Poll for draft-ietf-bes

Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

2018-04-02 Thread Ali Sajassi (sajassi)
y the draft so both HRW and AC-DF. My point is really on the implementation side, not on the usage. Brgds, From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com] Sent: Wednesday, March 28, 2018 18:44 To: LITKOWSKI Stephane OBS/OINIS; Rabadan, Jorge (Nokia - US/Mountain View); bess@ietf.org Subjec

Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

2018-03-28 Thread Ali Sajassi (sajassi)
Hi Sasha, Thanks for your comments. I took care of them all in rev02 of the document that I just posted. Cheers, Ali From: Alexander Vainshtein Date: Wednesday, March 28, 2018 at 7:32 AM To: "Bocci, Matthew (Nokia - GB)" Cc:

Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

2018-03-28 Thread Ali Sajassi (sajassi)
Support as a co-author. I am not aware of any IPR that hasn’t already been disclosed. Cisco has implemented this draft for quite a while now (since 2014 I think). Cheers, Ali From: "Bocci, Matthew (Nokia - GB)" Date: Wednesday, March 28, 2018 at 5:50 AM To:

Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

2018-03-28 Thread Ali Sajassi (sajassi)
Hi Stephane, In section 2.3, it says that: Both, HRW and AC-DF MAY be used independently or simultaneously. The AC-DF capability MAY be used with the default DF Election algorithm too. Do you want further clarification? If so, please suggest text. Thanks, Ali From: BESS

Re: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework

2018-03-26 Thread Ali Sajassi (sajassi)
I am not aware of any IPR that hasn’t already been disclosed. Regarding implementation, Cisco has implemented HRW DF election. Regards, Ali From: BESS on behalf of "stephane.litkow...@orange.com" Date: Monday, March 26, 2018 at 7:21 AM

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

2018-03-26 Thread Ali Sajassi (sajassi)
: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description Ali, So, is this going to be a family of drafts dealing with inter-connection aspects across a set of use cases ? Would it be useful to right up a requirements draft like we did with EVPN?? Thanks,

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

2018-03-26 Thread Ali Sajassi (sajassi)
So is the plan to incorporate Sandy’s work in these docs?? Thanks, Jim Uttaro From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com] Sent: Monday, March 26, 2018 11:55 AM To: UTTARO, JAMES <ju1...@att.com>; John E Drake <jdr...@juniper.net>; Rabadan, Jorge (Nokia - US

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

2018-03-26 Thread Ali Sajassi (sajassi)
Subject: RE: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description All, Should we expand this conversation to a L2 EVPN<-> L3 EVPN space? IOW do we want to tackle this once and for all.. Thanks, Jim Uttaro From: BESS [mailto:bess-boun...@ietf.org] On

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

2018-03-25 Thread Ali Sajassi (sajassi)
sed last week, the SMET processing already includes what Sandy/Satya proposal wants to do. I.e., when a PE is no longer the DF on any of the ESes to which it is attached it withdraws its SMET routes. Sent from my iPhone On Mar 24, 2018, at 1:30 PM, Ali Sajassi (sajassi) <saja...@cisco.com

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

2018-03-24 Thread Ali Sajassi (sajassi)
Hi Jorge, As I pointed out in my previous email, the use of flag is not a viable option because it requires update to every single PE for it to be effective. Before getting too much into a new solution with many restrictions, we should evaluate the current mechanisms and if they fall short,

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

2018-03-24 Thread Ali Sajassi (sajassi)
Hi John, Your suggestion (of defining a flag mcast flag EC) requires that in addition to gateways upgrade, all other PEs to be upgraded. I think option-A in my earlier email is the best option for Sandy’s use case and it provide that with the existing WG drafts without inventing/developing a

Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

2018-03-24 Thread Ali Sajassi (sajassi)
Eric, Jorge, At the time I wrote RFC 7432, I had an implicit assumption that IMET routes advertisement is based on EVI/BD configuration only and thus it is not dependent on failure scenario, single-homing scenario, etc. If there was not a better option to solve Sandy’s use case, then I would

Re: [bess] About draft-ietf-bess-evpn-igmp-mld-proxy

2018-03-21 Thread Ali Sajassi (sajassi)
Hi Jorge, Please refer to my comments inline marked w/ "Ali>" On 3/21/18, 1:59 AM, "Rabadan, Jorge (Nokia - US/Mountain View)" wrote: Ali and authors, As discussed during the BESS session, these are the points that I think should be addressed in

Re: [bess] Slots requests for BESS WG session - IETF 101 - London

2018-03-04 Thread Ali Sajassi (sajassi)
Hi Stephane, We’d like to request a 10 min slot for the following: Draft: https://www.ietf.org/id/draft-sajassi-bess-evpn-per-mcast-flow-df-election-00.txt Presenter: Mankamana / Ali Slot: 10 min Regards, Ali From: BESS on behalf of "stephane.litkow...@orange.com"

Re: [bess] Slots requests for BESS WG session - IETF 101 - London

2018-02-26 Thread Ali Sajassi (sajassi)
Hi Stephane, I’d like to request a 20 min slot to go over the status of the following drafts and request for WG LC/WG call: https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-vpls-seamless-integ/ https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-igmp-mld-proxy/

Re: [bess] Call for adoption: draft-skr-bess-evpn-pim-proxy

2018-02-19 Thread Ali Sajassi (sajassi)
Hi Stephane, Matthew: Is there a process for WG call (or WG LC) call that you are following? I thought it is based on maturity of the draft, adoptions of the draft, history of the draft (how long it has been around), and a public request for it. I am a co-author of the above draft and

Re: [bess] Request for WG call for draft-sajassi-bess-evpn-vpws-fxc-02.txt

2018-02-16 Thread Ali Sajassi (sajassi)
signaled via LDP to the other end which in turn soft-shut the port. I wonder if the same behavior could be replicated by EVPN VPWS. In that case remote PE(s) would have to react to BGP prefix withdrawals. Thank you Regards On Tue, Feb 13, 2018 at 8:17 PM, Ali

[bess] Request for WG LC of draft-ietf-bess-evpn-vpls-seamless-integ-01.txt

2018-02-14 Thread Ali Sajassi (sajassi)
Dear Chairs, This is a WG draft that has been implemented by several vendors and it is needed for interop between EVPN/PBB-EVPN and legacy L2VPN solutions (VPLS and PBB-VPLS). The chair made an inquiry about this draft during IETF 96 and the response was to update the draft and request for WG

Re: [bess] Request for WG call for draft-sajassi-bess-evpn-vpws-fxc-02.txt

2018-02-13 Thread Ali Sajassi (sajassi)
It has already been updated and the rev02 has been checked in. Regards, Ali On 2/13/18, 6:43 AM, "Martin Vigoureux" <martin.vigour...@nokia.com> wrote: ok, let us know when you've updated it, we'll call it for adoption fater that. -m Le 2018-0

Re: [bess] New bess WG Co-Chair

2018-02-13 Thread Ali Sajassi (sajassi)
Martin, thank you for all your work and efforts for this WG and reviewing/ shepherding many drafts. Matthew, welcome to BESS. Cheers, Ali From: BESS on behalf of Alvaro Retana Date: Tuesday, February 13, 2018 at 8:11 AM To: "bess@ietf.org"

[bess] Request for WG call for draft-sajassi-bess-evpn-vpws-fxc-02.txt

2018-02-12 Thread Ali Sajassi (sajassi)
Hi Martin, Stephane: This is one of the draft in my plate that I needed to update and ask for a WG call. It has already been implemented by number of vendors and has had pretty good consensus. Regards, Ali ___ BESS mailing list BESS@ietf.org

Re: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast

2018-02-12 Thread Ali Sajassi (sajassi)
I am not aware of any undisclosed IPR regarding this draft. Regards, Ali On 1/11/18, 2:12 AM, "Martin Vigoureux" wrote: Hello working group, This email starts a two-week call for adoption on draft-lin-bess-evpn-irb-mcast-04 [1] as a BESS Working

Re: [bess] IPR Disclosure Eric Rescorla's Statement about IPR related to draft-ietf-bess-evpn-overlay belonging to Chemtron Research LLC

2018-01-17 Thread Ali Sajassi (sajassi)
Hi Martin, I have the following two questions: 1) The disclosed IPR doesn’t have the licensing declaration section filled up. Is this section optional or is it just being overlooked? 2) I found the following url for this IPR: https://www.google.com.pg/patents/US7936693. It would be good for

Re: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast

2018-01-15 Thread Ali Sajassi (sajassi)
Support Cheers, Ali On 1/11/18, 2:12 AM, "Martin Vigoureux" wrote: Hello working group, This email starts a two-week call for adoption on draft-lin-bess-evpn-irb-mcast-04 [1] as a BESS Working Group Document. Please state on the list if

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

2018-01-12 Thread Ali Sajassi (sajassi)
Le 2017-12-15 à 19:21, Ali Sajassi (sajassi) a écrit : > Hi Thomas, > > On 12/15/17, 8:42 AM, "BESS on behalf of Thomas Morin" <bess-boun...@ietf.org on behalf of thomas.mo...@orange.com> wrote: > > > Here I wo

Re: [bess] RtgDir review: draft-ietf-bess-evpn-overlay-10

2018-01-12 Thread Ali Sajassi (sajassi)
Lou, Thanks for your comments. Please refer my responses inline. On 1/9/18, 3:37 PM, "Lou Berger" wrote: Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related

Re: [bess] Genart last call review of draft-ietf-bess-evpn-overlay-10

2018-01-12 Thread Ali Sajassi (sajassi)
As requested, added a note in the IANA section. Cheers, Ali From: Alvaro Retana Date: Friday, December 22, 2017 at 5:34 AM To: Vijay Gurbani , "draft-ietf-bess-evpn-overlay@ietf.org" Cc: "bess@ietf.org"

Re: [bess] Adam Roach's No Objection on draft-ietf-bess-evpn-overlay-10: (with COMMENT)

2018-01-12 Thread Ali Sajassi (sajassi)
Hi Adam, Thanks for your comments. They all have been incorporated into the next rev of the draft (rev 11). Cheers, Ali On 1/10/18, 5:45 PM, "Adam Roach" wrote: Adam Roach has entered the following ballot position for draft-ietf-bess-evpn-overlay-10: No Objection

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

2017-12-15 Thread Ali Sajassi (sajassi)
lp people better understand the reasoning behind the design, is it really best to remove it? Wouldn't a rephrasing be more appropriate? -m Le 2017-12-15 à 19:21, Ali Sajassi (sajassi) a écrit : > Hi Thomas, > > On 12/15/17, 8:42 AM, "BESS on behal

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

2017-12-15 Thread Ali Sajassi (sajassi)
Hi Thomas, On 12/15/17, 8:42 AM, "BESS on behalf of Thomas Morin" wrote: Here I would suggest to authors to consider purely removing this paragraph, not because it would be wrong or ambiguous (as said above, I don't

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

2017-12-15 Thread Ali Sajassi (sajassi)
Hi Don, On 12/15/17, 7:35 AM, "BESS on behalf of Fedyk, Don" wrote: Hi Thomas I'm good with the interpretation of RFC7432 and RFC6514 in this area as I said. But at least one implementation got it wrong. You

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

2017-12-14 Thread Ali Sajassi (sajassi)
Hi Marco, If an implementation doesn’t add PMSI to an IMET route, then that implementation is broken. RFC 7432 says: “In order to identify the P-tunnel used for sending broadcast, unknown unicast, or multicast traffic, the Inclusive Multicast Ethernet Tag route MUST carry a Provider

Re: [bess] New bess Co-Chair

2017-12-10 Thread Ali Sajassi (sajassi)
Thomas, Thanks for your all your works and efforts that you put into this WG. Your thorough reviews of WG docs that you have shepherded are much appreciated. Sometimes it seemed to be a thankless job but we do appreciate the efforts that you have put into them. Wishing you the best.

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

2017-12-10 Thread Ali Sajassi (sajassi)
Hi Thomas, I have incorporated your comments into rev11 of the document. Cheers, Ali On 12/8/17, 1:45 AM, "Thomas Morin" wrote: Ali, A few nits, sorry for not answering earlier: > > I added the following paragraph to section 6 for

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

2017-12-07 Thread Ali Sajassi (sajassi)
ess-cha...@ietf.org>, Cisco Employee <saja...@cisco.com> Cc: Thomas Morin <thomas.mo...@orange.com>, "bess@ietf.org" <bess@ietf.org> Subject: Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08 On December 5, 2017 at 10:53:02 PM, Ali Sajassi (sajassi) (saja...@cis

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

2017-12-06 Thread Ali Sajassi (sajassi)
I will add the following sentence to the abstract. “This specification is also applicable to other NVO encapsulations such as GENEVE, GPE, and GUE; however, these encapsulations may require additional incremental work and thus will be specified in separate document(s).” I think that

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

2017-12-06 Thread Ali Sajassi (sajassi)
Hi Thomas, Please see my reply inline. On 12/5/17, 6:25 AM, "BESS on behalf of thomas.mo...@orange.com" wrote: All, Martin Vigoureux, 2017-12-05 11:34: Perhaps draft-ietf-bess-evpn-overlay could hint on such a

  1   2   3   >