Hi Gunter, 

Thanks for the comment.

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : Gunter Van de Velde via Datatracker <[email protected]>
> Envoyé : mardi 22 avril 2025 15:35
> À : The IESG <[email protected]>
> Cc : [email protected]; [email protected]
> Objet : Gunter Van de Velde's No Objection on charter-ietf-grow-04-
> 02: (with COMMENT)
> 
> 
> 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.)
> 
> 
> -------------------------------------------------------------------
> 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?

[Med] That's answered in the SIDROPS Charter itself:

   The global deployment of SIDR, consisting of RPKI, Origin Validation of
   BGP announcements, and BGPSEC, is underway, creating an Internet
   Routing System consisting of SIDR-aware and non-SIDR-aware networks.

   ..

   The SIDR Operations Working Group (sidrops) develops guidelines for
   the operation of SIDR-aware networks, and provides operational guidance
   on how to deploy and operate SIDR technologies in existing and new
   networks.

> 
> 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?
> 

[Med] Works for me. I can update the text as follows:

OLD:
  SIDR operations related work will occur in SIDROPS working group.

NEW: 
   Work related to SIDR operations (consisting of RPKI, Origin Validation of
   BGP announcements, and BGPSEC operations) will occur in SIDROPS working 
group.

Better?
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to