HTTP usage in the Registration Data Access Protocol (RDAP)
draft-ietf-weirds-using-http-14
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7480.
|
|
|---|---|---|---|
| Authors | Andy Newton , Byron Ellacott , Ning Kong | ||
| Last updated | 2014-10-30 (Latest revision 2014-10-28) | ||
| Replaces | draft-designteam-weirds-using-http | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Murray Kucherawy | ||
| Shepherd write-up | Show Last changed 2014-09-24 | ||
| IESG | IESG state | Became RFC 7480 (Internet Standard) | |
| Consensus boilerplate | Yes | ||
| Telechat date |
(None)
Needs a YES. Needs 10 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Pete Resnick | ||
| Send notices to | weirds-chairs@tools.ietf.org, draft-ietf-weirds-using-http@tools.ietf.org, weirds@ietf.org | ||
| IANA | IANA review state | IANA OK - Actions Needed |
draft-ietf-weirds-using-http-14
Use of an unknown parameter to overcome misbehaving caches is not part of any specification and is offered here for informational purposes. Appendix C. Bootstrapping and Redirection The traditional deployment model of WHOIS [RFC3912] does not provide a mechanism for determining the authoritative source for information. Some approaches have been implemented in the past, most notably the Joint WHOIS [lacnic-joint-whois] initiative. However, among other shortcomings, Joint WHOIS is implemented using proxies and server- side referrals. These issues are solved in RDAP using HTTP redirects and bootstrapping. Bootstrapping is discussed in [I-D.ietf-weirds-bootstrap]. In constrained environments, the processes outlined in [I-D.ietf-weirds-bootstrap] may not be viable and there may be need for servers acting as a "redirector". Redirector servers issue HTTP redirects to clients using a redirection table informed by [I-D.ietf-weirds-bootstrap]. Figure 2 diagrams a client using a redirector for bootstrapping. REDIRECTOR ARIN RDAP RDAP . . | | Q: 23.1.1.1? -----------------> | | | | <---------- HTTP 301 --------| | ('Try ARIN RDAP') | | | | | Q: 23.1.1.1? -------------------------------> | | <---------- HTTP 200 --------------------- | (JSON response is returned) | | | . Querying RDAP data for 23.1.1.1 Figure 2 Newton, et al. Expires May 1, 2015 [Page 14] Internet-Draft RDAP over HTTP October 2014 In some cases, particularly sub-delegations made between RIRs known as "ERX space" and transfers of networks, multiple HTTP redirects will be issued. Figure 3 shows such a scenario. REDIRECTOR LACNIC ARIN RDAP RDAP RDAP . . . Q: 23.1.1.1? ----> | | | | | | <-- HTTP 301 --- | | | ('Try LACNIC') | | | | | | | | | Q: 23.1.1.1? -----------------> | | | | <---------- HTTP 301 --------| | ('Try ARIN RDAP') | | | | | Q: 23.1.1.1? -------------------------------> | | <---------- HTTP 200 --------------------- | (JSON response is returned) | | | . Querying RDAP data for data that has been transfered Figure 3 Appendix D. Changelog RFC Editor: Please remove this section. Initial WG -00: Updated to working group document 2012-September-20 -01 * Updated for the sections moved to the JSON responses draft. * Simplified media type, removed "level" parameter. * Updated 2119 language and added boilerplate. * In section 1, noted that redirects can go to redirect servers as well. Newton, et al. Expires May 1, 2015 [Page 15] Internet-Draft RDAP over HTTP October 2014 * Added Section 9.2 and Section 9.3. -02 * Added a section on 429 response codes. * Changed Accept header language in section 4.1 * Removed reference to the now dead requirements draft. * Added contributing authors and acknowledgements section. * Added some clarifying text regarding complete URLs in the redirect section. * Changed media type to application/rdap+json * Added media type registration -03 * Removed forward reference to draft-ietf-weirds-json-response. * Added reference and recommended usage of CORS -04 * Revised introduction and abstract. * Added negative responses other than 404. * Added security considerations. * Added and corrected references: CORS, RFC3912, RFC3987, RFC5890. * Expanded on first use several acronyms. * Updated 2119 language. -05 * Update the media type registration. * Further explained the SHOULD in section 5. * Split the references into normative and informative. Newton, et al. Expires May 1, 2015 [Page 16] Internet-Draft RDAP over HTTP October 2014 * Other minor fixes. -06 * Rewritten the third paragraph in Section 3 to avoid contradictions * Simplified the wording in Seciton 5.1. * Removed some RFC 2119 words in Section 5.2, 5.3, 5.4 and 5.5. * Corrected RFC 6839 as an informative reference. * Replaced MAYs with cans in Seciton 9.1. * Replaced MAY with can in Appendix B. * Added a note in in Appendix C for the RFC Editor to remove this section. -07 * Dropped reference to MUST with application/rdap+json * Dropped IANA registration of application/rdap+json -08 * Keep alive version. -09 * Changed status lines in example to include http version number. * Removed charset from media types in examples. * Changed wording of 404 negative response to specifically say "empty result set". * Changed references to HTTP. -10 * Corrected references to HTTP. * Added a reference to draft-ietf-weirds-json-response (discuss item from Barry Leiba) Newton, et al. Expires May 1, 2015 [Page 17] Internet-Draft RDAP over HTTP October 2014 * Added a reference to draft-ietf-weirds-rdap-query (discuss item from Barry Leiba) * Noted that redirect URLs do not have to conform to draft-ietf- weirds-rdap-query (comment by Richard Barnes) * Noted that CORS header is most likely to be "*" (comment by Richard Barnes) * Added reference to draft-ietf-weirds-rdap-sec (comment by Richard Barnes) * Added a sentence to the abstract explaining the purpose of RDAP (comment by Stephen Farrell) * Added further references to draft-ietf-weirds-rdap-query and draft-ietf-weirds-json-response (comment by Stephen Farrell) * Added comment regarding the use of the CORS header (comment by Stephen Farrell) * Explanded SSAC (comment by Sean Turner) * Added text about HEAD and GET. -11 * Changed JSON reference to RFC 7159. * Noted that clients MUST support HTTPS. -12 * Added reference to REST. * Numerous textual clarifications. * Added an actual reference to RFC 5226 instead of just talking about it. * A reference to draft-ietf-weirds-bootstrap was added. * Included a section on redirectors. -13 * Addressed AD feedback. Newton, et al. Expires May 1, 2015 [Page 18] Internet-Draft RDAP over HTTP October 2014 -15 * Addressed Last Call comments. Authors' Addresses Andrew Lee Newton American Registry for Internet Numbers 3635 Concorde Parkway Chantilly, VA 20151 US Email: andy@arin.net URI: http://www.arin.net Byron J. Ellacott Asia Pacific Network Information Center 6 Cordelia Street South Brisbane QLD 4101 Australia Email: bje@apnic.net URI: http://www.apnic.net Ning Kong China Internet Network Information Center 4 South 4th Street, Zhongguancun, Haidian District Beijing 100190 China Phone: +86 10 5881 3147 Email: nkong@cnnic.cn Newton, et al. Expires May 1, 2015 [Page 19]