Re: [Drip] Revised Abstract -- Re: I-D Action: draft-ietf-drip-rid-18.txt

[Robert Moskowitz <[e-mail]>]

On 4/4/22 11:10, [e-mail] wrote:
> Standard
>
> Hi Bob,
>
> The easiest fix would to go simply go for:
>
> ==
>
> NEW:
>
>    This document describes the use of Hierarchical Host Identity Tags
>
> (HHITs) as self-asserting IPv6 addresses and thereby a trustable
>
>    identifier for use as the Unmanned Aircraft System Remote
>
>    Identification and tracking (UAS RID).
>
>    This document updates RFC7401 and RFC 7343.
>
> ==
>

Ok.  Don't bury rfcs in abstract content.

> … but I wanted us to be explicit whether we are modifying any text 
> from these RFCs or we are just extending them.
>

extends 7401 and updates 7343.  I will look at fixing Intro per below 
comment.

> Please note that the introduction only says:
>
> ==
>
>    This addition of hierarchy to HITs requires updates to both [RFC7401]
>
> and [RFC7343].
>
> ==
>
> Cheers,
>
> Med
>
> *De :* Tm-rid <[e-mail]> *De la part de* Robert Moskowitz
> *Envoyé :* lundi 4 avril 2022 16:26
> *À :* BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> *Cc :* [e-mail]
> *Objet :* [Drip] Revised Abstract -- Re: I-D Action: 
> draft-ietf-drip-rid-18.txt
>
> Removing citations and not exploding the following text are at odds, 
> as I was instructed that the abstract needs to say it is updating 
> prior rfcs.  I would have to dig to find out where this was added, but 
> lets look at this:
>
>    This document describes the use of Hierarchical Host Identity Tags
>    (HHITs), updating both [RFC7401] and [RFC7343], as self-asserting
>    IPv6 addresses and thereby a trustable identifier for use as the
>    Unmanned Aircraft System Remote Identification and tracking (UAS
>    RID).
>
> updating both HIPv2 and ORCHIDv2  ???
>
> What are those, do I expand them to Host Identity Protocol version 2 
> and Overlay Routable Cryptographic Hash Identifiers Version 2  ???
>
> or
>
> updating existing standards defining the Host Identity Tag (HIT) and 
> its hash(ed) construction  ???
>
> The Introduction explains what and why Hierarchical Host Identity Tags 
> and thus needing to update 7401 and 7343.  How these rfcs are updated 
> is covered in later sections.
>
> This is probably the hardest comment to resolved based on prior 
> comments...
>
> thanks
>
> On 4/1/22 09:07, [e-mail] wrote:
>
>     Rob,
>
>     Please find below my comments to -18:
>
>      1. pdf:
>         https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.pdf
>         <https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.pdf>
>      2. doc:
>         https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-drip-rid-18-rev%20Med.doc
>
>
>     Thank you.
>
>     Cheers,
>
>     Med
>
>     *De :* Tm-rid <[e-mail]>
>     <mailto:[e-mail]> *De la part de*
>     [e-mail]
>     *Envoyé :* vendredi 1 avril 2022 09:41
>     *À :* Robert Moskowitz <[e-mail]>
>     <mailto:[e-mail]>; [e-mail]
>     *Objet :* Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt
>
>     Hi Bob, all,
>
>     Thank you for implementing the list of agreed changes
>     (https://mailarchive.ietf.org/arch/msg/tm-rid/K1tOOlHcdsz1RdMZXsahP2qrBvA/).
>
>     I invite everyone to carefully look into this version and share
>     any remaining concern by ** April, 07 **.
>
>     Absent any follow-up, we will request publication for this
>     document next Friday 08/04.
>
>     If we hear back from IANA before then, Rob will take care of the
>     comments. If not, IANA-related comments will be addressed in due
>     time (IETF LC).
>
>     As I already reviewed the document several times, I may have only
>     nits/minor fixes that I will directly share with Rob.
>
>     Cheers,
>
>     Med
>
>     *De :* Tm-rid <[e-mail]> *De la part de* Robert
>     Moskowitz
>     *Envoyé :* jeudi 31 mars 2022 17:50
>     *À :* [e-mail]
>     *Objet :* Re: [Drip] I-D Action: draft-ietf-drip-rid-18.txt
>
>     Fixed outstanding items of supporting 8-bit HHIT Suite ID. Please
>     check out that I now have this all done. Particularly sections 4.2
>     and 5.
>
>     Moved HID registration to drip-registries (and changed reference
>     to ietf-drip-registries!).  That is no longer asking ICAO, here,
>     to manage RAA space.
>
>     Some other cleanup, please look at diff.
>
>     Still to do:  waiting for IANA review.  So I anticipate a -19
>
>     On 3/31/22 11:45, [e-mail] wrote:
>
>           
>
>         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 Entity Tag (DET) for Unmanned Aircraft System Remote Identification (UAS RID)
>
>                  Authors         : Robert Moskowitz
>
>                                    Stuart W. Card
>
>                                    Adam Wiethuechter
>
>                                    Andrei Gurtov
>
>           Filename        : draft-ietf-drip-rid-18.txt
>
>           Pages           : 33
>
>           Date            : 2022-03-31
>
>           
>
>         Abstract:
>
>             This document describes the use of Hierarchical Host Identity Tags
>
>             (HHITs), updating both [RFC7401] and [RFC7343], as self-asserting
>
>             IPv6 addresses and thereby a trustable identifier for use as the
>
>             Unmanned Aircraft System Remote Identification and tracking (UAS
>
>             RID).  Within the context of RID, HHITs will be called DRIP Entity
>
>             Tags (DET).  HHITs self-attest to the included explicit hierarchy
>
>             that provides Registrar discovery for 3rd-party identifier
>
>             attestation.
>
>           
>
>           
>
>         The IETF datatracker status page for this draft is:
>
>         https://datatracker.ietf.org/doc/draft-ietf-drip-rid/
>
>           
>
>         There is also an HTML version available at:
>
>         https://www.ietf.org/archive/id/draft-ietf-drip-rid-18.html
>
>           
>
>         A diff from the previous version is available at:
>
>         https://www.ietf.org/rfcdiff?url2=draft-ietf-drip-rid-18
>
>           
>
>           
>
>         Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>
>           
>
>           
>
>     -- 
>     Robert Moskowitz
>     Owner
>     HTT Consulting
>     C: 248-219-2059
>     F: 248-968-2824
>     E: [e-mail]
>
>     There's no limit to what can be accomplished if it doesn't matter
>     who gets the credit
>
>     _________________________________________________________________________________________________________________________
>
>       
>
>     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.
>
>     _________________________________________________________________________________________________________________________
>
>     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.
>
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>

-- 
Standard Robert Moskowitz
Owner
HTT Consulting
C:248-219-2059
F:248-968-2824
E:[e-mail]

There's no limit to what can be accomplished if it doesn't matter who 
gets the credit