Re: [core] Next steps: draft-ietf-core-dns-over-coap

[[e-mail]]

Hi Martine, all,

FWIW: 

With regards to [1], and given that DNR was explicitly mentioned, please note that the DNR version in the RFC Editor queue says:  

      The "alpn" SvcParam may not be required in contexts
      such as a variant of DNS over CoAP where messages are encrypted
      using Object Security for Constrained RESTful Environments
      (OSCORE) [RFC8613].

Also, Ben made a similar change to accommodate non-alpn cases: https://github.com/ietf-wg-add/draft-ietf-add-svcb-dns/commit/65927be7ba79fbc6c93a2c793f8b8b455b394ea5. I don't think this change made it to public version though. 

Cheers,
Med

> -----Message d'origine-----
> De : core <[e-mail]> De la part de Martine Sophie
> Lenders
> Envoyé : vendredi 23 juin 2023 21:38
> À : [e-mail]
> Cc : [e-mail]; dnsop
> <[e-mail]>; DNS Privacy Working Group <[e-mail]>
> Objet : [core] Next steps: draft-ietf-core-dns-over-coap
> 
> Hi!
> 
> we, the authors of draft-ietf-core-dns-over-coap, are planning to
> present on DNS over CoAP at the next core interim (and at IETF
> 117) again.
> 
> In preparation for that, there are still some things to do and
> discuss
> ahead:
> 
> Discussions on 'ALPN "coap" for DTLS' [1] and 'Using SVCB with
> OSCORE/EDHOC' [2] somewhat got stalled. For our document, I think
> we need at least confirmation or decline that the "coap" ALPN
> could be used for DTLS, SVCB for OSCORE/EDHOC, I think is out of
> scope at the moment anyways.
> 
> Furthermore, there is still an open question, if DoC can or should
> be translated at a CoAP-HTTP proxy to DoH. Namely, how the FETCH
> that DoC uses should be translated into the POST/GET of DoH [3].
> 
> And last but not least, is there further feedback we did not
> address yet or is there new feedback that you want us to address?
> 
> Best
> Martine
> 
> [1]
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> mailarchive.ietf.org%2Farch%2Fmsg%2Fcore%2FI_vkEz046qEWQKGh6dOE1Wo
> bIM4%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Ce73a1654e1
> e441fb021208db74217818%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%
> 7C638231459321660865%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat
> a=VQKOYvAStq6d%2BamExRbwr1B98AdjRXoafJmRjzfbB3Q%3D&reserved=0
> [2]
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> mailarchive.ietf.org%2Farch%2Fmsg%2Fcore%2FQnZdheePgNi3HspxDpmreu3
> pbxU%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Ce73a1654e1
> e441fb021208db74217818%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%
> 7C638231459321660865%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat
> a=7GgaXv%2F%2F2jy4D2mu%2FUy8SWTefC3bcS%2FR9CmJ8mOOWQI%3D&reserved=
> 0
> [4]
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> github.com%2Fcore-wg%2Fdraft-dns-over-coap%2Fblob%2Fmain%2Fdraft-
> ietf-core-dns-over-coap.md%23using-a-coap-http-proxy-to-translate-
> to-doh-seccoap-http-
> proxy&data=05%7C01%7Cmohamed.boucadair%40orange.com%7Ce73a1654e1e4
> 41fb021208db74217818%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C
> 638231459321660865%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=
> XhCqUMeTM8k4m3%2F1CIrKEM06%2B1fkHHSCWYie4NtOXHU%3D&reserved=0
____________________________________________________________________________________________________________
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.