Re: New Version Notification for draft-obispo-epp-idn-00.txt

On 22 dec 2011, at 07:10, Francisco Obispo wrote:

> On Dec 21, 2011, at 9:49 PM, Patrik Fältström wrote:
> 
>> 1. What if the domain name is mapped to more languages than one?
> 
> 
> Looking at the IDN implementation guidelines, item #5 states:
> 
> 5.All code points in a single label will be taken from the same
>  script as determined by the Unicode Standard Annex #24: Script
>  Names <http://www.unicode.org/reports/tr24>. Exceptions to this
>  guideline are permissible for languages with established 
>  orthographies and conventions that require the commingled use of
>  multiple scripts. Even in the case of this exception, visually 
>  confusable characters from different scripts will not be allowed 
>  to co-exist in a single set of permissible code points unless a 
>  corresponding policy and character table is clearly defined.
> 
> So it would not be possible to have multiple languages associated to a label.

Then let me ask a meta question: Why is this defined _only_ for the _current_ "IDN Implementation *guidelines*"? I thought IETF was a bit better than that when looking at what is the best *protocol*. And one of the reasons I asked was because I wanted to know in what direction you felt normative references should be referring between ICANN and IETF documents.

FWIW: I think it is a very bad idea if there are normative references regarding cases like these from IETF to ICANN documents. This because normative references so far is in the other direction.

And the I-D does not make this clear.

>> 2. What values are acceptable for the field?
> 
> XML Schema "language" type[1]:
> 
> [Definition:]   language represents natural language identifiers as defined by by [RFC 3066][2] . The ·value space· of language is the set of all strings that are valid language identifiers as defined [RFC 3066] . The ·lexical space· of language is the set of all strings that conform to the pattern [a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})* . The ·base type· of language is token.
> 
> 3.3.3.1 Constraining facets
> 
> language has the following ·constraining facets·:
> 
> 	• length
> 	• minLength
> 	• maxLength
> 	• pattern
> 	• enumeration
> 	• whiteSpace
> 
> 
> [1] http://www.w3.org/TR/xmlschema-2/#language
> [2] http://www.ietf.org/rfc/rfc3066.txt

So, what is the normative reference?

The W3C definition?

Or only what is registered with IANA in the Language Tags registry?

This is still unclear to me, and I encourage you to make that clear in the next version of the document.

And another question: How is equivalence between language tags to be calculated? Someone use "en" and someone else en-UK and a third party en-US or en-US-UK?

   Patrik

> Francisco
> 
> 
> 
> 
>> 
>>  Patrik
>> 
>> On 22 dec 2011, at 01:32, Francisco Obispo wrote:
>> 
>>> Draft for EPP-IDN extension has been submitted.
>>> 
>>> 
>>> 
>>> Begin forwarded message:
>>> 
>>>> From: [email protected]
>>>> Subject: New Version Notification for draft-obispo-epp-idn-00.txt
>>>> Date: December 21, 2011 4:22:34 PM PST
>>>> To: [email protected]
>>>> Cc: [email protected], [email protected], [email protected]
>>>> 
>>>> A new version of I-D, draft-obispo-epp-idn-00.txt has been successfully submitted by Paul Selkirk and posted to the IETF repository.
>>>> 
>>>> Filename:	 draft-obispo-epp-idn
>>>> Revision:	 00
>>>> Title:		 Internationalized Domain Name Mapping Extension for the Extensible Provisioning Protocol (EPP)
>>>> Creation date:	 2011-12-21
>>>> WG ID:		 Individual Submission
>>>> Number of pages: 8
>>>> 
>>>> Abstract:
>>>> This document describes an Extensible Provisioning Protocol (EPP)
>>>> extension mapping for the provisioning of Internationalized Domain
>>>> Names (IDN) stored in a shared central repository.  This mapping
>>>> extends the EPP domain name mapping to provide additional features
>>>> required to implement registrations of domain names in characters
>>>> sets other than ASCII.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> The IETF Secretariat
>>> 
>>> Francisco Obispo 
>>> email: [email protected]
>>> Phone: +1 650 423 1374 || INOC-DBA *3557* NOC
>>> Key fingerprint = 532F 84EB 06B4 3806 D5FA  09C6 463E 614E B38D B1BE
>>> 
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> provreg mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/provreg
>>> 
> 
> Francisco Obispo 
> email: [email protected]
> Phone: +1 650 423 1374 || INOC-DBA *3557* NOC
> Key fingerprint = 532F 84EB 06B4 3806 D5FA  09C6 463E 614E B38D B1BE
> 
> 
> 
> 
> 
> 

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg