Consensus Call Tranche 3 (Permanence)

[Yoshiro YONEYA]

Consensus Call Tranche 3 (Permanence)

Place your reply here: [NO]

COMMENTS:

For (3.b), DISALLOWED to CONTEXTO may happen.  It should be well 
described.

-- 
Yoshiro YONEYA <yone at jprs.co.jp>

On Sun, 12 Oct 2008 05:21:48 -0400 Vint Cerf <vint at google.com> wrote:

> Consensus Call Tranche 3 (Permanence)
> 
> Place your reply here: [YES or NO]
> 
> COMMENTS:
> 
> 
> Procedure:
> 
> 
> There are several decisions that the working group will need to make  
> to confirm consensus.  I will send a series of proposals over the  
> next two weeks requesting YES or NO positions on each within a 4 day  
> window. If NO is the response, a reason for that position needs to be  
> stated. If there is a clear consensus based on responses or in the  
> absence of a consensus against each proposal, it will be assumed that  
> the proposal is acceptable to the Working Group.
> 
> 
> Parenthesized symbols (e.g., "(R.1)") after the items are references  
> to the issues lists where additional explanations can be found, as  
> sent by John Klensin as body parts "idnabis-protocol-issues-rev3" and  
> "idnabis-rationale-issues-03" on a message titled 'Issues lists and  
> the "preprocessing" topic'  to the working group on 18 August (http:// 
> www.alvestrand.no/pipermail/idna-update/2008-August/002537.html)
> 
> This group needs to get its documents out; it is behind its original  
> schedule. It should be noted that the IDN ccTLD and gTLD selection  
> initiatives at ICANN have already begun so that delay may weaken the  
> IETF's ability to assist in a rational deployment of IDNA.
> 
> 
> 
> (3) Permanence of DISALLOWED and PROTOCOL-VALID
> 
> (3.a) Once a character is classified as PROTOCOL-VALID, it
> will remain in that category for all future versions of the
> protocol and tables unless serious and unanticipated
> circumstances occur.  (R.10)
> 
> (3.b) Once a character is classified as DISALLOWED, it will
> remain in that category for all future versions of the protocol
> and tables unless serious and unanticipated circumstances
> occur.  Note that UNASSIGNED characters are not, for this
> purpose, DISALLOWED.  (R.5)
> ------------
> 
> 
> NOTE NEW BUSINESS ADDRESS AND PHONE
> Vint Cerf
> Google
> 1818 Library Street, Suite 400
> Reston, VA 20190
> 202-370-5637
> vint at google.com
> 
> 
> 
> 
>