Hi,
The draft had some good discussions prior to its adoption and we believe we
have resolved issues/comments raised at that time.
A few months ago Hejia did a RtgDir Early review, and a -01 revision was posted
to address the comments
(https://mailarchive.ietf.org/arch/msg/bess/sZmyDbMVznyH1vFx
Hi Ashutosh,
Sorry for the late response. Please see zzh> below.
From: Ashutosh Gupta
mailto:ashutoshgupta.i...@gmail.com>>
Sent: Wednesday, August 15, 2018 3:57 AM
To: Jeffrey (Zhaohui) Zhang mailto:zzh...@juniper.net>>
Cc: Ali Sajassi mailto:saja...@cisco.com>>;
bess
Resend with PIM WG added.
We had good comments and discussions early on, and I believe all concerns have
been addressed. Please see if you have more comments/concerns with this - would
like to progress the document.
Thanks!
Jeffrey
Hi,
The draft had some good dis
Support, as co-author J
I am not aware of any related IPR.
Jeffrey
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Tuesday, October 30, 2018 4:22 PM
To: bess@ietf.org
Subject: [bess] WG adoption poll for
draft-zzhang-bess-mvpn-evpn-aggregation-label-01
Hi WG,
This email begins a
Hi,
I have the following questions/comments:
The procedure described here is an OPTIONAL procedure that consists
of having a downstream PE take into account the status of P-tunnels
rooted at each possible upstream PEs, for including or not including
each given PE in the list of candid
Jingrong,
Please see zzh> below.
From: BESS On Behalf Of Xiejingrong
Sent: Tuesday, December 11, 2018 8:14 PM
To: stephane.litkow...@orange.com; bess@ietf.org
Subject: Re: [bess] Poll for early allocation request for
draft-ietf-bess-mvpn-evpn-aggregation-label
Objection.
Zzh> Please note that
Hi Jingrong,
Please see zzh2> below.
From: BESS On Behalf Of Xiejingrong
Sent: Wednesday, December 12, 2018 9:24 PM
To: Jeffrey (Zhaohui) Zhang ;
stephane.litkow...@orange..com; bess@ietf.org
Subject: Re: [bess] Poll for early allocation request for
draft-ietf-bess-mvpn-evpn-aggregation-la
Please see zzh3> below.
From: Xiejingrong
Sent: Friday, December 14, 2018 2:10 AM
To: Jeffrey (Zhaohui) Zhang ;
stephane.litkow...@orange..com; bess@ietf.org
Subject: RE: Poll for early allocation request for
draft-ietf-bess-mvpn-evpn-aggregation-label
Hi Jeffrey,
Please see xjr3>&
Hi Jingrong,
Allocating a special label from the 0~15 block is super difficult. I don't
think our use case is strong enough for that.
Thanks.
Jeffrey
From: Xiejingrong
Sent: Sunday, December 16, 2018 11:02 PM
To: Jeffrey (Zhaohui) Zhang ;
stephane.litkow...@orange..com; bess@ietf.org
Su
As a co-author, I am not aware of any undisclosed IPR on this draft.
Jeffrey
From: BESS On Behalf Of Ali Sajassi (sajassi)
Sent: Thursday, December 20, 2018 9:52 PM
To: stephane.litkow...@orange.com; bess@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for
draft-ietf-bess-evpn-bu
Jingrong,
> It is determined by the sender site PE whether to steer the flow of (C-S,
> C-G) into (*,*) PMSI-tunnel or (S,G)PMSI-tunnel, and the receiver site PE
> should work correctly in any case.
Why would the sender PE send into (*, *) when there is a match for (S,G)?
Jeffrey
> -Origi
ry 22, 2019 8:47 PM
> To: Jeffrey (Zhaohui) Zhang ; draft-ietf-bess-mvpn-expl-
> tr...@ietf.org
> Cc: bess@ietf.org
> Subject: RE: Question regarding RFC6625 and this draft-->//RE: [bess] I-D
> Action: draft-ietf-bess-mvpn-expl-track-13.txt
>
> Hi Jeffrey,
>
> The sender PE
The receiver PE cannot keep its state to receive on both tunnels forever. After
some time, it has to leave the old tunnel.
Jeffrey
> -Original Message-
> From: Xiejingrong [mailto:xiejingr...@huawei.com]
> Sent: Wednesday, January 23, 2019 9:09 PM
> To: Jeffrey (Zhaohui) Z
Robert,
You may want to leave the previous tunnel (if it is no longer needed for other
traffic). E.g., sending an mldp label withdrawal or withdrawing a Leaf A-D
route.
Jeffrey
From: Robert Raszuk [mailto:rras...@gmail.com]
Sent: Thursday, January 24, 2019 8:36 AM
To: Jeffrey (Zhaohui) Zhang
Somehow I did not get this reminder and the original email. Or maybe I just
somehow delete them by accident.
Anyway sorry for the late response. Some update for the following:
1. draft-ietf-bess-evpn-irb-mcast
We recently submitted a new revision to revive the expired revision and also
mad
Sorry for the delay. Will take care of it this week.
Thanks.
Jeffrey
> -Original Message-
> From: Mankamana Mishra (mankamis)
> Sent: Tuesday, March 12, 2019 12:15 PM
> To: Jeffrey (Zhaohui) Zhang
> Cc: Greg Mirsky ; bess-cha...@ietf.org; EXT -
> thomas.mo...@orange.c
my previous email for correlation/details.
Jeffrey
On Thu, Mar 14, 2019 at 3:04 AM Jeffrey (Zhaohui) Zhang
mailto:zzh...@juniper.net>> wrote:
Thomas, Bob,
Some questions below for you. Some old, and some new.
==
Zzh> It’s not that the “rules … are not c
Hi Greg,
Sorry for the late response.
Please see zzh2> in snipped text below.
From: Greg Mirsky
Sent: Saturday, May 11, 2019 3:24 PM
To: Jeffrey (Zhaohui) Zhang
Cc: bess-cha...@ietf.org; EXT - thomas.mo...@orange.com
; Robert Kebler ; BESS
Subject: Re: [bess] WGLC, IPR and implementat
Hi Sandy,
Thanks for your review and comments. I have submitted -07 revision.
Please see zzh> below.
From: zhang.zh...@zte.com.cn
Sent: Wednesday, July 17, 2019 9:43 PM
To: Jeffrey (Zhaohui) Zhang ; Wen Lin ;
jorge.raba...@nokia.com; ke...@arrcus.com; saja...@cisco.com;
ext-zzhan
Hi Greg,
I've trimmed some text. Please see zzh3> below.
Because all PEs may arrive at a different
conclusion regarding the state of the tunnel,
procedures described in Section 9.1.1 of [RFC 6513] MUST be used
when using inclusive tunnels.
GIM3>> Got it, thx. Would s/may/could/ be acc
Looks good!
Thanks.
Jeffrey
From: BESS On Behalf Of Greg Mirsky
Sent: Tuesday, August 20, 2019 1:38 PM
To: Jeffrey (Zhaohui) Zhang
Cc: Robert Kebler ; EXT - thomas.mo...@orange.com
; bess-cha...@ietf.org; BESS
Subject: Re: [bess] WGLC, IPR and implementation poll for
draft-ietf-bess-mvpn
Support as co-author. Not aware of IPRs.
Jeffrey
From: Ali Sajassi (sajassi)
Sent: Wednesday, September 4, 2019 2:25 PM
To: Bocci, Matthew (Nokia - GB) ;
draft-keyupate-bess-evpn-virtual-...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: WG adoption and IPR poll for
draft-keyupa
Not aware of any relevant IPR.
Juniper has an implementation.
Jeffrey
-Original Message-
From: Lenny Giuliano
Sent: Friday, September 13, 2019 3:07 PM
To: Bocci, Matthew (Nokia - GB)
Cc: bess@ietf.org; draft-ietf-bess-mvpn-msdp-sa-interoperat...@ietf.org
Subject: Re: [bess] WG Last Ca
Another way to look at different flavors/profiles of MVPN is to consider the
following two aspects:
1. How are C-multicast state (customer (s,g)/(*,g) or mLDP FEC signaled on
PC-CE interfaces) are signaled over provider core
2. How are C-multicast traffic transported through the provider
Hi Gyan,
No such RFC exists, because different customers have different preferences in
both aspects; one flavor may be optimal for customer 1 but not desired for
customer 2 😊
Jeffrey
From: Gyan Mishra
Sent: Tuesday, October 1, 2019 4:02 PM
To: Jeffrey (Zhaohui) Zhang
Cc: bess@ietf.org
+1
From: BESS On Behalf Of Wen Lin
Sent: Wednesday, October 2, 2019 2:15 PM
To: Oya Luengo, Roberto (Nokia - US/Mountain View)
; Stephane Litkowski ;
stephane.litkow...@orange.com
Cc: draft-snr-bess-evpn-loop-prot...@ietf.org; bess-cha...@ietf.org;
bess@ietf.org
Subject: Re: [bess] WG adoption
Hi Matthew,
I have addressed Stig’s comments and posted -04 revision.
Thanks!
Jeffrey
From: Bocci, Matthew (Nokia - GB)
Sent: Tuesday, October 15, 2019 6:29 AM
To: bess@ietf.org
Cc: draft-ietf-bess-mvpn-msdp-sa-interoperat...@ietf.org
Subject: Re: [bess] WG Last Call, IPR and Implementation pol
Hi Stephane,
Thanks for your review and comments/suggestions. Please see zzh> below (and
diff in
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-bum-procedure-updates-08).
From: slitkows.i...@gmail.com
Sent: Wednesday, November 13, 2019 9:11 PM
To: bess@ietf.org; draft-ietf-bess-evpn-bu
Support as co-author.
Not aware of relevant IPRs.
Jeffrey
From: slitkows.i...@gmail.com
Sent: Monday, January 6, 2020 9:15 AM
To: bess@ietf.org
Cc: bess-cha...@ietf.org; draft-zzhang-bess-bgp-multic...@ietf.org
Subject: WG adoption and IPR poll for draft-zzhang-bess-bgp-multicast-03
Hello,
Thi
Support as co-author.
Not aware of undisclosed IPR relevant to this draft.
Thanks!
Jeffrey
From: BESS On Behalf Of slitkows.i...@gmail.com
Sent: Monday, January 6, 2020 9:13 AM
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WG adoption poll and IPR poll for
draft-zzhang-bess-bgp-mu
Hi Gyan,
Please see zzh> below.
From: Gyan Mishra
Sent: Monday, January 6, 2020 7:10 PM
To: slitkows.i...@gmail.com
Cc: bess@ietf.org; bess-cha...@ietf.org;
draft-zzhang-bess-bgp-multic...@ietf.org
Subject: Re: [bess] WG adoption and IPR poll for
draft-zzhang-bess-bgp-multicast-03
Authors
W
Hi Gyan,
Please see zzh> below.
From: Gyan Mishra
Sent: Tuesday, January 7, 2020 12:39 AM
To: Jeffrey (Zhaohui) Zhang
Cc: bess-cha...@ietf.org; bess@ietf.org;
draft-zzhang-bess-bgp-multic...@ietf.org; slitkows.i...@gmail.com
Subject: Re: [bess] WG adoption and IPR poll for
draft-zzhang-b
Hi Gyan,
Please see zzh3> below. I trimmed some text.
From: Gyan Mishra
Sent: Wednesday, January 8, 2020 2:50 AM
To: Jeffrey (Zhaohui) Zhang
Cc: bess-cha...@ietf.org; bess@ietf.org;
draft-zzhang-bess-bgp-multic...@ietf.org; slitkows.i...@gmail.com
Subject: Re: [bess] WG adoption and IPR p
PM
To: Gyan Mishra
Cc: Jeffrey (Zhaohui) Zhang ; bess-cha...@ietf.org;
bess@ietf.org; draft-zzhang-bess-bgp-multic...@ietf.org; slitkows.i...@gmail.com
Subject: Re: [bess] WG adoption and IPR poll for
draft-zzhang-bess-bgp-multicast-03
On Thu, 9 Jan 2020, Gyan Mishra wrote:
|
| Actuall
Please see zzh> below.
From: Gyan Mishra
Sent: Thursday, January 9, 2020 1:25 PM
To: Jeffrey (Zhaohui) Zhang
Cc: Lenny Giuliano ; bess-cha...@ietf.org; bess@ietf.org;
draft-zzhang-bess-bgp-multic...@ietf.org; slitkows.i...@gmail.com
Subject: Re: [bess] WG adoption and IPR poll for
dr
Hi Gyan,
Please zzh4> below.
From: Gyan Mishra
Sent: Thursday, January 9, 2020 7:22 PM
To: Jeffrey (Zhaohui) Zhang
Cc: bess-cha...@ietf.org; bess@ietf.org;
draft-zzhang-bess-bgp-multic...@ietf.org; slitkows.i...@gmail.com
Subject: Re: [bess] WG adoption and IPR poll for
draft-zzhang-bess-
result” in both sections?
Jeffrey
From: Greg Mirsky
Sent: Wednesday, January 22, 2020 3:41 PM
To: slitkows.i...@gmail.com; Jeffrey (Zhaohui) Zhang
Cc: BESS ; bess-cha...@ietf.org
Subject: Re: Shepherd's review of draft-ietf-bess-mvpn-fast-failover
Hi Jeffrey,
happy New Years (the Spring Festiv
In 3.1.4 you missed “as a result”.
From: BESS On Behalf Of Greg Mirsky
Sent: Friday, January 31, 2020 3:55 PM
To: slitkows.i...@gmail.com
Cc: Jeffrey (Zhaohui) Zhang ; bess-cha...@ietf.org; BESS
Subject: Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-fast-failover
Hi Jeffrey,
Right 😊
From: Greg Mirsky
Sent: Friday, January 31, 2020 4:41 PM
To: Jeffrey (Zhaohui) Zhang
Cc: slitkows.i...@gmail.com; bess-cha...@ietf.org; BESS
Subject: Re: [bess] Shepherd's review of draft-ietf-bess-mvpn-fast-failover
Hi Jeffrey,
my apologies, I misunderstood your proposed c
Support the adoption.
Jeffrey
From: BESS On Behalf Of Wen Lin
Sent: Wednesday, February 5, 2020 2:01 PM
To: UTTARO, JAMES ; ext-zhang.zh...@zte.com.cn
; slitkows.i...@gmail.com
Cc: bess-cha...@ietf.org; draft-wsv-bess-extended-evpn-optimized...@ietf.org;
bess@ietf.org
Subject: Re: [bess] WG ad
Support as co-author.
I am not aware of undisclosed IPRs.
Thanks.
Jeffrey
From: BESS On Behalf Of Wen Lin
Sent: Wednesday, February 26, 2020 11:07 PM
To: slitkows.i...@gmail.com; 'BESS'
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for
draft-ietf-bess-evpn-irb-
EVPN/VLXAN uses Local Bias method for MH split horizon, which is specified in
RFC 8365.
Extending EVPN to servers don’t require new IETF standards – the servers just
need to support existing relevant standards. Having said that, with many
servers in the underlay, routing in the underlay needs t
Hi Acee,
Thanks for clarifying that.
Hi Mankamana,
Please see zzh> below.
From: Acee Lindem (acee)
Sent: Sunday, April 12, 2020 7:53 AM
To: Mankamana Mishra (mankamis) ;
draft-ietf-bess-mvpn-msdp-sa-interoperat...@ietf.org
Cc: Bocci, Matthew (Nokia - GB) ; bess@ietf.org
Subject: Re: [bess] Sh
Hub and spoke EVPN and E-tree are different.
However, draft-ietf-bess-evpn-virtual-hub should address the following two at
least:
* MPLS EVPN can't support hub/spoke usecase, where the spoke PEs can
only connect to each other through the hub PE. Especially when at
least two of t
o you still think there is a problem?
RR is only used for route distribution and should not make any difference.
Thanks.
Jeffrey
Juniper Business Use Only
From: wang.yub...@zte.com.cn
Sent: Thursday, August 20, 2020 9:52 PM
To: bess@ietf.org; Jeffrey (Zhaohui) Zhang ;
alexander.vainsht...@rbbn.c
used by the V-hub to receive traffic
on the IR tunnel from the V-spoke. Therefore, the same PED Label
attribute serves two purposes.
Jeffrey
Juniper Business Use Only
From: Alexander Vainshtein
Sent: Sunday, August 23, 2020 12:37 PM
To: wang.yub...@zte.com.cn; Jeffrey (Zhao
, August 23, 2020 10:23 PM
To: Jeffrey (Zhaohui) Zhang
Cc: alexander.vainsht...@rbbn.com; chen@zte.com.cn;
ext-zhang.zh...@zte.com.cn ; bess@ietf.org
Subject: Re:[bess] Hub-and-spoke support in EVPN:
RFC8317vs.draft-wang-bess-evpn-context-label-04
[External Email. Be cautious of content]
Hi Bob,
Please see zzh> below.
Juniper Business Use Only
From: wang.yub...@zte.com.cn
Sent: Monday, August 24, 2020 8:30 AM
To: Jeffrey (Zhaohui) Zhang
Cc: alexander.vainsht...@rbbn.com; chen@zte.com.cn;
ext-zhang.zh...@zte.com.cn ; bess@ietf.org
Subject: Re:[bess] Hub-and-spoke supp
Support as co-author.
Not aware of any IPR.
Thanks.
Jeffrey
From: Bocci, Matthew (Nokia - GB)
Sent: Monday, November 2, 2020 7:42 AM
To: bess@ietf.org; draft-parekh-bess-mvpn-evpn-sr-p...@ietf.org
Subject: WG Adoption and IPR all for draft-parekh-bess-mvpn-evpn-sr-p2mp-02
Hello,
This email beg
Hi Andy, Stewart,
Please see zzh> below.
From: Andrew G. Malis
Sent: Wednesday, November 11, 2020 8:17 AM
To: Stewart Bryant
Cc: Jeffrey (Zhaohui) Zhang ;
draft-zzhang-tsvwg-generic-transport-functi...@ietf.org; mpls ;
p...@ietf.org
Subject: Re: [Pals] Mail regarding
draft-zzhang-ts
Forwarding this discussion to BESS list as the main use case now is EVPN.
This draft is also on the BESS agenda.
Later discussions on the thread include BESS list already.
From: Jeffrey (Zhaohui) Zhang
Sent: Wednesday, November 11, 2020 11:13 AM
To: Stewart Bryant
Cc: Andrew G. Malis ;
draft
Forwarding this discussion to BESS list as the main use case now is EVPN.
This draft is also on the BESS agenda.
From: Jeffrey (Zhaohui) Zhang
Sent: Tuesday, November 10, 2020 6:13 PM
To: Andrew G. Malis ; Stewart Bryant
Cc: draft-zzhang-tsvwg-generic-transport-functi...@ietf.org; mpls
; p
.
Jeffrey
From: Stewart Bryant
Sent: Thursday, November 12, 2020 7:16 AM
To: Jeffrey (Zhaohui) Zhang
Cc: Stewart Bryant ; Andrew G. Malis
; draft-zzhang-tsvwg-generic-transport-functi...@ietf.org;
mpls ; p...@ietf.org; bess@ietf.org
Subject: Re: [Pals] Mail regarding
draft-zzhang-tsvwg-generic
Hi Stewart,
In my previous email, I acknowledged that ECMP issue you brought up and
proposed a solution.
In fact, we can make the GFH to start with nibble .
Thanks.
Jeffrey
From: Stewart Bryant
Sent: Monday, November 16, 2020 4:35 AM
To: Jeffrey (Zhaohui) Zhang
Cc: Stewart Bryant
Hi,
It seems that the draft is about using data-plane mac learning in an EVPN-like
solution. That retains other properties of EVPN, but removes the need for
advertising MAC addresses, with the consequences/problems that Ali was trying
to point out.
Leaving the pros and cons of data plane mac l
Stewart,
Please see zzh2> below.
From: Stewart Bryant
Sent: Thursday, November 19, 2020 1:21 AM
To: Jeffrey (Zhaohui) Zhang
Cc: Stewart Bryant ; Andrew G. Malis
; draft-zzhang-tsvwg-generic-transport-functi...@ietf.org;
mpls ; p...@ietf.org; bess@ietf.org
Subject: Re: [Pals] Mail regard
(Zhaohui) Zhang ; bess@ietf.org
Subject: Re: [bess] comments on draft-boutros-bess-elan-services-over-sr
[External Email. Be cautious of content]
Hi Jorge,
On Nov 19, 2020, at 5:09 AM, Rabadan, Jorge (Nokia - US/Mountain View)
mailto:jorge.raba...@nokia.com>> wrote:
Hi everyone,
Jeffre
Support as co-author.
Not aware of IPRs.
Thanks.
Jeffrey
From: slitkows.i...@gmail.com
Sent: Tuesday, December 1, 2020 4:31 AM
To: bess@ietf.org; draft-skr-bess-evpn-redundant-mcast-sou...@ietf.org
Subject: WG adoption for draft-skr-bess-evpn-redundant-mcast-source
[External Email. Be cautious
Support as co-author.
Not aware of undisclosed IPRs.
Thanks.
Jeffrey
From: slitkows.i...@gmail.com
Sent: Friday, December 11, 2020 10:53 AM
To: draft-ietf-bess-mvpn-evpn-aggregation-la...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG Last Call, IPR and Implementation Poll for
dra
Ah. Perhaps vendors forgot/neglected to respond on the implementation question
for this particular spec, I know of two implementations.
Jeffrey
-Original Message-
From: BESS On Behalf Of slitkows.i...@gmail.com
Sent: Wednesday, December 16, 2020 5:39 AM
To: 'Éric Vyncke' ; 'The IESG'
C
Hi Stephane,
I forgot to mention that Juniper has a Proof of Concept implementation.
As soon as Ice confirms his new affiliation I'll submit a new revision with
updated contact information for Eric and Ice.
Thanks.
Jeffrey
From: slitkows.i...@gmail.com
Sent: Monday, January 4, 2021 5:43 AM
To:
Support.
Jeffrey
From: BESS On Behalf Of Bocci, Matthew (Nokia - GB)
Sent: Tuesday, April 13, 2021 5:37 AM
To: draft-mishra-bess-deployment-guide-ipv4nlri-ipv...@ietf.org; bess@ietf.org
Subject: [bess] WG Adoption and IPR Poll for
draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03
[External
Hi, Stephane,
Thanks you so much for your review!
Please see zzh> below (I skipped all those that will be fixed as you pointed
out).
From: Stephane Litkowski (slitkows)
Sent: Monday, April 12, 2021 5:56 AM
To: draft-ietf-bess-mvpn-evpn-aggregation-la...@ietf.org
Cc: bess@ietf.org
Subject: draf
Hi Stephane,
Thanks again for your review, comments and suggestions. I have uploaded -06
that should address all your comments.
Jeffrey
From: Stephane Litkowski (slitkows)
Sent: Wednesday, April 14, 2021 3:59 AM
To: Jeffrey (Zhaohui) Zhang ;
draft-ietf-bess-mvpn-evpn-aggregation-la
Hi Qin,
Thank you for your review and comments. Let me share a diff to see if it
addresses the issues, before I post a revision.
Please see zzh> below.
-Original Message-
From: Qin Wu via Datatracker
Sent: Friday, April 23, 2021 11:20 AM
To: ops-...@ietf.org
Cc: bess@ietf.org; draft-ie
Hi Qin,
Please see zzh2> below for clarifications.
-Original Message-
From: Qin Wu
Sent: Tuesday, April 27, 2021 2:38 AM
To: Jeffrey (Zhaohui) Zhang ; Lenny Giuliano
; ops-...@ietf.org
Cc: bess@ietf.org; draft-ietf-bess-mvpn-msdp-sa-interoperation@ietf.org;
last-c...@ietf.
Hi Qin,
Please see zzh3> below, and attached diff.
-Original Message-
From: Qin Wu
Sent: Tuesday, April 27, 2021 9:53 PM
To: Jeffrey (Zhaohui) Zhang ; Lenny Giuliano
; ops-...@ietf.org
Cc: bess@ietf.org; draft-ietf-bess-mvpn-msdp-sa-interoperation@ietf.org;
last-c...@ietf.
u
Sent: Friday, April 30, 2021 9:43 AM
To: Jeffrey (Zhaohui) Zhang ; Lenny Giuliano
; ops-...@ietf.org
Cc: bess@ietf.org; draft-ietf-bess-mvpn-msdp-sa-interoperation@ietf.org;
last-c...@ietf.org
Subject: RE: Opsdir last call review of
draft-ietf-bess-mvpn-msdp-sa-interoperation-05
[External Ema
.
Jeffrey
From: Qin Wu
Sent: Friday, April 30, 2021 10:21 AM
To: Jeffrey (Zhaohui) Zhang ; Lenny Giuliano
; ops-...@ietf.org
Cc: bess@ietf.org; draft-ietf-bess-mvpn-msdp-sa-interoperation@ietf.org;
last-c...@ietf.org
Subject: RE: Opsdir last call review of
draft-ietf-bess-mvpn-msdp-sa
Hi Jingrong, WG,
I somehow missed this email. Sorry for replying late.
Please see zzh> below.
From: BESS On Behalf Of Xiejingrong (Jingrong)
Sent: Wednesday, April 7, 2021 3:20 AM
To: slitkows.i...@gmail.com; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: [bess] Cross WG review request for
Hi Qin,
Thank you so much for the review and comments. I have posted -06 revision.
Jeffrey
From: Qin Wu
Sent: Friday, April 30, 2021 11:59 AM
To: Jeffrey (Zhaohui) Zhang ; Lenny Giuliano
; ops-dir
Cc: bess ; draft-ietf-bess-mvpn-msdp-sa-interoperation.all
; last-call
Subject: RE: Opsdir
C-Tree" in RFC 6514).
Thanks.
Jeffrey
-Original Message-
From: Gyan Mishra
Sent: Friday, May 7, 2021 12:55 PM
To: Jeffrey (Zhaohui) Zhang
Cc: Lenny Giuliano ; Qin Wu ; bess
; draft-ietf-bess-mvpn-msdp-sa-interoperation.all
; last-call
; ops-dir
Subject: Re: [bess] Opsdir last ca
Hi Jingrong,
Please see zzh> below.
From: Xiejingrong (Jingrong)
Sent: Friday, May 7, 2021 8:19 AM
To: Jeffrey (Zhaohui) Zhang ; slitkows.i...@gmail.com;
bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: RE: [bess] Cross WG review request for draft-ietf-bier-evpn
[External Email. Be cautious
Hi John,
You're spot on with all the points below. I have submitted -07 to address them:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-mvpn-msdp-sa-interoperation-07.txt.
Thanks!
Jeffrey
-Original Message-
From: John Scudder via Datatracker
Sent: Friday, May 14, 2021 10:30 AM
To: T
Hi Benjamin,
Thanks for your review and comments. I have posted -08 revision.
Please see zzh> below.
-Original Message-
From: BESS On Behalf Of Benjamin Kaduk via Datatracker
Sent: Wednesday, May 19, 2021 9:25 PM
To: The IESG
Cc: Matthew Bocci ; manka...@cisco.com;
bess-cha...@ietf.or
Hi Scott,
Thanks for your review and comments/suggestions.
Yes I will change the SHOULD to MUST as you pointed out.
As for the complexity, unfortunately due to the nature of the tunnel
segmentation (if different tunnel technology/instantiation is needed in
different regions) the procedures are
Hi Satya,
That is part of the optional procedure to provide backwards compatibility. An
implementation would likely to have configuration controlling whether this
procedure is used or not.
For the origination of per-region I-PMSI routes, whether it is for the purpose
of backwards compatibility
Hi Gorry,
Thank you for your comments. I missed it hence the late response. Sorry about
that.
Please see zzh> below.
-Original Message-
From: Gorry Fairhurst via Datatracker
Sent: Monday, August 30, 2021 5:59 AM
To: tsv-...@ietf.org
Cc: bess@ietf.org; draft-ietf-bess-evpn-bum-procedure
...
Thanks.
Jeffrey
-Original Message-
From: Scott Bradner
Sent: Wednesday, September 8, 2021 3:44 PM
To: Jeffrey (Zhaohui) Zhang
Cc: ops-...@ietf.org; bess@ietf.org;
draft-ietf-bess-evpn-bum-procedure-updates@ietf.org; last-c...@ietf.org
Subject: Re: Opsdir last call review of
draf
: Tuesday, September 14, 2021 8:50 PM
To: Jeffrey (Zhaohui) Zhang ; last-c...@ietf.org;
IETF-Announce
Cc: ext-zzhang_i...@hotmail.com ;
martin.vigour...@nokia.com; bess-cha...@ietf.org;
draft-ietf-bess-evpn-bum-procedure-upda...@ietf.org; bess@ietf.org
Subject: Re: [bess] Last Call:
(Updates on
Hi Scott, Gorry, Paul,
I posted -10 revision to address some comments you posted. Thanks a lot!
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-bum-procedure-updates-10
Jeffrey
-Original Message-
From: iesg-secret...@ietf.org
Sent: Tuesday, August 24, 2021 10:33 AM
To: IETF-
hank Jeffrey
(Zhaohui Zhang) for excellent cooperation.
The following has raised some concerns for me.
1. Section 7 “Multi-homing Support” discusses two deployment scenarios:
* Multi-homed segments do not span different ACs or regions. In this
case the draft says that “a segmentatio
Hi Eric,
Thanks for your comments. Please see zzh> below.
-Original Message-
From: Éric Vyncke via Datatracker
Sent: Monday, October 18, 2021 7:34 AM
To: The IESG
Cc: draft-ietf-bess-evpn-bum-procedure-upda...@ietf.org; bess-cha...@ietf.org;
bess@ietf.org; ext-zzhang_i...@hotmail.com ;
Hi Scott,
Please see zzh> below.
-Original Message-
From: Scott Bradner via Datatracker
Sent: Monday, October 11, 2021 10:18 AM
To: ops-...@ietf.org
Cc: bess@ietf.org; draft-ietf-bess-evpn-bum-procedure-updates@ietf.org;
last-c...@ietf.org
Subject: Opsdir telechat review of draft-ie
Hi Roman,
Thanks for your review and comments. Please see zzh> below.
-Original Message-
From: Roman Danyliw via Datatracker
Sent: Tuesday, October 19, 2021 7:07 PM
To: The IESG
Cc: draft-ietf-bess-evpn-bum-procedure-upda...@ietf.org; bess-cha...@ietf.org;
bess@ietf.org; ext-zzhang_i..
Hi Murray, Ben,
Thanks for your review and comments.
Indeed the registry is the one to be created in the other draft. I will make
the text clearer in a revision.
Jeffrey
From: Murray S. Kucherawy
Sent: Thursday, October 21, 2021 3:42 AM
To: Benjamin Kaduk
Cc: The IESG ; ext-zzhang_i...@hotmai
Hi Ben,
Thanks for your review and comments. Let me first address the DISCUSS point
below and then follow up with another email on other points.
-Original Message-
From: Benjamin Kaduk via Datatracker
Sent: Thursday, October 21, 2021 1:50 AM
To: The IESG
Cc: draft-ietf-bess-evpn-bum-pr
ent: Thursday, October 21, 2021 11:08 PM
To: Jeffrey (Zhaohui) Zhang
Cc: The IESG ;
draft-ietf-bess-evpn-bum-procedure-upda...@ietf.org; bess-cha...@ietf.org;
bess@ietf.org; ext-zzhang_i...@hotmail.com
Subject: Re: Benjamin Kaduk's Discuss on
draft-ietf-bess-evpn-bum-procedure-updates-11: (with DIS
Hi Ben,
Text snipped to focus on outstanding issues. The draft posting window is not
open yet, so let me post a diff file here.
Please see zzh3> below.
-
(By the way, I see that one place in §3.3 changed from saying that the
route key for the Leaf A-D route is the route-typ
Hi,
draft-ietf-bess-bgp-multicast-controller is mainly about setting up multicast
trees (IP/MPLS/SR) in the underlay, though it can also be used to set up overly
multicast state in VRFs (e.g. as a replacement for MVPN, as discussed in
Section 2 "Alternative to BGP-MVPN").
In last IETF I mentio
Support.
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
> Sent: Monday, October 27, 2014 4:46 AM
> To: bess
> Cc: draft-ietf-l3vpn-orf-covering-prefi...@tools.ietf.org; bess ADs;
> draft-bonica-l3vpn-orf-covering-prefi...@tools.ietf.org
> Subject
As a co-author, I am not aware of IPRs related to this.
Jeffrey
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
> Sent: Thursday, December 04, 2014 11:30 AM
> To: bess@ietf.org
> Cc: draft-rosen-l3vpn...@tools.ietf.org; Eric Rosen
> Subject: [bes
Thanks, Thomas. The BESS version has been submitted:
http://www.ietf.org/internet-drafts/draft-ietf-bess-mvpn-bidir-ingress-replication-00.txt
Jeffrey
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
> Sent: Monday, January 12, 2015 6:44 AM
> To:
As co-author, I support the adoption, and I am not aware of relevant IPRs.
Jeffrey
> -Original Message-
> From: Martin Vigoureux [mailto:martin.vigour...@alcatel-lucent.com]
> Sent: Monday, January 26, 2015 4:47 AM
> To: bess@ietf.org
> Cc: draft-morin-bess-multicast-damp...@tools.ietf.or
Support.
Jeffrey
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
Hi Lucy,
Please see zzh> below.
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Lucy yong
Sent: Tuesday, September 01, 2015 1:35 PM
To: draft-ietf-bess...@tools.ietf.org
Cc: bess@ietf.org
Subject: [bess] comment on draft-ietf-bess-ir
Hi Authors,
The draft is well written. Some simper imp
y the child to include the RT for the new parent
> and the RT for the old parent for a while, and then remove the RT for the old
> parent later
That is actually not feasible. The updated route has the label allocated for
the new parent and should not be imported by the old parent.
Jef
Lucy,
Please see zzh2> below.
From: Lucy yong [mailto:lucy.y...@huawei.com]
Sent: Tuesday, September 01, 2015 3:48 PM
To: Jeffrey (Zhaohui) Zhang ;
draft-ietf-bess...@tools.ietf.org
Cc: bess@ietf.org
Subject: RE: [bess] comment on draft-ietf-bess-ir
Hi Jeffery,
Thank you for your quick re
015 4:08 PM
To: Jeffrey (Zhaohui) Zhang ;
draft-ietf-bess...@tools.ietf.org
Cc: bess@ietf.org
Subject: RE: [bess] comment on draft-ietf-bess-ir
From: Jeffrey (Zhaohui) Zhang [mailto:zzh...@juniper.net]
Sent: Tuesday, September 01, 2015 3:01 PM
To: Lucy yong;
draft-ietf-bess...@tools.ietf.org
it's better to have precise/hard rules on label allocation.
Jeffrey
From: Lucy yong [mailto:lucy.y...@huawei.com]
Sent: Wednesday, September 02, 2015 9:47 AM
To: Jeffrey (Zhaohui) Zhang ;
draft-ietf-bess...@tools.ietf.org
Cc: bess@ietf.org
Subject: RE: [bess] comment on draft-ietf-bess-ir
Hi Jef
1 - 100 of 254 matches
Mail list logo
