RFC 4114
E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)
RFC 4114: E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) 📞✨
Okay bestie, this is RFC 4114 💅 It was written by S. Hollenbeck at VeriSign, Inc., it's a Standards Track document, and it dropped in June 2005. Its header doesn't list anything it obsoletes or updates. This is part 1 of 3 🎀
Status of This Memo 📋
This document is an Internet standards track protocol for the Internet community, and it's asking folks to discuss it and suggest improvements 🫶 For the standardization state and status of this protocol, check the current edition of the "Internet Official Protocol Standards" (STD 1). Distribution of this memo is unlimited 🦋
Copyright Notice 🌸
Copyright (C) The Internet Society (2005).
Abstract 💜
This doc describes an Extensible Provisioning Protocol (EPP) extension mapping for provisioning and managing E.164 numbers, which stand in for domain names kept in a shared central repository 🧚 It's written in XML, and it extends the EPP domain name mapping to add the extra features needed to provision E.164 numbers 💖
Table of Contents 🗂️
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. E.164 Domain Names . . . . . . . . . . . . . . . . . . . . 3
2.2. NAPTR Fields . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.1. Order . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.2. Preference. . . . . . . . . . . . . . . . . . . . . 4
2.2.3. Flags . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.4. Service . . . . . . . . . . . . . . . . . . . . . . 4
2.2.5. Regular Expression. . . . . . . . . . . . . . . . . 4
2.2.6. Replacement . . . . . . . . . . . . . . . . . . . . 4
3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . . 4
3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 5
3.1.1. EPP <check> Command . . . . . . . . . . . . . . . . 5
3.1.2. EPP <info> Command. . . . . . . . . . . . . . . . . 5
3.1.3. EPP <transfer> Command. . . . . . . . . . . . . . . 7
3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 7
3.2.1. EPP <create> Command. . . . . . . . . . . . . . . . 7
3.2.2. EPP <delete> Command. . . . . . . . . . . . . . . . 9
3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . . 9
3.2.4. EPP <transfer> Command. . . . . . . . . . . . . . . 9
3.2.5. EPP <update> Command. . . . . . . . . . . . . . . . 9
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. Internationalization Considerations . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . 15
9. References. . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 161. Introduction ✨
This doc describes an E.164 number mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) 🌈 The mapping is an extension of the domain name mapping described in [1], it's specified using the Extensible Markup Language (XML) 1.0 as described in [2], and it uses XML Schema notation as described in [3] and [4] 💅
The EPP core protocol specification [5] gives a complete rundown of EPP command and response structures. You need a solid grip on the base protocol specification to get the mapping in this document, so don't skip it 🫶
ENUM [6] explains how the Domain Name System (DNS) can be used to identify services tied to an E.164 number 🔥 The EPP mapping here gives you a way to provision and manage E.164 numbers stored in a shared central repository. Info exchanged through this mapping can be pulled out of the repository and used to publish DNS resource records, as described in ENUM [6]. The examples in this doc were picked specifically to show provisioning concepts for the example resource records in the ENUM spec 🦋
1.1. Conventions Used in This Document 📖
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [7] 💜
In the examples, "C:" marks lines sent by a protocol client, and "S:" marks lines returned by a protocol server 🍓 Indentation and white space in examples are only there to show how elements relate. They are not a REQUIRED feature of this specification, so don't stress about matching them 😭
XML is case sensitive 🙈 Unless stated otherwise, XML specifications and examples in this document MUST be interpreted in the character case presented, so you can build a conforming implementation.
2. Object Attributes 🧁
This extension adds elements to the EPP domain name mapping [1]. Only the descriptions of the new elements are covered here, so keep the base mapping open next to this one 📌
2.1. E.164 Domain Names 📞
An E.164 domain name is an E.164 number that has been translated so it fits domain name syntax, as described in the ENUM specification [6] 🌸 How the labels in an E.164 domain name's name space are organized is a policy matter, and that's out of scope for this document 🙃
2.2. NAPTR Fields 🗝️
According to ENUM [6], Naming Authority Pointer (NAPTR) resource records are used to find the available ways to contact a specific node. That node is identified by a domain name made from translating an E.164 number 🧚 The basic NAPTR record format is described in RFC 3403 [8]. The rules for structuring and using NAPTR records with ENUM are described in RFC 3761 [6] ✨
Several NAPTR field values are optional per RFC 3403. RFC 3761 describes processing rules that require certain NAPTR field values to be present, and this document describes the field value requirements that match up with RFC 3761 💅
2.2.1. Order 🔢
The NAPTR order field is a 16-bit unsigned integer. In this mapping it's represented with the XML Schema unsignedShort data type 💖
2.2.2. Preference 🌟
The NAPTR preference field is also a 16-bit unsigned integer. In this mapping it's represented with the XML Schema unsignedShort data type 🎀
2.2.3. Flags 🚩
The NAPTR flags field is represented in this mapping as a single character. Case doesn't matter for the flag character, so it's not significant 🦋
2.2.4. Service 🛎️
The NAPTR service field is represented in this mapping as a character string with no specified maximum length. Valid values depend on the application 🌈
2.2.5. Regular Expression 🙈
The NAPTR regexp field is represented in this mapping as a character string with no specified maximum length. This field can contain lots of backslashes, so it should be treated with care 💀
2.2.6. Replacement 🔁
The NAPTR replacement field has a domain name as its value. In this mapping it's represented as a character string with a maximum length of 255 characters 🫶
3. EPP Command Mapping 🚀
A detailed description of EPP syntax and semantics is in the EPP core protocol specification [5] 👑 The command mappings here are meant specifically for implementing ENUM provisioning processes through EPP, so that's the lens to read them through 💜
3.1. EPP Query Commands 🔍
EPP gives you three commands for retrieving object information. <check> tells you if the server knows about an object, <info> pulls the detailed info tied to an object, and <transfer> retrieves an object's transfer status information ⭐
3.1.1. EPP <check> Command ✅
This extension doesn't add any elements to the EPP <check> command or the <check> response described in the EPP domain mapping [1]. The base mapping's <check> behaviour is all you need here 🎀
3.1.2. EPP <info> Command ✨
okay so this extension doesn't add anything new to the EPP <info> command from the EPP domain mapping [1] 💅 but it does add stuff to the <info> response 🎀
when an <info> command goes through successfully, the <resData> element MUST have the child elements that the EPP domain mapping [1] describes. on top of that, the EPP <extension> element MUST hold a child <e164:infData> element. that one tells everyone which extension namespace is in use and where to find the extension schema 🗺️ the <e164:infData> element has one or more <e164:naptr> elements, and each of those has these child elements:
- An
<e164:order>element that contains a NAPTR order value. 🔢 - An
<e164:pref>element that contains a NAPTR preference value. 💜 - An OPTIONAL
<e164:flags>element that contains a NAPTR flags value. 🚩 - An
<e164:svc>element that contains a NAPTR service value. 🛎️ - An OPTIONAL
<e164:regex>element that contains a NAPTR regular expression value. ✍️ - An OPTIONAL
<e164:replacement>element that contains a NAPTR replacement value. 🔁
here's an example <info> response, bestie, look at how clean it is 🦋
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
S: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
S: epp-1.0.xsd">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
S: domain-1.0.xsd">
S: <domain:name>3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok"/>
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns2.example.com</domain:hostObj>
S: </domain:ns>
S: <domain:host>ns1.example.com</domain:host>
S: <domain:host>ns2.example.com</domain:host>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:upID>ClientX</domain:upID>
S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <e164:infData xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
S: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
S: e164epp-1.0.xsd">
S: <e164:naptr>
S: <e164:order>10</e164:order>
S: <e164:pref>100</e164:pref>
S: <e164:flags>u</e164:flags>
S: <e164:svc>E2U+sip</e164:svc>
S: <e164:regex>"!^.*$!sip:info@example.com!"</e164:regex>
S: </e164:naptr>
S: <e164:naptr>
S: <e164:order>10</e164:order>
S: <e164:pref>102</e164:pref>
S: <e164:flags>u</e164:flags>
S: <e164:svc>E2U+msg</e164:svc>
S: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
S: </e164:naptr>
S: </e164:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S:</epp>and if an extended <info> command can not be processed for any reason, an EPP error response MUST be returned 🚨 no excuses, periodt 😭
3.1.3. EPP <transfer> Command 🦋
this one's a chill pass 🌸 this extension doesn't add any elements to the EPP <transfer> command or the <transfer> response from the EPP domain mapping [1]. nothing new, nothing extra, just vibes ✨
3.2. EPP Transform Commands 🛠️
okay so EPP gives us five commands to transform objects 🎀 there's <create> to make an instance of an object, <delete> to delete one, <renew> to extend how long an object is valid, <transfer> to manage sponsorship changes, and <update> to change the info attached to an object. five main characters, iconic 👑
3.2.1. EPP <create> Command 💖
this extension defines additional elements for the EPP <create> command from the EPP domain mapping [1] 💅 but the <create> response doesn't get any new elements, so it's giving simple 🫶
the EPP <create> command is the transform operation that lets a client create a domain object 🏠 on top of the EPP command elements from the EPP domain mapping [1], the command MUST have an <extension> element. that <extension> element MUST hold a child <e164:create> element, which names the extension namespace and where the extension schema lives. the <e164:create> element has one or more <e164:naptr> elements, and each one has these child elements:
- An
<e164:order>element that contains a NAPTR order value. 🔢 - An
<e164:pref>element that contains a NAPTR preference value. 💜 - An OPTIONAL
<e164:flags>element that contains a NAPTR flags value. 🚩 - An
<e164:svc>element that contains a NAPTR service value. 🛎️ - An OPTIONAL
<e164:regex>element that contains a NAPTR regular expression value. ✍️ - An OPTIONAL
<e164:replacement>element that contains a NAPTR replacement value. 🔁
here's an example <create> command, it's giving main character energy 🧚
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <create>
C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa</domain:name>
C: <domain:period unit="y">2</domain:period>
C: <domain:ns>
C: <domain:hostObj>ns1.example.com</domain:hostObj>
C: <domain:hostObj>ns2.example.com</domain:hostObj>
C: </domain:ns>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <e164:create
C: xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
C: e164epp-1.0.xsd">
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>100</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+sip</e164:svc>
C: <e164:regex>"!^.*$!sip:info@example.com!"</e164:regex>
C: </e164:naptr>
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>102</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+msg</e164:svc>
C: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
C: </e164:naptr>
C: </e164:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>when an extended <create> command has been processed successfully, the EPP response is just as described in the EPP domain mapping [1] 🎉
3.2.2. EPP <delete> Command 🗑️
no drama here 🙈 this extension doesn't add any elements to the EPP <delete> command or the <delete> response from the EPP domain mapping [1]. same as before, nothing new to see ✨
3.2.3. EPP <renew> Command 🔄
same energy again, bestie 🌈 this extension doesn't add any elements to the EPP <renew> command or the <renew> response from the EPP domain mapping [1]. literally nothing new, and I'm here for the consistency 💅
3.2.4. EPP <transfer> Command 🦋
yep, it's the transfer one again 💜 this extension doesn't add any elements to the EPP <transfer> command or the <transfer> response from the EPP domain mapping [1]. we've been here before, we're fine 🫶
3.2.5. EPP <update> Command 🛠️
okay this one's a little more interesting 👀 this extension defines additional elements for the EPP <update> command from the EPP domain mapping [1], but the <update> response doesn't get anything new 💖
the EPP <update> command is the transform operation that lets a client change the state of a domain object ✨ on top of the EPP command elements from the EPP domain mapping [1], the <update> command MUST have an <extension> element. that <extension> element MUST hold a child <e164:update> element, which names the extension namespace and where the extension schema lives. the <e164:update> element has one or more <e164:add> or <e164:rem> elements. each <e164:add> and <e164:rem> element contains an <e164:naptr> element, and that one has these child elements:
- An
<e164:order>element that contains a NAPTR order value. 🔢 - An
<e164:pref>element that contains a NAPTR preference value. 💜 - An OPTIONAL
<e164:flags>element that contains a NAPTR flags value. 🚩 - An
<e164:svc>element that contains a NAPTR service value. 🛎️ - An OPTIONAL
<e164:regex>element that contains a NAPTR regular expression value. ✍️ - An OPTIONAL
<e164:replacement>element that contains a NAPTR replacement value. 🔁
here's an example <update> command 🎀
C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
C: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
C: epp-1.0.xsd">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
C: domain-1.0.xsd">
C: <domain:name>3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <e164:update xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
C: xsi:schemaLocation="urn:ietf:params:xml:ns:e164epp-1.0
C: e164epp-1.0.xsd">
C: <e164:rem>
C: <e164:naptr>
C: <e164:order>10</e164:order>
C: <e164:pref>102</e164:pref>
C: <e164:flags>u</e164:flags>
C: <e164:svc>E2U+msg</e164:svc>
C: <e164:regex>"!^.*$!mailto:info@example.com!"</e164:regex>
C: </e164:naptr>
C: </e164:rem>
C: </e164:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C:</epp>and when an extended <update> command has been processed successfully, the EPP response is just as described in the EPP domain mapping [1] 💜✨
4. Formal Syntax 🎀
okay so the EPP object mapping is written in XML Schema notation, and this is the full schema bestie 💅 It's a complete representation, so you can use it to auto-validate EPP XML instances. The BEGIN and END lines aren't part of the schema itself. They just mark where it starts and ends for URI registration purposes ✨
BEGIN
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:e164epp-1.0"
xmlns:e164="urn:ietf:params:xml:ns:e164epp-1.0"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<annotation>
<documentation>
Extensible Provisioning Protocol v1.0
domain name extension schema for E.164 number provisioning.
</documentation>
</annotation>
<!--
Child elements found in EPP commands.
-->
<element name="create" type="e164:createType"/>
<element name="update" type="e164:updateType"/>
<!--
Global elements.
-->
<element name="naptr" type="e164:naptrType"/>
<!--
Child elements of the <create> command.
-->
<complexType name="createType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="naptrType">
<sequence>
<element name="order" type="unsignedShort"/>
<element name="pref" type="unsignedShort"/>
<element name="flags" type="e164:flagsType"
minOccurs="0"/>
<element name="svc" type="e164:svcType"/>
<element name="regex" type="e164:regexType"
minOccurs="0"/>
<element name="repl" type="e164:replType"
minOccurs="0"/>
</sequence>
</complexType>
<simpleType name="flagsType">
<restriction base="token">
<pattern value="[A-Z]|[a-z]|[0-9]"/>
<length value="1"/>
</restriction>
</simpleType>
<simpleType name="svcType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<simpleType name="regexType">
<restriction base="token">
<minLength value="1"/>
</restriction>
</simpleType>
<simpleType name="replType">
<restriction base="token">
<minLength value="1"/>
<maxLength value="255"/>
</restriction>
</simpleType>
<!--
Child elements of the <update> command.
-->
<complexType name="updateType">
<sequence>
<element name="add" type="e164:addRemType"
minOccurs="0"/>
<element name="rem" type="e164:addRemType"
minOccurs="0"/>
</sequence>
</complexType>
<!--
Data elements that can be added or removed.
-->
<complexType name="addRemType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
Child response elements.
-->
<element name="infData" type="e164:infDataType"/>
<!--
<info> response elements.
-->
<complexType name="infDataType">
<sequence>
<element ref="e164:naptr" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!--
End of schema.
-->
</schema>
END5. Internationalization Considerations 🌍
EPP is written in XML, and XML natively handles Unicode characters, including the compact forms like UTF-8 [10]. Conformant XML processors understand both UTF-8 and UTF-16 [11] ✨ XML can also work with other encodings if you declare one with an "encoding" attribute in the <?xml?> declaration, but UTF-8 is RECOMMENDED wherever parsers might not support the encoding you picked. Otherwise things get messy, and nobody wants that 🙈
This is an extension of the EPP domain mapping [1], so the elements, element content, attributes, and attribute values in this document MUST inherit the internationalization conventions already used for the higher-layer domain and core protocol structures in any XML instance that includes this extension. Basically, it has to match its family 🫶
6. IANA Considerations 🦋
This document uses URNs to describe XML namespaces and XML schemas, following a registry mechanism from RFC 3688 [9]. Two URI assignments have been completed by the IANA, so they're officially in the books 👑
Registration for the extension namespace:
URI: urn:ietf:params:xml:ns:e164epp-1.0
Registrant Contact: IESG
XML: None. Namespace URIs do not represent an XML specification.Registration for the extension XML schema:
URI: urn:ietf:params:xml:schema:e164epp-1.0
Registrant Contact: IESG
XML: See the "Formal Syntax" section of this document.7. Security Considerations 💀
okay this part is serious, so listen up 🔥 The mapping extensions here don't add any security services beyond what EPP [5], the EPP domain name mapping [1], and the protocol layers EPP sits on already give you. Security concerns for ENUM are covered in the "Security Considerations" section of the ENUM specification [6]. Security concerns for the Dynamic Delegation Discovery System and NAPTR records are covered in the "Security Considerations" section of RFC 3403 [8]. All of those apply to this spec too, so don't skip them 😭
Just like with other domain object transforms, the EPP transform operations in this document MUST be restricted to the sponsoring client, authenticated using the mechanisms described in sections 2.9.1.1 and 7 of RFC 3730 [5]. If any client that isn't the sponsoring client tries to transform a domain object, it MUST be rejected with an appropriate EPP authorization error. No sneaking in, bestie 🚫
8. Acknowledgements 🫶
The author would like to thank the following people, who made significant contributions to this document: Lawrence Conroy, Edward Lewis, Michael Mealling, Allison Mankin, Chip Sharp, and James Yu. Literal legends 🌸
9. References 📚
9.1. Normative References
- [1] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", RFC 3731, March 2004.
- [2] Paoli, J., Sperberg-McQueen, C., Bray, T., and E. Maler, "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C FirstEdition REC-xml-20001006, October 2000.
- [3] Maloney, M., Beech, D., Mendelsohn, N., and H. Thompson, "XML Schema Part 1: Structures", W3C REC REC-xmlschema-1-20010502, May 2001.
- [4] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes", W3C REC REC-xmlschema-2-20010502, May 2001.
- [5] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 3730, March 2004.
- [6] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
- [7] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
- [8] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403, October 2002.
- [9] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
9.2. Informative References
- [10] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
- [11] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, February 2000.
Author's Address 🖋️
Scott Hollenbeck
VeriSign, Inc.
21345 Ridgetop Circle
Dulles, VA 20166-6503
US
EMail: shollenbeck@verisign.comFull Copyright Statement ©️
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property 🔒
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document, or the extent to which any license under such rights might or might not be available. It also doesn't represent that it has made any independent effort to identify any such rights. Information on the procedures for rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat, any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
Acknowledgement 💖
Funding for the RFC Editor function is currently provided by the Internet Society. ✨
📦 where this page comes from
- ietf: rfc4114 2005-06
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms