Re: [yam] Rough notes for IETF76 YAM WG Session

Ned Freed <ned.freed@mrochek.com> Sun, 13 December 2009 03:22 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F5B43A6803 for <yam@core3.amsl.com>; Sat, 12 Dec 2009 19:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level:
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Al3QPH7ooSlz for <yam@core3.amsl.com>; Sat, 12 Dec 2009 19:22:00 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 1D4A63A67BD for <yam@ietf.org>; Sat, 12 Dec 2009 19:22:00 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NH6I74FWPC003NAR@mauve.mrochek.com> for yam@ietf.org; Sat, 12 Dec 2009 19:21:44 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NH6HBMBQ1S0002QL@mauve.mrochek.com>; Sat, 12 Dec 2009 19:21:42 -0800 (PST)
Message-id: <01NH6I73A4L20002QL@mauve.mrochek.com>
Date: Sat, 12 Dec 2009 19:17:10 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 02 Dec 2009 20:12:52 +0100" <4B16BC34.3030504@tana.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format="flowed"
References: <6.2.5.6.2.20091202003803.03ed05a8@elandnews.com> <4B16BC34.3030504@tana.it>
To: Alessandro Vesely <vesely@tana.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1260674305; bh=lH07VysRYGZ2Q+6HknVaK41ZM7ndgujC3AADFx0Dny8=; h=Cc:Message-id:Date:From:Subject:In-reply-to:MIME-version: Content-type:References:To; b=K8Xn27bK2OKMwUfs2sBHizR/I5FTpK2V8Ez0sS1RFKfqlCAFqXGCWh/aMSW6qXTt2 5/jXGK5FpHi00kFPgvKVI1Ac/rpG/f+OSx8Kcp2F9Dsbof4/T1fqC1LSJ88OWeNtYL tXW/1vWYoljgvhIwruIsaIMghljmQRKjVyM6zzyc=
Cc: yam@ietf.org
Subject: Re: [yam] Rough notes for IETF76 YAM WG Session
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Dec 2009 03:22:01 -0000

> S Moonesamy wrote:
> > The YAM Working Group held a meeting at IETF 76 on November 10, 2009.
> > [...]
> > Tony: Do we want to have a quick hum?  Whether to reach 5321 first.

> +1, fwiw. I feel 5321bis as the most exciting target, and that's why I
> subscribed to the yam list.

I will again repeat that 5321bis moving from draft to full is not a time for
lots of changes of the sort that you seem to be after. Indeed, there is
substantive risk with the present course continues 5321 will become ineligable
for processing under the rules for this WG.

> IMHO, putting forward 8bitmime has been wisely careful, but it
> resulted in a 90%-boilerplate pre-evaluation, which may partially
> justify IESG's reaction.

Nonsense. Had the IESG objected to the boilerplate nature of the pre-eval, they
could have, you know, actually reviewed the document and found the actual
problems it contained that weren't addressed in the pre-eval. They did nothing
of the sort.

> The WG can pursue the 2-step experimental
> process even without full IESG's cooperation --since we don't formally
> need their approval for those drafts-- and eventually present the
> final result as if it were produced by a 1-step process: In any case,
> the 2-step experiment will have been carried out, with visible results.

I myself am not so optimistic. But there's no need to speculate - we run the
process and see what happens.

				Ned