| rfc9953v2.txt | rfc9953.txt | |||
|---|---|---|---|---|
| skipping to change at line 241 ¶ | skipping to change at line 241 ¶ | |||
| to the client. | to the client. | |||
| 3.2. Discovery Using SVCB Resource Records or DNR | 3.2. Discovery Using SVCB Resource Records or DNR | |||
| A DoC server can also be discovered using Service Binding (SVCB) | A DoC server can also be discovered using Service Binding (SVCB) | |||
| Resource Records (RRs) [RFC9460] [RFC9461] resolved via another DNS | Resource Records (RRs) [RFC9460] [RFC9461] resolved via another DNS | |||
| service (e.g., provided by an unencrypted local resolver) or | service (e.g., provided by an unencrypted local resolver) or | |||
| Discovery of Network-designated Resolvers (DNR) Service Parameters | Discovery of Network-designated Resolvers (DNR) Service Parameters | |||
| [RFC9463] via DHCP or Router Advertisements. [RFC8323] defines the | [RFC9463] via DHCP or Router Advertisements. [RFC8323] defines the | |||
| Application-Layer Protocol Negotiation (ALPN) ID for CoAP over TLS | Application-Layer Protocol Negotiation (ALPN) ID for CoAP over TLS | |||
| servers and [PRE-RFC9952] defines the ALPN ID for CoAP over DTLS | servers and [RFC9952] defines the ALPN ID for CoAP over DTLS servers. | |||
| servers. DoC servers that use only OSCORE [RFC8613] and Ephemeral | DoC servers that use only OSCORE [RFC8613] and Ephemeral Diffie- | |||
| Diffie-Hellman Over COSE (EDHOC) [RFC9528] (COSE stands for "Concise | Hellman Over COSE (EDHOC) [RFC9528] (COSE stands for "Concise Binary | |||
| Binary Object Notation (CBOR) Object Signing and Encryption" | Object Notation (CBOR) Object Signing and Encryption" [RFC9052]) to | |||
| [RFC9052]) to support security cannot be discovered using these SVCB | support security cannot be discovered using these SVCB RR or DNR | |||
| RR or DNR mechanisms. Specifying an alternate discovery mechanism is | mechanisms. Specifying an alternate discovery mechanism is out of | |||
| out of the scope of this document. | the scope of this document. | |||
| This document is not an SVCB mapping document for the CoAP schemes as | This document is not an SVCB mapping document for the CoAP schemes as | |||
| defined in Section 2.4.3 of [RFC9460]. A full SVCB mapping is | defined in Section 2.4.3 of [RFC9460]. A full SVCB mapping is | |||
| specified in [TRANSPORT-IND]. It generalizes mechanisms for all CoAP | specified in [TRANSPORT-IND]. It generalizes mechanisms for all CoAP | |||
| services. This document introduces only the discovery of DoC | services. This document introduces only the discovery of DoC | |||
| services. | services. | |||
| This document specifies "docpath" as a single-valued Service | This document specifies "docpath" as a single-valued Service | |||
| Parameter Key (SvcParamKey) that is mandatory for DoC SVCB records. | Parameter Key (SvcParamKey) that is mandatory for DoC SVCB records. | |||
| If the "docpath" SvcParamKey is absent, the service should not be | If the "docpath" SvcParamKey is absent, the service should not be | |||
| skipping to change at line 315 ¶ | skipping to change at line 315 ¶ | |||
| To use the service binding from an SVCB RR or DNR Encrypted DNS | To use the service binding from an SVCB RR or DNR Encrypted DNS | |||
| option, the DoC client MUST send a DoC request constructed from the | option, the DoC client MUST send a DoC request constructed from the | |||
| SvcParams including "docpath". The construction algorithm for DoC | SvcParams including "docpath". The construction algorithm for DoC | |||
| requests is as follows, with the provided records in order of their | requests is as follows, with the provided records in order of their | |||
| priority. For the purposes of this algorithm, the DoC client is | priority. For the purposes of this algorithm, the DoC client is | |||
| assumed to be SVCB-optional (see Section 3 of [RFC9460]). | assumed to be SVCB-optional (see Section 3 of [RFC9460]). | |||
| * If the "alpn" SvcParam value for the service is "coap", a CoAP | * If the "alpn" SvcParam value for the service is "coap", a CoAP | |||
| request for CoAP over TLS MUST be constructed [RFC8323]. If it is | request for CoAP over TLS MUST be constructed [RFC8323]. If it is | |||
| "co", a CoAP request for CoAP over DTLS MUST be constructed | "co", a CoAP request for CoAP over DTLS MUST be constructed | |||
| [PRE-RFC9952]. Any other SvcParamKeys specifying a transport are | [RFC9952]. Any other SvcParamKeys specifying a transport are out | |||
| out of the scope of this document. | of the scope of this document. | |||
| * The destination address for the request SHOULD be taken from | * The destination address for the request SHOULD be taken from | |||
| additional information about the target. This may include (1) A | additional information about the target. This may include (1) A | |||
| or AAAA RRs associated with the target name and delivered with the | or AAAA RRs associated with the target name and delivered with the | |||
| SVCB RR (see [RFC9462]), (2) "ipv4hint" or "ipv6hint" SvcParams | SVCB RR (see [RFC9462]), (2) "ipv4hint" or "ipv6hint" SvcParams | |||
| from the SVCB RR (see [RFC9461]), or (3) IPv4 or IPv6 addresses | from the SVCB RR (see [RFC9461]), or (3) IPv4 or IPv6 addresses | |||
| provided if DNR [RFC9463] is used. As a fallback, an address MAY | provided if DNR [RFC9463] is used. As a fallback, an address MAY | |||
| be queried for the target name of the SVCB record from another DNS | be queried for the target name of the SVCB record from another DNS | |||
| service. | service. | |||
| skipping to change at line 854 ¶ | skipping to change at line 854 ¶ | |||
| 9.5. DNS Extensions | 9.5. DNS Extensions | |||
| DNS extensions that are specific to the choice of transport, such as | DNS extensions that are specific to the choice of transport, such as | |||
| described in [RFC7828], are not applicable to DoC. | described in [RFC7828], are not applicable to DoC. | |||
| 10. References | 10. References | |||
| 10.1. Normative References | 10.1. Normative References | |||
| [PRE-RFC9952] | ||||
| Lenders, M. S., Amsüss, C., Schmidt, T. C., and M. | ||||
| Wählisch, "The Application-Layer Protocol Negotiation | ||||
| (ALPN) ID Specification for the Constrained Application | ||||
| Protocol (CoAP) over DTLS", RFC PRE-9952, DOI | ||||
| 10.17487/PRE-RFC9952, March 2026, | ||||
| <https://www.rfc-editor.org/info/rfc9952>. | ||||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform | [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform | |||
| Resource Identifier (URI): Generic Syntax", STD 66, | Resource Identifier (URI): Generic Syntax", STD 66, | |||
| RFC 3986, DOI 10.17487/RFC3986, January 2005, | RFC 3986, DOI 10.17487/RFC3986, January 2005, | |||
| <https://www.rfc-editor.org/info/rfc3986>. | <https://www.rfc-editor.org/info/rfc3986>. | |||
| skipping to change at line 959 ¶ | skipping to change at line 951 ¶ | |||
| Jensen, "Discovery of Designated Resolvers", RFC 9462, | Jensen, "Discovery of Designated Resolvers", RFC 9462, | |||
| DOI 10.17487/RFC9462, November 2023, | DOI 10.17487/RFC9462, November 2023, | |||
| <https://www.rfc-editor.org/info/rfc9462>. | <https://www.rfc-editor.org/info/rfc9462>. | |||
| [RFC9463] Boucadair, M., Ed., Reddy.K, T., Ed., Wing, D., Cook, N., | [RFC9463] Boucadair, M., Ed., Reddy.K, T., Ed., Wing, D., Cook, N., | |||
| and T. Jensen, "DHCP and Router Advertisement Options for | and T. Jensen, "DHCP and Router Advertisement Options for | |||
| the Discovery of Network-designated Resolvers (DNR)", | the Discovery of Network-designated Resolvers (DNR)", | |||
| RFC 9463, DOI 10.17487/RFC9463, November 2023, | RFC 9463, DOI 10.17487/RFC9463, November 2023, | |||
| <https://www.rfc-editor.org/info/rfc9463>. | <https://www.rfc-editor.org/info/rfc9463>. | |||
| [RFC9952] Lenders, M. S., Amsüss, C., Schmidt, T. C., and M. | ||||
| Wählisch, "Application-Layer Protocol Negotiation (ALPN) | ||||
| ID for CoAP over DTLS", RFC 9952, DOI 10.17487/RFC9952, | ||||
| March 2026, <https://www.rfc-editor.org/info/rfc9952>. | ||||
| [STD13] Internet Standard 13, | [STD13] Internet Standard 13, | |||
| <https://www.rfc-editor.org/info/std13>. | <https://www.rfc-editor.org/info/std13>. | |||
| At the time of writing, this STD comprises the following: | At the time of writing, this STD comprises the following: | |||
| Mockapetris, P., "Domain names - concepts and facilities", | Mockapetris, P., "Domain names - concepts and facilities", | |||
| STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, | STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, | |||
| <https://www.rfc-editor.org/info/rfc1034>. | <https://www.rfc-editor.org/info/rfc1034>. | |||
| Mockapetris, P., "Domain names - implementation and | Mockapetris, P., "Domain names - implementation and | |||
| specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, | specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, | |||
| skipping to change at line 1002 ¶ | skipping to change at line 999 ¶ | |||
| Protocol (CoAP) using Group Object Security for | Protocol (CoAP) using Group Object Security for | |||
| Constrained RESTful Environments (Group OSCORE)", Work in | Constrained RESTful Environments (Group OSCORE)", Work in | |||
| Progress, Internet-Draft, draft-ietf-core-cacheable- | Progress, Internet-Draft, draft-ietf-core-cacheable- | |||
| oscore-01, 2 March 2026, | oscore-01, 2 March 2026, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-core- | <https://datatracker.ietf.org/doc/html/draft-ietf-core- | |||
| cacheable-oscore-01>. | cacheable-oscore-01>. | |||
| [CoAP-CORR-CLAR] | [CoAP-CORR-CLAR] | |||
| Bormann, C., "Constrained Application Protocol (CoAP): | Bormann, C., "Constrained Application Protocol (CoAP): | |||
| Corrections and Clarifications", Work in Progress, | Corrections and Clarifications", Work in Progress, | |||
| Internet-Draft, draft-ietf-core-corr-clar-03, 22 December | Internet-Draft, draft-ietf-core-corr-clar-04, 19 March | |||
| 2025, <https://datatracker.ietf.org/doc/html/draft-ietf- | 2026, <https://datatracker.ietf.org/doc/html/draft-ietf- | |||
| core-corr-clar-03>. | core-corr-clar-04>. | |||
| [CRI] Bormann, C. and H. Birkholz, "Constrained Resource | [CRI] Bormann, C. and H. Birkholz, "Constrained Resource | |||
| Identifiers", Work in Progress, Internet-Draft, draft- | Identifiers", Work in Progress, Internet-Draft, draft- | |||
| ietf-core-href-30, 21 November 2025, | ietf-core-href-30, 21 November 2025, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-core- | <https://datatracker.ietf.org/doc/html/draft-ietf-core- | |||
| href-30>. | href-30>. | |||
| [DoC-paper] | [DoC-paper] | |||
| Lenders, M. S., Amsüss, C., Gündogan, C., Nawrocki, M., | Lenders, M. S., Amsüss, C., Gündogan, C., Nawrocki, M., | |||
| Schmidt, T., and M. Wählisch, "Securing Name Resolution in | Schmidt, T., and M. Wählisch, "Securing Name Resolution in | |||
| skipping to change at line 1042 ¶ | skipping to change at line 1039 ¶ | |||
| <https://www.rfc-editor.org/info/rfc6690>. | <https://www.rfc-editor.org/info/rfc6690>. | |||
| [RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for | [RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for | |||
| Constrained-Node Networks", RFC 7228, | Constrained-Node Networks", RFC 7228, | |||
| DOI 10.17487/RFC7228, May 2014, | DOI 10.17487/RFC7228, May 2014, | |||
| <https://www.rfc-editor.org/info/rfc7228>. | <https://www.rfc-editor.org/info/rfc7228>. | |||
| [RFC7228bis] | [RFC7228bis] | |||
| Bormann, C., Ersue, M., Keränen, A., and C. Gomez, | Bormann, C., Ersue, M., Keränen, A., and C. Gomez, | |||
| "Terminology for Constrained-Node Networks", Work in | "Terminology for Constrained-Node Networks", Work in | |||
| Progress, Internet-Draft, draft-ietf-iotops-7228bis-04, 2 | Progress, Internet-Draft, draft-ietf-iotops-7228bis-05, 14 | |||
| March 2026, <https://datatracker.ietf.org/doc/html/draft- | March 2026, <https://datatracker.ietf.org/doc/html/draft- | |||
| ietf-iotops-7228bis-04>. | ietf-iotops-7228bis-05>. | |||
| [RFC7828] Wouters, P., Abley, J., Dickinson, S., and R. Bellis, "The | [RFC7828] Wouters, P., Abley, J., Dickinson, S., and R. Bellis, "The | |||
| edns-tcp-keepalive EDNS0 Option", RFC 7828, | edns-tcp-keepalive EDNS0 Option", RFC 7828, | |||
| DOI 10.17487/RFC7828, April 2016, | DOI 10.17487/RFC7828, April 2016, | |||
| <https://www.rfc-editor.org/info/rfc7828>. | <https://www.rfc-editor.org/info/rfc7828>. | |||
| [RFC7858] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., | [RFC7858] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., | |||
| and P. Hoffman, "Specification for DNS over Transport | and P. Hoffman, "Specification for DNS over Transport | |||
| Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May | Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May | |||
| 2016, <https://www.rfc-editor.org/info/rfc7858>. | 2016, <https://www.rfc-editor.org/info/rfc7858>. | |||
| End of changes. 7 change blocks. | ||||
| 22 lines changed or deleted | 19 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||