draft-ietf-weirds-bootstrap-03.txt   draft-ietf-weirds-bootstrap-04.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft G. Guillaume Internet-Draft G. Leclanche
Intended status: Standards Track Viagenie Intended status: Standards Track Viagenie
Expires: December 30, 2014 June 28, 2014 Expires: January 4, 2015 July 3, 2014
Finding the Authoritative Registration Data (RDAP) Service Finding the Authoritative Registration Data (RDAP) Service
draft-ietf-weirds-bootstrap-03.txt draft-ietf-weirds-bootstrap-04.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. System numbers.
Status of This Memo Status of This Memo
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 December 30, 2014. This Internet-Draft will expire on January 4, 2015.
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
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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. Conventions Used In This Document . . . . . . . . . . . . . . 2 2. Conventions Used In This Document . . . . . . . . . . . . . . 2
3. Structure of RDAP Bootstrap Registries . . . . . . . . . . . 3 3. Structure of RDAP Bootstrap Registries . . . . . . . . . . . 3
4. Domain Name RDAP Bootstrap Registry . . . . . . . . . . . . . 3 4. Domain Name RDAP Bootstrap Registry . . . . . . . . . . . . . 4
5. Internet Numbers RDAP Bootstrap Registries . . . . . . . . . 4 5. Internet Numbers RDAP Bootstrap Registries . . . . . . . . . 5
5.1. IPv4 Address Space RDAP Bootstrap Registry . . . . . . . 5 5.1. IPv4 Address Space RDAP Bootstrap Registry . . . . . . . 5
5.2. IPv6 Address Space RDAP Registry . . . . . . . . . . . . 6 5.2. IPv6 Address Space RDAP Registry . . . . . . . . . . . . 6
5.3. Autonomous Systems RDAP Bootstrap Registry . . . . . . . 6 5.3. Autonomous Systems RDAP Bootstrap Registry . . . . . . . 7
6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 7 7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 9
8. Deployment and Implementation Considerations . . . . . . . . 8 8. Deployment and Implementation Considerations . . . . . . . . 9
9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 10
10. Security Considerations . . . . . . . . . . . . . . . . . . . 9 10. Security Considerations . . . . . . . . . . . . . . . . . . . 10
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
13.1. Normative References . . . . . . . . . . . . . . . . . . 10 13.1. Normative References . . . . . . . . . . . . . . . . . . 11
13.2. Non-Normative References . . . . . . . . . . . . . . . . 10 13.2. Non-Normative References . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
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 the fact that allocation data for
names and IP addresses are maintained by IANA, are publicly available domain names and IP addresses are maintained by IANA, are publicly
and are in a structured format. The mechanism assumes some data available and are in a structured format. The mechanism assumes some
structure within these registries and request IANA to create these data structure within these registries and request IANA to create
registries for the specific purpose of RDAP use, herein named RDAP these registries for the specific purpose of RDAP use, herein named
Bootstrap registries. An RDAP client fetches the RDAP bootstrap RDAP Bootstrap registries. An RDAP client fetches the RDAP bootstrap
registries, extract the data and then do a match with the query data registries, extract the data and then do a match with the query data
to find the authoritative registration data server and appropriate to find the authoritative registration data server and appropriate
query base URL. query base URL.
2. Conventions Used In This Document 2. Conventions Used In This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Structure of RDAP Bootstrap Registries 3. Structure of RDAP Bootstrap Registries
The RDAP Bootstrap Registries are implemented as JSON [RFC7159] The RDAP Bootstrap Registries are implemented as JSON [RFC7159]
objects. A registry starts with metadata such as a version id objects. A registry starts with metadata such as a version id
identified as a timestamp of the publication date of the registry and identified as a timestamp of the publication date of the registry and
some defaults values. Then follows an array of arrays. Each second some defaults values. Then the "services" element is an array of
level array lists all the entries available by the same template arrays. Each second level array contains two elements, each of them
method. There is no assumption of sorting at the first or second being an array (third-level arrays). The first third-level array
level arrays. An example structure of a JSON RDAP Bootstrap Registry contains all entries that have the same set of base RDAP URLs, as
is illustrated: strings, arrays, or integers. The second third-level array contains
the list of base RDAP URLs usable for the entries found in the first
third-level array. There is no assumption of sorting at the first-
level arrays. The two arrays found in each second-level array MUST
appear in the correct order: array of entries first, then array of
base RDAP URLs. An example structure of a JSON RDAP Bootstrap
Registry is illustrated:
{ {
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "1.0", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ", "publication": "YYYY-MM-DDTHH:MM:SSZ",
"scheme": [ https http ],
"services": [ "services": [
["entry1", "entry2", "entry3"]: { [
"template": "{proto}://registry.example.com/myrdap/{resource}", ["entry1", "entry2", "entry3"],
"proto": [ https ], [
}, "https://registry.example.com/myrdap/",
["entry4"]: { "http://registry.example.com/myrdap/"
"template": "{proto}://example.org/{resource}", ]
}, ],
], [
} ["entry4"],
[
"http://example.org/"
]
]
]
}
} }
The version corresponds to the format version of the registry. This The version corresponds to the format version of the registry. This
specification defines "1.0". The syntax of "publication" value specification defines "1.0". The syntax of "publication" value
conforms to the Internet date/time format [RFC3339]. The "proto" conforms to the Internet date/time format [RFC3339]. Per [RFC7258],
object is an array of transport protocols used to access the in each array of base RDAP URLs, the secure version of the transport
resource. The RDAP bootstrap client SHOULD try the transport protocol SHOULD be first.
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.
Any unknown or unspecified JSON object properties or values should be Any unknown or unspecified JSON object properties or values should be
ignored by implementers. ignored by implementers.
4. Domain Name RDAP Bootstrap Registry 4. Domain Name RDAP Bootstrap Registry
This registry contains domain labels entries attached to the root, This registry contains domain labels entries attached to the root,
grouped by templates, as shown in this example. grouped by base RDAP URLs, as shown in this example.
{ {
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "1.0", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ", "publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ],
"services": [ "services": [
["net", "com"]: { [
"template": "https://registry.example.com/myrdap/{resource}", ["net", "com"],
}, [
["org", "mytld"]: { "https://registry.example.com/myrdap/"
"template": "{proto}://example.org/{resource}", ]
}, ],
], [
["mytld2"]: { ["org", "mytld"],
"template": "{proto}://example.net/rdapmytld2/{resource}", [
"proto": [ "http", "https"], "http://example.org/"
}, ]
], ],
} [
["mytld2"],
[
"https://example.net/rdapmytld2/",
"http://example.net/rdapmytld2/"
]
]
]
}
} }
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 domain doing the longest match of the target domain name with the domain
values in the arrays in the IANA Domain Name RDAP Bootstrap Registry. values in the arrays in the IANA Domain Name RDAP Bootstrap Registry.
This is a string search of the longest match starting from the end of This is a string search of the longest match starting from the end of
the target name and the end of each value in the arrays. The value the target name and the end of each value in the arrays. The values
of the corresponding "template" object is the base RDAP URL as contained in the second element of the array are the valid base RDAP
described in [I-D.ietf-weirds-rdap-query]. URLs as described in [I-D.ietf-weirds-rdap-query].
For example, a domain RDAP query for a.b.example.com matches the com For example, a domain RDAP query for a.b.example.com matches the com
entry in one of the arrays of the registry. Following the example entry in one of the arrays of the registry. The base RDAP URL for
above, the base RDAP URL for this query is this query is then taken from the second element of the array, which
"https://registry.example.com/myrdap/". The {resource} specified in is an array of base RDAP URLs valid for this entry. The client
[I-D.ietf-weirds-rdap-query] is then appended to the base URL to chooses one of the base URLs from this array; in this example it
complete the query. The complete query is then chooses the only one available, "https://registry.example.com/myrdap/
"https://registry.example.com/myrdap/domain/a.b.example.com". This ". The segment specified in [I-D.ietf-weirds-rdap-query] is then
example is not normative. appended to the base URL to complete the query. The complete query
is then "https://registry.example.com/myrdap/domain/a.b.example.com".
This example is not normative.
5. Internet Numbers RDAP Bootstrap Registries 5. Internet Numbers RDAP Bootstrap Registries
This section discusses IPv4 and IPv6 address space and autonomous This section discusses IPv4 and IPv6 address space and autonomous
system numbers. system numbers.
For IP address space, the 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 arrays in the corresponding Address Space RDAP Bootstrap of the arrays in the corresponding Address Space RDAP Bootstrap
registry. The longest match is done the same way as for routing: the registry. The longest match is done the same way as for routing: the
addresses are converted in binary form and then the binary strings addresses are converted in binary form and then the binary strings
are compared to find the longest match. The value of the template are compared to find the longest match. The values contained in the
object is the base RDAP url as described in second element of the array are the base RDAP URLs as described in
[I-D.ietf-weirds-rdap-query]. The longest match method enables [I-D.ietf-weirds-rdap-query]. The longest match method enables
covering prefixes of a larger address space pointing to one RDAP covering prefixes of a larger address space pointing to one base RDAP
template while more specific prefixes within the covering prefix URL while more specific prefixes within the covering prefix being
being served by another RDAP template. served by another base RDAP URL.
5.1. IPv4 Address Space RDAP Bootstrap Registry 5.1. IPv4 Address Space RDAP Bootstrap Registry
This registry contains IPv4 prefix entries, specified in CIDR format This registry contains IPv4 prefix entries, specified in CIDR format
and grouped by templates, as shown in this example. and grouped by RDAP URLs, as shown in this example.
{ {
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "1.0", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ", "publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ],
"services": [ "services": [
["1.0.0.0/8", "192.0.0.0/8"]: { [
"template": "https://rir1.example.com/myrdap/{resource}", ["1.0.0.0/8", "192.0.0.0/8"],
}, [
["28.2.0.0/16", "192.0.2.0/24"]: { "https://rir1.example.com/myrdap/"
"template": "{proto}://example.org/{resource}", ]
}, ],
], [
["28.3.0.0/16"]: { ["28.2.0.0/16", "192.0.2.0/24"],
"template": "{proto}://example.net/rdaprir2/{resource}", [
"proto": [ "http", "https"], "http://example.org/"
}, ]
], ],
} [
["28.3.0.0/16"],
[
"https://example.net/rdaprir2/",
"http://example.net/rdaprir2/"
]
]
]
}
} }
For example, a query for "192.0.2.0/24" matches the "192.0.0.0/8" 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. 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 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 RDAP URL for this query is then taken from the second element of the
expands to "{proto}://example.org/". The {resource} specified in array, which is an array of base RDAP URLs valid for this entry. The
[I-D.ietf-weirds-rdap-query] is then appended to the base URL to client chooses one of the base URLs from this array; in this example
complete the query. The complete query is then "https://example.org/ it chooses the only one available, "http://example.org/". The
ip/192.0.2.0/24". This example is not normative. {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 5.2. IPv6 Address Space RDAP Registry
This registry contains IPv6 prefix entries, using [RFC4291] text This registry contains IPv6 prefix entries, using [RFC4291] text
representation of address prefixes format, grouped by templates, as representation of address prefixes format, grouped by base RDAP URLs,
shown in this example. as shown in this example.
{ {
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "1.0", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ", "publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ],
"services": [ "services": [
["2001:0200::/23", "2001:db8::/32"]: { [
"template": "https://rir2.example.com/myrdap/{resource}", ["2001:0200::/23", "2001:db8::/32"],
}, [
["2600::/16", "2100:ffff::/32"]: { "https://rir2.example.com/myrdap/"
"template": "{proto}://example.org/{resource}", ]
}, ],
["2001:0200:1000::/28"]: { [
"template": "{proto}://example.net/rdaprir2/{resource}", ["2600::/16", "2100:ffff::/32"],
"proto": [ "http", "https"], [
}, "http://example.org/"
], ]
} ],
[
["2001:0200:1000::/28"],
[
"https://example.net/rdaprir2/",
"http://example.net/rdaprir2/"
]
]
]
}
} }
For example, a query for "2001:0200:1000::/48" matches the For example, a query for "2001:0200:1000::/48" matches the
"2001:0200::/23" entry and the "2001:0200:1000::/28" entry in 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 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 longest match. The base RDAP URL for this query is then taken from
the template object "{proto}://example.net/rdaprir2/". The the second element of the array, which is an array of base RDAP URLs
{resource} specified in [I-D.ietf-weirds-rdap-query] is then appended valid for this entry. The client chooses one of the base URLs from
to the base URL to complete the query. The complete query is this array; in this example it chooses "https://example.net/rdaprir2/
therefore "https://example.net/rdaprir2/ip/2001:0200:1000::/48". " because it's the secure version of the protocol. The segment
This example is not normative. 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". If the server
does not answer, the client can then use another URL prefix from the
array. This example is not normative.
5.3. Autonomous Systems RDAP Bootstrap Registry 5.3. Autonomous Systems RDAP Bootstrap Registry
This registry contains Autonomous Systems Number Ranges entries, This registry contains Autonomous Systems Number Ranges entries,
grouped by templates, as shown in this example. Entries in the grouped by base RDAP URLs, as shown in this example. The first
arrays are either single AS numbers or ranges of AS numbers where the element of each second-level array is an array containing the list of
lower appears first, then the "-" separator and then the upper AS numbers served by the base RDAP URLs found in the second element.
number. Both 16bit and 32 bit AS numbers are specified in decimal. When an element of the AS Numbers array is an array with two AS
numbers, then it represents the range of AS Numbers between the two
elements of this array.
{ {
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "1.0", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ", "publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ],
"services": [ "services": [
["2045", "20116-20117"]: { [
"template": "https://rir2.example.com/myrdap/{resource}", [2045],
}, [
["10000-12000", "65900-66000"]: { "https://rir3.example.com/myrdap/"
"template": "{proto}://example.org/{resource}", ]
}, ],
["65512-65534"]: { [
"template": "{proto}://example.net/rdaprir2/{resource}", [[10000, 12000], [300000, 400000]],
"proto": [ "http", "https"], [
}, "http://example.org/"
], ]
} ],
[
[[64512, 65534]],
[
"http://example.net/rdaprir2/",
"https://example.net/rdaprir2/"
]
]
]
}
} }
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 example registry above. The base RDAP URL for this query is then the example registry above. The base RDAP URL for this query is then
taken from the template object "{proto}://example.net/rdaprir2/". taken from the second element of the array, which is an array of base
The {resource} specified in [I-D.ietf-weirds-rdap-query] is then RDAP URLs valid for this entry. The client chooses one of the base
appended to the base URL to complete the query. The complete query URLs from this array; in this example it chooses "https://example.net
is therefore "https://example.net/rdaprir2/autnum/65411". This /rdaprir2/". The segment specified in [I-D.ietf-weirds-rdap-query]
example is not normative. is then appended to the base URL to complete the query. The complete
query is therefore "https://example.net/rdaprir2/autnum/65411". If
the server does not answer, the client can then use another URL
prefix from the array. This example is not normative.
6. 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.
7. 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.
8. Deployment and Implementation 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 registries to then find the servers locally. Clients SHOULD not IANA registries to then find the servers locally. Clients SHOULD NOT
fetch every time the registry. Clients SHOULD cache the registry, fetch every time the registry. Clients SHOULD cache the registry,
but use underlying protocol signalling, such as HTTP Expires header but use underlying protocol signalling, such as HTTP Expires header
field [RFC7234], to identify when it is time to refresh the cached field [RFC7234], to identify when it is time to refresh the cached
registry. registry.
If the query data does not match any entry in the client cached If the query data does not match any entry in the client cached
registry, then the client may implement various methods, such as the registry, then the client may implement various methods, such as the
following: following:
o In the case of a domain object to be RDAP queried, the client may o In the case of a domain object to be RDAP queried, the client may
skipping to change at page 9, line 30 skipping to change at page 10, line 45
o Create a new registry "IPv6 Address Space RDAP Bootstrap Service" o Create a new registry "IPv6 Address Space RDAP Bootstrap Service"
in the JSON format, as shown above. in the JSON format, as shown above.
o Create a new registry "Autonomous System Number Space RDAP o Create a new registry "Autonomous System Number Space RDAP
Bootstrap Service" in the JSON format, as shown above. Bootstrap Service" in the JSON format, as shown above.
o Create a new registry "Domain Name Space RDAP Bootstrap Service" o Create a new registry "Domain Name Space RDAP Bootstrap Service"
in the JSON format, as shown above. in the JSON format, as shown above.
It is envisionned that these new registries will have similar entries It is envisioned that these new registries will have similar entries
than the corresponding IANA allocation registries, such as than the corresponding IANA allocation registries, such as
[ipv4reg],[ipv6reg],[asreg], [domainreg], and possibly similar [ipv4reg],[ipv6reg],[asreg], [domainreg], and possibly similar
registration policies. However, the registration policies for the registration policies. However, the registration policies for the
new registries of this document are left to IANA. new registries of this document are left to IANA.
The registries may be maintained in IANA own format, such as XML. The registries may be maintained in IANA own format, such as XML.
However, the registry should be available in the JSON format, and However, the registry should be available in the JSON format, and
optionally in other formats such as XML. optionally in other formats such as XML.
12. Acknowledgements 12. Acknowledgements
skipping to change at page 11, line 6 skipping to change at page 12, line 26
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC7234] Fielding, R., Nottingham, M., and J. Reschke, "Hypertext [RFC7234] Fielding, R., Nottingham, M., and J. Reschke, "Hypertext
Transfer Protocol (HTTP/1.1): Caching", RFC 7234, June Transfer Protocol (HTTP/1.1): Caching", RFC 7234, June
2014. 2014.
[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an [RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
Attack", BCP 188, RFC 7258, May 2014. 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/as- System (AS) Numbers", <http://www.iana.org/assignments/
numbers/as-numbers.xml>. as-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/ipv4-address- Space", <http://www.iana.org/assignments/
space/ipv4-address-space.xml>. ipv4-address-space/ipv4-address-space.xml>.
[ipv6reg] Internet Assigned Numbers Authority(IANA), , "IPv6 Global [ipv6reg] Internet Assigned Numbers Authority(IANA), , "IPv6 Global
Unicast Address Assignments", Unicast Address Assignments", <http://www.iana.org/
<http://www.iana.org/assignments/ipv6-unicast-address- assignments/ipv6-unicast-address-assignments/
assignments/ipv6-unicast-address-assignments.xml>. ipv6-unicast-address-assignments.xml>.
[ipv6regparent]
Internet Assigned Numbers Authority(IANA), , "Internet
Protocol Version 6 Address Space",
<http://www.iana.org/assignments/ipv6-address-space/
ipv6-address-space.xml>.
Authors' Addresses Authors' Addresses
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
 End of changes. 36 change blocks. 
173 lines changed or deleted 219 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/