A new Request for Comments is now available in online RFC libraries.

        
        RFC 9953

        Title:      DNS over CoAP (DoC) 
        Author:     M. S. Lenders,
                    C. Amsüss,
                    C. Gündoğan,
                    T. C. Schmidt,
                    M. Wählisch
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2026
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-dns-over-coap-20.txt

        URL:        https://www.rfc-editor.org/info/rfc9953

        DOI:        10.17487/RFC9953

This document defines a protocol for exchanging DNS queries (OPCODE
0) over the Constrained Application Protocol (CoAP). These CoAP
messages can be protected by (D)TLS-Secured CoAP or Object Security
for Constrained RESTful Environments (OSCORE) to provide encrypted
DNS message exchange for constrained devices in the Internet of
Things (IoT).

This document is a product of the Constrained RESTful Environments Working 
Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org

Reply via email to