I support adoption.
Acee
> On Oct 5, 2023, at 06:45, Matthew Bocci (Nokia)
> wrote:
>
> WG
>
> This email starts a one-week WG adoption poll for
> draft-ietf-bess-bgp-sdwan-uasge-16 [1]
>
> A little bit of history: A previous version was adopted, completed WG last
> call, and
I also support merger of the four documents with identification of common
procedures.
Thanks,
Acee
> On Aug 6, 2023, at 21:03, Jeff Tantsura wrote:
>
> As co-author I support the merge of the documents proposed, please do provide
> any objections you might have.
>
> Cheers,
> Jeff
>
>> On
ussion of why the algorithm provides a
good distribution of traffic this reference should be accompanied with text
explaining how these benefits extend to individual multicast flows.
Thanks,
Acee
>
> Please let me know if you want only reference to be given or content to be
> copi
Call comments that you receive, and strive to
resolve them through discussion or by updating the draft.
Document: draft-ietf-bess-evpn-per-mcast-flow-df-election-09
Reviewer: Acee Lindem
Review Date: 07/20/2023
IETF LC End Date: N/A
Intended Status: Standards Track
Summary:
This document
Hi Jeffrey,
Thanks for addressing my comments. See some comments inline.
From: Jeffrey Zhang
Date: Monday, November 28, 2022 at 9:09 AM
To: Acee Lindem , "draft-ietf-bess-evpn-irb-mc...@ietf.org"
, Routing ADs
Cc: Routing Directorate , "bess@ietf.org"
Subject: RE: Rout
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of "Stephane Litkowski (slitkows)"
Date: Monday, October 10, 2022 at 4:40 AM
To: "bess-cha...@ietf.org" , "bess@ietf.org"
Subject: [bess] WG adoption poll and IPR poll for
draft-sajassi-bess-evpn-ac-aware-bundling
Hello,
This email
I’ve reread the draft and support publication.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Monday, January 31, 2022 at 9:00 AM
To: "draft-ietf-bess-evpn-fast-df-recov...@ietf.org"
, "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: [bess] WGLC, IPR and
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Tuesday, September 7, 2021 at 8:42 AM
To: "bess@ietf.org"
Cc: "draft-mohanty-bess-ebgp-...@ietf.org"
Subject: [bess] WG adoption poll and IPR poll for
draft-mohanty-bess-ebgp-dmz-03 [1].
Hello,
There are a number of drafts that were waiting years on the IDR tunnel Encap
draft – they will all be published together in this cluster:
https://www.rfc-editor.org/cluster_info.php?cid=C349
Thanks,
Acee
From: BESS on behalf of Gyan Mishra
Date: Saturday, April 24, 2021 at 1:14 PM
To: John
I just read the document and it seems reasonable. I support publication.
Thanks,
Acee
From: Idr on behalf of Susan Hares
Date: Thursday, March 11, 2021 at 7:12 AM
To: IDR List , "bess@ietf.org"
Subject: [Idr] IDR WG last call for draft-ietf-idr-bgp-ext-com-registry-01
(3/11 to 3/25/2021)
Hi Gyan,
Agree with Jakob. There is no reason for the BGP Identifier to be a unique IPv4
address. Consider an IPv6 only AS. However, there is nothing precluding you
from using an IPv4 address if you are uncomfortable.
Thanks,
Acee
From: BESS on behalf of "Jakob Heitz (jheitz)"
Date:
Hi Ali,
This should be updated automatically if the chairs update the “Replaced by”
meta data for
https://datatracker.ietf.org/doc/draft-malhotra-bess-evpn-irb-extended-mobility/
BTW, I support publication.
Thanks,
Acee
From: BESS on behalf of "Ali Sajassi (sajassi)"
Date: Tuesday,
Hi Stephane, et al,
I did another quick read of the draft and I support publication. I think it
would be good to state in the introduction which sections of the draft our
normative and which are informative.
Thanks,
Acee
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Monday, January
t-mohanty-bess-weighted-hrw-01
Resent-From:
Resent-To: , , Acee Lindem
, , John E Drake
Resent-Date: Tuesday, January 5, 2021 at 11:39 AM
Hi WG
Thanks to those who have already read and commented on the draft.
I would like to see a few more responses before moving this forward, so I will
extend th
To: "bess@ietf.org"
Cc: "draft-mohanty-bess-weighted-...@ietf.org"
Subject: REMINDER: WG adoption and IPR poll for
draft-mohanty-bess-weighted-hrw-01
Resent-From:
Resent-To: , , Acee Lindem
, , John E Drake
Resent-Date: Tuesday, January 5, 2021 at 11:39 AM
Hi WG
Thanks
ss-weighted-hrw-01
Resent-From:
Resent-To: , , Acee Lindem
, , John E Drake
Resent-Date: Wednesday, December 9, 2020 at 4:22 AM
Hello,
This email begins a two-week WG adoption poll for
draft-mohanty-bess-weighted-hrw-01 [1].
Please review the draft and post any comments to the BESS working gr
Hi Linda, et al, +BESS,
Isn’t this draft under the auspices of the BESS charter?
Thanks,
Acee
From: Idr on behalf of Linda Dunbar
Date: Tuesday, November 10, 2020 at 6:02 PM
To: Jie Dong , IDR List
Cc: "idr-cha...@ietf.org"
Subject: Re: [Idr] IETF 109 draft idr agenda
Jimmy and IDR chairs,
Hi Erik,
On 8/17/20, 7:32 AM, "Acee Lindem (acee)" wrote:
Hi Erik,
On 8/16/20, 7:50 PM, "BESS on behalf of Erik Kline via Datatracker"
wrote:
Erik Kline has entered the following ballot position for
draft-ietf-bess-rfc5549revision-04: No Obj
Hi Erik,
On 8/16/20, 7:50 PM, "BESS on behalf of Erik Kline via Datatracker"
wrote:
Erik Kline has entered the following ballot position for
draft-ietf-bess-rfc5549revision-04: No Objection
When responding, please keep the subject line intact and reply to all
email addresses
With the BESS mailing list administer login, it is possible to add someone to
the list using “Membership Management->Mass Subscriptions”. However, it seems
that https://www.ietf.org/mailman/listinfo/bess should work.
Thanks,
Acee
From: BESS on behalf of "Mankamana Mishra (mankamis)"
Date:
I support publication of the draft as a standards track RFC.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Monday, June 15, 2020 at 6:56 AM
To: "draft-ietf-bess-evpn-oam-req-fr...@ietf.org"
, "bess@ietf.org"
Subject: [bess] WG Last Call and IPR Poll for
As a designated expert for this registry, I approve these allocations.
Thanks,
Acee
From: BESS on behalf of Gaurav Dawra
Date: Tuesday, March 3, 2020 at 10:54 AM
To: "bess-cha...@ietf.org" , "bess@ietf.org"
Subject: [bess] Request for IANA early allocation for
draft-ietf-bess-srv6-services
Hi Mankamana,
From: BESS on behalf of "Mankamana Mishra (mankamis)"
Date: Saturday, April 11, 2020 at 4:41 PM
To: "draft-ietf-bess-mvpn-msdp-sa-interoperat...@ietf.org"
Cc: "Bocci, Matthew (Nokia - GB)" , "bess@ietf.org"
Subject: [bess] Shepherd review comment
Support – though I’ve always thought MC-LAG was a hack, it is part of the
landscape.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Tuesday, January 21, 2020 at 9:51 AM
To: "bess@ietf.org"
Cc: "draft-brissette-bess-evpn-mh...@ietf.org"
, "bess-cha...@ietf.org"
Hi Stephane, BESS WG,
I support publication as a proposed standard. The mechanisms require capability
advertisement and these must be standardized.
Thanks,
Acee
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Friday, January 17, 2020 at 3:56 AM
To: "bess@ietf.org" ,
I support publication. I have reviewed the document and have the following
suggestions.
1. It would read better if the document simply used “Next Hop Address
Family” or “Next Hop address AF” as opposed to “set of network-layer protocols
to which the address in the Next Hop field may
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Monday, January 6, 2020 at 9:15 AM
To: "bess@ietf.org"
Cc: "draft-zzhang-bess-bgp-multic...@ietf.org"
, "bess-cha...@ietf.org"
Subject: [bess] WG adoption and IPR poll for
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Monday, January 6, 2020 at 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-multicast-controller
Hello,
This email
this helps,
Acee
From: Robert Raszuk
Date: Tuesday, December 3, 2019 at 11:39 AM
To: Acee Lindem
Cc: "slitkows.i...@gmail.com" , "Bocci, Matthew (Nokia
- GB)" , "bess-cha...@ietf.org"
, "bess@ietf.org"
Subject: Re: [bess] WG Adoption and IPR Poll for
Hi Robert,
From: Robert Raszuk
Date: Tuesday, December 3, 2019 at 8:25 AM
To: Acee Lindem
Cc: "slitkows.i...@gmail.com" , "Bocci, Matthew (Nokia
- GB)" , "bess-cha...@ietf.org"
, "bess@ietf.org"
Subject: Re: [bess] WG Adoption and IPR Poll for
draft-l
.
Anyway, I don’t wish to engage in a protracted debate and I don’t believe the
WG wishes to delay publication of this draft. Your lone objection can be noted
in the shepherds report.
Thanks,
Acee
From: Robert Raszuk
Date: Monday, December 2, 2019 at 6:37 PM
To: Acee Lindem
Cc: "slitk
Robert,
What you’re suggesting doesn’t really solve the problem that all the currently
deployed routers that do not follow RFC 5549. No known implementations follow
RFC 5549. Were you on the meetecho when this was presented in the BESS meeting
at IETF 106? There was clear consensus in the
I support WG adoption. This is update is desperately needed to reflect current
implementations and deployments.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Wednesday, November 27, 2019 at 7:37 AM
To: "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: [bess] WG
Support
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Monday, October 28, 2019 at 6: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 for
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Friday, September 27, 2019 at 6:01 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
Hi Gyan,
See one inline.
From: BESS on behalf of Gyan Mishra
Date: Saturday, September 28, 2019 at 2:06 PM
To: Gyan Mishra , "bess@ietf.org"
Subject: Re: [bess] RFC or Draft that lists all standards track rfc’s of all
mvpn profiles
I did some research and theseare the main RFCs for MVPN
Support working group publication of this document. There are implementations.
Thanks,
Acee
From: BESS on behalf of Stephane Litkowski
Date: Monday, June 17, 2019 at 4:56 AM
To: "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: [bess] WGLC, IPR and implementation poll for
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of Stephane Litkowski
Date: Tuesday, May 7, 2019 at 3:37 AM
To: "bess@ietf.org"
Subject: [bess] WG adoption call & IPR poll for draft-jain-bess-evpn-lsp-ping
Hi,
This email begins a two-week poll for adoption of
I support WG adoption. The draft precisely defines the host mobility for EVPN
IRB and the attendant route types.
Thanks,
Acee
From: BESS on behalf of Stephane Litkowski
Date: Wednesday, March 20, 2019 at 8:53 AM
To: Stephane Litkowski , "bess@ietf.org"
,
Hi Stephane,
No objection - I think the question on whether BOS should be encoded in those
bits confirms that this should be specified.
Thanks,
Acee
On 10/22/18, 9:47 AM, "BESS on behalf of stephane.litkow...@orange.com"
wrote:
Hi,
Does anyone disagree with the additional
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of Stephane Litkowski
Date: Tuesday, September 4, 2018 at 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 BESS working group adoption
Hi Stephane, Authors,
I support advancement. This is a useful optimization that has been implemented .
Two comments:
1. Call the new BGP Community “Router MAC” rather than “Router’s MAC”.
2. Consistently use “TSes” to refer to multiple Tenant Systems and “TS’s”
to refer to an address
I support WG adoption.
Thanks,
Acee
From: BESS on behalf of Stephane Litkowski
Date: Wednesday, August 8, 2018 at 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 WG,
This email begins a two-week poll for
I also support WG adoption.
Thanks,
Acee
From: BESS on behalf of "Patrice Brissette (pbrisset)"
Date: Saturday, June 2, 2018 at 5:27 PM
To: "Bocci, Matthew (Nokia - GB)"
Cc: "draft-sajassi-bess-evpn-virtual-eth-segm...@ietf.org"
, "bess@ietf.org"
Subject: Re: [bess] WG Adoption and IPR
This draft solves a real problem with DF election and I support WG adoption.
Thanks,
Acee
From: BESS on behalf of Stephane Litkowski
Date: Monday, May 14, 2018 at 5:48 AM
To: "bess@ietf.org"
Subject: [bess] WG adoption and
I support WG adoption of this draft.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Monday, April 9, 2018 at 9:23 AM
To: "draft-sajassi-bess-evpn-vpws-...@ietf.org"
,
Hi John,
So I must surmise that all the MAC routes are associated with the more granular
virtual ESs? If so, what is the purpose of the aggregate DC ES?
Thanks,
Acee
From: BESS on behalf of John E Drake
Date: Friday, April 6, 2018 at 9:46 AM
To:
I support publication.
Thanks,
Acee
From: BESS on behalf of "Bocci, Matthew (Nokia - GB)"
Date: Wednesday, March 28, 2018 at 8:50 AM
To: "draft-ietf-bess-evpn-vpls-seamless-in...@ietf.org"
,
I support publication.
Thanks,
Acee
From: BESS on behalf of Stephane Litkowski
Date: Monday, March 26, 2018 at 10:21 AM
To: "bess@ietf.org"
Subject: [bess] WGLC on draft-ietf-bess-evpn-df-election-framework
Hello working
;
Date: Monday, August 21, 2017 at 11:14 AM
To: Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>>, "Ivory, William"
<william.iv...@intl.att.com<mailto:william.iv...@intl.att.com>>,
"'net...@ietf.org<mailto:'net...@ietf.org>'"
<net...@ie
Support
On 6/12/17, 12:27 PM, "BESS on behalf of Martin Vigoureux"
wrote:
>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-fat-pw-bgp-02 [1] which is considered mature and ready
>for a final
I support publication.
Thanks,
Acee
On 6/6/17, 10:11 AM, "BESS on behalf of Martin Vigoureux"
wrote:
>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-usage-04 [1] which is considered
I support WG adoption as the described mechanisms fully satisfy Service
Provider (SP) EVPN DF election control requirements.
Thanks,
Acee
On 6/6/17, 9:44 AM, "BESS on behalf of thomas.mo...@orange.com"
wrote:
>Hello working group,
>
Hi Loa, et al,
I support publication of this draft as a standards track document. It is
well-written and handles previously unspecified details of single and
multiple label BGP advertisement.
Thanks,
Acee
On 4/4/17, 8:33 AM, "BESS on behalf of Loa Andersson"
Support. While I won’t comment on specifics, the IPR appears to only apply
to one aspect of the proposed SFC mechanisms.
Thanks,
Acee
On 4/13/17, 2:04 PM, "BESS on behalf of Martin Vigoureux"
wrote:
>WG
>
>Given the IPR disclosed
Hi Spencer,
On 4/7/17, 5:46 PM, "BESS on behalf of Spencer Dawkins"
wrote:
>Spencer Dawkins has entered the following ballot position for
>draft-ietf-bess-evpn-vpws-11: No Objection
>
>When responding, please keep the subject
ami Boutros" <sbout...@vmware.com> wrote:
>
>Hi Acee,
>
>Please find attached document with all comments addresses, if all
>good will
>Submit before the cut-off tomorrow.
>
>Please see comments inline.
>On 3/12/17, 11:36 AM, "Acee Li
Hi Sami,
This version satisfies all my comments.
Thanks,
Acee
On 3/12/17, 2:36 PM, "BESS on behalf of Acee Lindem (acee)"
<bess-boun...@ietf.org on behalf of a...@cisco.com> wrote:
>Hi Sami,
>
>I think this version reads much better. I still have a couple comments and
r edits
>below.
>
>Thanks,
>
>Sami
>
>
>
>On 3/3/17, 8:30 AM, "Acee Lindem (acee)" <a...@cisco.com> wrote:
>
>>Hello,
>>
>>
>>
>>I have been selected as the Routing Directorate reviewer for this draft.
>>
>>The R
Hi Dhanendra,
From: "Dhanendra Jain (dhjain)" <dhj...@cisco.com<mailto:dhj...@cisco.com>>
Date: Tuesday, February 14, 2017 at 4:12 PM
To: Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>>, Xufeng Liu
<xufeng.liu.i...@gmail.com<mailto:xufeng.liu.i...@gm
Support.
Thanks,
Acee
On 2/13/17, 5:07 PM, "BESS on behalf of Martin Vigoureux"
wrote:
>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-prefix-advertisement-04 [1] which is considered
the models would use?
Thanks,
Acee
From: Giles Heron <giles.he...@gmail.com<mailto:giles.he...@gmail.com>>
Date: Friday, February 10, 2017 at 11:18 AM
To: Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>>
Cc: "Patrice Brissette (pbrisset)"
<pbris...@cisco.co
Hi Patrice - we are working fervently on a common IETF routing types model. We
have both route-target and router-distinguisher types defined there. The work
is being done in the Routing WG. Our intension is to accelerate standardization
so it doesn't hold up standardization of the importing
In case it is not obvious, I support MPLS WG adoption of the subject draft in
its current form ;^). I already supported it on the MPLS list.
Thanks,
Acee
From: Idr > on behalf of Loa
Andersson >
Date: Wednesday,
Hi Robert,
From: <rras...@gmail.com<mailto:rras...@gmail.com>> on behalf of Robert Raszuk
<rob...@raszuk.net<mailto:rob...@raszuk.net>>
Date: Wednesday, August 31, 2016 at 10:40 AM
To: Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>>
Cc: Eric C
Hi Robert,
Currently, everything in draft-rosen-mpls-rfc3107bis is pretty much backward
compatible with our more than a decade old RFC 3107 implementations and
deployments. What you are proposing is not and has implications in both the
control and forwarding planes. If you really believe that
Hi Loa, et al,
Since I commented on the MPLS-RT review with respect to the IDR-specific
content, there may be some confusion as to where I stand on the ownership
of this draft. I’ve reviewed this document and agree with the approach
described below. I’m convinced we will get the right level
Hi Robert,
I think this would defeat the purpose of clarifying RFC 3101 multi-label
behavior in a BIS draft. Let’s see if we can reach consensus first.
Thanks,
Acee
From: Idr > on behalf of
Robert Raszuk
68 matches
Mail list logo