Re: [Drip] (AD review) RE: I-D Action: draft-ietf-drip-arch-22.txt:

Med,

Thank you for your reminder even if I know the diff tool and the next step: IETF last call.

This is the IETF week as we all know, so hyper busy from 0800 to 2000 with meetings, but I managed to review the diff:
- many of my suggestions were simply ignored even if several editorial ones were implemented.
- still wondering why FAA is not prefixed by USA-based but up to the authors, also wondering about the lack of explanation about "commercial", ...
- section 8 still looks like a piggy-back addition
- ...

All in all, I am not confident that the document will have an easy ride for the IETF last call and later for an IESG evaluation. But, as the WG and the chairs seem to think that the document is ready for publication, I will shortly start the IETF Last Call.

See you tomorrow at the DRIP WG meeting at IETF-113,

Regards,

-éric

-----Original Message-----
From: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Date: Tuesday, 22 March 2022 at 07:51
To: Eric Vyncke <evyncke@cisco.com>
Cc: "tm-rid@ietf.org" <tm-rid@ietf.org>
Subject: (AD review) RE: I-D Action: draft-ietf-drip-arch-22.txt: 

    Hi Éric,

    Many thanks for your careful review which enhanced this specification.

    Please use this diff to track the changes since your review: https://www.ietf.org/rfcdiff?url1=draft-ietf-drip-arch-20&url2=draft-ietf-drip-arch-22

    Looking forward to see this draft in the IETF LC SOON :-)

    Cheers,
    Med 

    > -----Message d'origine-----
    > De : I-D-Announce <i-d-announce-bounces@ietf.org> De la part de
    > internet-drafts@ietf.org
    > Envoyé : lundi 21 mars 2022 20:44
    > À : i-d-announce@ietf.org
    > Cc : tm-rid@ietf.org
    > Objet : I-D Action: draft-ietf-drip-arch-22.txt
    > 
    > 
    > A New Internet-Draft is available from the on-line Internet-Drafts
    > directories.
    > This draft is a work item of the Drone Remote ID Protocol WG of the
    > IETF.
    > 
    >         Title           : Drone Remote Identification Protocol (DRIP)
    > Architecture
    >         Authors         : Stuart W. Card
    >                           Adam Wiethuechter
    >                           Robert Moskowitz
    >                           Shuai Zhao
    >                           Andrei Gurtov
    > 	Filename        : draft-ietf-drip-arch-22.txt
    > 	Pages           : 27
    > 	Date            : 2022-03-21
    > 
    > Abstract:
    >    This document describes an architecture for protocols and services to
    >    support Unmanned Aircraft System (UAS) Remote Identification (RID)
    >    and tracking, plus UAS RID-related communications.  This architecture
    >    adheres to the requirements listed in the DRIP Requirements document
    >    (RFC9153).
    > 
    > 
    > The IETF datatracker status page for this draft is:
    > https://datatracker.ietf.org/doc/draft-ietf-drip-arch/
    > 
    > There is also an htmlized version available at:
    > https://datatracker.ietf.org/doc/html/draft-ietf-drip-arch-22
    > 
    > A diff from the previous version is available at:
    > https://www.ietf.org/rfcdiff?url2=draft-ietf-drip-arch-22
    > 
    > 
    > Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
    > drafts
    > 
    > 
    > _______________________________________________
    > I-D-Announce mailing list
    > I-D-Announce@ietf.org
    > https://www.ietf.org/mailman/listinfo/i-d-announce
    > Internet-Draft directories: http://www.ietf.org/shadow.html or
    > ftp://ftp.ietf.org/ietf/1shadow-sites.txt

    _________________________________________________________________________________________________________________________

    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.