Commit 85982ad0 authored by Stephane Bortzmeyer's avatar Stephane Bortzmeyer

Hildebrand draft on other RR types provisioning

parent 19875dbd
......@@ -24,6 +24,8 @@
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.7535.xml'>
<!ENTITY I-D.bortzmeyer-dname-root SYSTEM
'http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.bortzmeyer-dname-root'>
<!ENTITY I-D.hildebrand-deth SYSTEM
'http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.hildebrand-deth'>
<!ENTITY W3C.xml PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-xml-20001006.xml'>
<!ENTITY W3C.xmlschema-1 PUBLIC ''
......@@ -534,6 +536,7 @@ END
&rfc5910;
&rfc7535;
&I-D.bortzmeyer-dname-root;
&I-D.hildebrand-deth;
</references>
<section title="Generic Resource Records type">
......@@ -541,7 +544,10 @@ END
Resource record types (such as TXT or LOC). Such a mapping would
require the ability to add, update and remove individual
records, but it would allow the EPP server to implement a
"delegation-less" registry. Instead, we keep the idea that the
"delegation-less" registry. An example of such attempt to define
a standard protocol for provisioning a lot of resource record
types is <xref target="I-D.hildebrand-deth"/>. But we don't
follow that path. Instead, we keep the idea that the
EPP server registers only delegations, either through NS records
or, as here, a DNAME record. This keeps the mapping much
simpler.</t>
......
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