Hi,
As a co-author, I support this draft for WG adoption.
I am not aware of any IPR relevant to this document.
Thank you,
Jorge
From: BESS on behalf of Stephane Litkowski (slitkows)
Date: Monday, October 10, 2022 at 10:40 AM
To: bess-cha...@ietf.org , bess@ietf.org
Subject: [bess] WG
Hi Mankamana,
Thank you for your review. We’ve published version 04, which addresses your
comments. Also incorporates Greg Mirsky’s comments (thanks Greg!) about the
section that talks about the optional use of BFD in the solution. By the way,
this section has a reference to
Saumya,
Please see in-line.
Thanks.
Jorge
From: BESS on behalf of Dikshit, Saumya
Date: Thursday, July 14, 2022 at 10:43 AM
To: draft-ietf-bess-evpn-pref-df@ietf.org
Cc: bess@ietf.org , bess-cha...@ietf.org
Subject: Re: [bess] Few queries on draft-ietf-bess-evpn-pref-df
Hello Authors,
Hi Stewart,
Thanks for reviewing. Changes are incorporated in version 10 that we just
published. Please see my comments in-line with [jorge].
Thx
Jorge
From: Stewart Bryant via Datatracker
Date: Tuesday, August 30, 2022 at 12:41 PM
To: rtg-...@ietf.org
Cc: bess@ietf.org ,
Hi Sue,
Sorry, it took us longer than we wanted.
We appreciate your comments. We put some work onto the draft with some back and
forth discussions among the authors and other WG members. Based on that, we
published version 7.
With version 7 in mind, please see my responses in-line with
Hi Sasha,
Sorry for the big delay.
That was indeed a bug, fixed in version 09, just posted.
Thank you very much for letting us know.
Thanks.
Jorge
From: Alexander Vainshtein
Date: Monday, February 21, 2022 at 4:04 PM
To: Rabadan, Jorge (Nokia - US/Sunnyvale)
Cc: bess@ietf.org , draft-ietf
FYI
This is an update of the draft that addresses the comments made during the
WGLC. Some other changes are added to improve readability.
Please let us know if you have comments.
Thank you!
Jorge
From: BESS on behalf of internet-dra...@ietf.org
Date: Thursday, June 23, 2022 at 1:12 PM
To:
Hi Yubao,
RFC7432 assumes MPLS transport and hence label fields are 20-bit long.
RFC8365 though assumes NVO transport and the label fields are 24-bit long.
That’s why Ketan mentioned the label field in EVPN routes is 24-bit long.
Thanks.
Jorge
From: BESS on behalf of wang.yub...@zte.com.cn
the control plane
out of synch sounds wrong to me.
Thanks.
Jorge
From: Dikshit, Saumya
Date: Friday, June 17, 2022 at 1:35 PM
To: Rabadan, Jorge (Nokia - US/Sunnyvale) ,
draft-ietf-bess-rfc7432...@ietf.org
Cc: bess@ietf.org
Subject: RE: (Authors of draft-ietf-bess-rfc7432bis) : Query regarding Loop
Hi,
It refers to the fact that the MAC is flushed from the bridge-table and
therefore it is no longer duplicate. The router needs to clear the duplicate
state and obviously, if the mac keeps moving, the router starts counting the
moves again withing the duplication window.
The key point is
I concur with Sasha.
We’ve been gone through a significant effort to unify the service signaling by
using EVPN. If we are missing anything in EVPN VPWS compared to T-LDP based
PWs, I would rather look at extending EVPN VPWS (if needed). If not an option,
it would good to discuss at least why
Hi,
As a co-author I’m not aware of any relevant IPR.
Nokia is planning to implement this, but no implementation yet.
Thanks.
Jorge
From: slitkows.i...@gmail.com
Date: Wednesday, May 18, 2022 at 12:23 AM
To: draft-ietf-bess-evpn-redundant-mcast-sou...@ietf.org
, bess@ietf.org
Cc:
Hi Saumya,
From: Dikshit, Saumya
Date: Tuesday, March 29, 2022 at 2:13 PM
To: Luc André Burdet , Rabadan, Jorge (Nokia -
US/Sunnyvale) ,
draft-saumvinayak-bess-all-df-...@ietf.org
, bess@ietf.org
Subject: RE: draft-saumvinayak-bess-all-df-bum
Hello Jorge, Luc,
Thanks a lot, for suggesting
you need? Sorry
if I’m missing something here.
Please help me understand why you are using a non-zero ethernet segment here.
Thanks!
Jorge
From: Dikshit, Saumya
Date: Thursday, March 24, 2022 at 11:15 AM
To: Rabadan, Jorge (Nokia - US/Sunnyvale) ,
draft-saumvinayak-bess-all-df-...@ietf.org
Hi Saumya,
Best path selection for EVPN routes is something that indeed we will clarify in
rfc7432bis, as mentioned at the BESS session during the presentation of
draft-sr-bess-evpn-dpath-01. We will update the draft in next version, Luc and
the rest of the authors will take the action. Luc
Dear Saumya and authors,
I wanted to follow up on what I mentioned at the mic this morning during the
BESS session:
1. You are requesting DF Alg codepoint 2 for this draft, which clashes with
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-pref-df-08#section-6
– a Working Group
Hi Loa,
We changed the draft’s name before posting it at the very last minute and I
failed to update the chairs/Mankamana with the new name for the agenda.
My apologies for that. The agenda should list this one instead:
draft-sr-bess-evpn-vpws-gateway-00
Hi,
I fully support this document for WG adoption.
1) Does this technology support the SR P2MP features
that distributes candidate paths which connect
a multicast distribution tree (tree to leaves).
Yes, it does.
2) Is the technology correctly specified for the
NLRI (AFI/SAFI) and the tunnel
I agree with Vasilenko.
The meaning of the label is given by the encapsulation, e.g. for the EVPN
family, label=VNI if the bgp encapsulation extended community indicates VXLAN,
and label=MPLS-label if the encapsulation indicates MPLS.
In this document, the label is a transposed function if the
the necessary edits to make the text
consistent with that, as part of this WGLC.
Thanks!
Jorge
From: Gyan Mishra
Date: Tuesday, February 15, 2022 at 8:37 PM
To: Rabadan, Jorge (Nokia - US/Sunnyvale)
Cc: Anoop Ghanwani , BESS ,
bess-cha...@ietf.org ,
draft-ietf-bess-evpn-mh-split-hori...@ietf.org
Hi Sasha,
Sorry for the delay, this email fell through the cracks..
Please see in-line.
Thanks for the feedback.
Jorge
From: Alexander Vainshtein
Date: Thursday, December 9, 2021 at 1:12 PM
To: draft-ietf-bess-evpn-pref-df@ietf.org
Cc: bess@ietf.org
Subject: Queries on
Thank you Anoop. We will fix those in the next version.
Jorge
From: Anoop Ghanwani
Date: Saturday, February 5, 2022 at 12:19 AM
To: slitkows.i...@gmail.com
Cc: BESS , draft-ietf-bess-evpn-mh-split-hori...@ietf.org
, bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll
Hi everyone,
I’m not aware of any relevant undisclosed IPR.
Thanks.
Jorge
From: Bocci, Matthew (Nokia - GB)
Date: Monday, January 31, 2022 at 2:58 PM
To: draft-ietf-bess-evpn-fast-df-recov...@ietf.org
, bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WGLC, IPR and Implementation Poll for
in the other two drafts. It would be
bad to publish 7432-bis to have it updated immediately after.
Can we create the registry in 7432-bis then?
Thanks!
Jorge
From: Luc André Burdet
Date: Friday, January 28, 2022 at 11:26 AM
To: Rabadan, Jorge (Nokia - US/Sunnyvale) ,
slitkows.i...@gmail.com , bess
Hi,
As a co-author, I’m not aware of any related IPR.
Nokia’s implementation follow the default aspects described in the document,
and plans to add support for the full specification in the coming releases.
Thank you.
Jorge
From: slitkows.i...@gmail.com
Date: Wednesday, January 26, 2022 at
Hi Luc,
As usual, that is an excellent point.
One of the two draft should start a registry in the IANA section. Stephane,
chairs, any preference where this should reside?
@Luc, about this:
“This has come up before for e.g. draft-ietf-bess-evpn-l2gw-proto which
requests a 3-bit field for
Thank you John.
Jorge
From: John Scudder
Date: Tuesday, January 25, 2022 at 8:32 AM
To: Rabadan, Jorge (Nokia - US/Sunnyvale)
Cc: The IESG , draft-ietf-bess-evpn-optimized...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew (Nokia -
GB)
Subject: Re: John Scudder's Discuss
with [jorge].
Thank you John.
Jorge
From: John Scudder
Date: Friday, January 7, 2022 at 11:09 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: The IESG , draft-ietf-bess-evpn-optimized...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew (Nokia -
GB)
Subject: Re: John Scudder's
Hi Eduard,
Sounds like a reasonable request to me. We’ll look into it for the next version.
Thank you!
Jorge
From: Vasilenko Eduard
Date: Wednesday, January 12, 2022 at 7:09 PM
To: draft-ietf-bess-evpn-ipvpn-interworking@ietf.org
Cc: bess@ietf.org
Subject: Is
Hi Saumya,
I was just referring to sections 4.1, 4.2 and 4.3 in RFC9136.
Thanks.
Jorge
From: Dikshit, Saumya
Date: Friday, December 3, 2021 at 6:53 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) , Joshi,
Vinayak , bess@ietf.org
Cc: John E Drake
Subject: RE: Query about Ethernet Tag Id
.
Jorge
From: Rabadan, Jorge (Nokia - US/Mountain View)
Date: Thursday, December 2, 2021 at 6:00 PM
To: Joshi, Vinayak , bess@ietf.org
Subject: Re: Query about Ethernet Tag Id for TYpe-5 routes (RFC 9136)
Hi Vinayak,
RFC9136 does not have any use case for the use of a non-zero ethernet tag id
Hi Vinayak,
RFC9136 does not have any use case for the use of a non-zero ethernet tag id.
The IP Prefix route includes the ethernet tag id as part of the key for
consistency with the rest of the EVPN service routes, for future use.
Thanks.
Jorge
From: BESS on behalf of Joshi, Vinayak
Date:
Hi Yubao,
We’ll try to clarify further in the next revision, but I hope the three use
cases and procedures are clear now.
Thanks for the feedback.
Jorge
From: wang.yub...@zte.com.cn
Date: Saturday, November 13, 2021 at 3:56 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Thanks.
Jorge
From: Pascal Thubert (pthubert)
Date: Monday, November 15, 2021 at 12:11 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) ,
draft-thubert-bess-secure-evpn-mac-signal...@ietf.org
, bess@ietf.org
Subject: RE: draft-thubert-bess-secure-evpn-mac-signaling and RFC9047 ARP/ND
Hi Russ,
Thank you very much for reviewing. We published version 04 to address your
comments.
Please see my comments in-line with [jorge].
Thanks.
Jorge
From: op...@riw.us
Date: Friday, October 22, 2021 at 10:06 PM
To: rtg-...@ietf.org
Cc: rtg-...@ietf.org ,
Hi John,
Thanks again.
We just published version 11, addressing some other reviews.
Let us know if you have any other comments.
Thanks,
Jorge
From: John Scudder
Date: Tuesday, November 9, 2021 at 9:02 PM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: The IESG , draft-ietf-bess-evpn
Hi Tim,
Thank you very much for your review.
Version 11 should address all your comments.
Please see in-line with [jorge].
Thanks.
Jorge
From: Tim Chown via Datatracker
Date: Sunday, October 31, 2021 at 12:47 PM
To: ops-...@ietf.org
Cc: bess@ietf.org ,
Hi Benjamin,
Thank you very much for the thorough review! Version 11 addresses those
comments that were not covered in version 10.
Please see my comments in-line with [jorge].
Thx
Jorge
From: Benjamin Kaduk via Datatracker
Date: Thursday, October 28, 2021 at 4:53 AM
To: The IESG
Cc:
Hi Alvaro,
Thank you very much for reviewing. We published version 11, which should
address your comments (those that were not addressed in version 10).
Please see my comments in-line with [jorge].
Thanks.
Jorge
From: Alvaro Retana via Datatracker
Date: Thursday, October 21, 2021 at 3:56 PM
Hi Francesca,
Thank you very much for reviewing.
John’s review has been addressed in version 10 (hence in version 11 too).
We also reviewed the use of SHOULD again.
I hope the latest version can address your comments.
Thank you.
Jorge
From: Francesca Palombini via Datatracker
Date: Thursday,
Hi Murray,
Thank you for reviewing!
GENEVE is now removed, please check out version 11. Also IR forwarding mode is
expanded as Ingress Replication forwarding mode and used as such throughout the
document.
Hope that addresses your comments.
Thank you!
Jorge
From: Murray Kucherawy via
Hi Derek,
Thank you very much for reviewing.
The Security section (along with the other sections) has been improved quite a
bit in the latest revision compared to version 09.
All in all, a forged BM packet sent into an EVPN PE will reach all the remote
EVPN PEs of the same Broadcast Domain.
: Monday, November 15, 2021 at 4:58 PM
To: Luc André Burdet , Rabadan, Jorge (Nokia -
US/Mountain View) , Anoop Ghanwani
, Patrice Brissette (pbrisset)
Cc: slitkows.i...@gmail.com , Joshi, Vinayak
, bess-cha...@ietf.org , BESS
Subject: RE: [bess] WGLC, IPR and implementation poll on
draft-ietf
addresses symmetric IRB (RFC9135) and interface-less model (RFC9136)
only.
Thanks.
Jorge
From: wang.yub...@zte.com.cn
Date: Friday, November 12, 2021 at 7:16 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re:Questions on draft-sajassi-bess-evpn-ip-aliasing-03
From: wang.yub...@zte.com.cn
Date: Friday, November 12, 2021 at 8:04 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re:Comments on draft-ietf-bess-evpn-prefix-advertisement and
draft-wang-bess-evpn-distributed-bump-in-the-wire
Hi Jorge,
Please see in-line
Hi Saumya,
I fail to see why you are asking for a discussion on
draft-saumvinayak-bess-all-df-bum before draft-ietf-bess-evpn-mh-pa can pass WG
Last Call.
Your draft addresses a completely different use-case, that we can discuss
separately, but it has nothing to do with
need to use the ethernet-tag-id, which is used for
vlan-aware-bundle in general.
Thanks.
Jorge
From: wang.yub...@zte.com.cn
Date: Friday, July 30, 2021 at 5:18 PM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re:Comments on draft-ietf-bess-evpn-prefix-advertisement
Hi Yubao,
Please see my comments with [jorge2].
Thx
Jorge
From: wang.yub...@zte.com.cn
Date: Wednesday, November 10, 2021 at 3:55 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re:Questions on draft-sajassi-bess-evpn-ip-aliasing-03
Hi Jorge,
please see
Dear authors,
As requested by Pascal, this is an email mostly to suggest the use of the
ARP/ND ext community.
Also some additional comments about this draft:
1. Minor one: the acronym that we are using in all the EVPN specs is “EVPN”
and not “eVPN” – it seems the document is using both, it
Hi Yubao,
Please see in-line.
Thanks.
Jorge
From: wang.yub...@zte.com.cn
Date: Tuesday, November 9, 2021 at 9:06 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Questions on draft-sajassi-bess-evpn-ip-aliasing-03
Hi Jorge,
I read the draft, and have
Hi Roman,
Thanks for the review.
Please see the resolution of your comments in-line with [jorge].
Thx
Jorge
From: Roman Danyliw via Datatracker
Date: Monday, October 18, 2021 at 2:32 PM
To: The IESG
Cc: draft-ietf-bess-evpn-optimized...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org ,
Hi Éric,
Please see in-line with [jorge].
Thanks for reviewing!
Jorge
From: Éric Vyncke via Datatracker
Date: Monday, October 18, 2021 at 1:40 AM
To: The IESG
Cc: draft-ietf-bess-evpn-optimized...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew (Nokia -
GB) , Bocci, Matthew
Hi Pascal,
Thank you for the thorough review. All the changes are incorporated in version
10.
Please see in-line.
Thanks.
Jorge
From: Pascal Thubert via Datatracker
Date: Friday, October 15, 2021 at 6:44 AM
To: int-...@ietf.org
Cc: bess@ietf.org ,
Hi Julien,
Thanks very much for the review. Great points.
We took all your suggestions and incorporate them in version 10. Please see the
resolutions in-line below with [jorge].
Thanks!
Jorge
-Original Message-
From: julien.meu...@orange.com
Date: Thursday, October 14, 2021 at 12:39
Hi Lars,
Thanks for reviewing.
We incorporated all your suggestions in version 10.
Thanks!
Jorge
From: Lars Eggert via Datatracker
Date: Monday, October 11, 2021 at 7:08 AM
To: The IESG
Cc: draft-ietf-bess-evpn-optimized...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew
To: Rabadan, Jorge (Nokia - US/Mountain View) , The
IESG , draft-ietf-bess-evpn-proxy-arp...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew (Nokia -
GB) , jeanmichel.com...@orange.com
Subject: Re: Éric Vyncke's Discuss on draft-ietf-bess-evpn-proxy-arp-nd-11:
(with DISCUSS and COMMENT
ble. An unsuccessful lookup will result
on a ‘forward’ behavior (i.e., flood the NS message based on
the MAC DA.
Please let me know if you are ok with it.
Thank you!
Jorge
From: Eric Vyncke (evyncke)
Date: Wednesday, October 6, 2021 at 5:17 PM
To: Rabadan, Jorge (Nokia -
Hi Gyan,
Thank you very much for review the document!
I’m adding comments along your comments with [jorge].
Please check them out.
Thanks again,
Jorge
From: Gyan Mishra via Datatracker
Date: Saturday, October 2, 2021 at 8:09 PM
To: gen-...@ietf.org
Cc: bess@ietf.org ,
As co-author, I support the publication of this document as Standards Track RFC.
Not aware of any relevant IPR.
Thanks.
Jorge
From: BESS on behalf of slitkows.i...@gmail.com
Date: Tuesday, September 28, 2021 at 8:03 AM
To: 'BESS'
Cc: bess-cha...@ietf.org
Subject: [bess] WG Last Call, IPR
As co-author, I support this document for publication as standards track RFC.
Not aware of any relevant IPR.
Thanks.
Jorge
From: Bocci, Matthew (Nokia - GB)
Date: Tuesday, September 28, 2021 at 11:00 AM
To: bess@ietf.org
Cc: draft-ietf-bess-evpn-gen...@ietf.org
Subject: CORRECTION WG Last
: Joshi, Vinayak
Date: Tuesday, September 28, 2021 at 4:21 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) , The
IESG , draft-ietf-bess-evpn-proxy-arp...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew (Nokia -
GB) , jeanmichel.com...@orange.com
, Eric Vyncke (evyncke)
Subject: RE
it sounds like a corner case and in any case, the tables will be updated anyway.
Maybe we can add some text in the security section if it helps?
Thanks.
Jorge
From: Joshi, Vinayak
Date: Monday, September 27, 2021 at 12:34 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) , The
IESG , draft-ietf
Hi Michael,
Thanks for the review. Just published revision 09 addressing your comments.
Please see in-line with [jorge].
Thanks!
Jorge
From: Michael Tüxen via Datatracker
Date: Tuesday, September 7, 2021 at 9:57 PM
To: tsv-...@ietf.org
Cc: bess@ietf.org ,
addresses Erik Kline’s comments, and it
is now ready to go.
Thanks.
Jorge
From: Eric Vyncke (evyncke)
Date: Tuesday, September 14, 2021 at 2:50 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) , The
IESG , draft-ietf-bess-evpn-proxy-arp...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org
Hi Sue,
My apologies for the delay.
Thank you very much for your review!
We’ve just published rev 06 which addresses some of your comments.
Please see below in-line with [jorge].
Thanks.
Jorge
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, July 27, 2021
Ali’s reasoning makes sense to me too.
Thanks.
Jorge
From: BESS on behalf of gregory.mir...@ztetx.com
Date: Tuesday, August 31, 2021 at 11:37 PM
To: jdrake=40juniper@dmarc.ietf.org
Cc: Bocci, Matthew (Nokia - GB) ,
sajassi=40cisco@dmarc.ietf.org ,
From: Dikshit, Saumya
Date: Thursday, August 19, 2021 at 8:49 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) ,
draft-ietf-bess-evpn-fast-df-recov...@ietf.org
,
draft-ietf-bess-evpn-df-election-framew...@ietf.org
Cc: bess@ietf.org
Subject: RE: Query to authors of draft-ietf-bess-evpn-fast-df
y, August 19, 2021 at 8:28 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) ,
draft-ietf-bess-evpn-fast-df-recov...@ietf.org
,
draft-ietf-bess-evpn-df-election-framew...@ietf.org
Cc: bess@ietf.org
Subject: RE: Query to authors of draft-ietf-bess-evpn-fast-df-recovery and rfc
Thanks A
and the one from the EVPN route should be installed.
Thx
Jorge
From: Dikshit, Saumya
Date: Thursday, August 19, 2021 at 7:56 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) ,
draft-ietf-bess-evpn-fast-df-recov...@ietf.org
,
draft-ietf-bess-evpn-df-election-framew...@ietf.org
Cc: bess@ietf.org
Hi Saumya,
To be clear, your query has nothing to do with the two documents you refer to.
In fact I don’t see any issue related to multihoming.
Given that in your example host-1 and FW-1 are directly connected to the same
leaf, and host-2 and FW-2 are connected to the same leaf too, I can see
Thank you Arvind for clarifying and making the change for the second point.
Jorge
From: Arvind Venkateswaran (arvvenka)
Date: Friday, July 30, 2021 at 12:34 PM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: draft-ietf-bess-mvpn-evpn-sr-p...@ietf.org
, bess@ietf.org
Subject: Re: draft-ietf
Hi Yubao,
More in-line.
Thanks.
Jorge
From: wang.yub...@zte.com.cn
Date: Wednesday, July 28, 2021 at 5:35 PM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re:Comments on draft-sajassi-bess-evpn-ip-aliasing-02
Hi Jorge,
I don't agree with you
Dear draft-ietf-bess-mvpn-evpn-sr-p2mp authors,
I have some comments about yesterday’s presentation of revision 03. In the
slides, this caught my attention:
“Current Updates (Version 03)
• Includes procedures for binding MVPN/EVPN service to an ingress-replication
P-tunnel in a Segment Routing
.
Jorge
From: wang.yub...@zte.com.cn
Date: Wednesday, July 28, 2021 at 2:06 PM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re:Comments on draft-sajassi-bess-evpn-ip-aliasing-02
Hi Jorge,
Please see in-line with [Yubao_2].
Thanks,
Yubao
原始邮件
发件人：Rabadan
Hi Yubao,
Please see in-line with [jorge].
Thanks.
Jorge
From: wang.yub...@zte.com.cn
Date: Wednesday, July 28, 2021 at 9:53 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Re:Comments on draft-sajassi-bess-evpn-ip-aliasing-02
Hi Jorge,
Thanks for your email
Michael,
The chairs asked me to take my comments to the list, so here you are.
1. Section 2.6 – RT5 synch
* using non-zero ESI *and* non-zero GW-IP in the IP Prefix routes is
non-backwards compatible with draft-ietf-bess-evpn-prefix-advertisement and
will break interoperability with
Date: Wednesday, July 28, 2021 at 12:14 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Subject: Comments on draft-sajassi-bess-evpn-ip-aliasing-02
Hi Jorge,
This is the detailed explanation of the question I asked in the IETF 111
meeting.
In page 7 of
slides-111-bess
are suggesting.
Thanks.
Jorge
From: Rajesh M
Date: Monday, July 19, 2021 at 3:24 PM
To: Rajesh M , Ketan Talaulikar (ketant)
, gdawra.i...@gmail.com , Clarence
Filsfils (cfilsfil) , rob...@raszuk.net
, bruno.decra...@orange.com ,
Rabadan, Jorge (Nokia - US/Mountain View)
Cc: spr...@ietf.org , b
Dear chairs,
This is just a refresh, with a couple minor clarifications based on the
feedback from some people.
How do we progress the document?
Thanks.
Jorge
From: BESS on behalf of internet-dra...@ietf.org
Date: Tuesday, June 22, 2021 at 10:05 AM
To: i-d-annou...@ietf.org
Cc:
Nokia has an implementation in SROS, shipping code for a few years now.
Thanks.
Jorge
From: Bocci, Matthew (Nokia - GB)
Date: Friday, June 18, 2021 at 4:19 PM
To: 松田 卓
Cc: Rabadan, Jorge (Nokia - US/Mountain View) ,
bess@ietf.org , draft-ietf-bess-pbb-evpn-isid-cmacfl...@ietf.org
, bess-cha
Hi Eric,
No problem whatsoever. The rev 14 includes all the changes.
Thanks!
Jorge
From: Eric Vyncke (evyncke)
Sent: Friday, June 11, 2021 13:52
To: Rabadan, Jorge (Nokia - US/Mountain View); The IESG;
draft-ietf-bess-evpn-proxy-arp...@ietf.org; bess-cha
to
clear your DISCUSS.
Thanks!
Jorge
From: Eric Vyncke (evyncke)
Date: Monday, May 3, 2021 at 4:37 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) , The
IESG
Cc: draft-ietf-bess-evpn-proxy-arp...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew (Nokia -
GB) , jeanmichel.com
As co-author, I support this document for publication as standards track RFC.
Not aware of any related IPR.
Thanks.
Jorge
From: Bocci, Matthew (Nokia - GB)
Date: Tuesday, June 1, 2021 at 2:48 PM
To: bess@ietf.org
Cc: draft-ietf-bess-pbb-evpn-isid-cmacfl...@ietf.org
, bess-cha...@ietf.org
As a co-author, not aware of any relevant IPR.
The document is ready for publication.
Thanks.
Jorge
From: BESS on behalf of Patrice Brissette (pbrisset)
Date: Tuesday, June 1, 2021 at 3:59 PM
To: slitkows.i...@gmail.com , 'BESS'
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and
Hi Sasha,
That is very helpful feedback, and adding a section about the changes makes
sense to me.
Thanks.
Jorge
From: Alexander Vainshtein
Date: Thursday, May 27, 2021 at 5:16 AM
To: jdr...@juniper.net , saja...@cisco.com
, Rabadan, Jorge (Nokia - US/Mountain View)
Cc: bess@ietf.org
Hi Bruno,
Thanks for your comments.
About the first point, we do have use cases where the bandwidth is not what we
want to encode in the EC but rather a generalized weight that is derived from
the link count, logical weight or simply a configured value. Among the
co-authors we also discussed
As co-author, I support this document for WG adoption.
Not aware of any related IPR, except for the one already stated by other
co-authors.
Thanks.
Jorge
From: BESS on behalf of slitkows.i...@gmail.com
Date: Monday, April 19, 2021 at 8:06 PM
To: bess@ietf.org
Cc: bess-cha...@ietf.org
: Erik Kline
Date: Wednesday, March 31, 2021 at 1:56 AM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: The IESG , draft-ietf-bess-evpn-proxy-arp...@ietf.org
, bess-cha...@ietf.org
, bess@ietf.org , Bocci, Matthew (Nokia -
GB)
Subject: Re: Erik Kline's Discuss on draft-ietf-bess-evpn-proxy-arp
Hi Donald,
Thanks.
Looking forward to reading the updated draft.
Jorge
From: Donald Eastlake
Date: Tuesday, April 6, 2021 at 10:17 PM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: draft-ietf-bess-evpn-...@ietf.org ,
bess@ietf.org
Subject: Re: Comments about draft-ietf-bess-evpn-bfd-03
Hi DJ,
Appreciate it.
Thx
Jorge
From: Dhananjaya Rao (dhrao)
Date: Thursday, March 25, 2021 at 6:20 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) ,
draft-dskc-bess-bgp-...@ietf.org ,
bess@ietf.org
Subject: Re: [bess] About draft-dskc-bess-bgp-car
Hi Jorge,
Thank you once again
Hi Éric,
Thanks for this, it is very useful. Please see my comments in-line with [jorge].
We just published a revision, addressing yours and all the comments received in
all the reviews.
Thanks again!
Jorge
From: Éric Vyncke via Datatracker
Date: Thursday, January 21, 2021 at 3:13 PM
To: The
Hi Erik,
Thank you for your thorough review. Will publish a new version addressing your
great comments as well as the ones in other reviews too.
Please see in-line with [jorge].
Thx
Jorge
From: Erik Kline via Datatracker
Date: Thursday, January 21, 2021 at 8:21 AM
To: The IESG
Cc:
Hi Murray,
Thanks for reviewing. Please see my comments in-line with [jorge].
We have addressed your comments, you should see the changes in the next
revision.
Thx
Jorge
From: Murray Kucherawy via Datatracker
Date: Thursday, January 21, 2021 at 5:23 AM
To: The IESG
Cc:
Hi Roman,
Thank you for reviewing, please see my comments with [jorge]. Will publish the
new version after addressing the rest of the reviews too.
Thx
Jorge
From: Roman Danyliw via Datatracker
Date: Thursday, January 21, 2021 at 3:06 AM
To: The IESG
Cc:
Hi Jean-Michel,
Thank you very much for the thorough review and my apologies for the delay in
my reply.
Please see my comments in-line with [jorge].
Thank you.
Jorge
From: Jean-Michel Combes via Datatracker
Date: Wednesday, January 20, 2021 at 9:52 PM
To: int-...@ietf.org
Cc: bess@ietf.org ,
and VNI lookup is something
that all chipsets support?
Thanks.
Jorge
From: Aijun Wang
Date: Tuesday, March 16, 2021 at 4:42 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) , 'Wei
Wang' , 'linda.dunbar'
Cc: 'bess'
Subject: RE: [bess] About draft-wang-bess-l3-accessible-evpn
Hi, Jorge:
Thanks
Luc, Stephane,
Rev 07 has just been published with the discussed changes.
Thank you very much.
Jorge
From: slitkows.i...@gmail.com
Date: Wednesday, March 10, 2021 at 8:32 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) , 'Luc
Andre Burdet (lburdet)' , 'Luc André Burdet'
Cc: draft-ietf-bess
use all the BGP route dissemination tools that are based on
route-targets.
I don’t see any benefit in the solution you are suggesting, but of course I may
miss a lot of things.
Thanks.
Jorge
From: Wei Wang
Date: Friday, March 12, 2021 at 9:14 AM
To: linda.dunbar , Rabadan, Jorge (Nokia -
US
DJ, Swadesh,
Thanks for your time about these two drafts during the BESS session.
I just wanted to follow up on the two comments I made:
1) About this and the security section
“The indication of the key length enables BGP Speakers to determine
the key portion of the NLRI and use it along
Dear authors,
(Most of) these comments were made during the last IETF as well. Thank you in
advance for considering them.
1. About fault detection for unicast:
By default, it advertises this discriminator with
BGP using the BFD Discriminator Attribute [ietf-bess-mvpn-fast-
1 - 100 of 344 matches
Mail list logo
