Re: [ssac-gnso-irdwg] What do we require from IRD?, question (1a)

[Dave Piscitello <dave.piscitello@xxxxxxxxx>]

Hi Jay,

Apologies for not replying earlier.
I'm really pleased with the insights and added focus you've provided in your
comments. I'm going to break the discussion down into multiple threads so
each can focus on a specific question. I'll try to distinguish the threads
in the subject line, and will reply as I have an opportunity to mull over
each issue you raise.


On 1/6/10 4:23 PM  Jan 6, 2010, "Jay Daley" <jay@xxxxxxxxxxx> wrote:

> Hi Dave
> 
> On 7/01/2010, at 6:20 AM, Dave Piscitello wrote:
> 
>> 1) What do we require from internationalized registration data?
>> 
>>   a) that a user can submit or have a domain name displayed in
>>      the IDN A-label (xn--) format or U-label (local language
>>      readable) format?
> 
> That is two separate questions and both are incomplete.   The first: "can a
> user submit" needs a definition of what "submit" means in this context.  Does
> it means to register?  The second "have a domain displayed" needs an
> explanation of where the display takes place.  Otherwise these two questions
> are too general.

Yes, let's try to do this.

By "submit", I meant "enter into a web input form, an application input
field, or type at a command line prompt".

A user would submit a string or domain name in any of the above manners to:

a- query the availability of a label in a given TLD
  (e.g., is "example" available in "com"?)
b- query a Whois web, command line, or application for the
  registration information associated with a domain name
c- register a domain via a web form at a registrar's web site

An application or automation would also submit in this manner
(where permitted, certain of these submission methods may
 take measures to detect and only accept human input)

By "display" I meant "render a visual response to a human on a computer or a
machine-readable response to an application or automation", for all of (a-c)
above. 

I see value in offering users with the ability to "use" U-label or A-label
as they choose. Users may most often prefer a U-label since this is more
visually recognizable and familiar than "xn--<g1b63r1sh>" strings but I can
imagine a user of a command line who might want to submit and display
A-labels when using a command line, especially in situations where he is
writing a script and the input or output of a whois command would be "piped"
to/from another command (sed/awk/grep).

Did you have something different or broader in mind?