Re: [Drip] draft-ietf-drip-registries: Shepherd & Milestone

[[e-mail]]

Hi Jim, Adam,

Sending this nudge as we didn't get any update :-)

Also, I would appreciate if you can consider replying to Daniel's review.

Thank you.

Cheers,
Med

De : BOUCADAIR Mohamed INNOV/NET
Envoyé : vendredi 23 février 2024 01:08
À : 'Jim Reid' <[e-mail]>; 'Adam Wiethuechter' <[e-mail]>
Cc : '[e-mail]' <[e-mail]>; '[e-mail]' <[e-mail]>
Objet : RE: draft-ietf-drip-registries: Shepherd & Milestone

Hi Jim, Adam,

Unless I'm mistaken, I didn't see any progress on the RRType request.

Adam, now that auth rush is over :), can you please cleanup the issues so that we have a better visibility on the pending ones? Thanks.

Also, I remember that the SN mapping would be left out of this document. Is that still the plan? Thanks.

Cheers,
Med

De : BOUCADAIR Mohamed INNOV/NET
Envoyé : jeudi 7 décembre 2023 09:06
À : 'Adam Wiethuechter' <[e-mail]<mailto:[e-mail]>>; Jim Reid <[e-mail]<mailto:[e-mail]>>
Cc : [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Objet : RE: draft-ietf-drip-registries: Shepherd & Milestone

Hi Jim, Adam,

Sound like a plan. Will reflect that in the Datatracker.

Adam, can you please update Issues · ietf-wg-drip/draft-ietf-drip-registries (github.com)<https://github.com/ietf-wg-drip/draft-ietf-drip-registries/issues> taking into account the scope and changes made into the spec? For example, clarify those raised in the previous directorate reviews.

Jim, I don't think that the SN mapping issue is relevant to whether you can proceed with the request for the DET RR. In other terms, are we ready to complete the template [1] and have the registration for the meta RR done in the coming weeks? If so, can you please prepare the template and send it to a [e-mail]<mailto:[e-mail]>.

Thank you.

Cheers,
Med

[1] https://www.rfc-editor.org/rfc/rfc6895.html#appendix-A

De : Adam Wiethuechter <[e-mail]<mailto:[e-mail]>>
Envoyé : mercredi 6 décembre 2023 23:46
À : Jim Reid <[e-mail]<mailto:[e-mail]>>; BOUCADAIR Mohamed INNOV/NET <[e-mail]<mailto:[e-mail]>>
Cc : [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Objet : Re: draft-ietf-drip-registries: Shepherd & Milestone

As of the latest version (which I posted earlier this week) the mapping of Serial Numbers to DNS (not necessarily into IPv6, though that is accomplished via RFC9374 Section 4.2) is removed and is in its own document [1].

This is the change I proposed at IETF118 and had marked in the previous version of the document every section that would be removed. It was done because that particular mapping was not well defined (where and what is the DNS apex, who owns/maintains it, etc.). Thus, would slow down this document that really is focusing on how to put and lookup DETs specifically.

I strongly believe figuring out how Serial Numbers map into DNS is important, but not for this specific document and by moving into its own document focuses the discussion.

I agree with Jim that we won't make the Dec 2023 milestone and IETF119 seems a more reasonable target with WGLC sometime soon before.

[1] https://datatracker.ietf.org/doc/draft-wiethuechter-drip-uas-sn-dns/<https://datatracker.ietf.org/doc/draft-wiethuechter-drip-uas-sn-dns/>
--------
73,
Adam T. Wiethuechter
Software Engineer; AX Enterprize, LLC
________________________________
From: Jim Reid <[e-mail]<mailto:[e-mail]>>
Sent: Wednesday, December 6, 2023 5:31 PM
To: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: Re: draft-ietf-drip-registries: Shepherd & Milestone



> On 5 Dec 2023, at 09:24, [e-mail]<mailto:[e-mail]> wrote:
>
> I don't think we can make it. Authors, can you please propose a reasonable target date?

You're right Med. The EOY deadline is going to be missed. I'm not sure when the doc will be ready for WGLC. Maybe around IETF119? The mapping of serial numbers into IPv6 addresses needs careful thought/scrutiny and the way forward isn't yet clear - at least to me.
____________________________________________________________________________________________________________
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.