Re: [GROW] Fwd: RFC 4384 rejected errata, wrong call

On Mon, Jan 30, 2023 at 12:19 PM, Jeffrey Haas wrote: > At the request of Warren, making this observation in public. > Thank you, Jeff! I requested this so that there is some traceability / transparency. I think that this is especially important when changing the state of a previous Errata

Re: [GROW] [Technical Errata Reported] RFC7854 (7194)

Ooof. Yes, this seems to be correct (but I wouldn't mind someone else confirming) — what I don't know is how we get the IANA registry updated — can an errata do this (with a note to the IANA), or does it need a new document ? I'll email the IANA and ask… W On Sun, Oct 30, 2022 at 8:32 AM,

[GROW] Fwd: Reminder: Call for Papers: IAB workshop on Management Techniques in Encrypted Networks (M-TEN)

Hi there all, The IAB is organizing a workshop on Management Techniques in Encrypted Networks (M-TEN), and I figured that this might be interesting and relevant to many people in this WG. Please see below for details, W -- Forwarded message -- From: IAB Executive

Re: [GROW] Proposing a well-known BGP community for Anycast

On Mon, Jul 11, 2022 at 12:46 PM, heasley wrote: > Sat, Jul 09, 2022 at 09:32:51PM +0200, Robert Raszuk: > > And here comes I think need for authors to clarify something. They said > that such marking is going to be used along with NO-EXPORT. > > no, you might have misread that; with no-export

Re: [GROW] Proposing a well-known BGP community for Anycast

On Sat, Jul 09, 2022 at 6:33 AM, Robert Raszuk wrote: > Hi, > > While it may sound like I am against it - I am not. I am just trying to > make sure what we ship can actually effectively work. > > One key question for example which no one answered so far is this: > > If I have one very important

[GROW] IETF "leadership pipeline"

Hi there all, An ongoing topic in the IETF & IESG is how to grow the IETF "leadership pipeline", so that when we need new AD and / or chairs, we have good candidates. Currently when a new chair needs to be appointed the process goes something like this (with some added hyperbole): The AD(s)

Re: [GROW] draft minutes. ietf 112

Email the secretariat -- they can do, AFACIT, anything :-) W On Thu, Dec 9, 2021 at 12:43 PM Christopher Morrow < christopher.mor...@gmail.com> wrote: > > > On Thu, Dec 9, 2021 at 12:25 PM tom petch wrote: > >> From: Christopher Morrow >> Sent: 09 December 2021 15:42 >> >> On Thu, Dec 9, 2021

[GROW] Fwd: NomCom 2021-2022 Call for Community Feedback

Please provide feedback to the NomCom -- the IESG you get is the one that *you* help select. Even a few sentences help... W -- Forwarded message - From: NomCom Chair 2021 Date: Tue, Oct 19, 2021 at 10:28 AM Subject: NomCom 2021-2022 Call for Community Feedback To: IETF

Re: [GROW] IRTF - An "interim" workshop on Evolving Routing Security in the Internet

the "Stop sending my spam about random conferences" response :-) I've CCed in Adrian, who probably has more details and can provide background so GROWers know if they should attend... W > On Fri, Sep 17, 2021 at 12:42 PM Warren Kumari wrote: > >> Hi there, >> >

[GROW] IRTF - An "interim" workshop on Evolving Routing Security in the Internet

Hi there, I stumbled across an announcement of a workshop on Evolving Routing Security in the Internet on the IRTF list: https://mailarchive.ietf.org/arch/msg/irtf-discuss/1TshQOGrKGe-5QsLn7OeYwa3_vg/ And figured it might be of interest to SIDROPS/GROW, etc. --- [irtf-discuss] An "interim"

[GROW] Fwd: NomCom 2021-2022 Call for Nominations

Dear all, You've probably already seen this multiple times by now, but it's sufficiently important that I figured I'd send it again. There are many open positions that the NomCom needs to fill: ART AD: 1 position INT AD: 1 position OPS AD: 1 position RTG AD: 1

Re: [GROW] [Technical Errata Reported] RFC6396 (6640)

Awesome thanks Colin! W On Thu, Jul 15, 2021 at 5:03 AM Colin Petrie wrote: > > I checked the encoding of the attribute, the errata looks correct to me > also. > > Thanks, > Colin > > > > > On 13/07/2021 15:22, Warren Kumari wrote: > > [ - RFC E

Re: [GROW] [Technical Errata Reported] RFC6396 (6640)

[ - RFC Editor (for clutter) ] Dear GROW, AFAICT, this errata is correct, and should be Verified, but I'd like some confirmation / double-checkin'. Note that there is already a somewhat related errata: https://www.rfc-editor.org/errata_search.php?rfc=6396_status=0 Please let me know by Friday

Re: [GROW] draft-ietf-grow-bmp-local-rib-11 Peer Flags IANA Conflict Resolution

[ + John Scudder ] Just a quick note. The latest version (-12) of the document was just published; the diff is here: https://www.ietf.org/rfcdiff?url1=draft-ietf-grow-bmp-local-rib-11=draft-ietf-grow-bmp-local-rib-12 I'm planning on releasing it by Friday unless I hear any strong objections...

Re: [GROW] Alvaro Retana's Discuss on draft-ietf-grow-bmp-local-rib-10: (with DISCUSS and COMMENT)

On Wed, Apr 28, 2021 at 11:12 AM Job Snijders wrote: > Hi all, > > We (GROW chairs + Alvaro + draft authors Tim & Paolo) had a productive > call, a number of suggestions for clarification came to light. > > Tim will follow up by sending a summary of proposed changes to the list. > And some

Re: [GROW] Alvaro Retana's Discuss on draft-ietf-grow-bmp-local-rib-10: (with DISCUSS and COMMENT)

On Wed, Apr 21, 2021 at 1:34 PM Job Snijders wrote: > Dear Alvaro, draft authors, > > Perhaps it would be good to have a voice discussion? This might expedite > figuring out a solution to how we describe things. > Yup, that sounds like a good idea to me. Also, I'd like to apologize to the

Re: [GROW] AD Review of draft-ietf-grow-bmp-local-rib

On Mon, Mar 8, 2021 at 7:16 PM Tim Evens (tievens) wrote: > Hi Warren, > > > > I have just submitted revision 10 with the updates. > Ta! IETF LC has just been requested. Thanks again to the authors and WG. W > > > Thanks, > > Tim > > > > &g

Re: [GROW] AD Review of draft-ietf-grow-bmp-local-rib

F ends, so that people can pay attention... Thank again for the quick turn around, W > > > Thanks, > > Tim > > > > On 2/22/21, 9:27 AM, "Warren Kumari" wrote: > > > > Hi authors and WG, > > > > Thank you for this document, I be

[GROW] AD Review of draft-ietf-grow-bmp-local-rib

Hi authors and WG, Thank you for this document, I believe that allowing BMP to share Loc-RIB is clearly a good thing. I do have a few comments/nits that addressing now should help the IETF LC and IESG eval go more smoothly. Please SHOUT loudly once you've had a chance to address these. AD

Re: [GROW] Barry Leiba's No Objection on charter-ietf-grow-03-00: (with COMMENT)

On Thu, Jan 28, 2021 at 11:19 AM Barry Leiba via Datatracker wrote: > > Barry Leiba has entered the following ballot position for > charter-ietf-grow-03-00: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines.

Re: [GROW] grow - Requested session has been scheduled for IETF 108

On Fri, Jul 3, 2020 at 5:16 AM Nick Hilliard wrote: > > "IETF Secretariat" wrote on 03/07/2020 01:20: > > grow Session 1 (1:40 requested) > > Monday, 27 July 2020, Session III 1410-1550 > > Is this UTC? Yes -- the attached ICS file contains: DTSTART;TZID="UTC":20200727T141000 (and the

Re: [GROW] [Sidrops] Deprecation of AS_SET and AS_CONFED_SET -- feedback requested

Thank you Sriram and Lilia -- this is helpful / useful. I wonder if the people who configured the 21 "Routes that seem meaningful" still know that they are doing this, or if it is a lurking horror W On Wed, Oct 23, 2019 at 11:45 AM Sriram, Kotikalapudi (Fed) wrote: > > Earlier in this

Re: [GROW] Deprecation of AS_SET and AS_CONFED_SET -- feedback requested

On Thu, Sep 26, 2019 at 10:52 PM Jeffrey Haas wrote: > > > > On Sep 26, 2019, at 6:43 PM, Warren Kumari wrote: > > This is nice, but what would make it more useful would be if it also > reported if there are *useful* AS_SETS / if the AS_SET means anything. > > For

Re: [GROW] Deprecation of AS_SET and AS_CONFED_SET -- feedback requested

On Wed, Sep 25, 2019 at 11:32 PM Sriram, Kotikalapudi (Fed) wrote: > > Jared, > > >(Obviously my search in e-mail today went afoul, I see it’s adopted.. > > Yes, the draft was adopted. You can see the discussion here: >

[GROW] AD review of: draft-ietf-grow-bmp-adj-rib-out

Hi there, Thanks to the authors and WG for this document -- it provides a useful mechanism / enhancement, is well written, and easy to understand. I do have a few editorial comments that I'd like to see addressed before starting IETF LC. Note that these are mostly nit type things, and could be

Re: [GROW] Some comments on draft-chen-grow-enhanced-as-loop-detection-00

On Thu, Mar 21, 2019 at 12:59 AM Jeffrey Haas wrote: > Authors, > > Some various comments on the draft in no particular order: > - Consider using the document ASes from the reserved ranges; i.e. RFC 5398 > - Construct a unified table of the "results" and a short term for their > meaning. One

Re: [GROW] [Technical Errata Reported] RFC6396 (5511)

James is correct -- I'll mark this one as verified. For those whose hex-dump reading skill have atrophied, here is the fixed version: Border Gateway Protocol - UPDATE Message Marker: Length: 62 Type: UPDATE Message (2) Withdrawn Routes Length: 0

Re: [GROW] Discourage asdot+/asdot?

On Mon, Aug 13, 2018 at 7:33 AM Nick Hilliard wrote: > > Daniel Shaw wrote on 10/08/2018 08:29: > > I think that on closer examination you may find the AFRINIC whois also > > changed around the same timeframe, perhaps a year later. It seems that > > there may be one (or possibly some other very

Re: [GROW] [Technical Errata Reported] RFC8326 (5402)

On Thu, Jun 21, 2018 at 3:36 PM RFC Errata System wrote: > The following errata report has been submitted for RFC8326, > "Graceful BGP Session Shutdown". > > -- > You may review the report below and at: > http://www.rfc-editor.org/errata/eid5402 > >

Re: [GROW] [Technical Errata Reported] RFC7948 (5366)

On Wed, May 23, 2018 at 1:09 PM Nick Hilliard wrote: > This errata report isn't wrong, but belongs to a bigger category of > problems relating to how the IETF handles third party references in RFCs. > > It's unlikely that the researchgate url will be persistent in the longer >

Re: [GROW] Peter stepping down as chair - volunteers?

again - I really appreciate your willingness to step forward when needed. Also, I'd like to thank Peter again for all of this time and energies running the group. Thanks and see you all in London, W [0]: I've decided that this is the new collective noun :-P On Tue, Feb 27, 2018 at 9:28 AM, Warren

Re: [GROW] Peter stepping down as chair - volunteers?

Hi all, So far I have one good candidate, but I felt it only correct to give everyone a chance, and so I’ll wait till Tuesday to select a chair. W On Tue, Feb 27, 2018 at 9:28 AM Warren Kumari <war...@kumari.net> wrote: > Hi there GROWers, > > Sadly, Peter has just let me

[GROW] Peter stepping down as chair - volunteers?

Hi there GROWers, Sadly, Peter has just let me know that, due to other time commitments, he will be stepping down as one of the GROW chairs. I'd like to take a moment to thank him for all of his hard work, and also to ask for volunteers who would be willing to set up and serve. GROW is always a

Re: [GROW] AD Review of draft-ietf-grow-bgp-session-culling

On Mon, Sep 11, 2017 at 12:16 PM, Warren Kumari <war...@kumari.net> wrote: > On Mon, Sep 11, 2017 at 11:57 AM, Job Snijders <j...@ntt.net> wrote: >> Dear Warren, >> >> On Sun, Sep 10, 2017 at 06:55:00PM -0400, Warren Kumari wrote: >>> I've just completed m

Re: [GROW] AD Review of draft-ietf-grow-bgp-session-culling

On Mon, Sep 11, 2017 at 11:57 AM, Job Snijders <j...@ntt.net> wrote: > Dear Warren, > > On Sun, Sep 10, 2017 at 06:55:00PM -0400, Warren Kumari wrote: >> I've just completed my AD review of draft-ietf-grow-bgp-session-culling. >> >> I only had a few small nits: >

[GROW] AD Review of draft-ietf-grow-bgp-session-culling

Hi there, I've just completed my AD review of draft-ietf-grow-bgp-session-culling. I only had a few small nits: Section 3: "Involuntary BGP Session Teardown: The Caretaker of the lower layer network disrupts BGP control-plane traffic in the upper layer, causing the BGP Hold Timers of the

Re: [GROW] Genart telechat review of draft-ietf-grow-large-communities-usage-07

On Mon, May 8, 2017 at 12:48 PM, Job Snijders wrote: > Thanks Stewart! Yes, indeed. Thank you Stewart - Directorate reviews are always appreciated. W > > On Mon, 8 May 2017 at 18:42, Stewart Bryant > wrote: >> >> Reviewer: Stewart Bryant >> Review

Re: [GROW] IETF LC for IDR-ish document (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard

[ + authors ] On Sat, May 6, 2017 at 3:16 AM, Robert Raszuk wrote: > Hi Warren, > >> This is clearly not unanimous/ not everyone is happy, but (in my view) >> there is *rough* consensus for this to progress. > > > The group of users of BGP which this update impacts the most

Re: [GROW] Working Group Adoption Call: draft-mauch-bgp-reject

On Monday, November 2, 2015, Christopher Morrow < christopher.mor...@gmail.com> wrote: > Howdy Grow folk (again), > Please consider this as the start of a 3wk working group adoption call > for the subject draft who's abstract is: > > "This document defines the default behaviour of a BGP speaker

Re: [GROW] Requesting Grow's review of draft-ietf-idr-as-private-reservation-02.txt

On Dec 21, 2012, at 5:37 PM, Susan Hares sha...@ndzh.com wrote: Peter and Chris: We request that the GROW WG review draft-ietf-idr-as-private-reservation-02.txt? (http://datatracker.ietf.org/doc/draft-ietf-idr-as-private-reservation/) Since it modifies RFC 1930, a BCP, it is

Re: [GROW] RouteLeaks - problem or not?

On Nov 15, 2012, at 11:46 PM, Christopher Morrow christopher.mor...@gmail.com wrote: On Thu, Nov 15, 2012 at 11:10 PM, Shane Amante sh...@castlepoint.net wrote: is that better? I'm really asking whether or not there is a problem and if we (ietf in general) can get a solution (or even the

Re: [GROW] Call for GROW WG adoption of grow-overlapping-routes

On Aug 27, 2012, at 10:43 AM, Noel Chiappa wrote: From: Nick Hilliard n...@inex.ie Overall, then, it is desirable to remove overlapping routes from the global routing table where possible. People inject prefixes into the DFZ for specific reasons. If they are pruned by some upstream

Re: [GROW] WGLC: draft-ietf-grow-no-more-unallocated-slash8s-01 - ABBREVIATED - Ends 7/5/2011

On Jun 28, 2011, at 5:59 AM, Christopher Morrow wrote: Hello GROW Folks, We'd like to start an abbreviated Working-Group Last Call for: http://tools.ietf.org/html/draft-ietf-grow-no-more-unallocated-slash8s-01 Read and support. W Leo kicked out a new revision after LC comments last

Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling

And another support... On Apr 1, 2011, at 4:19 AM, Christopher Morrow wrote: (+wg this time, for realz) On Fri, Apr 1, 2011 at 9:20 AM, Christopher Morrow christopher.mor...@gmail.com wrote: Given the discussion in the room today, and the overlap of readers-of-draft + folk-asking-for-adoption

Re: [GROW] [Idr] Fwd: New Version Notification for draft-shakir-idr-ops-reqs-for-bgp-error-handling-01

aol Me too! /aol On Feb 25, 2011, at 11:44 AM, Renwei li wrote: +1 Renwei -Original Message- From: grow-boun...@ietf.org [mailto:grow-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim) Sent: Wednesday, February 23, 2011 9:57 PM To: Chris White; Smith, Donald Cc: i...@ietf.org;

[GROW] draft-ietf-grow-unique-origin-as-00 looks cooked to me...

Hi, I have reviewed draft-ietf-grow-unique-origin-as-00 and I believe it is fully cooked... W ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] last call for draft-ietf-grow-unique-origin-as-00

On Dec 16, 2010, at 11:54 PM, Peter Schoenmaker wrote: Hi, I would like to issue last call for draft-ietf-grow-unique-origin-as-00. We will close last call Jan 2nd 2011. Read it and support (and apologies, I didn't notice this thread when I sent out mail a short while ago, saying