Subject: [weirds] exact match search

From: Marc Blanchet <[email-masked]>
Date: Fri, 8 Nov 2013 07:42:01 -0800

Hello,
 I would like to try to better express what I was trying to say at the mike at the end of the search-i18n discussion.  I think I forgot to say the thinking behind what I say, which helps understand my point.  Hope I will succeed this time!  So:

- there are/will be various kind of rdap "clients": "well-implemented-following-the-spec clients, "domain-name-industry" clients. Both hopefully have some insight of issues. 
- but there is also the regular web developer, that has no clue of all this, and just heard by searching Internet that now whois is replaced by rdap and he needs for all kind of reasons to do some search/lookup of names so that the app interface is nicer for users (and here I'm not talking about the registrar industry)
- I bet that the regular web developer will only take the input from the user and don't do anything about IDNA and just spit out that utf-8 string to the server, therefore most likely not a properly prepared U-label.
- I bet that this will happen "often".

Therefore, here was my question at the mike: should we write something in the specification about this, not necessarily about the specific use case, but about what we should expect from the client and (mostly) the server behavior.  Of course, it could be "just reject" as it is implied now, but I wonder that given that it would be a "often" use case, we should be writing a bit more about that.  Our interop testing with various i18n test cases this week also hinted that(need for more clarity in the spec) too.

Marc.