Hi Wen,
I am thinking of adding the following paragraph as a clarification for the
originating router’s IP address.
“The Originating Router’s IP address does not need to be a routable address and
its purpose is to identify the originator of that EVPN route uniquely. It can
be either IPv4 or
Hi Stewart,
Thanks for your review and your comments. I have incorporated them in the next
revision of this draft (rev09). Please refer to my comments marked with “Ali>”
below for more details:
From: Stewart Bryant via Datatracker
Date: Monday, April 29, 2024 at 8:49 AM
To: gen-...@ietf.org
s a “typo” in the statement but the above statement
is correct! So, I don’t know why the commentator added “- seems like typo”!
Cheers,
Ali
From: John Scudder
Date: Monday, February 12, 2024 at 10:14 AM
To: Ali Sajassi (sajassi)
Cc: bess@ietf.org , The IESG ,
rfc-edi...@rfc-editor.org
Su
, February 9, 2024 at 1:18 PM
To: bess@ietf.org
Cc: Ali Sajassi (sajassi) , nabil.bi...@nokia.com
, rshek...@juniper.net ,
wim.henderi...@nokia.com , Alvaro Retana
, Andrew Alston - IETF ,
matthew.bo...@nokia.com , slitkows.i...@gmail.com
, Jeffrey (Zhaohui) Zhang , Gaurav
Sinha , Jim Uttaro
and thus they
are not installed in route table (IP-VRF) for asymmetric IRB. I think the
errata author has confused the subnet routes with individual host IP addresses.
Cheers,
Ali
From: John Scudder
Date: Friday, February 9, 2024 at 1:30 PM
To: bess@ietf.org
Cc: Ali Sajassi (sajassi) , Samer Salam
the IRB is
asymmetric.
Cheers,
Ali
From: RFC Errata System
Date: Friday, February 9, 2024 at 1:23 PM
To: vrkic.de...@gmail.com , Ali Sajassi (sajassi)
, Samer Salam (ssalam) , Samir Thoria
(sthoria) , jdr...@juniper.net ,
jorge.raba...@nokia.com
Cc: j...@juniper.net , i...@ietf.org ,
bess
, February 9, 2024 at 1:18 PM
To: bess@ietf.org
Cc: Ali Sajassi (sajassi) , nabil.bi...@nokia.com
, rshek...@juniper.net ,
wim.henderi...@nokia.com , Alvaro Retana
, Andrew Alston - IETF ,
matthew.bo...@nokia.com , slitkows.i...@gmail.com
, Jeffrey (Zhaohui) Zhang , Gaurav
Sinha , Jim Uttaro
if the operators still want to use the control word with EL, then
they still can!
Cheers,
Ali
From: Menachem Dodge
Date: Monday, February 5, 2024 at 5:55 AM
To: Ali Sajassi (sajassi) , Matthew Bocci (Nokia)
, draft-ietf-bess-rfc7432...@ietf.org
Cc: bess-cha...@ietf.org , bess@ietf.org
Subject: Re: Mail
Hi Matthew, Menachem:
The text in the yellow says: “If a network uses entropy labels per [RFC6790]” …
It should be noted that the word “network” is used which is inclusive of all
the PE and P nodes in that network. So, if the network uses entropy labels and
does ECMP based on that, then there
Thank you Sasha for catching this error. We will address it in the next rev
along with a few other things.
Cheers,
Ali
From: Alexander Vainshtein
Date: Thursday, December 21, 2023 at 4:40 AM
To: draft-sajassi-bess-evpn-l3-optimized-...@ietf.org
Cc: bess@ietf.org
Subject: A minor issue with
I support adoption of this document as a WG draft and I am not aware of any
undisclosed IPR.
Cheers,
Ali
From: Jeffrey (Zhaohui) Zhang
Date: Monday, November 13, 2023 at 3:51 AM
To: 'BESS'
Cc: 'bess-cha...@ietf.org' ,
draft-sajassi-bess-evpn-ip-alias...@ietf.org
Subject: WG Adoption and
Date: Monday, November 6, 2023 at 11:17 PM
To: Ali Sajassi (sajassi) , Neeraj Malhotra
Cc: draft-sajassi-bess-evpn-l3-optimized-...@ietf.org
, bess@ietf.org
, Nitsan Dolev , Ali Sajassi (sajassi)
Subject: RE: [bess] A question about draft-sajassi-bess-evpn-l3-optimized-irb
Ali, Neeraj and all
host mobility in EVPN is based on MAC
mobility which is tracked in L2RIB.”
Cheers,
Ali
From: Neeraj Malhotra
Date: Monday, November 6, 2023 at 4:13 PM
To: Ali Sajassi (sajassi)
Cc: Alexander Vainshtein ,
draft-sajassi-bess-evpn-l3-optimized-...@ietf.org
, bess@ietf.org
, Nitsan Dolev
Subject
Hi Sasha,
Each PE only learns local MAC addresses and NOT remote ones. So, lets says you
have a subnet that is stretched across 10 PEs and each PE has 100 locally
connected hosts. So, the total number of MAC addresses for the subnet is 1000
(10X100) but each PE ONLY learns 100 MAC addresses.
Also, I am not aware of a publicly-released implementation for this draft.
From: Ali Sajassi (sajassi)
Date: Sunday, November 5, 2023 at 8:34 AM
To: Jeff Tantsura , BESS
Cc: draft-ietf-bess-evpn-gen...@ietf.org
Subject: Re: [bess] I-D Action: draft-ietf-bess-evpn-geneve-06.txt
Hi Folks,
I
Hi Folks,
I am not aware of any undisclosed IPR for this draft.
Cheers,
Ali
From: Jeff Tantsura
Date: Wednesday, November 1, 2023 at 4:04 PM
To: BESS
Cc: draft-ietf-bess-evpn-gen...@ietf.org
Subject: Re: [bess] I-D Action: draft-ietf-bess-evpn-geneve-06.txt
Sami and team,
Friendly reminder,
As a co-author , I support the WG adoption of this draft.
From: Matthew Bocci (Nokia)
Date: Thursday, October 5, 2023 at 3:46 AM
To: bess@ietf.org
Cc: draft-ietf-bess-bgp-sdwan-us...@ietf.org
Subject: WG Adoption Poll for draft-ietf-bess-bgp-sdwan-uasge-16
WG
This email starts a one-week WG
Hi Sasha,
As always thanks for your insightful comments and questions and sorry for the
delayed response. Please refer to my responses inline marked with [AS].
From: BESS on behalf of Alexander Vainshtein
Date: Tuesday, September 26, 2023 at 2:56 AM
To:
Date: Sunday, September 24, 2023 at 2:05 AM
To: Ali Sajassi (sajassi) , Brian Haberman
, int-...@ietf.org
Cc: bess@ietf.org ,
draft-ietf-bess-evpn-virtual-eth-segment@ietf.org
, last-c...@ietf.org
Subject: Re: [bess] Intdir telechat review of
draft-ietf-bess-evpn-virtual-eth-segment-13
Ali
Hi Brian,
Thanks for the review and your comments. I have incorporated your comments into
the rev14 of this draft. Please refer to my inline responses below marked with
[AS].
From: Brian Haberman via Datatracker
Date: Wednesday, September 6, 2023 at 11:49 AM
To: int-...@ietf.org
Cc:
I am not aware of any undisclosed IPRs.
Cheers,
Ali
From: BESS on behalf of slitkows.i...@gmail.com
Date: Tuesday, September 19, 2023 at 12:45 AM
To: bess@ietf.org ,
draft-ietf-bess-evpn-irb-extended-mobil...@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WGLC, IPR, implementation poll
Hi Matthew,
A new version of the draft with the agreed upon changes has been published.
Regards,
Ali
From: Matthew Bocci (Nokia)
Date: Thursday, August 17, 2023 at 2:26 AM
To: Ali Sajassi (sajassi) , bess@ietf.org
Cc: bess-cha...@ietf.org , John Scudder
Subject: Re: 2nd WG last call
Hi Sasha,
Thanks for the comment. I welcome any comment for better clarification of this
draft. As such your comment is well taken and I’ll remove “multipoint” word
from the sentence. So, the new sentence will read: “… a family of solutions for
Ethernet services over MPLS/IP network …”
Hi Folks,
Just FYI – vast majority of changes for this new revision (rev12) have been
made for clarification purposes including the new paragraph added in section
5.5. The new paragraph describes fast convergence scenario for existing figure
5 in this section.
Thanks to IESG for their review
Hi Martin,
Elaborating a bit further to ensure there is no ambiguity …
(S1.2)
"In some cases, this aggregation of PWs that share the same LSP pair may not be
possible. For instance, if PW3 were terminated into a third PE, e.g. PE3,
instead of PE1, the vES would need to be defined on a per
Hi Mankamana,
I want to request a 10 min slot for
https://datatracker.ietf.org/doc/draft-sajassi-bess-rfc8317bis/
Cheers,
Ali
From: BESS on behalf of Mankamana Mishra (mankamis)
Date: Friday, June 30, 2023 at 7:33 AM
To: bess@ietf.org
Subject: [bess] Please send slot request for BESS IETF
Support as a co-author. I am not aware of any undisclosed IPRs related to this
draft.
Cheers,
Ali
From: BESS on behalf of slitkows.i...@gmail.com
Date: Wednesday, June 14, 2023 at 1:21 AM
To: bess@ietf.org
Subject: [bess] WGLC, IPR and Implementation Poll for
Hi Matthew,
Done and it is waiting for your check-in.
Cheers,
Ali
From: Matthew Bocci (Nokia)
Date: Tuesday, June 20, 2023 at 2:24 AM
To: Ali Sajassi (sajassi) , Linda Dunbar
, Lukas Krattiger (lkrattig)
, bess-cha...@ietf.org
Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org
Shunwan,
Good catch! ID length is in bytes and Nonce length is also in bytes. I will
update the draft accordingly.
Cheers,
Ali
From: Zhuangshunwan
Date: Monday, June 12, 2023 at 1:36 AM
To: draft-sajassi-bess-secure-e...@ietf.org
Cc: bess@ietf.org
Subject: Mail regarding
Linda,
Thanks for your comments. Please refer to my replies inline …
From: Linda Dunbar
Date: Tuesday, May 30, 2023 at 9:36 AM
To: Lukas Krattiger (lkrattig) , Matthew
Bocci (Nokia) , bess-cha...@ietf.org
Cc: bess@ietf.org , draft-sajassi-bess-secure-e...@ietf.org
Subject: RE: [bess] WG
Support as a co-author. Not aware of any undisclosed IPR(s).
Cheers,
Ali
From: BESS on behalf of slitkows.i...@gmail.com
Date: Wednesday, May 24, 2023 at 1:02 AM
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WG adoption for draft-brissette-bess-evpn-vpws-seamless
Hello,
This
Support as a co-author. There is an IPR associated with this draft and I have
already asked our legal department to register it with IETF.
Regards,
Ali
From: BESS on behalf of Matthew Bocci (Nokia)
Date: Thursday, May 25, 2023 at 3:36 AM
To: bess@ietf.org
Cc:
If you are talking about different VLAN IDs (VIDs) on the same physical
interface of an ES is getting mapped to a BD, and the is advertised
via Eth AD per EVI route with Eth-tag of zero, then this is VLAN-bundle service
interface. In VLAN bundle, it is assumed that the MAC addresses across
Hi Sami,
Please refer to my response inline in red …
From: BESS on behalf of Boutros, Sami
Date: Tuesday, May 23, 2023 at 2:31 PM
To: BESS
Subject: [bess] Question on symmetric EVPN IRB RFC 9135
Hi,
Looking at section 5.2, it doesn’t address quite few cases like for example.
* What
draft.
Cheers,
Ali
From: Nitsan Dolev
Date: Thursday, May 18, 2023 at 12:20 AM
To: Ali Sajassi (sajassi) , bess@ietf.org ,
Parag Jain (paragj) , Luc Andre Burdet (lburdet)
Cc: Alexander Vainshtein , Ron Sdayoor
Subject: RE: Coverage of ERL label within LSP-Ping Mechanisms for EVPN
Hi Ali
Hi Nitsan,
This draft has gone through the WGLC as well as IESG review and we are very
close to its publication (i.e., too late to make such changes). Once it is
published, we welcome enhancements and expansion to this document when needed.
IETF has a formal process of reporting “errata” on a
From: Menachem Dodge
Date: Saturday, April 1, 2023 at 11:58 PM
To: Ali Sajassi (sajassi) , bess@ietf.org
Subject: Re: Draft draft-ietf-bess-7432bis-07 section 7.11.2
Hello Ali,
Thanks very much for your helpful response.
Referring to #2 below, I assume that the default behavior of RFC 7432
Please refer to my comments below in red …
From: BESS on behalf of Menachem Dodge
Date: Thursday, March 30, 2023 at 8:51 AM
To: bess@ietf.org
Subject: [bess] Draft draft-ietf-bess-7432bis-07 section 7.11.2
Hello All,
Section 7.11.2 of the draft-ietf-bess-7432bis states that if there is a
Hi Folks,
We have been revising this baseline EVPN RFC for sometime now and I believe all
the comment resolutions have been incorporated. This latest revision
incorporates two additional comments - one from Sasha for section 6.3 and
another from Jeffrey on section 18.
Please take a look at
Hi Sasha,
Thanks for your insightful comments. A few comments:
1. The text that you provided, gives further clarification to the existing
text and thus I will incorporate it with some modifications as below:
“In the case where a single VLAN is represented by a single VID and
thus no VID
Hi Sasha,
Please refer to my comments below:
AS>> EVPN-VPWS has multiple modes, and it may be better to cover it in a
separate draft. I will talk to Parag about a write-up of a short draft about
EVPN-VPWS and put a clarification statement that this draft is limited to EVPN
and EVPN-IRB.
< sent the previous email by accident w/o completing my replies …>
Hi Sasha,
Thanks for your comments. Please refer to my replies marked with “AS>>”
From: Alexander Vainshtein
Date: Wednesday, November 23, 2022 at 11:54 PM
To: Ali Sajassi (sajassi)
Cc: bess@ietf.org , Alexa
Hi Sasha,
Thanks for your comments. Please refer to my replies marked with “AS>>”
From: Alexander Vainshtein
Date: Wednesday, November 23, 2022 at 11:54 PM
To: Ali Sajassi (sajassi)
Cc: bess@ietf.org , Alexander Ferdman
, Dmitry Valdman , Ron
Sdayoor , Nitsan Dolev ,
draft-ietf-bes
24, 2022 at 5:38 AM
To: Jorge Rabadan (Nokia) , Ali Sajassi (sajassi)
Cc: Luc André Burdet , bess@ietf.org ,
Nitsan Dolev , Alexander Ferdman
, Ron Sdayoor , Dmitry
Valdman , draft-sajassi-bess-evpn-ip-alias...@ietf.org
Subject: Re: A doubt about draft-sajassi-bess-evpn-ip-aliasing-05
Hi
Hi Sasha,
Thanks for your comments. Please refer to my responses below marked with “AS>”
From: BESS on behalf of Alexander Vainshtein
Date: Monday, November 14, 2022 at 1:36 AM
To: draft-ietf-bess-evpn-lsp-p...@ietf.org
Cc: bess@ietf.org , Alexander Ferdman
, Dmitry Valdman , Ron
Sdayoor
Hi Sasha,
EVPN based RFCs (7432 and 8365) define two types of multi-homing: All-Active
and Single-Active. Both of these multi-homing mechanism relies on multi-homing
PEs to control loop detection and prevention using DF election and
split-horizon filtering.
As a co-author, I support adoption of it and not aware of any undisclosed IPR.
Cheers,
Ali
From: BESS on behalf of Stephane Litkowski (slitkows)
Date: Monday, October 10, 2022 at 1:40 AM
To: bess-cha...@ietf.org , bess@ietf.org
Subject: [bess] WG adoption poll and IPR poll for
As a co-author, support publication of it and am not aware of any undisclosed
IPR.
Regards,
Ali
From: BESS on behalf of Bocci, Matthew (Nokia - GB)
Date: Monday, September 26, 2022 at 4:06 AM
To: bess@ietf.org
Subject: [bess] WG Last Call and IPR Poll for draft-ietf-bess-bgp-sdwan-usage-05
I support publication of this draft and I am not aware of any undisclosed IPR.
Regards,
Ali
From: slitkows.i...@gmail.com
Date: Wednesday, January 26, 2022 at 1:50 AM
To: bess@ietf.org ,
draft-ietf-bess-evpn-mh-split-hori...@ietf.org
Cc: bess-cha...@ietf.org
Subject: WGLC, IPR and
I support publication of this document and I am not aware of any IPR that
hasn’t been disclosed.
Cheers,
Ali
From: Bocci, Matthew (Nokia - GB)
Date: Monday, January 31, 2022 at 5:58 AM
To: draft-ietf-bess-evpn-fast-df-recov...@ietf.org
, bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WGLC,
I support the publication of this draft and I am not aware of any undisclosed
IPR.
Cheers,
Ali
From: BESS on behalf of slitkows.i...@gmail.com
Date: Monday, September 27, 2021 at 11:03 PM
To: 'BESS'
Cc: bess-cha...@ietf.org
Subject: [bess] WG Last Call, IPR and Implementation Poll for
Hi Matthew,
Some of the co-authors are on PTO and I couldn’t reach them (typical of the
month of August). So, I’d like to get a bit more extension.
Regarding the two questions below:
1. My company hasn’t implemented it.
2. I do think that we should process with the publication as it
Hi Ben,
I just published rev-14 of the draft with the updates to the IANA section.
Cheers,
Ali
From: John E Drake
Date: Wednesday, June 9, 2021 at 11:47 AM
To: Benjamin Kaduk
Cc: Ali Sajassi (sajassi) , The IESG ,
draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org
, bess-cha...@ietf.org
Thank you Ben for your meticulous review and valuable comments that you have
provided during the course of this document review.
Cheers,
Ali
From: Benjamin Kaduk
Date: Wednesday, June 9, 2021 at 10:26 AM
To: Ali Sajassi (sajassi)
Cc: The IESG ,
draft-ietf-bess-evpn-inter-subnet-forward
Hi Ben,
Sorry for the delayed response. I think we can address your last two comments
rather easily and hopefully close this review. Please refer to my replies
marked in red.
From: Benjamin Kaduk
Date: Saturday, February 27, 2021 at 4:06 PM
To: Ali Sajassi (sajassi)
Cc: The IESG ,
draft
Support as a co-author. We requested our legal department in Nov/2020 to
disclose an IPR related to this draft to IETF. We will follow it up to see why
it hasn’t been disclosed yet.
Cheers,
Ali
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Monday, April 19, 2021 at 11:07 AM
To:
Support as a co-author. There is an IPR which is being disclosed.
Cheers,
Ali
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Monday, March 29, 2021 at 12:13 AM
To: "bess@ietf.org"
Subject: [bess] WG adoption and IPR poll for
draft-brissette-bess-evpn-l2gw-proto
Hello,
This email
Support as a co-author. Not aware of any undisclosed IPR.
-Ali
From: "Bocci, Matthew (Nokia - GB)"
Date: Wednesday, December 9, 2020 at 1:23 AM
To: "bess@ietf.org"
Cc: "draft-mohanty-bess-weighted-...@ietf.org"
Subject: WG adoption and IPR poll for draft-mohanty-bess-weighted-hrw-01
Hi Ben,
I responded to your comments in the current thread but let me respond to your
comments in the draft’s ballot page more specifically here so that you don’t
have to go through that email. Please let me know if you have any further
comments.
1) I think
Hi Ben,
Please see my replies marked with AS>>
On 10/29/20, 5:26 PM, "Benjamin Kaduk" wrote:
Hi Ali,
Sorry for the delayed response. Comments inline.
On Thu, Sep 03, 2020 at 06:17:01AM +0000, Ali Sajassi (sajassi) wrote:
> Hi Ben,
>
>
Hi Erik,
Please see my reply marked w/ AS>>
On 12/9/20, 7:50 PM, "Erik Kline" wrote:
Ali,
Thanks for your replies.
On Sun, Oct 11, 2020 at 9:06 PM Ali Sajassi (sajassi)
wrote:
>
> Hi Erik,
>
> Thanks for your comments and sorry t
Hi Alvaro,
On 11/9/20, 12:33 PM, "Alvaro Retana" wrote:
On October 13, 2020 at 2:55:07 AM, Ali Sajassi wrote:
Ali:
Hi!
> Thanks very much for your comments and sorry for the delay, please refer
to
> my replies marked with [AS].
I looked at the replies and I'm
I looked into the IPR, and it has been disclosed and it shows up for the
individual version of the draft but for some reason not for the WG version of
it!
From: BESS on behalf of "Ali Sajassi (sajassi)"
Date: Tuesday, February 2, 2021 at 9:39 AM
To: "slitkows.i...@gma
Hi Stephane,
Jorge, John, DJ, and I met several times over the course of last two weeks to
address DJ and some of the other outstanding comments and in doing so covering
the following three cases as well:
1. Advertisements of routes learned over a local AC by a GW into the
participating
Support publication of this draft. I am not aware of any undisclosed IPR.
-Ali
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Monday, November 30, 2020 at 12:15
To: "draft-ietf-bess-srv6-servi...@ietf.org"
, "bess@ietf.org"
Subject: [bess] WG Last Call, IPR and
Please see my comments marked w/ [AS] below:
Just so that everyone is aware of the history, I introduced the control plane
signaling concept for L2VPN,
as well as PW status signaling, capability exchange and PW QoS signaling for
throttling the traffic.
EVPN utilized that idea and applied in
apply anycast SIDs to existing EVPN.
Thanks.
Jorge
From: Ali Sajassi (sajassi)
Date: Friday, November 20, 2020 at 7:21 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) ,
Jeffrey (Zhaohui) Zhang , Sami Boutros
Cc: bess@ietf.org
Subject: Re: [bess] comments on draft-boutros-bess-elan-services-o
yee , Sami Boutros ,
"Ali Sajassi (sajassi)"
Cc: "bess@ietf.org"
Subject: Re: [**EXTERNAL**] Re: [bess] Issues w/
draft-boutros-bess-elan-services-over-sr
Hi Ali,
Please see inline.
Sighhh! The first section of your draft (section 1) and the first two
paragraphs of that
Hi Jorge,
Agreed, any technology can use any cast SID.
[jorge] if you want to specify an anycast SID solution for EVPN as an
alternative to aliasing, since it may have its merits, I’ll be glad to
investigate it with you and help. However data plane-learning sounds a step
back to me.
I
is underlay topology decides LB instead of the actual link BW of MCLAG!!
Cheers,
Ali
From: Sami Boutros
Date: Thursday, November 19, 2020 at 6:32 PM
To: "Ali Sajassi (sajassi)"
Cc: "bess@ietf.org" , Cisco Employee , Sami
Boutros
Subject: Re: [bess] Issues w/ draft-boutros-bess-elan-
Sami,
Since we didn’t have time to discuss the issues during the BESS meeting, let me
explain and elaborate them here:
The draft states the following two main objectives for its purpose but both
have been addressed already !!
1. Reducing # of PWs in VPLS:
* VPLS (both BGP and LDP)
Hi Roman,
Thanks for your comments. Please see my replies inline marked with [AS]:
On 7/15/20, 6:45 PM, "BESS on behalf of Roman Danyliw via Datatracker"
wrote:
Roman Danyliw has entered the following ballot position for
draft-ietf-bess-evpn-inter-subnet-forwarding-09: No Objection
Hi Alvaro,
Thanks very much for your comments and sorry for the delay, please refer to my
replies marked with [AS].
On 7/14/20, 10:51 AM, "Alvaro Retana via Datatracker" wrote:
Alvaro Retana has entered the following ballot position for
Hi Erik,
Thanks for your comments and sorry to missed them in first place, please see my
replies in line marked w/ [AS]:
On 7/14/20, 11:22 PM, "Erik Kline via Datatracker" wrote:
Erik Kline has entered the following ballot position for
draft-ietf-bess-evpn-inter-subnet-forwarding-09:
he problem with propagating them
is sometimes implementations reorder things, so you could end up with
inconsistency in the network.
—John
On Oct 8, 2020, at 2:42 PM, Ali Sajassi (sajassi)
mailto:saja...@cisco.com>> wrote:
Hi John,
Sorry for the delay.
The answer to y
Hi John,
Sorry for the delay.
The answer to your 1st question is no and the answer to your 2nd question is
that the receiver should pick the first one in the list and ignore the rest. If
it helps, I can add couple of lines to that affect to the corresponding section.
Cheers,
Ali
From: John
As a co-author, I support WG adoption of this draft and I am not aware of any
relevant IPR.
Regards,
Ali
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Wednesday, September 9, 2020 at 3:43 AM
To: "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: [bess] WG adoption and IPR
ll improve the document
Regards
-éric
-Original Message-
From: "Ali Sajassi (sajassi)"
Date: Tuesday, 1 September 2020 at 00:25
To: Eric Vyncke , The IESG
Cc: "draft-ietf-bess-evpn-inter-subnet-forward...@ietf.org"
, "bess-cha
Hi Ben,
Thanks very much for your review and comments. Please refer to my replies
inline marked with [AS].
On 7/14/20, 2:00 PM, "Benjamin Kaduk via Datatracker" wrote:
Benjamin Kaduk has entered the following ballot position for
draft-ietf-bess-evpn-inter-subnet-forwarding-09:
Hi Eric,
Thanks for your review and your comments, please refer to my replies inline
marked with [AS].
On 7/14/20, 5:32 AM, "Éric Vyncke via Datatracker" wrote:
Éric Vyncke has entered the following ballot position for
draft-ietf-bess-evpn-inter-subnet-forwarding-09: No Objection
. IMHO a draft on the
interaction between RFC6514 and the tunnel-encapsulation draft – would be the
best thing at this point. Let me know if you are interested in working on such
a draft.
Sue
From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Friday, July 31, 2020 1:54
John, Jeff:
During the presentation of draft-ietf-bess-evpn-unequal-lb -03 at the BESS WG
meeting, you had a question/concern regarding why we are defining a new EC if
we are doing conditional transitive. First, I’d like to make a correction to
the preso by saying that the transitivity is not
Sue,
Before getting to the discussions of the three IPsec proposals, there are some
elements of draft-ietf-idr-tunnel-encaps-17.txt that I can see might have
caused some confusions and I’d like to get those sorted out first.
The tunnel-encap draft specifies sub-tlv for VxLAN, VxLAN GDP, and
nel-encaps - draft-ietf-idr-tunnel-encaps-17.txt
sajassi-s-evpn – draft-sajasssi-bess-secure-evpn-03.txt
RFC6514 – PMSI Tunnel Attribute (PMSI)
Cheerily, Sue
From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Tuesday, July 28, 2020 9:45 AM
To: Susan Hares; bess@ietf.org
Subject: Re: [
Sue,
Please see my responses below marked with AS>
From: BESS on behalf of Susan Hares
Date: Tuesday, July 28, 2020 at 5:43 AM
To: "bess@ietf.org"
Subject: [bess] Why are you specifying two new tunnel types for encapsulation
for EVPN?
Ali:
From draft-sajassi-bess-secure-evpn:
Linda,
Please see my responses inline marked with AS> …
From: Linda Dunbar
Date: Tuesday, July 28, 2020 at 5:49 AM
To: Cisco Employee , "bess@ietf.org"
Subject: Questions about the ESP-Transport and ESP-in-UDP transport in
SECURE-EVPN
Ali,
Just follow up with my question in the BESS WG
Hi Murray,
Thanks for your review and comments. Please see my responses inline marked with
"AS>".
Cheers,
Ali
On 7/13/20, 10:50 PM, "Murray Kucherawy via Datatracker"
wrote:
Murray Kucherawy has entered the following ballot position for
Hi Rob,
Thanks for your review and comments. Please see my reply inline marked with
"AS>".
On 7/16/20, 6:38 AM, "Robert Wilton via Datatracker" wrote:
Robert Wilton has entered the following ballot position for
draft-ietf-bess-evpn-inter-subnet-forwarding-09: No Objection
When
Support as a co-author. I am not aware of any undisclosed IPR.
From: "slitkows.i...@gmail.com"
Date: Friday, July 3, 2020 at 6:29 AM
To: "bess@ietf.org" , "draft-ietf-bess-evpn-lsp-p...@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: WGLC, IPR and implementation poll for
Hi Joel,
Thanks for your review and comments, please see inline for my reply marked with
AS>:
On 7/6/20, 8:06 PM, "Joel Jaeggli via Datatracker" wrote:
Reviewer: Joel Jaeggli
Review result: Ready
greetings,
I have reviewed draft-ietf-bess-evpn-inter-subnet-forwarding on
Support as a co-author. Not aware of any undisclosed IPRs related to this draft.
Cheers,
Ali
From: "Bocci, Matthew (Nokia - GB)"
Date: Monday, June 15, 2020 at 3:55 AM
To: "draft-ietf-bess-evpn-oam-req-fr...@ietf.org"
, "bess@ietf.org"
Subject: WG Last Call and IPR Poll for
This draft covers the different SDWAN use cases nicely and has come a long way
since its initial rev. As a co-author I support adoption of this draft and I am
not aware of any undisclosed IPRs related to this draft.
Cheers,
Ali
From: BESS on behalf of "slitkows.i...@gmail.com"
Date:
The issues raised during the email thread before the last IETF, have been
addressed in this rev and the doc is ready to be progressed.
Cheers,
Ali
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Monday, May 18, 2020 at 12:54 AM
To: "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
oposes is fine.
—John
On Apr 28, 2020, at 1:08 AM, Ali Sajassi (sajassi)
mailto:saja...@cisco.com>> wrote:
Hi John,
My objection to using two code points for RT-8 and do a migration from old to
new is two folds:
1. As I explained in my previous emails, there are vendors who have
i
t have technical
deficiencies that were pointed out months ago.
Just because you can hold things together with spit and baling wire, doesn’t
mean you should settle for that. I am perplexed as to why you’re so opposed to
doing what is both the normal and the right thing.
—John
On Apr 26,
nly in DC, but also in service provider and
enterprise networks. We not only have PBB-EVPN, but also EVPN/VXLAN,
EVPN/MPLS, EVPNoMPLSoUPD, etc. EVPN is supported by many vendors today.
Thanks,
Wen
From: "Ali Sajassi (sajassi)"
Date: Sunday, April 26, 2020 at 6:08 PM
To: John Scudder
C
guarantees
safety in a mixed network.
—John
On Apr 26, 2020, at 3:21 PM, Ali Sajassi (sajassi) wrote:
John,
Thanks for your insightful input and suggestion. We have had other situations
similar to this in the past and we have resolved them by the consensus and
without having a “ticking time bom
John,
Thanks for your insightful input and suggestion. We have had other situations
similar to this in the past and we have resolved them by the consensus and
without having a “ticking time bomb” to cause a network meltdown. One such
situation was the need to extend RT-4 to add the originator
Support and not aware of any undisclosed IPR
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Wednesday, February 26, 2020 at 6:28 AM
To: 'BESS'
Cc: "bess-cha...@ietf.org"
Subject: [bess] WGLC, IPR and implementation poll for
draft-ietf-bess-evpn-irb-mcast-04
Hi WG,
This email
Hi Stephane,
Thanks for reviewing the new rev of the document and providing us with your
comments. We’ll try to take care of your comments within next few days.
Regards,
Ali
From: "slitkows.i...@gmail.com"
Date: Tuesday, March 3, 2020 at 1:29 AM
To:
1 - 100 of 301 matches
Mail list logo
