Hi Martine, Please see inline.
Cheers, Med > -----Message d'origine----- > De : Martine Sophie Lenders <martine.lend...@tu-dresden.de> > Envoyé : mardi 30 juillet 2024 12:43 > À : c...@ietf.org; dnsop@ietf.org; BOUCADAIR Mohamed INNOV/NET > <mohamed.boucad...@orange.com> > Objet : Re: [core] Re: Fwd: WG Adoption Call for draft-lenders- > core-coap-dtls-svcb > > Hi Med, > > On 29.07.24 13:56, mohamed.boucad...@orange.com wrote: > > Hi Carsten, all, > > > > There is a mismatch between what is claimed in the > abstract/into vs. > > core documents. Concretely, when reading “This document > specifies the > > usage of Service Parameters..” or “This document specifies > which > > information from SvcParams ..”, I thought this is a discussion > about the > > applicability of existing parameters per > > https://www.iana.org/assignments/dns-svcb/dns-svcb.xhtml to > CoAP. > > However, the doc focuses on alpn. It seems to me that the main > > contribution is to register an ALPN ID for CoAP over DTLS > (i.e., Section > > 5.1). > > Noted, we will adapt the presentation for -01. [Med] Thanks. > > > Is there any specific reason why this request is not made as > part of > > I-D.ietf-core-dns-over-coap? > > We thought about this, but in the end, CoAP over DTLS is used in > other > contexts than just DNS over CoAP. Given that CoAP over TLS > defines its > ALPN ID in its RFC, and CoAP over DTLS was just too early for > that, we > thought it's better to have the ALPN ID for CoAP over DTLS to be > its own > document. [Med] I would agree with that reasoning if there were more specifics discussed in the document. However, all what the doc does is to register a new ALPN ID in a registry that follows "Expert Review" policy. Keeping the registration as part of I-D.ietf-core-dns-over-coap has the merit to bind it to a case that motivated the registration. Doing so does not restrict by any means the applicability of that ID. Note that the registry is authoritative by itself when there is a need to refer to "co" in other contexts. Thanks.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
