Gunter Van de Velde has entered the following ballot position for charter-ietf-grow-04-02: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-grow/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The line between SIDROPS and GROW is maybe a little vague. When looking at the obsoleted charter of SIDR we find in the (old) SIDR charter: "The purpose of the SIDR working group is to reduce vulnerabilities in the inter-domain routing system." The SIDROPS charter has following text: " Sidrops is responsible for encouraging deployment of theSIDR technologies while ensuring as secure of a global routing system, as possible, during the transition. " Now the new proposed GROW charter 04-02 states: " The working group will also provide inputs for addressing operational and routing security requirements of Internet- connected networks, and, where appropriate, recommend work to be taken up by those working groups. " and " Document the operational aspects of securing the Internet routing system. " When reading this with a bit of a skeptical lens, there’s potential for some overlap to be interpreted. The text says that SIDR operations belong in SIDROPS, but what exactly does that mean, especially considering that SIDR’s focus is on building a secure routing system? As I understand it, GROW wouldn’t be covering operational aspects of RPKI, origin validation of BGP announcements, or BGPSEC. Maybe it would help to call that out explicitly in the GROW charter, just to avoid any potential confusion down the road? _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
