[gtld-tech] Handling of "loc" and "int" contacts
michael.bauland at knipp.de
Fri Apr 25 08:58:02 UTC 2014
> We're currently evaluating the options regarding the "int" and "loc" postalInfo elements of the EPP contact mapping. Currently, we use the "int" type exclusively, but looking at the recent developtments in the "IRD" area (http://singapore49.icann.org/en/schedule/wed-ird-requirements), we're looking into the options to move forward with allowing "loc" postalInfo types as well.
> I'm trying to grasp a "sense of the room" with regards to the following questions, and would appreciate feedback:
> - For registries that implement "loc" postalInfo, which of the options do you support?
> a) just "loc"
> b) either "loc" or "int"
> c) "int" required, "loc" optional
> d) "loc" required, "int" optional
e) one of "loc" or "int" is required, the other optional
> - For registries that allow both "loc" and "int", do you require any connection between the two postalInfo data sets (for example, "identical cc", or "identical pc"?)
> - For registries that allow both "loc" and "int", which of the two are you displaying in WHOIS? Are you trying to serve "different views" depending on user location or (in the case of web whois) user agent information (eg. "accept-language" header?)
No, we display both, for example, "Name" and "Ext. Name"
> - Do you limit the text contents of "loc" fields to a certain sensible subset of UTF-8, for example to the set of scripts that are also the basis for the registry's IDN tables?
No, we also allow characters that are not within the same script. After
all, a Latin-script domain could also be registered by someone living in
China. And why shouldn't he be allowed to enter his localised address.
TANGO REGISTRY SERVICES® is a product of:
Knipp Medien und Kommunikation GmbH Dr. Michael Bauland
Technologiepark Phone: +49 231 9703-0
Martin-Schmeisser-Weg 9 Fax: +49 231 9703-200
D-44227 Dortmund E-Mail: Michael.Bauland at knipp.de
More information about the gtld-tech