Skip to main content

Global Routing Operations
charter-ietf-grow-05

Yes

Ketan Talaulikar
Mohamed Boucadair
(Erik Kline)

No Objection

Jim Guichard
Roman Danyliw
(Paul Wouters)

Note: This ballot was opened for revision 04-05 and is now closed.

Ballot question: "Do we approve of this charter?"

Ketan Talaulikar
Yes
Mohamed Boucadair
Yes
Deb Cooley
No Objection
Comment (2025-05-07 for -04-05) Sent
My previous comment: 
'In 2009, the starting paragraph focused on BGP, is that different now?  Is GROW still focused on BGP operational challenges?  Or has that focus expanded?  Has that scope creep been agreed with other working groups?'

This along with Gunter's comment, this resulted in a single addition of 'BGP' in one location down in the objectives section.  If 'the global (IP) routing network' is a euphemism for BGP, then that needs to be explained up at the top of the charter.
Éric Vyncke
No Objection
Comment (2025-05-05 for -04-05) Sent
Part of `The GROW working group will also develop and increase awareness to mitigations` should probably rewritten to specify 'operational mitigations' (i.e., no new protocols) and I find `develop and increase awareness` difficult to parse.

My previous comment still stands though: I have more problems with `Document operational aspects of IP interconnection` as it is rather vague/broad and goes beyond BGP.
Gunter Van de Velde
No Objection
Comment (2025-04-29 for -04-05) Not sent
Thanks for implementing the edits as earlier discussed before re-charter effort
Jim Guichard
No Objection
Mahesh Jethanandani
No Objection
Comment (2025-05-06 for -04-05) Sent
Paragraph 10
> *  Standardize YANG data models and automation building blocks
>    related to the operations of global routing system.

Wouldn't the WG where these routing protocols are being defined be the right place to do this work, with GROW providing the input? And, the YANG data models should already be defining the operational aspect of the protocols.

-------------------------------------------------------------------------------
NIT
-------------------------------------------------------------------------------

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

Paragraph 1
> The working group will document the operational aspects of
> measurement, monitoring, policy, operational global routing system
> security, or safe default behavior of global IP routing protocol
> implementations and deployments.  The GROW working group will also
> develop and increase awareness to mitigations to prevent malpractice
> (e.g., route leaks) in the global routing system.

Too many "operational" words in the first sentence??
Roman Danyliw
No Objection
Erik Kline Former IESG member
Yes
Yes (for -04-05) Not sent

                            
Paul Wouters Former IESG member
No Objection
No Objection (for -04-06) Not sent