Re: [I18n-discuss] Draft UTR 53 and associated issues

John C Klensin <john-ietf@jck.com> Fri, 06 October 2017 00:20 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: i18n-discuss@ietfa.amsl.com
Delivered-To: i18n-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA8C4132143 for <i18n-discuss@ietfa.amsl.com>; Thu, 5 Oct 2017 17:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pACnN9sdWZPK for <i18n-discuss@ietfa.amsl.com>; Thu, 5 Oct 2017 17:20:33 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAC2713219C for <i18n-discuss@iab.org>; Thu, 5 Oct 2017 17:20:33 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1e0GNU-000EXk-1I; Thu, 05 Oct 2017 20:20:32 -0400
Date: Thu, 05 Oct 2017 20:20:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Asmus Freytag <asmusf@ix.netcom.com>, i18n-discuss@iab.org
Message-ID: <B7F3FCEA6A57F0762637EE43@PSB>
In-Reply-To: <6597e548-f7c6-0845-a0d3-f5c0fa92a100@ix.netcom.com>
References: <07CBE38E286EBC149DD9EEF9@PSB> <6597e548-f7c6-0845-a0d3-f5c0fa92a100@ix.netcom.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18n-discuss/j_e0VzF3pp67BuWi0Rn63Uo_ZwY>
Subject: Re: [I18n-discuss] Draft UTR 53 and associated issues
X-BeenThere: i18n-discuss@iab.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Internationalization Program Open Discussion List <i18n-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/i18n-discuss>, <mailto:i18n-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18n-discuss/>
List-Post: <mailto:i18n-discuss@iab.org>
List-Help: <mailto:i18n-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/i18n-discuss>, <mailto:i18n-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Oct 2017 00:20:35 -0000


--On Thursday, October 5, 2017 13:55 -0700 Asmus Freytag
<asmusf@ix.netcom.com> wrote:

> There's an important clarification of scope that's missing
> from the document, but can be found in the mail-thread on
> idna-update.
> 
> Implication for IETF may be less than it appears without that
> clarified scope.
> 
> A./
> 
> PS: John, can you forward this as necessary - I'm not on all
> the lists you sent this to.

That is the reason I tried to force the discussion onto the
idna-update list and just tell people on the other two about it.
Will pull the other two lists in as needed.  So far, silence on
PRECIS, which is actually more likely to have problems than IDNA.

I may just not understand UTC procedures well enough but if the
need for rewriting and clarification is as clear as Mark's note
seemed to indicate, I don't understand why the draft has not
been withdrawn and rewritten.  An announcement to all three
lists about a new version would seem to me to be appropriate;
otherwise, this is my last posting to this one.

    john


best,
   john