Re: [Drip] WGLC for draft-ietf-drip-arch(Internet mail)

[[e-mail]]

Hi Shuai,

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Tm-rid [mailto:[e-mail]] De la part de
> shuaiizhao(Shuai Zhao)
> Envoyé : lundi 8 mars 2021 05:47
> À : [e-mail]
> Objet : Re: [Drip] WGLC for draft-ietf-drip-arch(Internet mail)
> 
> Hi Stephane, Thanks for reviewing the draft. Please see reply inline.
> 
> Best,
> Shuai
> 
> On 2/27/21, 2:48 AM, "Tm-rid on behalf of Stephane Bortzmeyer" <tm-
> [e-mail] on behalf of [e-mail]> wrote:
> 
>     On Tue, Feb 23, 2021 at 09:57:22AM -0500,
>      Daniel Migault <[e-mail]> wrote
>      a message of 54 lines which said:
> 
>     > This email starts a WGLC for  draft-ietf-drip-arch available
> here:
>     >  https://datatracker.ietf.org/doc/html/draft-ietf-drip-arch-10
>     >
>     > Please review the document and provide your feed back /
> comments by March
>     > 9.
> 
>     I've read -11. Drones are clearly not my area of expertise. The
> draft
>     is hard to follow, with a number of acronyms I'm not familiar
>     with. Some are in section "3.2.  Abbreviations", some are defined
> at
>     first use. There is certainly a reason for this difference but it
> does
>     not help the reader.
> 
> Shuai/ There were prior comments about two little definitions and too
> many TLAs. And WG has decided the architecture draft should be an
> independent draft without referring to the reqs- .

[Med] I may miss your point but the requirements I-D is our reference for these matters. Section 2.2 of draft-ietf-drip-reqs says the following:   

   This section defines a set of terms expected to be used in DRIP
   documents.  This list is meant to be the DRIP terminology reference.

This is ACKed in the arch I-D: 

==
This document uses terms defined in [I-D.ietf-drip-reqs]
==

To address Stéphane's comment, I suggest to remove Section 3.2 from the document + check that all these entries are present in I-D.ietf-drip-reqs.  

 Those are the
> reasons we explicitly give full names for acronyms. And I agree there
> are lots of them. Do you have specific TLAs you felt confused about?
> We can make it clear in the next revision.

[Med] I interpret Stéphane's comment as that the document need to be consistent. I think this can be addressed by my proposal above and expand on first use for all of them. Thanks.  

 

_________________________________________________________________________________________________________________________

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.