Re: [Drip] [IANA #1230004] Last Call: <draft-ietf-drip-rid-25.txt> (DRIP Entity Tag (DET) for Unmanned Aircraft System Remote ID (UAS RID)) to Proposed Standard

[Robert Moskowitz <[e-mail]>]

How is this?  Did I leave any off?

    Many thanks to Michael Richardson and Brian Haberman for the iotdir
    review, Magnus Nystrom for the secdir review, Elwyn Davies for genart
    review and DRIP co-chair and draft shepherd, Mohamed Boucadair for
    his extensive comments and help on document clarity.


On 5/13/22 10:40, [e-mail] wrote:
> Re-,
>
> Thanks, Bob.
>
> Please don't forget to add all the directorate reviewers to the Acknowledgments section.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : Robert Moskowitz<[e-mail]>
>> Envoyé : vendredi 13 mai 2022 14:34
>> À : BOUCADAIR Mohamed INNOV/NET<[e-mail]>;
>> [e-mail]
>> Objet : Re: [IANA #1230004] Last Call: <draft-ietf-drip-rid-
>> 25.txt> (DRIP Entity Tag (DET) for Unmanned Aircraft System Remote
>> ID (UAS RID)) to Proposed Standard
>>
>> Med,
>>
>> I will wait until noonish EDT today to push out -26.  Time for
>> IANA to respond and responses to the two open last call comments.
>>
>> Bob
>>
>> On 5/13/22 02:08,[e-mail]  wrote:
>>> Hi Sabrina, all,
>>>
>>>> Sixth, a new subregistry will be created called the EdDSA Curve
>> Label
>>>> on the Host Identity Protocol (HIP) Parameters registry page
>> located
>>>> at:
>>>>
>>>> https://www.iana.org/assignments/hip-parameters
>>>>
>>>> There are initial registrations in the subregistry as follows:
>>>>
>>>> Algorithm    Curve            Values		Reference
>>>>
>>>> EdDSA        RESERVED         0				[ RFC-to-be ]
>>>> EdDSA        EdDSA25519       1 			[RFC8032]
>>>> EdDSA        EdDSA25519ph     2 			[RFC8032]
>>>> EdDSA        EdDSA448         3 			[RFC8032]
>>>> EdDSA        EdDSA448ph       4 			[RFC8032]
>>>>                Unassigned      5-65535
>>>>
>>>> IANA Question: What is the registration procedure for this new
>>>> subregistry?
>>> I suggest we go for IETF Review to be consistent with the
>> registration procedure for "ECDSA Curve Label" under that same
>> registry.
>>> Thank you.
>>>
>>> Cheers,
>>> Med
>>>
>>>> -----Message d'origine-----
>>>> De : Sabrina Tanamal via RT<[e-mail]>  Envoyé :
>>>> vendredi 13 mai 2022 00:36 Cc :[e-mail];[e-mail];
>>>> [e-mail];[e-mail];[e-mail];
>>>> [e-mail];[e-mail];
>> BOUCADAIR
>>>> Mohamed INNOV/NET<[e-mail]>;
>>>> [e-mail]  Objet : [IANA #1230004] Last Call:
>>>> <draft-ietf-drip-rid-25.txt> (DRIP Entity Tag (DET) for
>> Unmanned
>>>> Aircraft System Remote ID (UAS
>>>> RID)) to Proposed Standard
>>>>
>>>> (BEGIN IANA COMMENTS)
>>>>
>>>> IESG/Authors/WG Chairs:
>>>>
>>>> The IANA Functions Operator has completed its review of draft-
>>>> ietf-drip-rid-25. If any part of this review is inaccurate,
>> please
>>>> let us know.
>>>>
>>>> The IANA Functions Operator has a question about one of the
>> actions
>>>> requested in the IANA Considerations section of this document.
>>>>
>>>> We understand that, upon approval of this document, there are
>> eight
>>>> actions which we must complete.
>>>>
>>>> First, in the IANA IPv6 Special-Purpose Address Registry
>> located
>>>> at:
>>>>
>>>> https://www.iana.org/assignments/iana-ipv6-special-registry
>>>>
>>>> a new registration is to be made as follows:
>>>>
>>>> Address Block: TBD (suggested: 2001:30::/28)
>>>> Name: DRIP Entity Tags (DETs) Prefix
>>>> RFC: [ RFC-to-be ]
>>>> Allocation Date: TBD
>>>> Termination Date: N/A
>>>> Source: False
>>>> Destination: False
>>>> Globally Reachable: False
>>>> Reserved-by-Protocol: False
>>>>
>>>> Second, a new registry page will be created called the Drone
>> Remote
>>>> ID Protocol. The Hierarchical HIT (HHIT) Prefixes registry will
>> be
>>>> created on the Drone Remote ID Protocol registry page.
>>>>
>>>> The registration procedure for the registry will be Expert
>> Review as
>>>> defined in RFC8126. There is an initial registration in the new
>>>> registry as follows:
>>>>
>>>> HHIT Use: DET
>>>> Bits: 28
>>>> Value: TBD (suggested: 2001:30::/28)
>>>> Reference: [ RFC-to-be ]
>>>>
>>>> Third, a new registry will be created called the Hierarchical
>> HIT
>>>> (HHIT) Suite ID registry also on the Drone Remote ID Protocol
>>>> registry page.
>>>>
>>>> The registration procedure for the registry will be IETF Review
>> as
>>>> defined in RFC8126. There are initial registrations in the new
>>>> registry as follows:
>>>>
>>>> HHIT Suite          Value	Reference
>>>> RESERVED            0		[ RFC-to-be ]
>>>> RSA,DSA/SHA-256     1    	[RFC7401]
>>>> ECDSA/SHA-384       2    	[RFC7401]
>>>> ECDSA_LOW/SHA-1     3    	[RFC7401]
>>>> EdDSA/cSHAKE128     TBD3 (suggested value 5)   (RECOMMENDED) [
>>>> RFC-to-be ]
>>>> HDA Private Use 1   TBD4 (suggested value 254)	[ RFC-to-be ]
>>>> HDA Private Use 2   TBD5 (suggested value 255)	[ RFC-to-be ]
>>>>
>>>> Fourth, in the CGA Extension Type Tags registry on the
>>>> Cryptographically Generated Addresses (CGA) Message Type Name
>> Space
>>>> registry page located at:
>>>>
>>>> https://www.iana.org/assignments/cga-message-types
>>>>
>>>> a new registration will be made as follows:
>>>>
>>>> CGA Type Tag: 0x00B5 A69C 795D F5D5 F008 7F56 843F 2C40
>>>> Reference: [ RFC-to-be ]
>>>>
>>>> In addition, we will also list this document as an additional
>>>> reference for the CGA Extension Type Tags registry.
>>>>
>>>> Fifth, in the HI Algorithm registry on the Host Identity
>> Protocol
>>>> (HIP) Parameters registry page located at:
>>>>
>>>> https://www.iana.org/assignments/hip-parameters
>>>>
>>>> a new registration will be made as follows:
>>>>
>>>> Value: TDB
>>>> Algorithm Profile: EdDSA
>>>> Reference: [RFC8032][ RFC-to-be ]
>>>>
>>>> IANA notes that the authors suggest a value 13 for this
>> registration.
>>>> Sixth, a new subregistry will be created called the EdDSA Curve
>> Label
>>>> on the Host Identity Protocol (HIP) Parameters registry page
>> located
>>>> at:
>>>>
>>>> https://www.iana.org/assignments/hip-parameters
>>>>
>>>> There are initial registrations in the subregistry as follows:
>>>>
>>>> Algorithm    Curve            Values		Reference
>>>>
>>>> EdDSA        RESERVED         0				[ RFC-to-be ]
>>>> EdDSA        EdDSA25519       1 			[RFC8032]
>>>> EdDSA        EdDSA25519ph     2 			[RFC8032]
>>>> EdDSA        EdDSA448         3 			[RFC8032]
>>>> EdDSA        EdDSA448ph       4 			[RFC8032]
>>>>                Unassigned      5-65535
>>>>
>>>> IANA Question: What is the registration procedure for this new
>>>> subregistry?
>>>>
>>>> Seventh, in the HIT Suite ID registry on the Host Identity
>> Protocol
>>>> (HIP) Parameters registry page located at:
>>>>
>>>> https://www.iana.org/assignments/hip-parameters
>>>>
>>>> a new registration will be made as follows:
>>>>
>>>> Value: TBD
>>>> Suite ID: EdDSA/cSHAKE128
>>>> Reference: [ RFC-to-be ]
>>>>
>>>> IANA notes that the authors suggest a value 5 for this
>> registration.
>>>> Eighth, in the Algorithm Type Field registry on the IPSECKEY
>> Resource
>>>> Record Parameters registry page located at:
>>>>
>>>> https://www.iana.org/assignments/ipseckey-rr-parameters
>>>>
>>>> a new registration will be made as follows:
>>>>
>>>> Value: TBD
>>>> Description: An EdDSA key is present, in the format defined in
>>>> [RFC8080]
>>>> Reference: [ RFC-to-be ]
>>>>
>>>> IANA notes that the authors suggest a value 4 for this
>> registration.
>>>> The IANA Functions Operator understands that these are the only
>>>> actions required to be completed upon approval of this
>> document.
>>>> Note:  The actions requested in this document will not be
>> completed
>>>> until the document has been approved for publication as an RFC.
>> This
>>>> message is meant only to confirm the list of actions that will
>> be
>>>> performed.
>>>>
>>>> Please note that specific values cannot be reserved. However,
>> early
>>>> allocation is available for some types of registrations. For
>> more
>>>> information, please see RFC 7120.
>>>>
>>>> For definitions of IANA review states, please see:
>>>>
>>>> https://datatracker.ietf.org/help/state/draft/iana-review
>>>>
>>>> Thank you,
>>>>
>>>> Sabrina Tanamal
>>>> Lead IANA Services Specialist
>>>>
>>>> (END IANA COMMENTS)
>>>
>> __________________________________________________________________
>> ____
>>> ___________________________________________________
>>>
>>> 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