Commit bc4f6979 authored by Stéphane Bortzmeyer's avatar Stéphane Bortzmeyer

Remarks by John Levine

parent ffa01ca5
......@@ -101,7 +101,10 @@
described in RFC 1034 <xref target="RFC1034"/> and RFC&nbsp;1035
<xref target="RFC1035"/> and with the DNS DNAME Resource Record
type described in RFC 6672 <xref target="RFC6672"/> is required
to understand the DNS concepts described in this document.</t>
to understand the DNS concepts described in this
document. (DNAME have properties that may be surprising at
first; for instance, it aliases only the subdomains, not the
owner name of the DNAME record itself.)</t>
<t>The EPP mapping described in this document specifies a mechanism
for the provisioning and management of domain names in a
......@@ -501,7 +504,8 @@ END
<section title="Acknowledgements" anchor="acks">
<t>Most of the text has been copied from <xref
target="RFC5910"/>, so thanks to its authors.</t>
<t>Thanks to James Gould for a detailed review.</t>
<t>Thanks to James Gould for a detailed review and for
John Levine for good remarks.</t>
</section>
</middle>
......@@ -538,6 +542,9 @@ END
EPP server registers only delegations, either through NS records
or, as here, a DNAME record. This keeps the mapping much
simpler.</t>
<t>For this reason, the possibility to add other resource
records together with the DNAME (<xref target="RFC6672"/>,
section 2.4) is out-of-scope here.</t>
</section>
<?rfc rfcedstyle="yes"?>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment