------ Original Message ------
From: "Patrick Mevzek" <p...@dotandco.com>
To: regext@ietf.org
Sent: 12/13/2017 8:08:38 AM
Subject: Re: [regext] FW: I-D Action:
draft-hollenbeck-regext-rdap-object-tag-05.txt
Think about this, though, Patrick: what the document describes is
essentially how bootstrapping for domain name queries works, too. The
only difference is that the separator is a "." and the operator
identifiers are top-level domains.
But in your case the domains are not into some kind of structured
format
like JSON.
Where on the opposite, inside RDAP we have the luxury of the JSON
structure.
Patrick,
Thanks for starting this conversation. I'm open to evolving this if
that's what we need.
As a user, I would not want to enter JSON into an RDAP client to do a
lookup. A simple and transcribable string is much easier to use.
I don't believe the goal here is to define more structure for entity
identifiers. RDAP already provides URLs for entities, and that is
probably enough structure.
All that said, I understand your hesitation here. This draft takes an
unstructured field already in use and applies structure to it. That
could be problematic, and care must be taken. Doing such a thing is not
ideal, but we wouldn't be the first to do so. The xn-- signifier for
IDNs comes to mind.
-andy
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
