See one typo.
From: GROW on behalf of "Acee Lindem (acee)"
Date: Monday, July 11, 2022 at 10:45 AM
To: Gyan Mishra , Yingzhen Qu
Cc: IDR List , "grow@ietf.org grow@ietf.org" ,
lsr
Subject: Re: [GROW] [Idr] [Lsr] IGP Monitoring Protocol
Hi Gyan,
From: GROW on behalf o
ilto:jefftant.i...@gmail.com>>
Sent: Saturday, July 9, 2022 3:40 PM
To: Robert Raszuk mailto:rob...@raszuk.net>>
Cc: Acee Lindem (acee) mailto:a...@cisco.com>>; lsr
mailto:l...@ietf.org>>; i...@ietf.org<mailto:i...@ietf.org>;
Susan Hares mailto:sha...@ndzh.com>>
t Raszuk mailto:rob...@raszuk.net>>
Cc: Acee Lindem (acee) mailto:a...@cisco.com>>; lsr
mailto:l...@ietf.org>>; i...@ietf.org<mailto:i...@ietf.org>;
Susan Hares mailto:sha...@ndzh.com>>;
grow@ietf.org<mailto:grow@ietf.org> grow@ietf.org<mailto:grow@ietf.
I also support publication.
Thanks
Acee
From: Idr on behalf of Jeff Tantsura
Date: Thursday, July 25, 2019 at 5:49 PM
To: IDR List , Susan Hares
Cc: "grow@ietf.org"
Subject: Re: [Idr] WG LC for Extended BGP Administrative Shutdown Communication
(bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9
20/19, 10:11 AM, "GROW on behalf of Acee Lindem (acee)"
mailto:grow-boun...@ietf.org> on behalf of
a...@cisco.com<mailto:a...@cisco.com>> wrote:
Hello,
I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing
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
Hi Jeff,
On 12/10/18, 5:33 PM, "GROW on behalf of Jeffrey Haas" wrote:
[Note, message reordered and reformatted for quoting clarity]
Tim,
Thank you for your patience for my response.
On Tue, Nov 20, 2018 at 05:42:37AM +, Tim Evens (tievens) wrote:
> On
I also support adoption.
Acee
On 9/25/18, 1:06 PM, "GROW on behalf of Tim Evens (tievens)"
wrote:
I support adoption of this document.
On 9/25/18, 9:04 AM, "GROW on behalf of Job Snijders"
wrote:
Dear working group,
Feedback from the working group
I support adoption as well.
Thanks,
Acee
From: GROW on behalf of Job Snijders
Date: Friday, September 21, 2018 at 7:55 AM
To: Joel Jaeggli
Cc: "grow@ietf.org grow@ietf.org"
Subject: Re: [GROW] Making BMP registries FCFS
Read the doc, looks fine to me. I support adoption.
Let’s give folks a
> On Jul 6, 2018, at 8:59 AM, Randy Bush wrote:
>
>> Why anyone would need BMP wrapper to monitor IGP ?
>
> probably similar reasons that folk seem to need bgp-ls to get the
> is-is/ospf databases. is-is and ospf have decades of complexity
> layered on un-simple bases. so we seek yet
rementally.
Best Regards,
Robin
-Original Message-
From: Jeff Tantsura [mailto:jefftant.i...@gmail.com]
Sent: Wednesday, July 04, 2018 5:15 AM
To: Acee Lindem (acee) ; Lizhenbin
; grow@ietf.org; ops...@ietf.org
Cc: l...@ietf.org; rt...@ietf.org; Guyu
management.
Expect to have more discussion with you in IETF 102.
I'm sure we will. I really don't think this meets the "stick to the wall" test
for GROW.
Thanks,
Acee
Thanks,
Robin
-Original Message-
From: Acee Lin
Hi Yunan, Shunwan, and Zhenbin,
What are the advantages of inventing a new protocol over just using YANG and
NETCONF, RESTCONF, or gNMI? Operators and vendors are doing this anyway. A
second alternative would be to listen passively in IS-IS (or OSPF for that
matter). Why would anyone want
e edges of the network.
Thanks - Fred
From: Christopher Morrow [mailto:christopher.mor...@gmail.com]
Sent: Tuesday, March 13, 2018 8:24 AM
To: Templin, Fred L <fred.l.temp...@boeing.com>
Cc: grow@ietf.org; Saccone, Gregory T <gregory.t.sacc...@boeing.com>; Gaurav
Dawra <gda
14 matches
Mail list logo
