Re: [bess] Request discussion on Cumulative Link Bandwidth Draft

The link bandwidth community has been implemented by Cisco and deployed by our customers for several years. Polarization of flows in multipath is a well known problem, but it hasn't deterred people from using it. Regards, Jakob. From: BESS On Behalf Of Gyan Mishra Sent: Tuesday, May 25, 2021

Re: [bess] WG Adoption and IPR Poll for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03

I also believe that a table of conforming implementations is not appropriate in an RFC, as it is forever changing as software is upgraded. What is however appropriate is a list of test cases that must be passed in order to claim interoperability. Claiming that a session comes up is not good

Re: [bess] [Idr] IDR WG last call for draft-ietf-idr-bgp-ext-com-registry-01 (3/11 to 3/25/2021)

Makes sense. Support. Regards, Jakob. From: Idr On Behalf Of Susan Hares Sent: Thursday, March 11, 2021 4:12 AM To: i...@ietf.org; bess@ietf.org Subject: [Idr] IDR WG last call for draft-ietf-idr-bgp-ext-com-registry-01 (3/11 to 3/25/2021) This begins a 2 week WG last call for

Re: [bess] [Idr] Type 1 RD for Pure IPv6 network -- EVPN

n IPv6 only AS. However, there is nothing precluding you from using an IPv4 address if you are uncomfortable. Thanks, Acee From: BESS mailto:bess-boun...@ietf.org>> on behalf of "Jakob Heitz (jheitz)" mailto:40cisco@dmarc.ietf.org>> Date: Thursday, February 4, 2021

Re: [bess] [Idr] Type 1 RD for Pure IPv6 network -- EVPN

RFC 6286 already updates RFC 4271. Basically, RID is not unique. (ASN,RID) is unique. The only limitation on RID is that RID != 0. Regards, Jakob. From: Gyan Mishra Sent: Wednesday, February 3, 2021 9:42 PM To: Jakob Heitz (jheitz) Cc: Muthu Arul Mozhi Perumal ; TULASI RAM REDDY ; bess

Re: [bess] [Idr] Type 1 RD for Pure IPv6 network -- EVPN

Syntactic correctness means that the BGP Identifier field represents a valid unicast IP host address. Gyan> I do see that verbiage in section 6.2 If the BGP Identifier field of the OPEN message is syntactically incorrect, then the Error Subcode MUST be set to Bad BGP

Re: [bess] [Idr] Type 1 RD for Pure IPv6 network -- EVPN

Why preclude RFC 6286 ? Regards, Jakob. From: Idr On Behalf Of Muthu Arul Mozhi Perumal Sent: Tuesday, February 2, 2021 9:21 PM To: Gyan Mishra Cc: TULASI RAM REDDY ; bess@ietf.org; i...@ietf.org Subject: Re: [Idr] [bess] Type 1 RD for Pure IPv6 network -- EVPN Hi Gyan, Please see inline..

Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-evpn-irb-extended-mobility-01

I support. Regards, Jakob. From: BESS On Behalf Of slitkows.i...@gmail.com Sent: Monday, January 18, 2021 12:58 AM To: bess@ietf.org Cc: bess-cha...@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-evpn-irb-extended-mobility-01 This email starts a

Re: [bess] [Idr] Type 1 RD for Pure IPv6 network -- EVPN

Note that the BGP identifier is not guaranteed to be unique across ASes, only within a single AS. Regards, Jakob. From: BESS On Behalf Of Gyan Mishra Sent: Friday, January 29, 2021 1:56 PM To: Muthu Arul Mozhi Perumal Cc: TULASI RAM REDDY ; bess@ietf.org; i...@ietf.org Subject: Re: [bess]

Re: [bess] WG adoption and IPR poll for draft-mohanty-bess-weighted-hrw-01

Support. Regards, Jakob. From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Wednesday, December 9, 2020 1:23 AM To: bess@ietf.org Cc: draft-mohanty-bess-weighted-...@ietf.org Subject: [bess] WG adoption and IPR poll for draft-mohanty-bess-weighted-hrw-01 Hello, This email begins a

Re: [bess] WG Adoption and IPR all for draft-parekh-bess-mvpn-evpn-sr-p2mp-02

Support. Regards, Jakob. From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Monday, November 2, 2020 4:42 AM To: bess@ietf.org; draft-parekh-bess-mvpn-evpn-sr-p...@ietf.org Subject: [bess] WG Adoption and IPR all for draft-parekh-bess-mvpn-evpn-sr-p2mp-02 Hello, This email begins a

Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-oam-req-frmwk-02

I support the draft for standards track. Regards, Jakob. From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Monday, June 15, 2020 3:56 AM To: draft-ietf-bess-evpn-oam-req-fr...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-oam-req-frmwk-02

Re: [bess] WG Last Call and Implementation Poll for draft-ietf-bess-rfc5549revision-00

Support. Regards, Jakob. From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Monday, January 6, 2020 9:53 AM To: bess@ietf.org Subject: [bess] WG Last Call and Implementation Poll for draft-ietf-bess-rfc5549revision-00 This email starts a two weeks Working Group Last Call on

Re: [bess] WG Adoption and IPR Poll for draft-litkowski-bess-rfc5549revision-00

I support adoption. Regards, Jakob. From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Wednesday, November 27, 2019 4:37 AM To: bess@ietf.org Cc: bess-cha...@ietf.org Subject: [bess] WG Adoption and IPR Poll for draft-litkowski-bess-rfc5549revision-00 Hello, This email begins a

Re: [bess] WG adoption poll for draft-sajassi-bess-evpn-mvpn-seamless-interop

Support. Regards, Jakob. From: BESS On Behalf Of slitkows.i...@gmail.com Sent: Monday, October 28, 2019 3:10 AM To: bess@ietf.org Cc: bess-cha...@ietf.org Subject: [bess] WG adoption poll for draft-sajassi-bess-evpn-mvpn-seamless-interop Hello, This email begins a two-weeks WG adoption poll

Re: [bess] WG adoption and IPR poll for draft-dawra-bess-srv6-services-02

Support. Regards, Jakob. From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Friday, September 27, 2019 4:00 AM To: draft-dawra-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG adoption and IPR poll for draft-dawra-bess-srv6-services-02 Hello, This email begins a two-weeks

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-igmp-mld-proxy

Support. Regards, Jakob. From: BESS On Behalf Of stephane.litkow...@orange.com Sent: Monday, June 17, 2019 1:53 AM To: bess@ietf.org Cc: bess-cha...@ietf.org Subject: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-igmp-mld-proxy Hello Working Group, This email starts a

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

bottom, regardless of any BOS bit on our precious label. Regards, Jakob. -Original Message- From: Acee Lindem (acee) Sent: Monday, October 22, 2018 7:58 AM To: stephane.litkow...@orange.com; Ali Sajassi (sajassi) ; Jakob Heitz (jheitz) ; Zhuangshunwan ; BESS Subject: Re: [bess] Encoding

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

How about: The lower order 4 bits SHOULD be sent as 0 and ignored on receipt. Regards, Jakob. -Original Message- From: Zhuangshunwan Sent: Monday, October 15, 2018 6:02 PM To: Jakob Heitz (jheitz) ; BESS Subject: RE: Encoding a 20 bit label in a 24 bit field. It is good to make

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

We have proposed the following erratum for RFC 7432. Opinions? Regards, Jakob. -Original Message- From: RFC Errata System Sent: Friday, October 12, 2018 12:37 PM To: Ali Sajassi (sajassi) ; raggarw...@yahoo.com; nabil.n.bi...@verizon.com; aisaa...@bloomberg.net; utt...@att.com;

Re: [bess] Working Group Last Call on draft-ietf-mpls-rfc3107bis

Support. Thanks, Jakob. > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Loa Andersson > Sent: Tuesday, April 04, 2017 5:33 AM > To: m...@ietf.org; i...@ietf.org; BESS > Cc: ; idr-cha...@ietf.org; >

Re: [bess] Poll for adoption: draft-boutros-bess-vxlan-evpn-01

I support the document. Belatedly :( Thanks, Jakob. > On Aug 16, 2016, at 5:23 AM, Thomas Morin wrote: > > Hi everyone, > > As announced during Berlin meeting, considering the small support base, this > document is not adopted. > > We will consider doing a call for

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

I support this document. I am not aware of IPR relevant to this document. Thanks, Jakob. > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of thomas.mo...@orange.com > Sent: Monday, June 13, 2016 5:26 AM > To: BESS > Cc:

[bess] New Version Notification for draft-heitz-bess-evpn-option-b-00.txt

A new version of I-D, draft-heitz-bess-evpn-option-b-00.txt has been successfully submitted by Jakob Heitz and posted to the IETF repository. Name: draft-heitz-bess-evpn-option-b Revision: 00 Title: Multi-homing in EVPN with Inter-AS Option B Document date: 2016-06-29

Re: [bess] draft-sajassi-bess-evpn-l3vpn- multihoming-00.txt

The point is that the CE does not realize that it is multihomed. The access node implements the multihoming, but the CE has only one BGP session and one interface. The APE-SPE connections is an ethernet with the same ESI towards SPE1 and SPE2 The SPEs talk EVPN, using route type 5 to implement an