Re: [Drip] I-D Action: draft-ietf-drip-auth-05.txt

"We" in this case being first ASTM to set up the process (after F3411-22
passes ballot), then IETF to register codes via that process.

On Tue, Mar 8, 2022, 13:08 Adam Wiethuechter <
adam.wiethuechter@axenterprize.com> wrote:

> Hi Med,
>
> This is an error. We have not contacted ICAO about this and AFAIK they
> have yet to stand up the registration process. I will fix the sentence
> accordingly to match Section 8.
>
> --------
> 73,
> Adam T. Wiethuechter
> Software Engineer; AX Enterprize, LLC
> ------------------------------
> *From:* mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> *Sent:* Tuesday, March 8, 2022 3:37 AM
> *To:* draft-ietf-drip-auth@ietf.org <draft-ietf-drip-auth@ietf.org>
> *Cc:* tm-rid@ietf.org <tm-rid@ietf.org>
> *Subject:* RE: I-D Action: draft-ietf-drip-auth-05.txt
>
> Hi Adam, all,
>
> FYI, I requested a security review for this version to make sure that
> potential security issues are tagged early in the process. I indicated
> March 22 as a tentative date, but this will depend on the reviewers
> availability.
>
> One quick question about ICAO-related matters:
>
> The draft says:
> ==
>    The SAM Type field is maintained by the International Civil Aviation
>    Organization (ICAO) and for DRIP four are allocated:
> ==
>
> but also:
>
> ==
> 8.  ICAO Considerations
>
>    DRIP requests the following SAM Type's to be allocated:
> ==
>
> Which seems to be conflicting.
>
> Can you please report about the currents status of these assignments? If
> the assignments are already made, then removing Section 8 would make
> sense.
>
> Thanks.
>
> 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 7 mars 2022 20:27
> > À : i-d-announce@ietf.org
> > Cc : tm-rid@ietf.org
> > Objet : I-D Action: draft-ietf-drip-auth-05.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           : DRIP Authentication Formats & Protocols for
> > Broadcast Remote ID
> >         Authors         : Adam Wiethuechter
> >                           Stuart Card
> >                           Robert Moskowitz
> >        Filename        : draft-ietf-drip-auth-05.txt
> >        Pages           : 48
> >        Date            : 2022-03-07
> >
> > Abstract:
> >    This document describes how to include trust into the ASTM Remote ID
> >    specification defined in ASTM F3411 under Broadcast Remote ID (RID).
> >    It defines a few message schemes (sent within the Authentication
> >    Message) that can be used to authenticate past messages sent by a
> >    unmanned aircraft (UA) and provide proof of UA trustworthiness even
> >    in the absence of Internet connectivity at the receiving node.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-drip-auth/
> >
> > There is also an HTML version available at:
> > https://www.ietf.org/archive/id/draft-ietf-drip-auth-05.html
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-drip-auth-05
> >
> >
> > 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.
>
>