[Roll] Re: [GROW] Fwd: RFC5706bis => draft-opsarea -rfc5706bis posted
Ketan Talaulikar <[email protected]> Thu, 10 Apr 2025 13:48:44 +0530
| Newsgroups | gmane.network.protocols.rpl,gmane.ietf.pce,gmane.ietf.ccamp,gmane.ietf.opsawg |
|---|---|
| Message-ID | <CAH6gdPyM-WUb2Pjxuq6+4M90531rU5z9L=4L8Sd1oG=f8TWuwg@mail.gmail.com> |
--===============8771268147486705632== Content-Type: multipart/alternative; boundary="000000000000b765500632683ccf" --000000000000b765500632683ccf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable FYI and a request to monitor this work as it will have implications on upcoming/ongoing work (and documents) in the routing areas well. Please contribute to the discussion on the opsawg mailing list. Thanks, Ketan On Wed, Apr 9, 2025 at 4:19=E2=80=AFPM Benoit Claise <benoit.claise=3D 40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]> wrote: > Dear all, > > The bcc option mentioned below doesn't work, surely because I reached the > maximum amount of recipients. > Hence this forwarded message to each individual OPS WG. > > Regards, Benoit > > > -------- Forwarded Message -------- > Subject: Fwd: RFC5706bis =3D> draft-opsarea-rfc5706bis posted > Resent-Date: Tue, 8 Apr 2025 11:11:41 -0700 > Resent-From: [email protected] > Resent-To: [email protected], [email protected], > [email protected], [email protected], [email protected], > thomas.graf-Zc0CTiu5wcBWk0Htik3J/[email protected], [email protected] > Date: Tue, 8 Apr 2025 20:09:23 +0200 > From: Benoit Claise <benoit.claise=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]> > <benoit.claise=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]> > To: opsawg <[email protected]> <[email protected]> > CC: [email protected] <[email protected]> <[email protected]>, > [email protected], ops-ads <[email protected]> > <[email protected]> > > Dear all, > > Sorry for sending this email to all OPS WGs (bcc'ed), however, we need to > reach all of you in the OPS area. > Below, you will see our AD's guidance to update the RFC 5706 "Guidelines > for Considering Operations and Management of New Protocols and Protocol > Extensions" > > Yes, it's about time to update this RFC, published in 2009, with the idea= l > end goal to have "Manageability Considerations" section all IETF drafts. = As > Med mentioned on the OPSAWG mailing list: "We need to find the right > balance between providing clear guidance while avoiding some rigidity. We > will explore that path together with other areas." > Med will be sponsoring this document, as BCP, while RFC 5706 was publishe= d > as Informational. > > Today, we passed the first milestone, with the publication of: > > A new version of Internet-Draft draft-opsarea-rfc5706bis-00.txt has been > successfully submitted by Benoit Claise and posted to the > IETF repository. > > Name: draft-opsarea-rfc5706bis > Revision: 00 > Title: Guidelines for Considering Operations and Management of New Pro= tocols and Protocol Extensions > Date: 2025-04-08 > Group: Individual Submission > Pages: 36 > URL: https://www.ietf.org/archive/id/draft-opsarea-rfc5706bis-00.txt > Status: https://datatracker.ietf.org/doc/draft-opsarea-rfc5706bis/ > HTML: https://www.ietf.org/archive/id/draft-opsarea-rfc5706bis-00.htm= l > HTMLized: https://datatracker.ietf.org/doc/html/draft-opsarea-rfc5706bis > > > Abstract: > > New protocols or protocol extensions are best designed with due > consideration of the functionality needed to operate and manage the > protocols. Retrofitting operations and management is sub-optimal. > The purpose of this document is to provide guidance to authors and > reviewers of documents that define new protocols or protocol > extensions regarding aspects of operations and management that should > be considered. > > This document obsoletes RFC 5706. > > > What are the diffs compared to RFC5706? At this stage, not much: "same > content as RFC5706. The only changes are the authors list and document > track", as Med mentioned below. > As this document is AD-sponsored, it now appears under > https://datatracker.ietf.org/ag/opsarea/documents/ > > What do we expect from all of you? > - please review the plan below. Feel free to comment. > - we would like to know about some specific questions/open > issues/improvements regarding the "Manageability Considerations" for your > WG > - PLEASE don't reply to all, as the discussion should happen on the OSPAW= G > mailing list. If you prefer, feel free to reply only to the contributors, > in cc. > > Next, we will set up a github repo, populate the open issues, and start > resolving them. > > Regards, Benoit on behalf of the contributors. > > -------- Forwarded Message -------- > Subject: [OPSAWG]RFC5706-Refresh: Action Plan > Date: Fri, 4 Apr 2025 06:22:36 +0000 > From: [email protected] > To: [email protected] <[email protected]> <[email protected]>, [email protected] > <[email protected]> <[email protected]> > CC: [email protected] <[email protected]> <[email protected]> > > Hi all, > > > > First of all, many thanks to all the expressions of interest and comments > sent on the list and also in private for this work. > > > > As indicated early this week, please find below the proposed action plan > for the refresh of the =E2=80=9CGuidelines for Considering Operations and > Management=E2=80=9D: > > > > - I will be sponsoring the document with joint LCs in all OPS WGs with > the expected outcome to produce a ** BCP ** > - The reference discussion venue will be OPSDIR + OPSAWG > - Week of April 7th: > - Authors to submit draft-ietf-opsarea-rfc5706bis-00 with the same > content as RFC5706. The only changes are the authors list and docum= ent > track. See attached. > - Authors to send a call for inputs to all OPS WGs + reminder of > the discussion venue. > - OPS AD to send a note to all ADs to seek for cross-area inputs. > - Authors to release revisions that address the initial list of change > items and any comment from the call for inputs. > - More clarity on the terminology and leverage the work led by > Adrian in NMOP > - IM part > - More guidance on the importance of DMs > - Soften the MIB part + IESG statement in MIBs > - Add more YANG > - Generalize the approach in RFC6123/ Manageability Considerations > Section in all IETF Specs > - IETF#123 Madrid: Present status and pending issues in OPSAREA > Session. A slot is already booked for this. > - Post IETF#123 > - Authors to send reminder of call for inputs to all OPS WGs or > follow-ups to specific points raised there in the first call. > - Authors to release revisions to address pending issues and any > received comments. > - 09/2025: OPS AD to issue a LC shared in all OPS WGs. > - 10/2025: IETF LC > > > > Here is the initial authors list: > > > > - Beno=C3=AEt Claise > - Joe Clarke > - Adrian Farrel > - Thomas Graf > - Samier Barguil > - Carlos Pignataro > - Ran Chen > > > > @authors: Please find attached a -00 of the text (md, xml, txt). I have a > preference for the use of md + set a gitbub repo but I let you > self-organize. You are holding the pen now :-) > > > > Please let me know if you have any comment. > > > > Thank you. > > > > Cheers, > > Med > > _________________________________________________________________________= ___________________________________ > Ce message et ses pieces jointes peuvent contenir des informations confid= entielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re= cu 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 o= u falsifie. Merci. > > This message and its attachments may contain confidential or privileged i= nformation 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 de= lete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have bee= n modified, changed or falsified. > Thank you. > > _______________________________________________ > GROW mailing list -- [email protected] > To unsubscribe send an email to [email protected] > --000000000000b765500632683ccf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">FYI and a request to monitor this work as it will have imp= lications on upcoming/ongoing work (and documents) in the routing areas wel= l.<div><br></div><div>Please contribute to the discussion on the opsawg mai= ling list.</div><div><br></div><div>Thanks,</div><div>Ketan<br></div></div>= <br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class= =3D"gmail_attr">On Wed, Apr 9, 2025 at 4:19=E2=80=AFPM Benoit Claise <be= noit.claise=3D<a href=3D"mailto:40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]">40huawei.com@d= marc.ietf.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" sty= le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi= ng-left:1ex"><u></u> =20 =20 =20 <div style=3D"overflow-wrap: break-word;" lang=3D"FR"> Dear all,<br> <br> The bcc option mentioned below doesn't work, surely because I reached the maximum amount of recipients.<br> Hence this forwarded message to each individual OPS WG.<br> <br> Regards, Benoit<br> <div><br> <br> -------- Forwarded Message -------- <table cellpadding=3D"0" cellspacing=3D"0" border=3D"0"> <tbody> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>Subject: </th> <td>Fwd: RFC5706bis =3D> draft-opsarea-rfc5706bis posted</td= > </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>Resent-Date: </th> <td>Tue, 8 Apr 2025 11:11:41 -0700</td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>Resent-From: </th> <td><a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a></td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>Resent-To: </th> <td><a href=3D"mailto:[email protected]" target=3D"_blank">ad= [email protected]</a>, <a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>, <a href=3D"mailto:[email protected]" target=3D"_blank">chen= [email protected]</a>, <a href=3D"mailto:[email protected]" target=3D"_blank= ">[email protected]</a>, <a href=3D"mailto:[email protected]" target=3D"_blank">jclark= [email protected]</a>, <a href=3D"mailto:thomas.graf-Zc0CTiu5wcBWk0Htik3J/[email protected]" target=3D"_bla= nk">thomas.graf-Zc0CTiu5wcBWk0Htik3J/[email protected]</a>, <a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a></td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>Date: </th> <td>Tue, 8 Apr 2025 20:09:23 +0200</td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>From: </th> <td>Benoit Claise <a href=3D"mailto:benoit.claise=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]= " target=3D"_blank"><benoit.claise=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]></a>= </td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>To: </th> <td>opsawg <a href=3D"mailto:[email protected]" target=3D"_blank"= ><[email protected]></a></td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>CC: </th> <td><a href=3D"mailto:[email protected]" target=3D"_blank">ops-d= [email protected]</a> <a href=3D"mailto:[email protected]" target=3D"_blank"><o= [email protected]></a>, <a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>, ops-ads <a href=3D"mailto:[email protected]" target=3D"_blank"><ops= [email protected]></a></td> </tr> </tbody> </table> <br> <br> =20 <div>Dear all,<br> <br> Sorry for sending this email to all OPS WGs (bcc'ed), however, we need to reach all of you in the OPS area.<br> Below, you will see our AD's guidance to update the RFC 5706 &q= uot;<span>Guidelines for Considering Operations and Management of</span> <span>New Protocols and Protocol Extensions"<br> <br> Yes, it's about time to update this RFC, published in 2009, with the ideal end goal to have "Manageability Consideration= s" section all IETF drafts. As Med mentioned on the OPSAWG mailing li</span>st: "We need to find the right balance between providing clear guidance while avoiding some rigidity. We will explore that path together with other areas."<br> <span>Med will be sponsoring this document, as BCP, while RFC 5706 was published as Informational. <br> <br> Today, we passed the first milestone, with the publication of:<br= > </span> <blockquote> <pre>A new version of Internet-Draft draft-opsarea-rfc5706bis-00.= txt has been successfully submitted by Benoit Claise and posted to the IETF repository. Name: draft-opsarea-rfc5706bis Revision: 00 Title: Guidelines for Considering Operations and Management of New Proto= cols and Protocol Extensions Date: 2025-04-08 Group: Individual Submission Pages: 36 URL: <a href=3D"https://www.ietf.org/archive/id/draft-opsarea-rfc5706b= is-00.txt" target=3D"_blank">https://www.ietf.org/archive/id/draft-opsarea-= rfc5706bis-00.txt</a> Status: <a href=3D"https://datatracker.ietf.org/doc/draft-opsarea-rfc5706= bis/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-opsarea-rfc5= 706bis/</a> HTML: <a href=3D"https://www.ietf.org/archive/id/draft-opsarea-rfc5706b= is-00.html" target=3D"_blank">https://www.ietf.org/archive/id/draft-opsarea= -rfc5706bis-00.html</a> HTMLized: <a href=3D"https://datatracker.ietf.org/doc/html/draft-opsarea-rf= c5706bis" target=3D"_blank">https://datatracker.ietf.org/doc/html/draft-ops= area-rfc5706bis</a> Abstract: New protocols or protocol extensions are best designed with due consideration of the functionality needed to operate and manage the protocols. Retrofitting operations and management is sub-optimal. The purpose of this document is to provide guidance to authors and reviewers of documents that define new protocols or protocol extensions regarding aspects of operations and management that should be considered. This document obsoletes RFC 5706.</pre> </blockquote> <span><br> </span>What are the diffs compared to RFC5706? At this stage, not much: "same content as RFC5706. The only changes are the authors list and document track"<span>, as Med mentioned below. <br> As this document is AD-sponsored, it now appears under <a href=3D= "https://datatracker.ietf.org/ag/opsarea/documents/" target=3D"_blank">http= s://datatracker.ietf.org/ag/opsarea/documents/</a><br> <br> What do we expect from all of you?<br> - please review the plan below. Feel free to comment.<br> - we would like to know about some specific questions/open issues/improvements regarding the=C2=A0</span><span>"Managea= bility Considerations"</span><span> for your WG<br> - PLEASE don't reply to all, as the discussion should happen on the OSPAWG mailing list. If you prefer, feel free to reply only to the contributors, in cc.<br> <br> Next, we will set up a github repo, populate the open issues, and start resolving them.<br> <br> Regards, Benoit on behalf of the contributors.</span><br> <div><br> -------- Forwarded Message -------- <table cellpadding=3D"0" cellspacing=3D"0" border=3D"0"> <tbody> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>Subject: </th> <td>[OPSAWG]RFC5706-Refresh: Action Plan</td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>Date: </th> <td>Fri, 4 Apr 2025 06:22:36 +0000</td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>From: </th> <td><a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a></td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>To: </th> <td><a href=3D"mailto:[email protected]" target=3D"_blank">op= [email protected]</a> <a href=3D"mailto:[email protected]" target=3D"_blank"><= [email protected]></a>, <a href=3D"mailto:[email protected]" target=3D"_blank">ops= [email protected]</a> <a href=3D"mailto:[email protected]" target=3D"_blank"><= ;[email protected]></a></td> </tr> <tr> <th valign=3D"BASELINE" align=3D"RIGHT" nowrap>CC: </th> <td><a href=3D"mailto:[email protected]" target=3D"_blank">o= [email protected]</a> <a href=3D"mailto:[email protected]" target=3D"_blank">&= lt;[email protected]></a></td> </tr> </tbody> </table> <br> <br> =20 =20 <div> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier= New"">Hi all,<u></u><u></u></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier= New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">First of all, many thanks to all the expressions of interest and comments sent on the list and also in private for this work. <u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">As indicated early this week, please find below the proposed action plan for the refresh of the =E2=80=9CGuidelines for Conside= ring Operations and Management=E2=80=9D:<u></u><u></u></span></p= > <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <ul style=3D"margin-top:0cm" type=3D"disc"> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">I will be sponsoring the document with joint LCs in all OPS WGs with the expected outcome to produce a ** BCP **<u></u><u= ></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">The reference discussion venue will be OPSDIR + OPSAWG<u></u>= <u></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">Week of April 7th: <u></u><u></u></span></li> <ul style=3D"margin-top:0cm" type=3D"circle"> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">Authors to submit draft-ietf-opsarea-rfc5706bis-00 with the same content as RFC5706. The only changes are the authors list and document track. See attached.<u></u><u= ></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">Authors to send a call for inputs to all OPS WGs + reminder of the discussion venue.<u></u><u></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">OPS AD to send a note to all ADs to seek for cross-area inputs.<u></u><u></u></span></li> </ul> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">Authors to release revisions that address the initial list of change items and any comment from the call for inputs.<u>= </u><u></u></span></li> <ul style=3D"margin-top:0cm" type=3D"circle"> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">More clarity on the terminology and leverage the work led by Adrian in NMOP<u></u><u></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">IM part<u></u><u= ></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">More guidance on the importance of DMs<u></u><u></u></span><= /li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">Soften the MIB part + IESG statement in MIBs<u></u><u></u></sp= an></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">Add more YANG<u></u><u></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">Generalize the approach in RFC6123/</span><span lang=3D"EN-US"> </= span><span lang=3D"EN-US" style=3D"font-family:"Courier New"">Man= ageability Considerations Section in all IETF Specs<u></u><u></u><= /span></li> </ul> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">IETF#123 Madrid: Present status and pending issues in OPSAREA Session. A slot is already booked for this.<u></u><u></u>= </span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">Post IETF#123<u></u><u></u></span></li> <ul style=3D"margin-top:0cm" type=3D"circle"> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">Authors to send reminder of call for inputs to all OPS WGs or follow-ups to specific points raised there in the first call.<u></u><u></u></span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span la= ng=3D"EN-US" style=3D"font-family:"Courier New"">Authors to release revisions to address pending issues and any received comments.<u></u><u></u></span></li> </ul> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">09/2025: OPS AD to issue a LC shared in all OPS WGs.<u></u><u></u>= </span></li> <li class=3D"MsoNormal" style=3D"margin-left:18pt"><span lang= =3D"EN-US" style=3D"font-family:"Courier New"">10/2025: IETF LC<u></u><u></u></span></li> </ul> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">Here is the initial authors list:<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <ul style=3D"margin-top:0cm" type=3D"disc"> <li style=3D"margin-left:0cm"><span style=3D"font-family:&quo= t;Courier New"">Beno=C3=AEt Claise<u></u><u></u></span></li> <li style=3D"margin-left:0cm"><span style=3D"font-family:&quo= t;Courier New"">Joe Clarke<u></u><u></u></span></li> <li style=3D"margin-left:0cm"><span style=3D"font-family:&quo= t;Courier New"">Adrian Farrel<u></u><u></u></span></li> <li style=3D"margin-left:0cm"><span style=3D"font-family:&quo= t;Courier New"">Thomas Graf<u></u><u></u></span></li> <li style=3D"margin-left:0cm"><span style=3D"font-family:&quo= t;Courier New"">Samier Barguil<u></u><u></u></span></li> <li style=3D"margin-left:0cm"><span style=3D"font-family:&quo= t;Courier New"">Carlos Pignataro<u></u><u></u></span></li> <li style=3D"margin-left:0cm"><span style=3D"font-family:&quo= t;Courier New"">Ran Chen<u></u><u></u></span></li> </ul> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">@authors: Please find attached a -00 of the text (md, xml, txt). I have a preference for the use of md + set a gitbub repo but I let you self-organize. You are holding the pen now :-)<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">Please let me know if you have any comment.<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">Thank you.<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New""><u></u>=C2=A0<u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">Cheers,<u></u><u></u></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-famil= y:"Courier New"">Med<u></u><u></u></span></p> </div> <pre>____________________________________________________________= ________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 message= s 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 inf= ormation 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 dele= te 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.</pre> </div> </div> </div> </div> _______________________________________________<br> GROW mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank">gro= [email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]" targ= et=3D"_blank">[email protected]</a><br> </blockquote></div> --000000000000b765500632683ccf-- --===============8771268147486705632== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUm9sbCBtYWls aW5nIGxpc3QgLS0gcm9sbEBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IHJvbGwtbGVhdmVAaWV0Zi5vcmcK --===============8771268147486705632==--