been allocated.
So to recap, we have no interest in or any need for remote next hops.
Yours Irrespectively,
John
-Original Message-
From: Susan Hares [mailto:sha...@ndzh.com]
Sent: Tuesday, February 03, 2015 6:13 AM
To: 'Ali Sajassi (sajassi)'; 'Russ White'; John E Drake; 'Rabadan
Russ,
Comments inline.
Yours Irrespectively,
John
-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Russ White
Sent: Monday, February 02, 2015 3:02 PM
To: Rabadan, Jorge (Jorge)
Cc: bess@ietf.org
Subject: Re: [bess] EVPN Draft Comments
If the
Russ,
Comments inline
Yours Irrespectively,
John
-Original Message-
From: Russ White [mailto:ru...@riw.us]
Sent: Monday, February 02, 2015 7:12 PM
To: John E Drake; 'Rabadan, Jorge (Jorge)'
Cc: bess@ietf.org
Subject: RE: [bess] EVPN Draft Comments
[JD] What RFC 7432
Russ,
I am under the impression that Adrian's email asked for comments on the
proposed change to section 6.3.
Yours Irrespectively,
John
-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Russ White
Sent: Monday, February 02, 2015 8:42 AM
To: bess@ietf.org
Tony,
The change you mention in your email below is editorial, clarifying what was
already supported in the encodings but not explicitly described.
The technical change is in the last paragraph and deals w/ VLAN Aware Bundle
service w/ VID translation. Previously the ingress PE translated
: Tuesday, February 03, 2015 12:25 AM
To: 'Russ White'; John E Drake; 'Rabadan, Jorge (Jorge)'
Cc: bess@ietf.org
Subject: RE: [bess] EVPN Draft Comments
Russ and John:
I have concerns about the issues Russ has raised as well as other concerns
regarding the EVPN. As I mentioned at the last IETF's
Sue,
Comments inline.
Yours Irrespectively,
John
-Original Message-
From: Susan Hares [mailto:sha...@ndzh.com]
Sent: Tuesday, February 03, 2015 7:28 AM
To: John E Drake; 'Russ White'; 'Rabadan, Jorge (Jorge)'
Cc: bess@ietf.org
Subject: RE: [bess] EVPN Draft Comments
John
, 2015 3:24 AM
To: John E Drake; Russ White; Rabadan, Jorge (Jorge)
Cc: bess@ietf.org
Subject: RE: [bess] EVPN Draft Comments
Hi Russ, as someone who was involved early on in the EVPN, I can assure you
that we had considered load-balancing as achieved via aliasing early on in the
process. John
: Russ White [mailto:ru...@riw.us]
Sent: Tuesday, February 03, 2015 7:17 AM
To: 'Ali Sajassi (sajassi)'; John E Drake; 'Rabadan, Jorge (Jorge)'
Cc: bess@ietf.org
Subject: RE: [bess] EVPN Draft Comments
Wrt this draft, the text is very clear as it has been implemented by
several
major
, 2015 7:17 AM
To: Ravi Shekhar; John E Drake
Cc: 'Rabadan, Jorge (Jorge)'; bess@ietf.org
Subject: RE: [bess] EVPN Draft Comments
The approach of A/B/C independently generating route to X only based
on local MAC learning works even if physical link failure detection is
not an option
Support
Yours Irrespectively,
John
-Original Message-
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
Sent: Wednesday, January 07, 2015 6:02 AM
To: bess@ietf.org
Cc: draft-rabadan-l2vpn-evpn-prefix-advertisem...@tools.ietf.org
Subject: [bess] Poll for
lead
to transient _duplicates_.
-Thomas
26/03/2015 20:05, John E Drake :
Weiguo,
I guess I wasn¹t clear. I think you draft, for the reasons I have
detailed, is a non-solution to a non-problem with tremendous
control plane cost.
Yours Irrespectively,
John
*From
Weiguo,
Snipped, comments inline.
Yours Irrespectively,
John
From: Haoweiguo [mailto:haowei...@huawei.com]
Sent: Monday, April 06, 2015 10:03 PM
To: John E Drake; Patrice Brissette (pbrisset)
Cc: Ali Sajassi (sajassi); bess@ietf.org
Subject: RE: [bess] Handshaking among PEs in an EVPN ES based
the EVPN routes are not time-stamped, you entire discussion of NTP
and PTP is completely irrelevant.
Yours Irrespectively,
John
From: John E Drake
Sent: Thursday, March 26, 2015 6:00 PM
To: 'Haoweiguo'; Patrice Brissette (pbrisset)
Cc: Ali Sajassi (sajassi); bess@ietf.org
Subject: RE: [bess
,
John
From: Haoweiguo [mailto:haowei...@huawei.com]
Sent: Wednesday, November 11, 2015 1:08 AM
To: Rabadan, Jorge (Jorge); saja...@cisco.com; John E Drake
Cc: bess@ietf.org
Subject: RE: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'
Jorge,
Understood, many thanks. Now that the default
Weiguo,
You're welcome.
Yours Irrespectively,
John
From: Haoweiguo [mailto:haowei...@huawei.com]
Sent: Wednesday, November 11, 2015 8:17 PM
To: John E Drake; Rabadan, Jorge (Jorge); saja...@cisco.com
Cc: bess@ietf.org
Subject: RE: [bess] One question about 'draft-ietf-bess-evpn-overlay-02
November 12, 2015 3:39 AM
> To: bess@ietf.org
> Subject: Re: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'
>
> HI John, Weiguo,
>
> John E Drake :
> >
> > It is needed in order to distinguish between an advertising node that
> > only supports no
ifies a feasible tunnel."
We hope this is satisfactory.
Yours Irrespectively,
John
> -Original Message-
> From: Thomas Morin [mailto:thomas.mo...@orange.com]
> Sent: Thursday, November 12, 2015 10:08 AM
> To: John E Drake; bess@ietf.org
> Cc: Eric Rosen
> Subject: Re:
Weiguo,
Comment inline.
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Haoweiguo
> Sent: Saturday, November 21, 2015 2:18 AM
> To: UTTARO, JAMES; John E Drake; EXT - thomas.mo...@orange.com; Lucy
> yong; Hende
No IPR
Yours Irrespectively,
John
> -Original Message-
> From: John E Drake
> Sent: Tuesday, January 12, 2016 8:24 AM
> To: 'Martin Vigoureux'; bess@ietf.org
> Cc: draft-mohanty-bess-evpn-df-elect...@tools.ietf.org
> Subject: RE: [bess] Poll for adoption: draft-mo
ng WG Last Call).
> >
> >Reviews are highly welcome anyway, in particular from people close to
> >the topic or implementations, and ideally from more than one person,
> >the best time being now or at least before the WG LC ends.
> >
> >We'll start the WG LC in a
Thomas,
E-TREE for EVPN (https://tools.ietf.org/html/draft-ietf-bess-evpn-etree-05)
will be GA this year. Root or leaf role can be defined on a port or VLAN
basis, and Single-Active and All-Active multi-homing are supported. E-TREE for
PBB-EVPN is on the roadmap.
Yours Irrespectively,
John
Thomas,
Comments inline.
Yours Irrespectively,
John
> -Original Message-
> From: Thomas Morin [mailto:thomas.mo...@orange.com]
> Sent: Wednesday, June 15, 2016 8:47 AM
> To: John E Drake; Rabadan, Jorge (Nokia - US); BESS; draft-ietf-bess-evpn-
> over...@tools.ietf.o
Jeffrey,
I don't think anyone would argue that the proper solution to per-ES mass
withdraw is to include the originating router's address in Ethernet AD and MAC
Advertisement routes and the only discussion is the best way to encode this
information.
Your suggestion of having an ingress PE use
Support. It provides a useful and much needed capability. Not aware of any
IPR.
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of thomas.mo...@orange.com
> Sent: Monday, June 20, 2016 8:44 AM
> To: bess@ietf.org
> Cc:
Support. I'm not aware of any undisclosed IPR.
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
> Sent: Tuesday, January 19, 2016 3:51 AM
> To: BESS; draft-ietf-bess-evpn-et...@tools.ietf.org
> Subject: [bess] WG Last
10:23 AM
To: John E Drake; IDR; BESS; draft-ietf-bess-evpn-over...@tools.ietf.org; Ali
Sajassi (sajassi); Rabadan, Jorge (Nokia - US);
draft-ietf-idr-tunnel-en...@tools.ietf.org
Subject: Re: [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps
John,
2016-05-18, John E Drake:
I
like to request that Jorge be the document shepherd for
this draft.
Yours Irrespectively,
John
From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Tuesday, May 24, 2016 3:05 AM
To: John E Drake; EXT - thomas.mo...@orange.com; IDR; BESS;
draft-ietf-bess-evpn-over...@tools.ietf.org
, leads me to the conclusion that the overlay draft should not be
tweaked to be in alignment with a future solution for encoding VNIs for
multicast.
Yours Irrespectively,
John
From: thomas.mo...@orange.com [mailto:thomas.mo...@orange.com]
Sent: Thursday, May 05, 2016 8:32 AM
To: John E Drake; IDR
Martin,
I support publishing this document as a Proposed Standard RFC and I'm not aware
of any undisclosed IPR.
Juniper supports VPWS all-active and single-active redundancy modes with
sub-second recovery on egress link failure.
Yours Irrespectively,
John
> -Original Message-
>
Thomas and Jorge,
Snipped, comments inline.
Yours Irrespectively,
John
> >
> >draft-ietf-bess-evpn-overlay (see section 9) relies on the BGP
> >Encapsulation extended to encode the tunnel encap to use for BUM
> >traffic, but contrary to other E-VPN routes, relies on the Ethernet Tag
> >field
FYI
Yours Irrespectively,
John
-Original Message-
From: John E Drake [mailto:jdr...@juniper.net]
Sent: Monday, May 09, 2016 9:54 AM
To: EXT - thomas.mo...@orange.com; Rabadan, Jorge (Nokia - US);
draft-ietf-bess-evpn-v...@ietf.org; EXT Ali Sajassi (sajassi); EXT Sami Boutros
Cc: BESS
Thomas,
I'm sorry for the tardy response. I support the publication of this draft as
it describes a de-facto industry standard control plane for NVO3 networks;
Juniper has implemented it on multiple platforms. I'm not aware of any IPR.
Yours Irrespectively,
John
> -Original
Thomas,
Not surprisingly I support the adoption of this draft. Here is our IPR
disclosure for it: https://datatracker.ietf.org/ipr/2942/
Yours Irrespectively,
John
> -Original Message-
> From: Thomas Morin [mailto:thomas.mo...@orange.com]
> Sent: Tuesday, January 31, 2017 9:58 AM
>
And I'm not aware of any IPR
Yours Irrespectively,
John
> -Original Message-
> From: John E Drake
> Sent: Monday, February 6, 2017 4:45 PM
> To: 'Martin Vigoureux' <martin.vigour...@nokia.com>; BESS <bess@ietf.org>
> Subject: RE: [bess] WG Last Call for draft
Support. Juniper has had support for this draft for several years and has
demonstrated interoperability with Nokia and Cisco on numerous occasions
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
> Sent:
Sami,
Snipped, comment inline
Yours Irrespectively,
John
> >
> >> Ethernet Tag ID 32-bit field MUST be set to the 24-bit VPWS service
> >> instance
> identifier value."
> >
> >
> >
> >Ok, but you still didn’t mention how the 24-bit value is to be aligned in
> >the 32-
> bit field. I’m
Support and I'm not aware of any IPR
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
> Sent: Monday, February 13, 2017 5:08 PM
> To: BESS
> Subject: [bess] WG Last Call for
Support and I'm not aware of any undisclosed IPR.
Yours Irrespectively,
John
> -Original Message-
> From: Martin Vigoureux [mailto:martin.vigour...@nokia.com]
> Sent: Monday, March 6, 2017 6:55 AM
> To: bess@ietf.org
> Cc: draft-mackie-bess-nsh-bgp-control-pl...@ietf.org
> Subject: Call
Support. A truly useful document that has already been used by a multiplicity
of other drafts.
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of John Scudder
> Sent: Friday, October 6, 2017 2:39 PM
> To: i...@ietf.org
> Cc:
Martin,
I am not aware of any IPR that applies to this draft.
Yours Irrespectively,
John
> -Original Message-
> From: Martin Vigoureux [mailto:martin.vigour...@nokia.com]
> Sent: Monday, September 25, 2017 5:43 AM
> To: bess@ietf.org
> Cc: draft-drake-bess-datacenter-gate...@ietf.org
Alvaro,
Comments inline.
Yours Irrespectively,
John
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Alvaro Retana
Sent: Monday, December 4, 2017 4:49 PM
To: bess-cha...@ietf.org
Cc: EXT - thomas.mo...@orange.com ; bess@ietf.org
Subject: [bess] AD Review of
Thomas,
I completely agree w/ your email, below.
Yours Irrespectively,
John
> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
> Sent: Friday, December 15, 2017 5:42 AM
> To: Fedyk, Don ; Marco Marzetti
>
>
erstand.
> >
> > OK, I will remove it in the next rev.
> >
> > Cheers,
> > Ali
> >
> > Best,
> >
> > -Thomas
> >
> >
> >
> >
> > -Original Message-
> > > From: John E Drake [mailto:jdr...@jun
Support, I’m not aware of any undisclosed IPR
Yours Irrespectively,
John
From: BESS On Behalf Of Bocci, Matthew (Nokia - GB)
Sent: Thursday, May 17, 2018 6:24 AM
To: bess@ietf.org
Cc: draft-sajassi-bess-evpn-virtual-eth-segm...@ietf.org
Subject: [bess] WG Adoption and
-evpn-igmp-mld-proxy].
Yours Irrespectively,
John
-Original Message-
From: stephane.litkow...@orange.com
Sent: Tuesday, June 5, 2018 11:09 AM
To: John E Drake
Subject: RE: IGMP Proxy
Hi John,
Thanks for the information.
It helps.
However, that would have been better to have
Support
Yours Irrespectively,
John
> -Original Message-
> From: Martin Vigoureux [mailto:martin.vigour...@nokia.com]
> Sent: Thursday, January 11, 2018 5:12 AM
> To: bess@ietf.org
> Cc: draft-lin-bess-evpn-irb-mc...@ietf.org
> Subject: Call for adoption: draft-lin-bess-evpn-irb-mcast
>
Hi,
The HRW DF election draft defines a new extended community, the DF Election
Extended Community
(https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-03#section-7),
which contains a DF election type registry. Why don’t we define a value for
AC-based DF election and have the PEs
Support. I'm not aware of any undisclosed IPR.
Yours Irrespectively,
John
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Wednesday, August 8, 2018 10:04 AM
To: bess@ietf.org
Subject: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05
Hello working group,
Support. I'm not aware of any undisclosed IPR.
Yours Irrespectively,
John
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Wednesday, August 8, 2018 9:38 AM
To: bess@ietf.org
Subject: [bess] WG adoption poll and IPR poll for
draft-sajassi-bess-evpn-per-mcast-flow-df-election
Hi
Support, not aware of any IPR.
Yours Irrespectively,
John
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Tuesday, September 4, 2018 3:29 AM
To: bess@ietf.org
Subject: [bess] WG adoption poll for draft-malhotra-bess-evpn-unequal-lb-04
Hi WG,
This email begins a two-week poll for
I’m not aware of any IPR
Yours Irrespectively,
John
From: BESS On Behalf Of Bocci, Matthew (Nokia - GB)
Sent: Monday, April 9, 2018 9:23 AM
To: draft-sajassi-bess-evpn-vpws-...@ietf.org; bess@ietf.org
Subject: [bess] WG adoption and IPR poll for
.
Yours Irrespectively,
John
From: Wen Lin
Sent: Friday, April 6, 2018 9:26 AM
To: Sandy Breeze <sandy.bre...@eu.clara.net>; Ali Sajassi (sajassi)
<saja...@cisco.com>; UTTARO, JAMES <ju1...@att.com>; John E Drake
<jdr...@juniper.net>; Rabadan, Jorge (Nokia - US/Mou
Satya,
Comment inline.
Yours Irrespectively,
John
[John] Wouldn’t it be better to have this draft define a bit in the Multicast
Flags extended community
Support, not aware of any undisclosed IPR.
Yours Irrespectively,
John
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Monday, March 26, 2018 10:21 AM
To: bess@ietf.org
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework
Hello working group,
Ali,
I don't mean to quibble but your option A also requires all PEs to be upgraded.
However, it's both a more mainstream upgrade and a better solution than the
Sandy/Satya proposal.
Also, as we discussed last week, the SMET processing already includes what
Sandy/Satya proposal wants to do.
Support. Juniper has been shipping an implementation of this draft for quite
some time and our customers seem to find the draft to be quite useful.
Yours Irrespectively,
John
From: BESS On Behalf Of Bocci, Matthew (Nokia - GB)
Sent: Wednesday, March 28, 2018 8:50 AM
Hi,
Comments inline
Yours Irrespectively,
John
From: Sandy Breeze <sandy.bre...@eu.clara.net>
Sent: Thursday, March 22, 2018 1:42 PM
To: John E Drake <jdr...@juniper.net>; Rabadan, Jorge (Nokia - US/Mountain
View) <jorge.raba...@nokia.com>; Eric Rosen <ero...@junipe
Mankamana,
Good catch! (I was remarkably provincial in my initial titles.)
Yours Irrespectively,
John
From: Mankamana Mishra (mankamis)
Sent: Thursday, March 22, 2018 4:27 PM
To: Rabadan, Jorge (Nokia - US/Mountain View)
Cc: Ali Sajassi (sajassi)
I don't think that's a good idea because depending upon their position in the
stack, these labels may not be at the bottom of the stack.
Yours Irrespectively,
John
> -Original Message-
> From: BESS On Behalf Of Zhuangshunwan
> Sent: Monday, October 15, 2018 9:02 PM
> To: Jakob Heitz
Jorge,
The other possibility for this case is for each PE to advertise a Per EVI
Ethernet A-D route for only those EVIs for which it would become DF if the
current DF were to fail.
Yours Irrespectively,
John
From: BESS On Behalf Of Rabadan, Jorge (Nokia -
US/Mountain View)
Sent: Tuesday,
Hi,
Comment inline
Yours Irrespectively,
John
From: BESS On Behalf Of Alexander Vainshtein
Sent: Wednesday, October 24, 2018 11:57 AM
To: Yutianpeng (Tim)
Cc: bess@ietf.org; draft-wang-bess-evpn-control-word.auth...@ietf.org;
Wanghaibo (Rainsword)
Subject: Re: [bess] A question regarding
Patrice,
I think it is much cleaner to treat the attachment of a set of L2GW PEs to an
L2 network as a set of individual ESes, one per L2GW PE, as Jorge suggests.
This is because a remote PE accesses different parts of the L2 network through
different L2GW PEs; i.e., to a remote PE the
Hi,
I agree w/ Jorge's proposal.
Yours Irrespectively,
John
> -Original Message-
> From: BESS On Behalf Of Rabadan, Jorge (Nokia -
> US/Mountain View)
> Sent: Monday, November 5, 2018 4:45 AM
> To: bess@ietf.org; draft-brissette-bess-evpn-l2gw-proto.auth...@ietf.org
> Subject: [bess]
Comment inline
Sent from my iPhone
On Dec 18, 2018, at 12:33 PM, Neeraj Malhotra
mailto:neeraj.i...@gmail.com>> wrote:
Hi,
Very solid and understandable. Couple of minor comments [NM]:
Section 2.1: Layer-2 devices are particularly susceptible to forwarding loops
because of the broadcast
Support, Juniper has supported this feature for an eternity, not aware of any
IPR
Yours Irrespectively,
John
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of
stephane.litkow...@orange.com
Sent: Monday, December 3, 2018 5:43 AM
To: bess@ietf.org
Subject: [bess] WGLC, IPR and
Wim,
The subject draft was designed w/ NSH in mind. We added an MPLS representation
of the NSH later, which is the subject of the first draft you referenced, below.
The way the subject draft is written, the representation of the NSH and the
type of transport tunnel can change on a hop-by-hop
Andy,
That sounds right.
Yours Irrespectively,
John
From: Andrew G. Malis
Sent: Friday, January 25, 2019 6:32 PM
To: John E Drake
Cc: Henderickx, Wim (Nokia - BE/Antwerp) ;
stephane.litkow...@orange.com; bess@ietf.org; bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation
Andy,
We’ll add it to the next revision. Thanks for your help.
Yours Irrespectively,
John
From: Andrew G. Malis
Sent: Sunday, January 27, 2019 11:48 AM
To: John E Drake
Cc: Henderickx, Wim (Nokia - BE/Antwerp) ;
stephane.litkow...@orange.com; bess@ietf.org; bess-cha...@ietf.org
Subject: Re
Support, not aware of any IPR
Yours Irrespectively,
John
From: stephane.litkow...@orange.com
Sent: Tuesday, March 5, 2019 3: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 for
Support
Yours Irrespectively,
John
From: mitesh kanjariya
Sent: Monday, March 18, 2019 4:49 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 adoption and IPR poll for
Not aware of any IPR
Yours Irrespectively,
John
From: mitesh kanjariya
Sent: Monday, March 18, 2019 4:49 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 adoption and IPR poll for
Support, not aware of any IPR
Yours Irrespectively,
John
From: Bocci, Matthew (Nokia - GB)
Sent: Wednesday, February 6, 2019 5: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
This email
Support. I'm not aware of any IPR.
Yours Irrespectively,
John
From: stephane.litkow...@orange.com
Sent: Monday, February 18, 2019 10:53 AM
To: draft-rabadan-sajassi-bess-evpn-ipvpn-interwork...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption and IPR poll for
I'm not aware of any IPR
Yours Irrespectively,
John
Juniper Internal
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Wednesday, May 22, 2019 9:55 AM
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WG adoption poll and IPR poll for draft-boutros-bess-evpn-geneve
Hi,
Hi,
We can't time-out an attribute, we would have to time-out the SFPR w/ which it
is associated. However, I don't think we should do that.
Rather, I think what we should do is indicate that at any point in time an SFF
selects its next hop from the intersection of the set of next hop RDs
Support. I'm not aware of any undisclosed IPR.
Yours Irrespectively,
John
Juniper Internal
From: BESS On Behalf Of stephane.litkow...@orange.com
Sent: Monday, June 17, 2019 4:53 AM
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WGLC, IPR and implementation poll for
Hi,
I agree w/ both Jorge and Krzysztof. All we need is a new DF Election
capability, port active load balancing, and a description of how each of the
defined DF elections is modified. For HRW, RFC 8584 already describes
computing a 32 bit CRC over the concatenation of Ethernet Tag and ESI
Support, I'm not aware of any IPR.
Yours Irrespectively,
John
Juniper Business Use Only
From: Bocci, Matthew (Nokia - GB)
Sent: Wednesday, September 4, 2019 4:36 AM
To: draft-keyupate-bess-evpn-virtual-...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption and IPR poll for
om> | phone: +1 613
254 4814
On Tue, Nov 12, 2019 at 10:30 AM John E Drake
mailto:40juniper@dmarc.ietf.org>>
wrote:
I agree
Sent from my iPhone
> On Nov 12, 2019, at 3:10 PM, Rabadan, Jorge (Nokia - US/Mountain View)
> mailto:jorge.raba...@nokia.com>> wrote:
>
>
This should be rejected as well.
Sent from my iPhone
> On Nov 12, 2019, at 5:32 PM, RFC Errata System
> wrote:
>
> The following errata report has been submitted for RFC8584,
> "Framework for Ethernet VPN Designated Forwarder Election Extensibility".
>
>
I agree
Sent from my iPhone
> On Nov 12, 2019, at 3:10 PM, Rabadan, Jorge (Nokia - US/Mountain View)
> wrote:
>
> Hi,
>
> I don't understand why this erratum was filed.
> "Broadcast Domain" is the correct term used in RFC7432 and all the EVPN
> documents.
> It should be rejected.
>
>
Support and not aware of any IPR
Yours Irrespectively,
John
Juniper Business Use Only
From: Bocci, Matthew (Nokia - GB)
Sent: Wednesday, February 26, 2020 6:29 AM
To: draft-ietf-bess-datacenter-gate...@ietf.org; bess@ietf.org
Subject: REMINDER Re: [bess] WG Last Call, IPR and Implementation
Support and not aware of any IPR
Yours Irrespectively,
John
Juniper Business Use Only
From: BESS On Behalf Of slitkows.i...@gmail.com
Sent: Wednesday, February 26, 2020 9:25 AM
To: 'BESS'
Cc: bess-cha...@ietf.org
Subject: [bess] WGLC, IPR and implementation poll for
Support, not aware of any IPR
Yours Irrespectively,
John
Juniper Business Use Only
From: slitkows.i...@gmail.com
Sent: Friday, January 17, 2020 3:56 AM
To: bess@ietf.org; draft-ietf-bess-evpn-unequal-lb.auth...@ietf.org
Cc: bess-cha...@ietf.org
Subject: WGLC , IPR and implementation poll for
Much better
Yours Irrespectively,
John
Juniper Business Use Only
From: BESS On Behalf Of Rabadan, Jorge (Nokia -
US/Mountain View)
Sent: Tuesday, May 19, 2020 4:09 PM
To: slitkows.i...@gmail.com; bess@ietf.org
Cc: Prabhu, Vinod (Nokia - CA/Ottawa) ;
bess-cha...@ietf.org; Dornon, Olivier
Ben,
Perhaps, although AFAIK the three values defined in RFC 4364 have not been
supplemented since it was published in 2006.
Yours Irrespectively,
John
Juniper Business Use Only
> -Original Message-
> From: Benjamin Kaduk
> Sent: Thursday, August 20, 2020 9:49 AM
> To:
Ben,
An RD is encoded using the same format as an extended community but it isn't an
extended community. Rather, it is actually part of the NLRI. The first octet
is always zero whereas the first octet of an SFIR Pool Identifier extended
community will always be non-zero (TBD6).
Yours
Hi,
I also agree with Ali. Eric specifically included the Tunnel Encapsulation
Extended Community in his draft at our request in order to support RFC 8365.
I.e., the draft that became RFC 8365 initially used the Tunnel Encapsulation
Extended Community defined in RFC 5512 and pre-dated by
Support, and I'm not aware of any IPR
Yours Irrespectively,
John
Juniper Business Use Only
From: BESS On Behalf Of slitkows.i...@gmail.com
Sent: Tuesday, June 23, 2020 8:14 AM
To: bess@ietf.org
Subject: [bess] WG adoption and IPR poll for
draft-dunbar-bess-bgp-sdwan-usage-07
[External
Support, and not aware of any IPR
Yours Irrespectively,
John
Juniper Business Use Only
From: Bocci, Matthew (Nokia - GB)
Sent: Monday, June 15, 2020 6:56 AM
To: draft-ietf-bess-evpn-oam-req-fr...@ietf.org; bess@ietf.org
Subject: WG Last Call and IPR Poll for
Support and not aware of any IPR
Yours Irrespectively,
John
Juniper Business Use Only
From: slitkows.i...@gmail.com
Sent: Monday, July 13, 2020 7:46 AM
To: bess@ietf.org; draft-ietf-bess-evpn-gen...@ietf.org
Cc: bess-cha...@ietf.org; 'idr@ietf. org'
Subject: WGLC, IPR and implementation
Support and I'm not aware of any IPR
Yours Irrespectively,
John
From: Bocci, Matthew (Nokia - GB)
Sent: Wednesday, December 9, 2020 4: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
[External Email.
Support, not aware of any IPR
Yours Irrespectively,
John
Juniper Business Use Only
From: Bocci, Matthew (Nokia - GB)
Sent: Monday, January 4, 2021 6:13 AM
To: bess@ietf.org; draft-ietf-bess-evpn-vpws-...@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG Last Call, IPR and Implementation Poll for
Support and I'm not aware of any IPR.
Yours Irrespectively,
John
Juniper Business Use Only
From: BESS On Behalf Of slitkows.i...@gmail.com
Sent: Monday, January 18, 2021 3:58 AM
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WG Last Call, IPR and Implementation Poll for
Thanks!
Yours Irrespectively,
John
Juniper Business Use Only
> -Original Message-
> From: Benjamin Kaduk
> Sent: Wednesday, June 9, 2021 1:26 PM
> To: Ali Sajassi (sajassi)
> Cc: The IESG ; draft-ietf-bess-evpn-inter-subnet-
> forward...@ietf.org; bess-cha...@ietf.org;
Ben,
Thanks for your help. I think Ali will add the text from Amanda in the next
published version of the draft.
Yours Irrespectively,
John
Juniper Business Use Only
> -Original Message-
> From: Benjamin Kaduk
> Sent: Wednesday, June 9, 2021 1:28 PM
> To: John E Drak
Excellent, thanks so much for your help on this.
Yours Irrespectively,
John
Juniper Business Use Only
> -Original Message-
> From: Gyan Mishra
> Sent: Tuesday, May 18, 2021 4:28 PM
> To: Lars Eggert
> Cc: General Area Review Team ; bess@ietf.org; draft-ietf-
>
Bruno,
I had suggested:
"The value field in the link bandwidth EC is to be treated as a 6 octet
unsigned integer and it is the provider's responsibility to encode it
consistently across all of the PEs attached to a given ES. So, for example, if
the provider wanted the EC to represent
...@orange.com
Sent: Thursday, May 6, 2021 10:06 AM
To: John E Drake
Cc: slitkows.i...@gmail.com; bess@ietf.org; Neeraj Malhotra
Subject: RE: [bess] New short WGLC for draft-ietf-bess-evpn-unequal-lb
[External Email. Be cautious of content]
John,
> It's *not* all egress PEs, it's only the mu
1 - 100 of 134 matches
Mail list logo