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,
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 Jakob
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"
, "draft-malhotra-bess-evpn-irb-extende
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
draft-jain-bess-evpn-
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
draft-ietf-bess-e
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 and
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 em
I have read the document and support publication.
Thanks,
Acee
From: BESS on behalf of "slitkows.i...@gmail.com"
Date: Tuesday, October 22, 2019 at 10:48 AM
To: "bess@ietf.org" , "draft-ietf-bess-evpn-pref...@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: [bess] WGLC, IPR and implementation p
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
d
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 A
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 meeti
ignored or is this an invalid attribute ?
On Mon, Dec 2, 2019 at 11:21 PM Acee Lindem (acee)
mailto:a...@cisco.com>> wrote:
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 f
plementation survey are included.
https://datatracker.ietf.org/meeting/106/materials/slides-106-bess-sessa-draft-litkowski-bess-vpnv4-ipv6-nh-handling-00-00
Thanks,
Acee
Thx a lot,
R.
On Tue, Dec 3, 2019, 13:17 Acee Lindem (acee)
mailto:a...@cisco.com>> wrote:
Hi Robert,
My point is that
in idr:
https://trac.ietf.org/trac/idr/wiki/Protocol%20implementations%20Reports
Example:
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-optimal-route-reflection%20implementations
Thx,
R.
On Tue, Dec 3, 2019 at 5:24 PM Acee Lindem (acee)
mailto:a...@cisco.com>> wro
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 begin
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 draft-zzhang-bess-bgp-multi
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 belong”
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" ,
"draft-ietf-bess-e
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"
Sub
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
draft-ietf-bess-mvpn-msdp-sa-
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 c
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
draft-ietf-
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:
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 i
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 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,
Support as co-author and not aware of any IPR.
Thanks,
Acee
From: "Bocci, Matthew (Nokia - GB)"
Date: Wednesday, December 9, 2020 at 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
Resent-From:
Speaking as Co-author,
I am aware of IPR on the document.
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-mohanty-bess-weighted-hrw
I am not aware of any undisclosed IPR.
Thanks,
Acee
From: "Bocci, Matthew (Nokia - GB)"
Date: Tuesday, January 5, 2021 at 11:39 AM
To: "bess@iet
Speaking as Co-author,
I support WG adoption.
Thanks,
Acee
From: "Bocci, Matthew (Nokia - GB)"
Date: Tuesday, January 5, 2021 at 11:39 AM
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
Resen
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
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, Februar
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: Thursday
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)
This
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 E
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,
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 mailto:idr-boun...@ietf.org>> on behalf of
Robert Raszuk mailto:rob...@raszuk.net>>
Date: Friday, April 1, 2016 at 4:23
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 cross
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 t
draft on this topic. If there is consensus, merger with the draft under WG
adoption can be considered.
Thanks,
Acee
Thx,
R.
On Wed, Aug 31, 2016 at 4:15 PM, Acee Lindem (acee)
mailto:a...@cisco.com>> wrote:
Hi Robert,
Currently, everything in draft-rosen-mpls-rfc3107bis i
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 mailto:idr-boun...@ietf.org>> on behalf of Loa
Andersson mailto:l...@pi.nu>>
Date: Wednesday, August 31, 2016 at 12:28 AM
To: IDR Li
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 modu
st of
RTs (which can be import, export or both) - so I'd prefer that to be defined in
a shared grouping (more or less as per the structure Patrice gave below) than
to force each model to redefine it.
Giles
On 10 Feb 2017, at 14:51, Acee Lindem (acee)
mailto:a...@cisco.com>> wrote:
H
d
have the same commonality.
Regards,
Patrice Brissette
From: Jeff Tantsura mailto:jefftant.i...@gmail.com>>
Date: Friday, February 10, 2017 at 2:43 PM
To: "Acee Lindem (acee)" mailto:a...@cisco.com>>, Giles Heron
mailto:giles.he...@gmail.com>>
Cc: Patrice Brissette mai
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
>mature and ready for a final working group review.
>Note that thi
"bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>,
Himanshu Shah mailto:hs...@ciena.com>>
Subject: Re: [bess] BGP common parameter Yang module
Hi Xefeng,
From: Xufeng Liu mailto:xufeng.liu.i...@gmail.com>>
Date: Tuesday, February 14, 2017 at 11:44 AM
"bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>,
Himanshu Shah mailto:hs...@ciena.com>>
Subject: Re: [bess] BGP common parameter Yang module
Hi Acee,
From: "Acee Lindem (acee)" mailto:a...@cisco.com>>
Date: Tuesday, February 14, 2017 at
Hello,
I have been selected as the Routing Directorate reviewer for this draft.
The Routing Directorate seeks to review all routing or routing-related
drafts as they pass through IETF last call and IESG review, and sometimes
on special request. The purpose of the review is to provide assistance to
ks,
>
>Sami
>
>
>
>On 3/3/17, 8:30 AM, "Acee Lindem (acee)" wrote:
>
>>Hello,
>>
>>
>>
>>I have been selected as the Routing Directorate reviewer for this draft.
>>
>>The Routing Directorate seeks to review all routing or r
Hi Sami,
This version satisfies all my comments.
Thanks,
Acee
On 3/12/17, 2:36 PM, "BESS on behalf of Acee Lindem (acee)"
wrote:
>Hi Sami,
>
>I think this version reads much better. I still have a couple comments and
>questions.
>
> 1. Why is receiving an extend
ase 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 Lindem (acee)" wrote:
>
>
>>Hi Sami,
>>
>
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 line intact and reply to all
>email addresses included in the To and
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 [1] against
>draft-mackie-bess-nsh-bgp-control-plane, we are star
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"
wrote:
>Working Groups,
>
>This i
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,
>
>This email starts a two-week call for adoption on
>draft-raba
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 mature and ready
>for a final working group review.
>
>Please read t
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 working group review.
>
>¤ Please read this document if you haven
something like the
following:
pattern:
'(0:[0-9]{1,5}:[0-9]{1,10})|
(1:([0-9]{1,3}\.){4}:[0-9]{1,5})|
(2:[0-9]{1,10}:0:[0-9]{1,5})|
(6(:[a-fA-F0-9]{2}){6})';
Of course, this would allow more invalid values, but most servers would be
expected to reject those when
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 group,
This email starts a two-week Working Group Last Call on
draf
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"
, "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: [bess] WG Last Call and IPR Poll for
draft-iet
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: Wen Lin , Sandy Breeze , "Ali
Sajassi (sajass
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"
, "bess@ietf.org"
Subject: [bess] WG adoption and IPR poll for
draft-sajassi-bess-evpn-vpws-fxc-03.tx
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 IPR poll for
draft-sajassi-bess-evpn-fast-df-recovery-02
Hi WG,
This
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 Poll
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 BES
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 or
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 Impleme
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 b
Juniper Business Use Only
From: Acee Lindem (acee)
Sent: Tuesday, November 15, 2022 1:49 PM
To: draft-ietf-bess-evpn-irb-mc...@ietf.org; Routing ADs
Cc: Routing Directorate ; bess@ietf.org
Subject: Routing Directorate Last Call Review for
draft-ietf-bess-evpn-irb-mcast-07.txt
[External Email.
68 matches
Mail list logo
