Re-,

Great, thanks. 

Can you please double check the milestones? Let me know if any change is 
needed. 

Cheers,
Med

> -----Message d'origine-----
> De : Paolo Lucente <[email protected]>
> Envoyé : vendredi 4 avril 2025 19:46
> À : BOUCADAIR Mohamed INNOV/NET <[email protected]>;
> Job Snijders <[email protected]>; [email protected]
> Objet : Re: [GROW] Re: rechartering GROW (2025 update)
> 
> 
> Hi Med,
> 
> Ack all & the "Document the operational aspects of IP
> interconnection."
> reads good, thanks!
> 
> Paolo
> 
> 
> On 4/4/25 16:29, [email protected] wrote:
> > Hi Paolo, all,
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : Paolo Lucente <[email protected]>
> >> Envoyé : vendredi 4 avril 2025 16:16
> >> À : Job Snijders <[email protected]>; [email protected] Objet :
> [GROW]
> >> Re: rechartering GROW (2025 update)
> >
> >>
> >> Hi Job, Med,
> >>
> >> A couple of comments on the latest revision of the charter on
> >> GitHub:
> >>
> >> * I like that we "should allow for presentations and
> discussions of
> >> operator issues and experience, and other work within scope for
> the
> >> working group", i have seen this happening in the NMOP working
> group
> >> incarnating in initiatives like "bring your own incident". I
> share
> >> Tobias comment about removing the "priority" wording because
> this
> >> should not get a dominating characteristic of the wg;
> >
> > [Med] I have already removed that sentence and only kep this
> part:
> >
> > "Agenda time at GROW sessions at IETF meetings should allow for
> presentations and discussions of operator issues and experience,
> and other work within scope for the working group."
> >
> >>
> >> * Similarly, it would be probably good to be explicit that the
> agenda
> >> should also allow for presentation of hackathon work related to
> the
> >> wg;
> >
> > [Med] I'm not sure we need to have an item for this. I trust the
> > Chairs can make sure they are promoting this and ensure that
> more
> > visibility is provided to this work. We do care about code after
> all
> > ;-)
> >
> >>
> >> * There is work ongoing about the Peering API, it may be good
> to
> >
> > [Med] Yes, we have a milestone for this one.
> >
> >> add the "interconnection" wording somewhere in the charter. Not
> sure
> >> if adding a line like "Document the operational aspects of
> >> interconnecting the Internet routing system." would be too
> much;
> >
> > [Med] The interconnection part falls under the "automation
> building blocks" of this item:
> >
> > "Standardize YANG data models and automation building blocks
> related to the operations of global routing system."
> >
> > That's said, if we want to cover direct/private interconnection,
> may be better to have a dedicated item for it. I went for now for:
> >
> > "Document the operational aspects of IP interconnection."
> >
> > Is that OK with you?
> >
> >>
> >> * Agree we should stay out of the VPN world.
> >
> > [Med] Glad to hear that.
> >
> >>
> >> Paolo
> >>
> >>
> >> On 18/3/25 07:41, Job Snijders wrote:
> >>> Dear all,
> >>>
> >>> Our incoming Area Director Med Boucadair requested the GROW
> >> working
> >>> group to re-evaluate its charter and update where needed.
> >>>
> >>> Perhaps intuitively, in an update of the GROW charter, we
> ought
> >> to
> >>> make sure we capture what this working group is working on.
> >>>
> >>> A draft proposal is available here:
> >>>
> >>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> >> gith
> >>> ub.com%2Fboucadair%2FWG-Charters%2Fblob%2Fmain%2Fgrow-
> >> 032025.md&data=0
> >>>
> >>
> 5%7C02%7Cmohamed.boucadair%40orange.com%7C8ae8121d61a746024eab08dd
> >> 7383
> >>>
> >>
> 4a5c%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6387937299058805
> >> 52%7
> >>>
> >>
> CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCI
> >> sIlA
> >>>
> >>
> iOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=V
> >> ZA%2
> >>> BbpaA9g1DqiLUHrxk9ZDA7D%2B%2FsUaRTcZTVf4Syk0%3D&reserved=0
> >>>
> >>> Your comments and feedback are most welcome!
> >>>
> >>> Kind regards,
> >>>
> >>> Job & Chris
> >>> co-chairs GROW
> >>>
> >>> _______________________________________________
> >>> GROW mailing list -- [email protected]
> >>> To unsubscribe send an email to [email protected]
> >>
> >> _______________________________________________
> >> GROW mailing list -- [email protected]
> >> To unsubscribe send an email to [email protected]
> >
> __________________________________________________________________
> ____
> > ______________________________________
> > 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.
> >
____________________________________________________________________________________________________________
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