draft-ietf-weirds-bootstrap-01.txt   draft-ietf-weirds-bootstrap-02.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft Viagenie Internet-Draft Viagenie
Intended status: Standards Track February 13, 2014 Intended status: Standards Track June 23, 2014
Expires: August 17, 2014 Expires: December 25, 2014
Finding the Authoritative Registration Data (RDAP) Service Finding the Authoritative Registration Data (RDAP) Service
draft-ietf-weirds-bootstrap-01.txt draft-ietf-weirds-bootstrap-02.txt
Abstract Abstract
This document specifies a method to find which Registration Data This document specifies a method to find which Registration Data
Access Protocol (RDAP) server is authoritative to answer queries for Access Protocol (RDAP) server is authoritative to answer queries for
a requested scope, such as domain names, IP addresses or Autonomous a requested scope, such as domain names, IP addresses or Autonomous
System numbers, using data available in IANA registries. System numbers.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 17, 2014. This Internet-Draft will expire on December 25, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Domain Name RDAP Registry . . . . . . . . . . . . . . . . . . 2 2. Conventions Used In This Document . . . . . . . . . . . . . . 2
3. Internet Numbers RDAP Registries . . . . . . . . . . . . . . 3 3. Structure of RDAP Bootstrap Registries . . . . . . . . . . . 3
3.1. IPv4 Address Space RDAP Registry . . . . . . . . . . . . 3 4. Domain Name RDAP Bootstrap Registry . . . . . . . . . . . . . 3
3.2. IPv6 Address Space RDAP Registry . . . . . . . . . . . . 3 5. Internet Numbers RDAP Bootstrap Registries . . . . . . . . . 4
3.3. Autonomous Systems RDAP Registry . . . . . . . . . . . . 3 5.1. IPv4 Address Space RDAP Bootstrap Registry . . . . . . . 5
4. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5.2. IPv6 Address Space RDAP Registry . . . . . . . . . . . . 5
5. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 4 5.3. Autonomous Systems RDAP Bootstrap Registry . . . . . . . 6
6. Deployment Considerations . . . . . . . . . . . . . . . . . . 4 6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. Deployment and Implementation Considerations . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 10. Security Considerations . . . . . . . . . . . . . . . . . . . 8
11. Non-Normative References . . . . . . . . . . . . . . . . . . 7 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
13.1. Normative References . . . . . . . . . . . . . . . . . . 10
13.2. Non-Normative References . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Querying and retrieving registration data from registries are defined Querying and retrieving registration data from registries are defined
in the Registration Data Access Protocol(RDAP)[I-D.ietf-weirds-rdap-q in the Registration Data Access Protocol(RDAP)[I-D.ietf-weirds-rdap-q
uery][I-D.ietf-weirds-using-http][I-D.ietf-weirds-json-response]. uery][I-D.ietf-weirds-using-http][I-D.ietf-weirds-json-response].
These documents do not specify where to send the queries. This These documents do not specify where to send the queries. This
document specifies a method to find which server is authoritative to document specifies a method to find which server is authoritative to
answer queries for the requested scope. answer queries for the requested scope.
The proposed mechanism is based on that allocation data for domain The proposed mechanism is based on that allocation data for domain
names and IP addresses are maintained by IANA, are publicly available names and IP addresses are maintained by IANA, are publicly available
and are in a structured format. The mechanism assumes some data and are in a structured format. The mechanism assumes some data
structure within these registries and request IANA to modify or structure within these registries and request IANA to create these
create these registries for the specific purpose of RDAP use. An registries for the specific purpose of RDAP use, herein named RDAP
RDAP client fetches the registries, extract the data and then do a Bootstrap registries. An RDAP client fetches the RDAP bootstrap
match with the query data to find the authoritative registration data registries, extract the data and then do a match with the query data
server and appropriate query base URL. to find the authoritative registration data server and appropriate
query base URL.
2. Domain Name RDAP Registry 2. 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 [RFC2119].
3. Structure of RDAP Bootstrap Registries
The RDAP Bootstrap Registries are implemented as JSON [RFC7159]
objects. A registry starts with metadata such as a version id
identified as a timestamp of the publication date of the registry and
some defaults values. Then follows an array of arrays. Each second
level array lists all the entries available by the same template
method. There is no assumption of sorting at the first or second
level arrays. An example structure of a JSON RDAP Bootstrap Registry
is illustrated:
"rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ https http ],
"services": [
["entry1", "entry2", "entry3"]: {
"template": "{proto}://registry.example.com/myrdap/{resource}",
"proto": [ https ],
},
["entry4"]: {
"template": "{proto}://example.org/{resource}",
},
],
}
The syntax of "version" value conforms to the Internet date/time
format [RFC3339]. The "proto" object is an array of transport
protocols used to access the resource. The RDAP bootstrap client
SHOULD try the transport protocols in the order they are presented in
the array. The "proto" object can be overriden in the specific
entries. Per [RFC7258], the secure version of the transport protocol
SHOULD be first.
4. Domain Name RDAP Bootstrap Registry
This registry contains domain labels entries attached to the root,
grouped by templates, as shown in this example.
"rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ],
"services": [
["net", "com"]: {
"template": "https://registry.example.com/myrdap/{resource}",
},
["org", "mytld"]: {
"template": "{proto}://example.org/{resource}",
},
],
["mytld2"]: {
"template": "{proto}://example.net/rdapmytld2/{resource}",
"proto": [ "http", "https"],
},
],
}
The domain names authoritative registration data service is found by The domain names authoritative registration data service is found by
doing the longest match of the target domain name with the values of doing the longest match of the target domain name with the domain
the Domain column in the IANA Domain Name RDAP registry as defined in values in the arrays in the IANA Domain Name RDAP Bootstrap Registry.
section Section 9. This is a string search of the longest match This is a string search of the longest match starting from the end of
starting from the end of the target name and the end of each value in the target name and the end of each value in the arrays. The value
the Domain column. The value of the "RDAP URL" column is the base of the corresponding "template" object is the base RDAP URL as
RDAP url as described in [I-D.ietf-weirds-rdap-query]. described in [I-D.ietf-weirds-rdap-query].
For example, a RDAP query for example.com matches the .com entry in For example, a domain RDAP query for a.b.example.com matches the com
the Domain column of the registry. The RDAP server URL for this entry in one of the arrays of the registry. Following the example
address is located in the corresponding "RDAP URL" column for that above, the base RDAP URL for this query is
entry, which could be http://rdap.example.org/rdap. Therefore the "https://registry.example.com/myrdap/". The {resource} specified in
query URL would be: http://rdap.example.org/rdap/domain/example.com. [I-D.ietf-weirds-rdap-query] is then appended to the base URL to
This example is not normative. complete the query. The complete query is then
"https://registry.example.com/myrdap/domain/a.b.example.com". This
example is not normative.
3. Internet Numbers RDAP Registries 5. Internet Numbers RDAP Bootstrap Registries
3.1. IPv4 Address Space RDAP Registry This section discusses IPv4 and IPv6 address space and autonomous
system numbers.
The IPv4 address space authoritative registration data service is For IP address space, the authoritative registration data service is
found by doing a longest match of the target address with the values found by doing a longest match of the target address with the values
of the Prefix column in the IANA IPv4 address space RDAP registry as of the arrays in the corresponding Address Space RDAP Bootstrap
defined in section Section 9. The longest match is done the same way registry. The longest match is done the same way as for routing: the
as for routing: the addresses are converted in binary form and then addresses are converted in binary form and then the binary strings
the binary strings are compared. The value of the "RDAP URL" column are compared to find the longest match. The value of the template
is the base RDAP url as described in [I-D.ietf-weirds-rdap-query]. object is the base RDAP url as described in
For example, a query for "192.0.2.0/24" matches the "192/8" entry in [I-D.ietf-weirds-rdap-query]. The longest match method enables
the Prefix column of the registry. The RDAP server URL for this covering prefixes of a larger address space pointing to one RDAP
address is located in the corresponding "RDAP URL" column for that template while more specific prefixes within the covering prefix
entry, which could be http://rdap.example.org/rdap. Therefore the being served by another RDAP template.
query URL would be: http://rdap.example.org/rdap/ip/192.0.2.0/24.
This example is not normative.
3.2. IPv6 Address Space RDAP Registry 5.1. IPv4 Address Space RDAP Bootstrap Registry
The IPv6 address space authoritative registration data service is This registry contains IPv4 prefix entries, specified in CIDR format
found by doing a longest match of the target address with the values and grouped by templates, as shown in this example.
of the Prefix column in the IANA IPv6 address space RDAP registry as
defined in section Section 9. The longest match is done the same way
as for routing: the addresses are converted in binary form and then
the binary strings are compared. The value of the "RDAP URL" column
is the base RDAP url as described in [I-D.ietf-weirds-rdap-query].
For example, a query for "2001:db8::/32" matches the "2001/16" entry "rdap.bootstrap": {
in the Prefix column of the registry. The RDAP server URL for this "version": "YYYY-MM-DDTHH:MM:SSZ",
address is located in the corresponding "RDAP URL" column for that "proto": [ "https", "http" ],
entry, which could be http://rdap.example.org/rdap. Therefore the
query URL would be: http://rdap.example.org/rdap/ip/2001:db8::/32. "services": [
["1.0.0.0/8", "192.0.0.0/8"]: {
"template": "https://rir1.example.com/myrdap/{resource}",
},
["28.2.0.0/16", "192.0.2.0/24"]: {
"template": "{proto}://example.org/{resource}",
},
],
["28.3.0.0/16"]: {
"template": "{proto}://example.net/rdaprir2/{resource}",
"proto": [ "http", "https"],
},
],
}
For example, a query for "192.0.2.0/24" matches the "192.0.0.0/8"
entry and the "192.0.2.0/24" entry in the example registry above.
The latter is chosen by the client given the longest match. The base
RDAP URL for this query is then taken from the template object and
expands to "{proto}://example.org/". The {resource} specified in
[I-D.ietf-weirds-rdap-query] is then appended to the base URL to
complete the query. The complete query is then "https://example.org/
ip/192.0.2.0/24". This example is not normative.
5.2. IPv6 Address Space RDAP Registry
This registry contains IPv6 prefix entries, using [RFC4291] text
representation of address prefixes format, grouped by templates, as
shown in this example.
"rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ],
"services": [
["2001:0200::/23", "2001:db8::/32"]: {
"template": "https://rir2.example.com/myrdap/{resource}",
},
["2600::/16", "2100:ffff::/32"]: {
"template": "{proto}://example.org/{resource}",
},
],
["2001:0200:1000::/28"]: {
"template": "{proto}://example.net/rdaprir2/{resource}",
"proto": [ "http", "https"],
},
],
}
For example, a query for "2001:0200:1000::/48" matches the
"2001:0200::/23" entry and the "2001:0200:1000::/28" entry in the
example registry above. The latter is chosen by the client given the
longest match. The base RDAP URL for this query is then taken from
the template object "{proto}://example.net/rdaprir2/". The
{resource} specified in [I-D.ietf-weirds-rdap-query] is then appended
to the base URL to complete the query. The complete query is
therefore "https://example.net/rdaprir2/ip/2001:0200:1000::/48".
This example is not normative. This example is not normative.
3.3. Autonomous Systems RDAP Registry 5.3. Autonomous Systems RDAP Bootstrap Registry
The Autonomous Systems (AS) authoritative registration data service This registry contains Autonomous Systems Number Ranges entries,
is found by identifying the range in which the target Autonomous grouped by templates, as shown in this example. Entries in the
System is, with the values of the Number column in the IANA arrays are either single AS numbers or ranges of AS numbers where the
Autonomous Systems (AS) Numbers RDAP registry as defined in section lower appears first, then the "-" separator and then the upper
Section 9. The value of the "RDAP URL" column is the base RDAP url number. Both 16bit and 32 bit AS numbers are specified in decimal.
as described in [I-D.ietf-weirds-rdap-query].
"rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ],
"services": [
["2045", "20116-20117"]: {
"template": "https://rir2.example.com/myrdap/{resource}",
},
["10000-12000", "65900-66000"]: {
"template": "{proto}://example.org/{resource}",
},
],
["65512-65534"]: {
"template": "{proto}://example.net/rdaprir2/{resource}",
"proto": [ "http", "https"],
},
],
}
For example, a query for AS 65411 matches the "64512-65534" entry in For example, a query for AS 65411 matches the "64512-65534" entry in
the Number column of the registry. The RDAP server URL for this the example registry above. The base RDAP URL for this query is then
address is located in the corresponding "RDAP URL" column for that taken from the template object "{proto}://example.net/rdaprir2/".
entry, which could be http://rdap.example.org/rdap. Therefore the The {resource} specified in [I-D.ietf-weirds-rdap-query] is then
query URL would be: http://rdap.example.org/rdap/autnum/65411. This appended to the base URL to complete the query. The complete query
is therefore "https://example.net/rdaprir2/autnum/65411". This
example is not normative. example is not normative.
4. Entity 6. Entity
Since there is no global namespace for entities, this document does Since there is no global namespace for entities, this document does
not describe how to find the authoritative RDAP server for entities. not describe how to find the authoritative RDAP server for entities.
It is possible however that, if the entity identifier was received It is possible however that, if the entity identifier was received
from a previous query, the same RDAP server could be queried for that from a previous query, the same RDAP server could be queried for that
entity or the entity identifier itself is a fully referenced URL that entity or the entity identifier itself is a fully referenced URL that
can be queried. can be queried.
5. Non-existent Entries or RDAP URL Values 7. Non-existent Entries or RDAP URL Values
The registries may not contain the requested value or the RDAP URL The registries may not contain the requested value or the RDAP URL
value may be empty. In these cases, there is no known RDAP server value may be empty. In these cases, there is no known RDAP server
for that requested value and the client should provide an appropriate for that requested value and the client SHOULD provide an appropriate
error message to the user. error message to the user.
6. Deployment Considerations 8. Deployment and Implementation Considerations
This method relies on the fact that RDAP clients are fetching the This method relies on the fact that RDAP clients are fetching the
IANA XML registries. Clients SHOULD not fetch every time the XML IANA registries to then find the servers locally. Clients SHOULD not
files. fetch every time the registry. Clients SHOULD cache the registry,
but use underlying protocol signalling, such as HTTP Expires header
field [RFC7234], to identify when it is time to refresh the cached
registry.
If the query data does not match any entry in the already fetched If the query data does not match any entry in the client cached
registry in the client, then the client may implement various registry, then the client may implement various methods, such as the
methods, such as the following: following:
o The client first queries the DNS to see if the respective entry o In the case of a domain object to be RDAP queried, the client may
has been recently delegated or if it is a mistyped information by first query the DNS to see if the respective entry has been
the user. The DNS query could be to fetch the NS records for a delegated or if it is a mistyped information by the user. The DNS
domain TLD. If the DNS answer is negative, then there is no need query could be to fetch the NS records for the TLD domain. If the
to fetch the new version of the XML registry. However, if the DNS DNS answer is negative, then there is no need to fetch the new
answer is positive, this means that the currently cached XML version of the registry. However, if the DNS answer is positive,
registry is no more current. The client should fetch the this may mean that the currently cached registry is no more
registry, parse and then do the normal matching as specified current. The client could then fetch the registry, parse and then
above. do the normal matching as specified above. This method may not
work for all types of RDAP objects.
o If the client knows the existence of a RDAP aggregator or o If the client knows the existence of a RDAP aggregator or
redirector and trust that service, then it could send the query to redirector and trust that service, then it could send the query to
the redirector, which would redirect the client if it knows the the redirector, which would redirect the client if it knows the
authoritative server that client has not found. authoritative server that client has not found.
o Clients can also rely on HTTP headers to verify if the registry
has changed since last time it was fetched, without the need to
fetch the whole registry.
IANA should make sure that the service of those registries is able to IANA should make sure that the service of those registries is able to
cope with a larger demand and should take appropriate measures such cope with a larger demand and should take appropriate measures such
as caching and load balancing. as caching and load balancing.
This specification makes no assumption on how the authorities of This specification does not assume while not prohibiting how some
registration data may work together on sharing their information for authorities of registration data may work together on sharing their
a common service. information for a common service, including mutual
redirection[I-D.ietf-weirds-redirects].
7. Limitations 9. Limitations
This method does not provide a direct way to find authoritative RDAP This method does not provide a direct way to find authoritative RDAP
servers: servers:
o for entities o for entities
o for queries using search patterns that do not contain a o for queries using search patterns that do not contain a
terminating string that matches some entries in the registries terminating string that matches some entries in the registries
8. Security Considerations 10. Security Considerations
By providing a bootstrap method to find RDAP servers, this document By providing a bootstrap method to find RDAP servers, this document
helps making sure that the end-users will get the RDAP data from helps making sure that the end-users will get the RDAP data from
authoritative source, instead of from rogue sources. The method authoritative source, instead of from rogue sources. The method
itself has the same security properties as the RDAP protocols itself has the same security properties as the RDAP protocols
themselves. The transport used to access the registries could be themselves. The transport used to access the registries could be
secured by TLS if IANA supports it. more secure by using TLS [RFC5246] if IANA supports it.
9. IANA Considerations 11. IANA Considerations
IANA is requested to do the following: IANA is requested to do the following:
o Create a new registry for IPv4 address space with the following o Create a new registry "IPv4 Address Space RDAP Bootstrap Service"
columns: the first column is the entries taken from the current in the JSON format, as shown above.
"IPv4 Address Space" registry[ipv4reg] and and the second column
is the RDAP server URL. The same registrants for these entries
are entitled to provide the RDAP URL value for their respective
space, using the same communication channels already established
between the registrants and IANA.
o Create a new registry for IPv6 address space with the following
columns: the first column is the entries taken from the current
IPv6 Address Space registries [ipv6regparent][ipv6reg] and the
second column is the RDAP server URL. The same registrants for
these entries are entitled to provide the RDAP URL value for their
respective space, using the same communication channels already
established between the registrants and IANA.
o Create a new registry for Autonomous System Number space with the o Create a new registry "IPv6 Address Space RDAP Bootstrap Service"
following columns: the first column is the entries taken from the in the JSON format, as shown above.
current "Autonomous System Number Space" registry[asreg] and the
second column is the RDAP server URL. The same registrants for
these entries are entitled to provide the RDAP URL value for their
respective space, using the same communication channels already
established between the registrants and IANA.
o Create a new registry of domain names, essentially TLDs, with the o Create a new registry "Autonomous System Number Space RDAP
following columns: Domain and RDAP URL. The content should be Bootstrap Service" in the JSON format, as shown above.
initially populated by an extract of the Root zone
database[domainreg]. The same registrants for these entries are
entitled to provide the RDAP URL value for their respective space,
using the same communication channels already established between
the registrants and IANA.
o A change happening in any of the source registries should trigger o Create a new registry "Domain Name Space RDAP Bootstrap Service"
a change in the corresponding new registry. For example, a new in the JSON format, as shown above.
IPv6 address block appearing in the source IPv6 address space
registry should trigger the same new entry in the corresponding
RDAP registry.
o IANA shall update its procedures to include the provisioning of It is envisionned that these new registries will have similar entries
these values. than the corresponding IANA allocation registries, such as
[ipv4reg],[ipv6reg],[asreg], [domainreg], and possibly similar
registration policies. However, the registration policies for the
new registries of this document are left to IANA.
o It is envisioned that the entries of each of these registries are The registries may be maintained in IANA own format, such as XML.
synched from the source assignment registries. There shall be no However, the registry should be available in the JSON format, and
additional records. If there is a need for additional records, optionally in other formats such as XML.
then the policy for updating the registry is Standards Track RFC.
10. Acknowledgements 12. Acknowledgements
The weirds working group had multiple discussions on this topic, The weirds working group had multiple discussions on this topic,
including a session during IETF 84. The idea of using IANA including a session during IETF 84, where various methods such as in-
registries was discovered by the editor during discussions with his DNS and others were debated. The idea of using IANA registries was
colleagues as well as by a comment from Andy Newton. All the people discovered by the editor during discussions with his colleagues as
involved in these discussions are herein acknowledged. Linlin Zhou, well as by a comment from Andy Newton. All the people involved in
Jean-Philippe Dionne, John Levine, Kim Davies, Ernie Dainow, Scott these discussions are herein acknowledged. Linlin Zhou, Jean-
Hollenbeck, Arturo Servin, Andy Newton have provided input and Philippe Dionne, John Levine, Kim Davies, Ernie Dainow, Scott
suggestions to this document. Hollenbeck, Arturo Servin, Andy Newton, Murray Kucherawy have
provided input and suggestions to this document.
11. Non-Normative References 13. References
13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, March 2014.
13.2. Non-Normative References
[I-D.ietf-weirds-json-response] [I-D.ietf-weirds-json-response]
Newton, A. and S. Hollenbeck, "JSON Responses for the Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", draft-ietf- Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-json-response-06 (work in progress), October 2013. weirds-json-response-07 (work in progress), April 2014.
[I-D.ietf-weirds-rdap-query] [I-D.ietf-weirds-rdap-query]
Newton, A. and S. Hollenbeck, "Registration Data Access Newton, A. and S. Hollenbeck, "Registration Data Access
Protocol Query Format", draft-ietf-weirds-rdap-query-10 Protocol Query Format", draft-ietf-weirds-rdap-query-10
(work in progress), February 2014. (work in progress), February 2014.
[I-D.ietf-weirds-redirects]
Martinez, C., Zhou, L., and G. Rada, "Redirection Service
for Registration Data Access Protocol", draft-ietf-weirds-
redirects-03 (work in progress), February 2014.
[I-D.ietf-weirds-using-http] [I-D.ietf-weirds-using-http]
Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the
Registration Data Access Protocol (RDAP)", draft-ietf- Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-using-http-08 (work in progress), February 2014. weirds-using-http-08 (work in progress), February 2014.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC7234] Fielding, R., Nottingham, M., and J. Reschke, "Hypertext
Transfer Protocol (HTTP/1.1): Caching", RFC 7234, June
2014.
[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
Attack", BCP 188, RFC 7258, May 2014.
[asreg] Internet Assigned Numbers Authority(IANA), , "Autonomous [asreg] Internet Assigned Numbers Authority(IANA), , "Autonomous
System (AS) Numbers", <http://www.iana.org/assignments/ System (AS) Numbers", <http://www.iana.org/assignments/as-
as-numbers/as-numbers.xml>. numbers/as-numbers.xml>.
[domainreg] [domainreg]
Internet Assigned Numbers Authority(IANA), , "Root Zone Internet Assigned Numbers Authority(IANA), , "Root Zone
Database", <http://www.iana.org/domains/root/db>. Database", <http://www.iana.org/domains/root/db>.
[ipv4reg] Internet Assigned Numbers Authority(IANA), , "IPv4 Address [ipv4reg] Internet Assigned Numbers Authority(IANA), , "IPv4 Address
Space", <http://www.iana.org/assignments/ Space", <http://www.iana.org/assignments/ipv4-address-
ipv4-address-space/ipv4-address-space.xml>. space/ipv4-address-space.xml>.
[ipv6reg] Internet Assigned Numbers Authority(IANA), , "IPv6 Global [ipv6reg] Internet Assigned Numbers Authority(IANA), , "IPv6 Global
Unicast Address Assignments", <http://www.iana.org/ Unicast Address Assignments",
assignments/ipv6-unicast-address-assignments/ <http://www.iana.org/assignments/ipv6-unicast-address-
ipv6-unicast-address-assignments.xml>. assignments/ipv6-unicast-address-assignments.xml>.
[ipv6regparent] [ipv6regparent]
Internet Assigned Numbers Authority(IANA), , "Internet Internet Assigned Numbers Authority(IANA), , "Internet
Protocol Version 6 Address Space", <http://www.iana.org/ Protocol Version 6 Address Space",
assignments/ipv6-address-space/ipv6-address-space.xml>. <http://www.iana.org/assignments/ipv6-address-space/
ipv6-address-space.xml>.
Author's Address Author's Address
Marc Blanchet Marc Blanchet
Viagenie Viagenie
246 Aberdeen 246 Aberdeen
Quebec, QC G1R 2E1 Quebec, QC G1R 2E1
Canada Canada
Email: Marc.Blanchet@viagenie.ca Email: Marc.Blanchet@viagenie.ca
URI: http://www.viagenie.ca URI: http://www.viagenie.ca
 End of changes. 50 change blocks. 
163 lines changed or deleted 311 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/