draft-ietf-weirds-bootstrap-02.txt   draft-ietf-weirds-bootstrap-03.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft Viagenie Internet-Draft G. Guillaume
Intended status: Standards Track June 23, 2014 Intended status: Standards Track Viagenie
Expires: December 25, 2014 Expires: December 30, 2014 June 28, 2014
Finding the Authoritative Registration Data (RDAP) Service Finding the Authoritative Registration Data (RDAP) Service
draft-ietf-weirds-bootstrap-02.txt draft-ietf-weirds-bootstrap-03.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 25, 2014. This Internet-Draft will expire on December 30, 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
skipping to change at page 2, line 13 skipping to change at page 2, line 13
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 . . . . . . . . . . . . . 3
5. Internet Numbers RDAP Bootstrap Registries . . . . . . . . . 4 5. Internet Numbers RDAP Bootstrap Registries . . . . . . . . . 4
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 . . . . . . . . . . . . 5 5.2. IPv6 Address Space RDAP Registry . . . . . . . . . . . . 6
5.3. Autonomous Systems RDAP Bootstrap Registry . . . . . . . 6 5.3. Autonomous Systems RDAP Bootstrap Registry . . . . . . . 6
6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 7 7. Non-existent Entries or RDAP URL Values . . . . . . . . . . . 7
8. Deployment and Implementation Considerations . . . . . . . . 7 8. Deployment and Implementation Considerations . . . . . . . . 8
9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 8
10. Security Considerations . . . . . . . . . . . . . . . . . . . 8 10. Security Considerations . . . . . . . . . . . . . . . . . . . 9
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
13.1. Normative References . . . . . . . . . . . . . . . . . . 10 13.1. Normative References . . . . . . . . . . . . . . . . . . 10
13.2. Non-Normative References . . . . . . . . . . . . . . . . 10 13.2. Non-Normative References . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 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.
skipping to change at page 3, line 16 skipping to change at page 3, line 16
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 follows an array of arrays. Each second
level array lists all the entries available by the same template level array lists all the entries available by the same template
method. There is no assumption of sorting at the first or second method. There is no assumption of sorting at the first or second
level arrays. An example structure of a JSON RDAP Bootstrap Registry level arrays. An example structure of a JSON RDAP Bootstrap Registry
is illustrated: is illustrated:
{
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ", "version": "1.0",
"proto": [ https http ], "publication": "YYYY-MM-DDTHH:MM:SSZ",
"scheme": [ https http ],
"services": [ "services": [
["entry1", "entry2", "entry3"]: { ["entry1", "entry2", "entry3"]: {
"template": "{proto}://registry.example.com/myrdap/{resource}", "template": "{proto}://registry.example.com/myrdap/{resource}",
"proto": [ https ], "proto": [ https ],
}, },
["entry4"]: { ["entry4"]: {
"template": "{proto}://example.org/{resource}", "template": "{proto}://example.org/{resource}",
}, },
], ],
} }
}
The syntax of "version" value conforms to the Internet date/time The version corresponds to the format version of the registry. This
format [RFC3339]. The "proto" object is an array of transport specification defines "1.0". The syntax of "publication" value
protocols used to access the resource. The RDAP bootstrap client conforms to the Internet date/time format [RFC3339]. The "proto"
SHOULD try the transport protocols in the order they are presented in object is an array of transport protocols used to access the
the array. The "proto" object can be overriden in the specific resource. The RDAP bootstrap client SHOULD try the transport
entries. Per [RFC7258], the secure version of the transport protocol protocols in the order they are presented in the array. The "proto"
SHOULD be first. 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
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 templates, as shown in this example.
{
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ], "proto": [ "https", "http" ],
"services": [ "services": [
["net", "com"]: { ["net", "com"]: {
"template": "https://registry.example.com/myrdap/{resource}", "template": "https://registry.example.com/myrdap/{resource}",
}, },
["org", "mytld"]: { ["org", "mytld"]: {
"template": "{proto}://example.org/{resource}", "template": "{proto}://example.org/{resource}",
}, },
], ],
["mytld2"]: { ["mytld2"]: {
"template": "{proto}://example.net/rdapmytld2/{resource}", "template": "{proto}://example.net/rdapmytld2/{resource}",
"proto": [ "http", "https"], "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 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 value
of the corresponding "template" object is the base RDAP URL as of the corresponding "template" object is the base RDAP URL as
described in [I-D.ietf-weirds-rdap-query]. 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
skipping to change at page 5, line 15 skipping to change at page 5, line 17
[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 RDAP
template while more specific prefixes within the covering prefix template while more specific prefixes within the covering prefix
being served by another RDAP template. being served by another RDAP template.
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 templates, as shown in this example.
{
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ], "proto": [ "https", "http" ],
"services": [ "services": [
["1.0.0.0/8", "192.0.0.0/8"]: { ["1.0.0.0/8", "192.0.0.0/8"]: {
"template": "https://rir1.example.com/myrdap/{resource}", "template": "https://rir1.example.com/myrdap/{resource}",
}, },
["28.2.0.0/16", "192.0.2.0/24"]: { ["28.2.0.0/16", "192.0.2.0/24"]: {
"template": "{proto}://example.org/{resource}", "template": "{proto}://example.org/{resource}",
}, },
], ],
["28.3.0.0/16"]: { ["28.3.0.0/16"]: {
"template": "{proto}://example.net/rdaprir2/{resource}", "template": "{proto}://example.net/rdaprir2/{resource}",
"proto": [ "http", "https"], "proto": [ "http", "https"],
}, },
], ],
} }
}
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 template object and
expands to "{proto}://example.org/". The {resource} specified in expands to "{proto}://example.org/". The {resource} specified in
[I-D.ietf-weirds-rdap-query] is then appended to the base URL to [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/ complete the query. The complete query is then "https://example.org/
ip/192.0.2.0/24". This example is not normative. 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 templates, as
shown in this example. shown in this example.
{
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ], "proto": [ "https", "http" ],
"services": [ "services": [
["2001:0200::/23", "2001:db8::/32"]: { ["2001:0200::/23", "2001:db8::/32"]: {
"template": "https://rir2.example.com/myrdap/{resource}", "template": "https://rir2.example.com/myrdap/{resource}",
}, },
["2600::/16", "2100:ffff::/32"]: { ["2600::/16", "2100:ffff::/32"]: {
"template": "{proto}://example.org/{resource}", "template": "{proto}://example.org/{resource}",
}, },
],
["2001:0200:1000::/28"]: { ["2001:0200:1000::/28"]: {
"template": "{proto}://example.net/rdaprir2/{resource}", "template": "{proto}://example.net/rdaprir2/{resource}",
"proto": [ "http", "https"], "proto": [ "http", "https"],
}, },
], ],
} }
}
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 template object "{proto}://example.net/rdaprir2/". The
{resource} specified in [I-D.ietf-weirds-rdap-query] is then appended {resource} specified in [I-D.ietf-weirds-rdap-query] is then appended
to the base URL to complete the query. The complete query is to the base URL to complete the query. The complete query is
therefore "https://example.net/rdaprir2/ip/2001:0200:1000::/48". therefore "https://example.net/rdaprir2/ip/2001:0200:1000::/48".
This example is not normative. 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 templates, as shown in this example. Entries in the
arrays are either single AS numbers or ranges of AS numbers where the arrays are either single AS numbers or ranges of AS numbers where the
lower appears first, then the "-" separator and then the upper lower appears first, then the "-" separator and then the upper
number. Both 16bit and 32 bit AS numbers are specified in decimal. number. Both 16bit and 32 bit AS numbers are specified in decimal.
{
"rdap.bootstrap": { "rdap.bootstrap": {
"version": "YYYY-MM-DDTHH:MM:SSZ", "version": "1.0",
"publication": "YYYY-MM-DDTHH:MM:SSZ",
"proto": [ "https", "http" ], "proto": [ "https", "http" ],
"services": [ "services": [
["2045", "20116-20117"]: { ["2045", "20116-20117"]: {
"template": "https://rir2.example.com/myrdap/{resource}", "template": "https://rir2.example.com/myrdap/{resource}",
}, },
["10000-12000", "65900-66000"]: { ["10000-12000", "65900-66000"]: {
"template": "{proto}://example.org/{resource}", "template": "{proto}://example.org/{resource}",
}, },
],
["65512-65534"]: { ["65512-65534"]: {
"template": "{proto}://example.net/rdaprir2/{resource}", "template": "{proto}://example.net/rdaprir2/{resource}",
"proto": [ "http", "https"], "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 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 template object "{proto}://example.net/rdaprir2/".
The {resource} specified in [I-D.ietf-weirds-rdap-query] is then The {resource} specified in [I-D.ietf-weirds-rdap-query] is then
appended to the base URL to complete the query. The complete query appended to the base URL to complete the query. The complete query
is therefore "https://example.net/rdaprir2/autnum/65411". This is therefore "https://example.net/rdaprir2/autnum/65411". This
example is not normative. example is not normative.
6. Entity 6. Entity
skipping to change at page 9, line 43 skipping to change at page 9, line 49
12. 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, where various methods such as in- including a session during IETF 84, where various methods such as in-
DNS and others were debated. The idea of using IANA registries was DNS and others were debated. The idea of using IANA registries was
discovered by the editor during discussions with his colleagues as discovered by the editor during discussions with his colleagues as
well as by a comment from Andy Newton. All the people involved in well as by a comment from Andy Newton. All the people involved in
these discussions are herein acknowledged. Linlin Zhou, Jean- these discussions are herein acknowledged. Linlin Zhou, Jean-
Philippe Dionne, John Levine, Kim Davies, Ernie Dainow, Scott Philippe Dionne, John Levine, Kim Davies, Ernie Dainow, Scott
Hollenbeck, Arturo Servin, Andy Newton, Murray Kucherawy have Hollenbeck, Arturo Servin, Andy Newton, Murray Kucherawy, Tom
provided input and suggestions to this document. Harrison, Naoki Kambe have provided input and suggestions to this
document.
13. References 13. References
13.1. Normative References 13.1. Normative References
[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.
skipping to change at page 11, line 28 skipping to change at page 11, line 28
Unicast Address Assignments", Unicast Address Assignments",
<http://www.iana.org/assignments/ipv6-unicast-address- <http://www.iana.org/assignments/ipv6-unicast-address-
assignments/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", Protocol Version 6 Address Space",
<http://www.iana.org/assignments/ipv6-address-space/ <http://www.iana.org/assignments/ipv6-address-space/
ipv6-address-space.xml>. ipv6-address-space.xml>.
Author's Address 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
URI: http://www.viagenie.ca URI: http://viagenie.ca
Guillaume Leclanche
Viagenie
246 Aberdeen
Quebec, QC G1R 2E1
Canada
Email: Guillaume.Leclanche@viagenie.ca
URI: http://viagenie.ca
 End of changes. 30 change blocks. 
28 lines changed or deleted 47 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/