> -----Original Message----- > From: Francisco Arias [mailto:francisco.ar...@icann.org] > Sent: Thursday, April 06, 2017 9:15 PM > To: Hollenbeck, Scott <shollenb...@verisign.com>; 'regext@ietf.org' > <regext@ietf.org> > Subject: [EXTERNAL] Re: [Ext] [regext] FW: I-D Action: draft-hollenbeck- > regext-rdap-object-tag-02.txt > > I can see how a RDAP user would see a domain name outside RDAP and wanted > to query the registration data, e.g., a user seeing an ad, (potentially > phishing) email, etc. So, it makes sense to have a bootstrapping mechanism > for that use case. > > In the case of entities, I don't think a RDAP user is likely to see an > entity id outside RDAP. If users would most likely obtain an entity handle > from another RDAP output, I'd argue that the problem could be solved the > way I mentioned before. In any case, if users are going to obtain the (not > so user-friendly) ids from RDAP output, should we better provide the URI > to the RDAP query for that object in the RDAP output that the user is > going to see (or even let the URI be the id)?
That might help, but it still means that clients have to be "smart" about processing query output, it still leaves entities as second-class objects, and it doesn't address the situation where an entity ID might appear out of context. What I'm proposing extends existing operational practice to provide a more general solution. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
