IETF Last Call Review of draft-ietf-core-coap-dtls-alpn-04
review-ietf-core-coap-dtls-alpn-04-dnsdir-lc-tale-2025-06-27-00
Request | Review of | draft-ietf-core-coap-dtls-alpn |
---|---|---|
Requested revision | No specific revision (document currently at 05) | |
Type | IETF Last Call Review | |
Team | DNS Directorate (dnsdir) | |
Deadline | 2025-06-16 | |
Requested | 2025-06-02 | |
Authors | Martine Sophie Lenders , Christian Amsüss , Thomas C. Schmidt , Matthias Wählisch | |
I-D last updated | 2025-09-16 (Latest revision 2025-08-11) | |
Completed reviews |
Dnsdir IETF Last Call review of -04
by David C Lawrence
(diff)
Genart IETF Last Call review of -04 by Christer Holmberg (diff) Artart IETF Last Call review of -04 by Barry Leiba (diff) Secdir IETF Last Call review of -04 by Joseph A. Salowey (diff) |
|
Assignment | Reviewer | David C Lawrence |
State | Completed | |
Request | IETF Last Call review on draft-ietf-core-coap-dtls-alpn by DNS Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/dnsdir/gqj_GPQo5SEJrkiXQutGI32VPXw | |
Reviewed revision | 04 (document currently at 05) | |
Result | Ready | |
Completed | 2025-06-27 |
review-ietf-core-coap-dtls-alpn-04-dnsdir-lc-tale-2025-06-27-00
From the DNS Directorate perspective, this document has very little impact. Its main reason for existence is to formalize the entry of "co", for CoAP over DTLS, in the TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs registry. It is already assigned per expert review, this just gives it an official RFC. The DNS relevance is with the SVCB and HTTPS records, which reference the ALPN registry via the alpn= parameter. The document is straightforward with no noteworthy issues.