Skip to content

Internationalization #205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pawel-kow wants to merge 1 commit into
base: ietf/draft-ietf-dconn-domainconnect-XX
Choose a base branch
from
Open

Internationalization #205

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 14 additions & 5 deletions docs/draft-ietf-dconn-domainconnect-04.clean.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2047,6 +2047,11 @@ Table of Contents
Table 8: URI template parameters of the apply call in the sync
flow

Where an apply parameter carries text intended for display to the
user, the Service Provider MAY set its value to text localized to
match the user agent's language preference (e.g. the HTTP "Accept-
Language" header).

An example query string:

GET
Expand Down Expand Up @@ -2250,9 +2255,10 @@ Table of Contents
"temporarily_unavailable".

* "error_description" - OPTIONAL. A developer-oriented plain-text
description of the error. The DNS Provider SHOULD keep
descriptions vague where disclosure of internal account or domain
state would be inappropriate.
description of the error, intended for developers rather than the
end user and therefore RECOMMENDED to be in English. The DNS
Provider SHOULD keep descriptions vague where disclosure of
internal account or domain state would be inappropriate.

As a RECOMMENDED convention, when the user explicitly cancels the
operation and the DNS Provider uses "error=access_denied", the
Expand Down Expand Up @@ -3449,6 +3455,9 @@ Change from draft-ietf-dconn-domainconnect-03 to -04
* Added dc-template-property, dc-unprefixed-property, and dc-vnd-
property to Terminology.

* Clarified how the language of user-facing and developer-facing
protocol text relates to the user agent's language preference.

Change from draft-ietf-dconn-domainconnect-02 to -03

* Classified template record types as Fully Specified, Computed, or
Expand Down Expand Up @@ -3722,9 +3731,9 @@ Normative References

Informative References

[RFC8499] "Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", IETF, DOI 10.17487/RFC8499, RFC 8499,
January 2019, >.".
January 2019, <https://www.rfc-editor.org/info/rfc8499>.

[RFC6839] Hansen, T. and A. Melnikov, "Additional Media Type
Structured Syntax Suffixes", IETF, DOI 10.17487/RFC6839,
Expand Down
31 changes: 18 additions & 13 deletions docs/draft-ietf-dconn-domainconnect-04.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4119,20 +4119,23 @@ <h4 id="name-parameters-properties">
</tbody>
</table>
</div>
<div id="_cf6a078e-4a99-02db-4672-47179821ecff">
<p id="section-8.3.2-3">An example query string:<a href="#section-8.3.2-3" class="pilcrow">¶</a></p>
<div id="_4bd0581a-e583-4b62-b37f-c184a1920cf6">
<p id="section-8.3.2-3">Where an apply parameter carries text intended for display to the user, the Service Provider MAY set its value to text localized to match the user agent's language preference (e.g. the HTTP <code>"Accept-Language"</code> header).<a href="#section-8.3.2-3" class="pilcrow">¶</a></p>
</div>
<div id="_5d96f9bb-de08-1aa4-0bba-535bd2ce96e9">
<p id="section-8.3.2-4">An example query string:<a href="#section-8.3.2-4" class="pilcrow">¶</a></p>
</div>
<div id="_9d4fbce5-fffb-92ba-d1de-043516ba9aad">
<div class="sourcecode" id="section-8.3.2-4">
<div class="sourcecode" id="section-8.3.2-5">
<pre>GET

https://web-connect.dnsprovider.example/v2/domainTemplates/providers/
exampleservice.example/services/template1/apply?domain=example.com&amp;
IP=192.168.42.42&amp;RANDOMTEXT=shm%3A1542108821%3AHello</pre><a href="#section-8.3.2-4" class="pilcrow">¶</a>
IP=192.168.42.42&amp;RANDOMTEXT=shm%3A1542108821%3AHello</pre><a href="#section-8.3.2-5" class="pilcrow">¶</a>
</div>
</div>
<div id="_92e399b2-4f1e-f3e7-dab0-9771bacded8b">
<p id="section-8.3.2-5">This call indicates that the Service Provider wishes to connect the domain example.com to the service using the template identified by the composite key of the provider (exampleservice.example) and the service template owned by them (template1). In this example, there are two variables in this template, "IP" and "RANDOMTEXT". These variables are passed as name/value pairs.<a href="#section-8.3.2-5" class="pilcrow">¶</a></p>
<div id="_06616899-d0bd-baed-4a96-83e6f048a905">
<p id="section-8.3.2-6">This call indicates that the Service Provider wishes to connect the domain example.com to the service using the template identified by the composite key of the provider (exampleservice.example) and the service template owned by them (template1). In this example, there are two variables in this template, "IP" and "RANDOMTEXT". These variables are passed as name/value pairs.<a href="#section-8.3.2-6" class="pilcrow">¶</a></p>
</div>
<div id="signing-procedure">
<section id="section-8.3.2.1">
Expand Down Expand Up @@ -4308,7 +4311,7 @@ <h4 id="name-template-apply-response">
</div>
</section>
</div>
<div id="_3d732d89-1638-ee8e-4fa2-0679013d029f">
<div id="_23d6c3a1-9b09-4c06-0656-878e7cc4242c">
<section id="section-8.3.6">
<h4 id="name-template-apply-error-respon">
<a href="#section-8.3.6" class="section-number selfRef">8.3.6. </a><a href="#name-template-apply-error-respon" class="section-name selfRef">Template Apply Error Response</a>
Expand All @@ -4324,8 +4327,8 @@ <h4 id="name-template-apply-error-respon">
<code>"error"</code> - REQUIRED on error. The value MUST be one of the error codes defined in Section 4.1.2.1 of <span>[<a href="#RFC6749" class="cite xref">RFC6749</a>]</span>: <code>"invalid_request"</code>, <code>"unauthorized_client"</code>, <code>"access_denied"</code>, <code>"unsupported_response_type"</code>, <code>"invalid_scope"</code>, <code>"server_error"</code>, or <code>"temporarily_unavailable"</code>.<a href="#section-8.3.6-3.1" class="pilcrow">¶</a>
</li>
<li class="normal" id="section-8.3.6-3.2">
<div id="_dfa5a96c-0248-ad4c-f715-7ad6dac8f289">
<p id="section-8.3.6-3.2.1"><code>"error_description"</code> - OPTIONAL. A developer-oriented plain-text description of the error. The DNS Provider SHOULD keep descriptions vague where disclosure of internal account or domain state would be inappropriate.<br><a href="#section-8.3.6-3.2.1" class="pilcrow">¶</a></p>
<div id="_3ad60700-0af0-b8e7-dd74-f1e983b04757">
<p id="section-8.3.6-3.2.1"><code>"error_description"</code> - OPTIONAL. A developer-oriented plain-text description of the error, intended for developers rather than the end user and therefore RECOMMENDED to be in English. The DNS Provider SHOULD keep descriptions vague where disclosure of internal account or domain state would be inappropriate.<br><a href="#section-8.3.6-3.2.1" class="pilcrow">¶</a></p>
</div>
<div id="_fd8049ee-439a-d4dc-f636-fff7b1df4920">
<p id="section-8.3.6-3.2.2">As a RECOMMENDED convention, when the user explicitly cancels the operation and the DNS Provider uses <code>"error=access_denied"</code>, the <code>"error_description"</code> value MAY carry the prefix <code>"user_cancel"</code> to allow the Service Provider to distinguish user cancellation from other denial reasons.<a href="#section-8.3.6-3.2.2" class="pilcrow">¶</a></p>
Expand Down Expand Up @@ -6116,13 +6119,13 @@ <h2 id="name-acknowledgements">
</ul>
</section>
</div>
<div id="_d853b6ab-7541-1a0d-229e-d73061b51a41">
<div id="_29529b7d-c648-46fe-c808-a2936b382f99">
<section id="section-15">
<h2 id="name-change-history">
<a href="#name-change-history" class="section-name selfRef">Change History</a>
</h2>
<p id="section-15-1">This section is to be removed before publishing as an RFC.<a href="#section-15-1" class="pilcrow">¶</a></p>
<div id="_b7f20842-9c37-b6e7-3041-9f639e2fbaa0">
<div id="_c947e588-dbf4-0d4f-e9eb-3aa243b8d8d3">
<section id="section-15.1">
<h3 id="name-change-from-draft-ietf-dcon">
<a href="#name-change-from-draft-ietf-dcon" class="section-name selfRef">Change from draft-ietf-dconn-domainconnect-03 to -04</a>
Expand All @@ -6141,6 +6144,8 @@ <h3 id="name-change-from-draft-ietf-dcon">
<li class="normal" id="section-15.1-1.6">Added the IANA "Domain Connect Template Properties" registry in <a href="#iana-template-properties" class="internal xref">Domain Connect Template Properties Registry</a>.<a href="#section-15.1-1.6" class="pilcrow">¶</a>
</li>
<li class="normal" id="section-15.1-1.7">Added <code>dc-template-property</code>, <code>dc-unprefixed-property</code>, and <code>dc-vnd-property</code> to <a href="#terminology" class="internal xref">Terminology</a>.<a href="#section-15.1-1.7" class="pilcrow">¶</a>
</li>
<li class="normal" id="section-15.1-1.8">Clarified how the language of user-facing and developer-facing protocol text relates to the user agent's language preference.<a href="#section-15.1-1.8" class="pilcrow">¶</a>
</li>
</ul>
</section>
Expand Down Expand Up @@ -6433,15 +6438,15 @@ <h2 id="name-normative-references">
</dl>
</section>
</div>
<div id="_caa3fd87-3022-d3b3-29e7-0717696251b9">
<div id="_450f5e0d-c691-497f-076a-3739617b36c2">
<section id="section-17">
<h2 id="name-informative-references">
<a href="#name-informative-references" class="section-name selfRef">Informative References</a>
</h2>
<dl class="references">
<dt id="RFC8499">[RFC8499]</dt>
<dd>
<span class="refTitle">"Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS Terminology", IETF, DOI 10.17487/RFC8499, RFC 8499, January 2019, &gt;."</span>. </dd>
<span class="refAuthor">Hoffman, P.</span>, <span class="refAuthor">Sullivan, A.</span>, and <span class="refAuthor">K. Fujiwara</span>, <span class="refTitle">"DNS Terminology"</span>, <span class="stream">IETF</span>, <span class="seriesInfo">DOI 10.17487/RFC8499</span>, <span class="seriesInfo">RFC 8499</span>, <time datetime="2019-01" class="refDate">January 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8499">https://www.rfc-editor.org/info/rfc8499</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6839">[RFC6839]</dt>
<dd>
Expand Down
Binary file modified docs/draft-ietf-dconn-domainconnect-04.pdf
View file
Open in desktop
Binary file not shown.
58 changes: 29 additions & 29 deletions docs/draft-ietf-dconn-domainconnect-04.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2481,6 +2481,11 @@ Internet-Draft Domain Connect July 2026
Table 8: URI template parameters of the apply call in the sync
flow

Where an apply parameter carries text intended for display to the
user, the Service Provider MAY set its value to text localized to
match the user agent's language preference (e.g. the HTTP "Accept-
Language" header).

An example query string:

GET
Expand Down Expand Up @@ -2509,11 +2514,6 @@ Internet-Draft Domain Connect July 2026

a. Take all apply parameters except "sig" and "key".

b. URL-encode each parameter name and value per [RFC3986].

c. Sort the parameters in ascending lexicographic order of the
URL-encoded parameter name.




Expand All @@ -2522,6 +2522,11 @@ Kowalik, et al. Expires 4 January 2027 [Page 45]
Internet-Draft Domain Connect July 2026


b. URL-encode each parameter name and value per [RFC3986].

c. Sort the parameters in ascending lexicographic order of the
URL-encoded parameter name.

d. Concatenate them as name=value pairs joined by "&".

2. Sign the canonical input string using the private key
Expand Down Expand Up @@ -2564,11 +2569,6 @@ Internet-Draft Domain Connect July 2026
specific parameters, apply parameter names are governed by the
following reservation rules:

* Parameter names beginning with "dc." are reserved for parameters
defined by future standards-track extensions that normatively
require this document as their base. Implementations MUST NOT use
the "dc." prefix for private parameters.




Expand All @@ -2578,6 +2578,11 @@ Kowalik, et al. Expires 4 January 2027 [Page 46]
Internet-Draft Domain Connect July 2026


* Parameter names beginning with "dc." are reserved for parameters
defined by future standards-track extensions that normatively
require this document as their base. Implementations MUST NOT use
the "dc." prefix for private parameters.

* Parameter names beginning with "vnd." are reserved for vendor-
specific and private-use parameters. A vendor SHOULD further
namespace such parameters with a vendor identifier (e.g.
Expand Down Expand Up @@ -2622,18 +2627,16 @@ Internet-Draft Domain Connect July 2026
"syncPubKeyDomain" is set, the DNS Provider MUST perform the
following steps and MUST reject the request if any step fails:

1. *Check for required parameters* - The request MUST carry both
"sig" and "key" parameters.





Kowalik, et al. Expires 4 January 2027 [Page 47]

Internet-Draft Domain Connect July 2026


1. *Check for required parameters* - The request MUST carry both
"sig" and "key" parameters.

2. *Retrieve the public key* - Query DNS for TXT records at the host
formed by prepending the "key" parameter value as a label to
"syncPubKeyDomain" (see Section 6.4). If no such records are
Expand Down Expand Up @@ -2682,9 +2685,6 @@ Internet-Draft Domain Connect July 2026






Kowalik, et al. Expires 4 January 2027 [Page 48]

Internet-Draft Domain Connect July 2026
Expand Down Expand Up @@ -2723,9 +2723,10 @@ Internet-Draft Domain Connect July 2026
"temporarily_unavailable".

* "error_description" - OPTIONAL. A developer-oriented plain-text
description of the error. The DNS Provider SHOULD keep
descriptions vague where disclosure of internal account or domain
state would be inappropriate.
description of the error, intended for developers rather than the
end user and therefore RECOMMENDED to be in English. The DNS
Provider SHOULD keep descriptions vague where disclosure of
internal account or domain state would be inappropriate.

As a RECOMMENDED convention, when the user explicitly cancels the
operation and the DNS Provider uses "error=access_denied", the
Expand All @@ -2740,7 +2741,6 @@ Internet-Draft Domain Connect July 2026




Kowalik, et al. Expires 4 January 2027 [Page 49]

Internet-Draft Domain Connect July 2026
Expand Down Expand Up @@ -4168,6 +4168,9 @@ Internet-Draft Domain Connect July 2026
* Added dc-template-property, dc-unprefixed-property, and dc-vnd-
property to Terminology.

* Clarified how the language of user-facing and developer-facing
protocol text relates to the user agent's language preference.

Change from draft-ietf-dconn-domainconnect-02 to -03

* Classified template record types as Fully Specified, Computed, or
Expand All @@ -4192,16 +4195,15 @@ Change from draft-ietf-dconn-domainconnect-02 to -03
Template Definition; phishing warnings are now default behavior,
see Template Variable Phishing.

* Clarified one-host-one-key rule in Public Key Publication.




Kowalik, et al. Expires 4 January 2027 [Page 75]

Internet-Draft Domain Connect July 2026


* Clarified one-host-one-key rule in Public Key Publication.

* Added Media Type Registration for application/
domainconnect-template+json in IANA Considerations.

Expand Down Expand Up @@ -4251,8 +4253,6 @@ Change from draft-ietf-dconn-domainconnect-00 to -01





Kowalik, et al. Expires 4 January 2027 [Page 76]

Internet-Draft Domain Connect July 2026
Expand Down Expand Up @@ -4489,9 +4489,9 @@ Internet-Draft Domain Connect July 2026

Informative References

[RFC8499] "Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", IETF, DOI 10.17487/RFC8499, RFC 8499,
January 2019, >.".
January 2019, <https://www.rfc-editor.org/info/rfc8499>.

[RFC6839] Hansen, T. and A. Melnikov, "Additional Media Type
Structured Syntax Suffixes", IETF, DOI 10.17487/RFC6839,
Expand Down
Loading