Hello,
this draft just posted is the result of discussions that happened in
ICANN RDAP profile discussions, where a missing piece was found in the
use case of thin domain registries. However, the proposal in the draft
is generic and may apply to other use cases in the future if necessary.
The draft is not fully baked but more than enough to have a discussion
on the issue and the proposed solution.
Looking for comments and reviews,
Marc.
--- Begin Message ---
A new version of I-D, draft-blanchet-regext-entityid2rdapserver-00.txt
has been successfully submitted by Marc Blanchet and posted to the
IETF repository.
Name: draft-blanchet-regext-entityid2rdapserver
Revision: 00
Title: Finding Additional Registration Data (RDAP) Service
Document date: 2019-03-11
Group: Individual Submission
Pages: 11
URL:
https://www.ietf.org/internet-drafts/draft-blanchet-regext-entityid2rdapserver-00.txt
Status:
https://datatracker.ietf.org/doc/draft-blanchet-regext-entityid2rdapserver/
Htmlized:
https://tools.ietf.org/html/draft-blanchet-regext-entityid2rdapserver-00
Htmlized:
https://datatracker.ietf.org/doc/html/draft-blanchet-regext-entityid2rdapserver
Abstract:
This document specifies a method to find which Registration Data
Access Protocol (RDAP) server is authoritative to answer additional
information for a query already answered by another server. It is
based on an entity id to RDAP server location mapping registry
managed by IANA. One use case of this specification is the domain
registry RDAP server providing a referral URL to the registrar RDAP
server, based on the registrar entity id, for information that the
registrar is authoritative for such as the contact or reseller
information.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
--- End Message ---
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
