Re: [EAI] UTF-8 in Message-IDs consensus

John C Klensin <klensin@jck.com> Wed, 14 September 2011 21:47 UTC

Return-Path: <klensin@jck.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5603921F8C32 for <ima@ietfa.amsl.com>; Wed, 14 Sep 2011 14:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pWHLLfvAfDqX for <ima@ietfa.amsl.com>; Wed, 14 Sep 2011 14:47:02 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id BDBFA21F8BF9 for <ima@ietf.org>; Wed, 14 Sep 2011 14:47:01 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1R3xKR-000MSq-Ay; Wed, 14 Sep 2011 17:49:11 -0400
Date: Wed, 14 Sep 2011 17:49:10 -0400
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org
Message-ID: <FC7B2A29FF4CF1799F230329@PST.JCK.COM>
In-Reply-To: <E14011F8737B524BB564B05FF748464A32B74C98@TK5EX14MBXC133.redmond.corp.microsoft.com>
References: <E14011F8737B524BB564B05FF748464A32B73F18@TK5EX14MBXC133.redmond.corp.microsoft.com> <14D07F2441ADA2EBD5D53677@PST.JCK.COM> <E14011F8737B524BB564B05FF748464A32B74C98@TK5EX14MBXC133.redmond.corp.microsoft.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
Subject: Re: [EAI] UTF-8 in Message-IDs consensus
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2011 21:47:02 -0000

--On Wednesday, September 14, 2011 21:30 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

> I don't care which one, except don't reopen the queued
> one, not high priority for me, just don't want a lot of back
> and forth.

Shawn (and others),

I'm asking for two main reasons:

(1) I think  there is a real possibility that the "advice"
documents will get lost, or at least deferred for a long time,
after we extrapolate from current levels of activity in the WG
to the likelihood of taking on new documents and getting them
done in a reasonable period.  IMO, the odds go up somewhat if we
handle those documents as Applicability Statements and can get
WG and IESG consensus for publishing versions at Proposed
Standard without broad consensus that all issues have been
addressed and all nits picked, but I don't know how realistic
that is.   In any event, if the WG decides that the text should
go into an "advice document" that has not yet been put on the
agenda, we need to be prepared to abandon that text if the WG
shuts down before that advice document is published.

(2) There has been a brief discussion of another option, which
would be to attach this sort of material as an appendix to
5335bis.  That has several disadvantages, including some risk of
5335bis being delayed while we quibble about text.

FWIW, my personal view is that we should narrow 5335bis and
5336bis as much as possible in the interest of getting agreement
and getting them out, but that is not a co-chair opinion.  Given
the risk of losing the material, I do not believe the co-chairs
or author team should make the decision without an opportunity
for advice from the WG.

   john