One document matched: draft-ietf-weirds-rdap-query-07.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "http://xml.resource.org/authoring/rfc2629.dtd"
[
<!ENTITY RFC0952 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.0952.xml'>
<!ENTITY RFC1123 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1123.xml'>
<!ENTITY RFC1166 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1166.xml'>
<!ENTITY RFC2119 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
<!ENTITY RFC2616 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml'>
<!ENTITY RFC3912 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3912.xml'>
<!ENTITY RFC3986 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml'>
<!ENTITY RFC4007 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4007.xml'>
<!ENTITY RFC4290 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4290.xml'>
<!ENTITY RFC4291 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4291.xml'>
<!ENTITY RFC4343 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4343.xml'>
<!ENTITY RFC4627 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4627.xml'>
<!ENTITY RFC4632 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4632.xml'>
<!ENTITY RFC4918 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4918.xml'>
<!ENTITY RFC5396 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5396.xml'>
<!ENTITY RFC5730 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5730.xml'>
<!ENTITY RFC5733 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5733.xml'>
<!ENTITY RFC5890 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml'>
<!ENTITY RFC5891 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5891.xml'>
<!ENTITY RFC5892 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5892.xml'>
<!ENTITY RFC5952 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5952.xml'>
<!ENTITY I-D.ietf-weirds-json-response PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-weirds-json-response.xml'>
<!ENTITY I-D.ietf-weirds-rdap-sec PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-weirds-rdap-sec.xml'>
<!ENTITY I-D.ietf-weirds-using-http PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-weirds-using-http.xml'>
<!ENTITY I-D.ietf-precis-nickname PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-precis-nickname.xml'>
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="4"?>
<?rfc compact="yes"?>
<?rfc subcompact="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc iprnotified="no"?>
<?rfc strict="yes" ?>
<rfc category="std" docName="draft-ietf-weirds-rdap-query-07" ipr="trust200902">
<front>
<title abbrev="RDAP Query Format">Registration Data Access Protocol Query Format</title>
<author fullname="Andrew Lee Newton" initials="A.L." surname="Newton">
<organization abbrev="ARIN">American Registry for Internet Numbers</organization>
<address>
<postal>
<street>3635 Concorde Parkway</street>
<city>Chantilly</city>
<region>VA</region>
<country>US</country>
<code>20151</code>
</postal>
<email>andy@arin.net</email>
<uri>http://www.arin.net</uri>
</address>
</author>
<author initials="S." surname="Hollenbeck" fullname="Scott Hollenbeck">
<organization>Verisign Labs</organization>
<address>
<postal>
<street>12061 Bluemont Way</street>
<city>Reston</city>
<region>VA</region>
<code>20190</code>
<country>US</country>
</postal>
<email>shollenbeck@verisign.com</email>
<uri>http://www.verisignlabs.com/</uri>
</address>
</author>
<date/>
<abstract>
<t>
This document describes uniform patterns to construct HTTP URLs that may be used to retrieve
registration information from registries (including both Regional Internet Registries (RIRs)
and Domain Name Registries (DNRs)) using "RESTful" web access patterns.
</t>
</abstract>
</front>
<middle>
<section title="Conventions Used in This Document">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 <xref target="RFC2119"/>.</t>
<section title="Acronyms and Abbreviations">
<t><list style="hanging">
<t>IDN: Internationalized Domain Name</t>
<t>IDNA: Internationalized Domain Names in Applications</t>
<t>DNR: Domain Name Registry</t>
<t>RDAP: Registration Data Access Protocol</t>
<t>REST: Representational State Transfer State Transfer. The term was first described in a doctoral dissertation <xref target="REST"/>.</t>
<t>RESTful: an adjective that describes a service using HTTP and the principles of REST.</t>
<t>RIR: Regional Internet Registry</t>
</list></t>
</section>
</section>
<section title="Introduction">
<t>
This document describes a specification for querying registration data using a RESTful web
service and uniform query patterns. The service is implemented using the Hypertext Transfer
Protocol (HTTP) <xref target="RFC2616"/>.
</t>
<t>
The protocol described in this specification is intended to address deficiencies with the
WHOIS protocol <xref target="RFC3912"/> that have been identified over time, including:</t>
<t><list style="symbols">
<t>Lack of standardized command structures,</t>
<t>lack of standardized output and error structures,</t>
<t>lack of support for internationalization and localization, and</t>
<t>lack of support for user identification, authentication, and access control.</t>
</list>
</t>
<t>
The patterns described in this document purposefully do not encompass all of the methods employed
in the WHOIS and RESTful web services of all of the RIRs and DNRs. The intent of the patterns
described here are to enable queries of:
</t>
<t><list style="symbols">
<t>networks by IP address,</t>
<t>autonomous system numbers by number,</t>
<t>reverse DNS meta-data by domain,</t>
<t>name servers by name,</t>
<t>registrars by name, and</t>
<t>entities (such as contacts) by identifier.</t>
</list>
</t>
<t>
It is envisioned that each registry will continue to maintain NICNAME/WHOIS and/or RESTful web services
specific to their needs and those of their constituencies, and the information retrieved through the
patterns described here may reference such services.
</t>
<t>
Likewise, future IETF standards may add additional patterns for additional query types. A simple pattern
namespacing scheme is described in <xref target="extensibility"/> to accomodate custom extensions that will not
interfere with the patterns defined in this document or patterns defined in future IETF standards.
</t>
<t>
WHOIS services, in general, are read-only services. Therefore <xref target="RFC3986">URL</xref> patterns
specified in this document are only applicable to the <xref target="RFC2616">HTTP</xref> GET and HEAD methods.
</t>
<t>
This document does not describe the results or entities returned from issuing
the described URLs with an HTTP GET. JSON <xref target="RFC4627"/> result formatting and processing is described in
<xref target="I-D.ietf-weirds-json-response"/>.
</t>
<t>
Additionally, resource management, provisioning and update functions are out of
scope for this document. Registries have various and divergent methods covering these
functions, and it is unlikely a uniform approach for these functions will ever
be possible.
</t>
<t>
HTTP contains mechanisms for servers to authenticate clients and for clients to authenticate servers (from which authorization schemes may be built) so such mechanisms are not described in this document. Policy, provisioning, and processing of authentication and authorization are out-of-scope for this document as deployments will have to make choices based on local criteria. Specified authentication mechanisms MUST use HTTP.
</t>
</section>
<section title="Path Segment Specification">
<t>
The uniform patterns start with a base <xref target="RFC3986">URL</xref> specified by each registry or any other
service provider offering this service. The base URL is followed by a resource-type-specific path segment.
The base URL may contain its own path segments (e.g. http://example.com/... or http://example.com/rdap/... ).
The characters used to form a path segment are limited to those that can be used to form a URI as specified in RFC 3986 <xref target="RFC3986"/>.
</t>
<section title="Lookup Path Segment Specification">
<t>
The resource type path segments for exact match lookup are:
<list style="symbols">
<t>'ip': Used to identify IP networks and associated data referenced using either an IPv4 or IPv6 address.</t>
<t>'autnum': Used to identify autonomous system registrations and associated data referenced using an AS Plain autonomous system number.</t>
<t>'domain': Used to identify reverse DNS (RIR) or domain name (DNR) information and associated data referenced using a fully-qualified domain name.</t>
<t>'nameserver': Used to identify a name server information query using a host name.</t>
<t>'entity': Used to identify an entity information query using a string identifier.</t>
</list>
</t>
<section title="IP Network Path Segment Specification" anchor="ip-network-paths">
<t>Syntax: ip/<IP address> or ip/<CIDR prefix>/<CIDR length></t>
<t>
Queries for information about IP networks are of the form /ip/XXX/... or /ip/XXX/YY/...
where the path segment following 'ip' is either an <xref target="RFC1166">IPv4</xref> or
<xref target="RFC5952">IPv6</xref> address (i.e. XXX) or an IPv4 or IPv6
<xref target="RFC4632">CIDR</xref> notation address block (i.e. XXX/YY).
Semantically, the simpler form using the address can be thought of as a CIDR block with a bitmask length of 32 for IPv4
and a bitmask length of 128 for IPv6. A given specific address or CIDR may fall within multiple
IP networks in a hierarchy of networks, therefore this query targets the "most-specific"
or smallest IP network which completely encompasses it in a hierarchy of IP networks.
</t>
<t>
The IPv4 and IPv6 address formats supported in this query are described in section 3.2.2 of <xref target="RFC3986"/>, as
IPv4address and IPv6address ABNF definitions. Any valid IPv6 text address format <xref target="RFC4291"/> can be used,
compressed or not compressed. The restricted rules to write a text representation of an IPv6 address <xref target="RFC5952"/>
are not mandatory. However, the zone id <xref target="RFC4007"/> is not appropriate in this context and therefore prohibited.
</t>
<t>
This is an example URL for the most specific network containing 192.0.2.0:
</t>
<t>
/ip/192.0.2.0
</t>
<t>
This is an example of a URL the most specific network containing 192.0.2.0/24:
</t>
<t>
/ip/192.0.2.0/24
</t>
<t>
This is an example URL for the most specific network containing 2001:db8:1:1::1:
</t>
<t>
/ip/2001:db8:1:1::1
</t>
</section>
<section title="Autonomous System Path Segment Specification">
<t>Syntax: autnum/<autonomous system number></t>
<t>
Queries for information regarding autonomous system number registrations are of the form
/autnum/XXX/... where XXX is an AS Plain <xref target="RFC5396">autonomous system number</xref>. In some registries,
registration of autonomous system numbers is done on an individual number basis, while
other registries may register blocks of autonomous system numbers. The semantics of this
query are such that if a number falls within a range of registered blocks, the target of
the query is the block registration, and that individual number registrations are considered
a block of numbers with a size of 1.
</t>
<t>For example, to find information on autonomous system number 65551, the following path would be used:</t>
<t>
/autnum/65551
</t>
<t>The following path would be used to find information on 4-byte autonomous system number 65538:</t>
<t>
/autnum/65538
</t>
</section>
<section title="Domain Path Segment Specification">
<t>Syntax: domain/<domain name></t>
<t>Queries for domain information are of the form /domain/XXXX/..., where XXXX is a
<xref target="RFC4343">fully-qualified domain name</xref> in either the
in-addr.arpa or ip6.arpa zones (for RIRs) or a fully-qualified domain name in a
zone administered by the server operator (for DNRs). Internationalized domain names
represented in either A-label or U-label format <xref target="RFC5890"/> are also
valid domain names. IDN labels SHOULD NOT be represented as a mixture of A-labels and U-labels.</t>
<t>If the client sends the server an IDN in U-label format, servers that support IDNs MUST convert the IDN into A-label format
and perform IDNA processing as specified in RFC 5891 <xref target="RFC5891"/>. The server should
perform an exact match lookup using the A-label.</t>
<t>The following path would be used to find information describing the zone serving the network 192.0.2/24: </t>
<t>/domain/2.0.192.in-addr.arpa</t>
<t>The following path would be used to find information describing the zone serving the network 2001:db8:1::/48:</t>
<t>/domain/1.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa</t>
<t>The following path would be used to find information for the example.com domain name:</t>
<t>/domain/example.com</t>
<t>The following path would be used to find information for the<vspace/>xn--xemple-9ua.example IDN:</t>
<t>/domain/xn--xemple-9ua.example</t>
</section>
<section title="Name Server Path Segment Specification">
<t>Syntax: nameserver/<name server name></t>
<t>The <name server name> parameter represents a fully qualified name as specified in RFC 952
<xref target="RFC0952"/> and RFC 1123 <xref target="RFC1123"/>. Internationalized names represented
in either A-label or U-label format <xref target="RFC5890"/> are also valid name server names.
IDN labels SHOULD NOT be represented as a mixture of A-labels and U-labels.</t>
<t>If the client sends the server an IDN in U-label format, servers that support IDNs MUST convert the IDN into A-label format
and perform IDNA processing as specified in RFC 5891 <xref target="RFC5891"/>. The server should
perform an exact match lookup using the A-label.</t>
<t>The following path would be used to find information for the ns1.example.com name server:</t>
<t>/nameserver/ns1.example.com</t>
<t>The following path would be used to find information for the<vspace/>ns1.xn--xemple-9ua.example name server:</t>
<t>/nameserver/ns1.xn--xemple-9ua.example</t>
</section>
<section title="Entity Path Segment Specification">
<t>Syntax: entity/<handle></t>
<t>The <handle> parameter represents an entity (such as a contact, registrant, or registrar) identifier. For example, for some DNRs contact identifiers are specified in RFC 5730 <xref target="RFC5730"/> and RFC 5733 <xref target="RFC5733"/>.</t>
<t>The following path would be used to find information for the entity associated
with handle CID-4005:</t>
<t>/entity/CID-4005</t>
</section>
<section title="Help Path Segment Specification">
<t>Syntax: help</t>
<t>The help path segment can be used to request helpful information (command syntax, terms of service, privacy policy, rate limiting policy, supported authentication methods, supported extensions, technical support contact, etc.) from an RDAP server. The response to "help" should provide basic information that a client needs to successfully use the service. The following path would be used to return "help" information:</t>
<t>/help</t>
</section>
</section>
<section title="Search Path Segment Specification">
<t>The resource type path segments for search are:
<list style="symbols">
<t>'domains': Used to identify a domain name information search using a pattern to match a fully-qualified domain name.</t>
<t>'nameservers': Used to identify a name server information search using a pattern to match a host name.</t>
<t>'entities': Used to identify an entity information search using a pattern to match a string identifier.</t>
</list>
</t>
<t>RDAP search path segments are formed using a concatenation of the plural form of the
object being searched for, a forward slash character ('/', ASCII value 0x002F), and an
HTTP query string. The HTTP query string is formed using a concatenation of the question
mark character ('?', ASCII value 0x003F), the JSON object value associated with the
object being searched for, the equal sign character ('=', ASCII value 0x003D), and
the search pattern. For the domain and entity objects described in this document the
plural object forms are "domains" and "entities".</t>
<section title="Domain Search" anchor="domain_search">
<t>Syntax: domains?name=<domain search pattern></t>
<t>Searches for domain information are of the form</t>
<t>/domains?name=XXXX</t>
<t>where XXXX is a search pattern representing a <xref target="RFC5890">domain name in
"letters, digits, hyphen" format</xref> in a zone administered by the server operator
of a DNR. The following path would be used to find DNR information for domain names
matching the "example*.com" pattern:</t>
<t>/domains?name=example*.com</t>
<t>Internationalized Domain Names (IDNs) in U-label format <xref target="RFC5890"/> can
also be used as search patterns (see <xref target="search_proc"></xref>). Searches for these
names are of the form /domains?name=XXXX, where XXXX is a search pattern representing
a <xref target="RFC5890">domain name in U-label format</xref>.</t>
</section>
<section title="Name Server Search" anchor="ns_search">
<t>Syntax: nameservers?name=<nameserver search pattern></t>
<t>Searches for name server information are of the form</t>
<t>/nameservers?name=XXXX</t>
<t>where XXXX is a search pattern representing a <xref target="RFC5890">host name in
"letters, digits, hyphen" format</xref> in a zone administered by the server operator
of a DNR. The following path would be used to find DNR information for name server
names matching the "ns1.example*.com" pattern:</t>
<t>/nameservers?name=ns1.example*.com</t>
<t>Internationalized name server names in U-label format <xref target="RFC5890"/> can
also be used as search patterns (see <xref target="search_proc"></xref>). Searches for these
names are of the form /nameservers?name=XXXX, where XXXX is a search pattern representing
a <xref target="RFC5890">name server name in U-label format</xref>.</t>
</section>
<section title="Entity Search" anchor="entity_search">
<t>Syntax: entities?fn=<entity name search pattern></t>
<t>Syntax: entities?handle=<entity handle search pattern></t>
<t>Searches for entity information by name are of the form</t>
<t>/entities?fn=XXXX</t>
<t>where XXXX is a search pattern representing an entity name as specified in Section 6.1
of <xref target="I-D.ietf-weirds-json-response"/>. The following path would be used to find
information for entity names matching the "Bobby Joe*" pattern.</t>
<t>/entities?fn=Bobby%20Joe*</t>
<t>Searches for entity information by handle are of the form</t>
<t>/entities?handle=XXXX</t>
<t>where XXXX is a search pattern representing an entity handle as specified in Section 6.1
of <xref target="I-D.ietf-weirds-json-response"/>. The following path would be used to find
information for entity names matching the "CID-40*" pattern.</t>
<t>/entities?handle=CID-40*</t>
<t>URLs MUST be properly encoded according to the rules of <xref target="RFC3986"/>.
In the example above, "Bobby Joe*" is encoded to "Bobby%20Joe*".</t>
</section>
</section>
</section>
<section title="Search Processing" anchor="search_proc">
<t>Partial string searching uses the asterisk ('*', ASCII value 0x002A) character to match
zero or more trailing characters. Additional pattern matching processing is beyond the scope
of this specification.</t>
<t>If a server receives a search request but cannot process the request because it does not
support a particular style of partial match searching, it SHOULD return an HTTP 422 <xref target="RFC4918"/> error.
When returning a 422 error, the server MAY also return an error response body as specified
in Section 7 of <xref target="I-D.ietf-weirds-json-response"/> if the requested media type
is one that is specified in <xref target="I-D.ietf-weirds-using-http"/>.</t>
<t>
Because Unicode characters may be combined with another Unicode character or characters,
partial matching is not feasible across combinations of Unicode characters.
Servers SHOULD NOT partially match combinations of Unicode characters where a Unicode
character may be legally combined with another Unicode character or characters.
Clients should avoid submitting a partial match search of Unicode characters where a Unicode
character may be legally combined with another Unicode character or characters.
Partial match searches with incomplete combinations of characters where a character
must be combined with another character or characters are invalid. Partial match
searches with characters that may be combined with another character or characters
are to be considered non-combined characters (that is, if character x may be combined
with character y but character y is not submitted in the search string then
character x is a complete character and no combinations of character x are to be
searched).
</t>
<t>
Because Unicode characters may be combined with another Unicode character or characters,
partial matching requires that a server maintain a list of valid character combinations
to be considered a match.
When comparing DNS U-labels, servers SHOULD use the code points specified in <xref target="RFC5892"></xref>
to determine partial matches. When comparing entity names, servers SHOULD use the normalization
rules and code points specified by <xref target="I-D.ietf-precis-nickname"></xref> to determine
partial matches.
</t>
</section>
<section title="Extensibility" anchor="extensibility">
<t>This document describes path segment specifications for a limited number of objects
commonly registered in both RIRs and DNRs. It does not attempt to describe path
segments for all of the objects registered in all registries. Custom path segments
can be created for objects not specified here using the process described in Section
6 of "HTTP usage in the Registration Data Access Protocol (RDAP)" <xref
target="I-D.ietf-weirds-using-http"/>.</t>
<t>Custom path segments can be created by prefixing the segment with a unique identifier
followed by an underscore character (0x5F). For example, a custom entity path
segment could be created by prefixing "entity" with "custom_", producing
"custom_entity". Servers MUST return an appropriate failure status code for a
request with an unrecognized path segment.</t>
</section>
<section anchor="i18n" title="Internationalization Considerations">
<t>There is value in supporting the ability to submit either a U-label (Unicode form of
an IDN label) or an A-label (ASCII form of an IDN label) as a query argument to an
RDAP service. Clients capable of processing non-ASCII characters may prefer a U-label since this
is more visually recognizable and familiar than A-label strings, but clients using programmatic
interfaces might find it easier to submit and display A-labels if they are unable to input U-labels with
their keyboard configuration. Both query forms are acceptable.</t>
<t>Internationalized domain and name server names can contain character variants and
variant labels as described in RFC 4290 <xref target="RFC4290"/>. Clients that
support queries for internationalized domain and name server names MUST accept
service provider responses that describe variants as specified in "JSON Responses
for the Registration Data Access Protocol" <xref target="I-D.ietf-weirds-json-response"/>.</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This document does not specify any IANA actions.</t>
</section>
<section anchor="Security" title="Security Considerations">
<t>Security services for the operations specified in this document are described in "Security Services for the Registration Data Access Protocol" <xref target="I-D.ietf-weirds-rdap-sec"/>.</t>
<t>Search functionality typically requires more server resources (such as memory, CPU cycles, and network bandwidth) when compared to basic lookup functionality. This increases the risk of server resource exhaustion and subsequent denial of service due to abuse. This risk can be mitigated by developing and implementing controls to restrict search functionality to identified and authorized clients. If those clients behave badly, their search privileges can be suspended or revoked. Rate limiting as described in Section 5.5 of "HTTP usage in the Registration Data Access Protocol (RDAP)" <xref target="I-D.ietf-weirds-using-http"/> can also be used to control the rate of received search requests. Server operators can also reduce their risk by restricting the amount of information returned in response to a search request.</t>
</section>
<section title="Acknowledgements">
<t>This document is derived from original work on RIR query formats developed by Byron J. Ellacott of APNIC, Arturo L. Servin of LACNIC, Kaveh Ranjbar of the RIPE NCC, and Andrew L. Newton of ARIN. Additionally, this document incorporates DNR query formats originally described by Francisco Arias and Steve Sheng of ICANN and Scott Hollenbeck of Verisign.</t>
<t>The authors would like to acknowledge the following individuals for their contributions to this document: Francisco Arias, Marc Blanchet, Ernie Dainow, Jean-Philippe Dionne, Behnam Esfahbod, Edward Lewis, and John Levine.</t>
</section>
</middle>
<back>
<references title="Normative References">
&RFC0952;
&RFC1123;
&RFC1166;
&RFC2119;
&RFC2616;
&RFC3986;
&RFC4290;
&RFC4291;
&RFC4343;
&RFC4632;
&RFC4918;
&RFC5396;
&RFC5730;
&RFC5733;
&RFC5890;
&RFC5891;
&RFC5892;
&RFC5952;
&I-D.ietf-weirds-json-response;
&I-D.ietf-weirds-rdap-sec;
&I-D.ietf-weirds-using-http;
&I-D.ietf-precis-nickname;
</references>
<references title="Informative References">
&RFC3912;
&RFC4007;
&RFC4627;
<reference anchor="REST">
<front>
<title>Principled Design of the Modern Web Architecture</title>
<author initials="R." surname="Fielding" fullname="Roy Fielding"></author>
<author initials="R." surname="Taylor" fullname="Richard Fielding"></author>
<date month="May" year="2002" />
</front>
<seriesInfo name="ACM Transactions on Internet Technology" value="Vol. 2, No. 2" />
</reference>
</references>
<section title="Change Log">
<t>
<list style="hanging">
<t hangText="Initial -00:">Adopted as working group document.</t>
<t hangText="-01:">Added "Conventions Used in This Document" section. Added
normative reference to draft-ietf-weirds-rdap-sec and some wrapping text in
the Security Considerations section.</t>
<t hangText="-02:">Removed "unified" from the title. Rewrote the last paragraph
of section 2. Edited the first paragraph of section 3 to more clearly note
that only one path segement is provided. Added "bitmask" to "length" in
section 3.1. Changed "lowest IP network" to "smallest IP network" in section
3.1. Added "asplain" to the description of autonomous system numbers in
section 3.2. Minor change from "semantics is" to "semantics are" in section
3.2. Changed the last sentence in section 4 to more clearly specify error
response behavior. Added acknowledgements. Added a paragraph in the
introduction regarding future IETF standards and extensibility.
</t>
<t hangText="-03:">Changed 'query' to 'lookup' in document title to better describe the 'exact match lookup' purpose of this document. Included a multitude of minor additions and clarifications provided by Marc Blanchet and Jean-Philippe Dionne. Modified the domain and name server sections to include support for IDN U-labels.</t>
<t hangText="-04:">Updated the domain and name server sections to use .example IDN U-labels. Added text to note that mixed IDN labels SHOULD NOT be used. Fixed broken sentences in <xref target="i18n"/>.</t>
<t hangText="-05:">Added "help" path segment.</t>
<t hangText="-06:">Added search text and removed or edited old search text.</t>
<t hangText="-07:">Fixed query parameter typo by replacing "/?" with "?". Changed "asplain" to "AS Plain". Added entity search by handle. Corrected section references. Updated IDN search text.</t>
</list>
</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 01:07:54 |