draft-ietf-weirds-bootstrap-04.txt   draft-ietf-weirds-bootstrap-05.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft G. Leclanche Internet-Draft G. Leclanche
Intended status: Standards Track Viagenie Intended status: Standards Track Viagenie
Expires: January 4, 2015 July 3, 2014 Expires: March 1, 2015 August 28, 2014
Finding the Authoritative Registration Data (RDAP) Service Finding the Authoritative Registration Data (RDAP) Service
draft-ietf-weirds-bootstrap-04.txt draft-ietf-weirds-bootstrap-05.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 January 4, 2015. This Internet-Draft will expire on March 1, 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 11 skipping to change at page 2, line 11
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 . . . . . . . . . . . . . 4 4. Domain Name RDAP Bootstrap Registry . . . . . . . . . . . . . 4
5. Internet Numbers RDAP Bootstrap Registries . . . . . . . . . 5 5. Internet Numbers RDAP Bootstrap Registries . . . . . . . . . 6
5.1. IPv4 Address Space RDAP Bootstrap Registry . . . . . . . 5 5.1. IPv4 Address Space RDAP Bootstrap Registry . . . . . . . 6
5.2. IPv6 Address Space RDAP Registry . . . . . . . . . . . . 6 5.2. IPv6 Address Space RDAP Registry . . . . . . . . . . . . 7
5.3. Autonomous Systems RDAP Bootstrap Registry . . . . . . . 7 5.3. Autonomous Systems RDAP Bootstrap Registry . . . . . . . 8
6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 9 7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 10
8. Deployment and Implementation Considerations . . . . . . . . 9 8. Deployment and Implementation Considerations . . . . . . . . 10
9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. Security Considerations . . . . . . . . . . . . . . . . . . . 10 10. Security Considerations . . . . . . . . . . . . . . . . . . . 11
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
13.1. Normative References . . . . . . . . . . . . . . . . . . 11 13.1. Normative References . . . . . . . . . . . . . . . . . . 12
13.2. Non-Normative References . . . . . . . . . . . . . . . . 11 13.2. Non-Normative References . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
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 the fact that allocation data for The proposed mechanism is based on the fact that allocation data for
domain names and IP addresses are maintained by IANA, are publicly domain names and IP addresses are maintained by IANA, are publicly
available and are in a structured format. The mechanism assumes some available and are in a structured format. The mechanism assumes some
data structure within these registries and request IANA to create data structure within these registries and request IANA to create
these registries for the specific purpose of RDAP use, herein named these registries for the specific purpose of RDAP use, herein named
RDAP 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].
skipping to change at page 3, line 23 skipping to change at page 3, line 23
contains all entries that have the same set of base RDAP URLs, as contains all entries that have the same set of base RDAP URLs, as
strings, arrays, or integers. The second third-level array contains strings, arrays, or integers. The second third-level array contains
the list of base RDAP URLs usable for the entries found in the first 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- third-level array. There is no assumption of sorting at the first-
level arrays. The two arrays found in each second-level array MUST level arrays. The two arrays found in each second-level array MUST
appear in the correct order: array of entries first, then array of appear in the correct order: array of entries first, then array of
base RDAP URLs. An example structure of a JSON RDAP Bootstrap base RDAP URLs. An example structure of a JSON RDAP Bootstrap
Registry is illustrated: 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",
"description": "RDAP Bootstrap file for example registries."
"services": [ "services": [
[ [
["entry1", "entry2", "entry3"], ["entry1", "entry2", "entry3"],
[ [
"https://registry.example.com/myrdap/", "https://registry.example.com/myrdap/",
"http://registry.example.com/myrdap/" "http://registry.example.com/myrdap/"
] ]
], ],
[ [
["entry4"], ["entry4"],
[ [
"http://example.org/" "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".
conforms to the Internet date/time format [RFC3339]. Per [RFC7258],
in each array of base RDAP URLs, the secure version of the transport
protocol SHOULD be first.
Any unknown or unspecified JSON object properties or values should be The syntax of "publication" value conforms to the Internet date/time
ignored by implementers. format [RFC3339].
Per [RFC7258], in each array of base RDAP URLs, the secure version of
the transport protocol SHOULD be first. Base RDAP URLs are likely to
have a trailing "/" character because they are aggregated to the
various segments defined in [I-D.ietf-weirds-rdap-query].
JSON names MUST follow format recommendations of
[I-D.ietf-weirds-using-http]. Any unknown or unspecified JSON object
properties or values should be ignored by implementers.
Internationalized Domain Names labels used as keys or base RDAP URLs
in the registries defined in this document MUST be only represented
using their A-Label form as defined in [RFC5890].
All Domain Names labels used as keys or base RDAP URLs in the
registries defined in this document MUST be only represented in
lowercase.
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 base RDAP URLs, 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",
"services": [ "services": [
[ [
["net", "com"], ["net", "com"],
[ [
"https://registry.example.com/myrdap/" "https://registry.example.com/myrdap/"
] ]
], ],
skipping to change at page 5, line 6 skipping to change at page 5, line 47
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 values the target name and the end of each value in the arrays. The values
contained in the second element of the array are the valid base RDAP contained in the second element of the array are the valid base RDAP
URLs as 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. The base RDAP URL for entry in one of the arrays of the registry. The base RDAP URL for
this query is then taken from the second element of the array, which this query is then taken from the second element of the array, which
is an array of base RDAP URLs valid for this entry. The client is an array of base RDAP URLs valid for this entry. The client
chooses one of the base URLs from this array; in this example it chooses one of the base URLs from this array; in this example it
chooses the only one available, "https://registry.example.com/myrdap/ chooses the only one available, "https://registry.example.com/
". The segment specified in [I-D.ietf-weirds-rdap-query] is then myrdap/". The segment specified in [I-D.ietf-weirds-rdap-query] is
appended to the base URL to complete the query. The complete query then appended to the base URL to complete the query. The complete
is then "https://registry.example.com/myrdap/domain/a.b.example.com". query is then "https://registry.example.com/myrdap/domain/
This example is not normative. 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
skipping to change at page 6, line 6 skipping to change at page 7, line 6
covering prefixes of a larger address space pointing to one base RDAP covering prefixes of a larger address space pointing to one base RDAP
URL while more specific prefixes within the covering prefix being URL while more specific prefixes within the covering prefix being
served by another base RDAP URL. 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 RDAP URLs, 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",
"services": [ "services": [
[ [
["1.0.0.0/8", "192.0.0.0/8"], ["1.0.0.0/8", "192.0.0.0/8"],
[ [
"https://rir1.example.com/myrdap/" "https://rir1.example.com/myrdap/"
] ]
], ],
skipping to change at page 7, line 6 skipping to change at page 8, line 6
"https://example.org/ip/192.0.2.0/24". This example is not "https://example.org/ip/192.0.2.0/24". This example is not
normative. 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 base RDAP URLs, representation of address prefixes format, grouped by base RDAP URLs,
as 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",
"services": [ "services": [
[ [
["2001:0200::/23", "2001:db8::/32"], ["2001:0200::/23", "2001:db8::/32"],
[ [
"https://rir2.example.com/myrdap/" "https://rir2.example.com/myrdap/"
] ]
], ],
skipping to change at page 7, line 40 skipping to change at page 8, line 40
] ]
} }
} }
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 second element of the array, which is an array of base RDAP URLs the second element of the array, which is an array of base RDAP URLs
valid for this entry. The client chooses one of the base URLs from valid for this entry. The client chooses one of the base URLs from
this array; in this example it chooses "https://example.net/rdaprir2/ this array; in this example it chooses "https://example.net/
" because it's the secure version of the protocol. The segment rdaprir2/" because it's the secure version of the protocol. The
specified in [I-D.ietf-weirds-rdap-query] is then appended to the segment specified in [I-D.ietf-weirds-rdap-query] is then appended to
base URL to complete the query. The complete query is therefore the base URL to complete the query. The complete query is therefore
"https://example.net/rdaprir2/ip/2001:0200:1000::/48". If the server "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 does not answer, the client can then use another URL prefix from the
array. This example is not normative. 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 base RDAP URLs, as shown in this example. The first grouped by base RDAP URLs, as shown in this example. The first
element of each second-level array is an array containing the list of element of each second-level array is an array containing the list of
AS numbers served by the base RDAP URLs found in the second element. AS numbers served by the base RDAP URLs found in the second element.
When an element of the AS Numbers array is an array with two AS 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 numbers, then it represents the range of AS Numbers between the two
elements of this array. 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",
"services": [ "services": [
[ [
[2045], [2045],
[ [
"https://rir3.example.com/myrdap/" "https://rir3.example.com/myrdap/"
] ]
], ],
skipping to change at page 8, line 42 skipping to change at page 9, line 42
] ]
] ]
] ]
} }
} }
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 second element of the array, which is an array of base taken from the second element of the array, which is an array of base
RDAP URLs valid for this entry. The client chooses one of the base RDAP URLs valid for this entry. The client chooses one of the base
URLs from this array; in this example it chooses "https://example.net URLs from this array; in this example it chooses
/rdaprir2/". The segment specified in [I-D.ietf-weirds-rdap-query] "https://example.net/rdaprir2/". The segment specified in
is then appended to the base URL to complete the query. The complete [I-D.ietf-weirds-rdap-query] is then appended to the base URL to
query is therefore "https://example.net/rdaprir2/autnum/65411". If complete the query. The complete query is therefore
the server does not answer, the client can then use another URL "https://example.net/rdaprir2/autnum/65411". If the server does not
prefix from the array. This example is not normative. 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 base RDAP
value may be empty. In these cases, there is no known RDAP server URL value may be empty. In these cases, there is no known RDAP
for that requested value and the client SHOULD provide an appropriate server for that requested value and the client SHOULD provide an
error message to the user. appropriate 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.
skipping to change at page 11, line 35 skipping to change at page 12, line 35
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002. Internet: Timestamps", RFC 3339, July 2002.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework",
RFC 5890, August 2010.
[RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, March 2014. Interchange Format", RFC 7159, March 2014.
13.2. Non-Normative References 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-07 (work in progress), April 2014. weirds-json-response-08 (work in progress), August 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-13
(work in progress), February 2014. (work in progress), August 2014.
[I-D.ietf-weirds-redirects] [I-D.ietf-weirds-redirects]
Martinez, C., Zhou, L., and G. Rada, "Redirection Service Martinez, C., Zhou, L., and G. Rada, "Redirection Service
for Registration Data Access Protocol", draft-ietf-weirds- for Registration Data Access Protocol", draft-ietf-weirds-
redirects-03 (work in progress), February 2014. redirects-04 (work in progress), July 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-10 (work in progress), August 2014.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(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/ 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>.
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. 25 change blocks. 
61 lines changed or deleted 81 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/