Dear Mohamed, thank you for your detailed feedback.
With best regards, Tobias On Tue, 2025-04-15 at 15:20 +0000, [email protected] wrote: > Hi Tobias, > > I used "e.g.," on purpose in my message to say that this is an > example to tweak the text. You may have a better inspiration ;-) > > All I-Ds includes a disclaimer about how they are intended to be > used/cited/etc. As such, the caution you included is redundant with > that. > > More importantly, the point of this change is to let your main > bgpopsecupd document progress in the publication process (and thus be > published as an RFC) and not be stale waiting for the two other two > pieces. This is helping you navigating in the process. Hope this > helps. > > Thank you, Tobias. > > Cheers, > Med > > > -----Message d'origine----- > > De : Tobias Fiebig <[email protected]> > > Envoyé : mardi 15 avril 2025 17:04 > > À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; > > [email protected] > > Objet : Re: [GROW] Re: draft-ietf-grow-bgpopsecupd-06: Normative > > dependency on many I-Ds > > > > > > Dear Mohamed, > > > [Med] You can delete that paragraph from Section 6 but update > > Section > > > 2, e.g., as follows: > > > > > > OLD: > > > > > > Instead, operators > > > are advised to consult applicable documentation and > > contemporary > > > informational documents describing implementation specifics. > > > > > > NEW: > > > > > > Instead, operators > > > are advised to consult applicable documentation and > > contemporary > > > informational documents describing implementation specifics > > (e.g., > > > [I-D.ietf-grow-routing-ops-sec-inform] and [I-D.ietf-grow- > > routing- > > > ops-terms]). > > > > > > > > Thank you for providing more detailed instructions on the changes > > you want to see implemented. I will of course implement that change > > immediately. > > > > However, would you mind sharing the reasoning behind your decision? > > Taking the path of documenting technical guidance and terminology > > in I- Ds and leveraging the expiration feature to ensure that we do > > not end up in a situation where we have stale technical guidance > > again had been discussed for over a year in GROW now. > > > > Of course, I do not want to question your authority here; Instead, > > I assume that you accounted for several considerations I may not > > even be aware of. As such, I believe that sharing further details > > would tremendously help me improve personally and be a more > > effective contributor on team outputs in the future. > > > > With best regards, > > Tobias > > > > > > -- > > Dr.-Ing. Tobias Fiebig > > T +31 616 80 98 99 > > M [email protected] > > Pronouns: he/him/his > > _____________________________________________________________________ > _______________________________________ > 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. -- Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M [email protected] Pronouns: he/him/his _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
