Re: [yam] Referencing 1652bis and update to RFC 5321/5322
John C Klensin <john-ietf@jck.com> Mon, 28 June 2010 03:22 UTC
Return-Path: <john-ietf@jck.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 2A4403A67D7 for <yam@core3.amsl.com>; Sun, 27 Jun 2010 20:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.327
X-Spam-Level:
X-Spam-Status: No, score=-0.327 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_50=0.001, SARE_RMML_Stock10=0.13]
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 iKko56pb0BY7 for <yam@core3.amsl.com>; Sun, 27 Jun 2010 20:22:52 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 1A4433A67A5 for <yam@ietf.org>; Sun, 27 Jun 2010 20:22:52 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1OT4vz-000GKA-7t; Sun, 27 Jun 2010 23:22:59 -0400
Date: Sun, 27 Jun 2010 23:22:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tony Hansen <tony@att.com>, yam@ietf.org
Message-ID: <E989214657844D69A6CFC2B5@PST.JCK.COM>
In-Reply-To: <4C27F351.9060604@att.com>
References: <6.2.5.6.2.20100626145920.0b610618@elandnews.com> <6785AF47EC3ACD933037ABE5@PST.JCK.COM> <6.2.5.6.2.20100626173821.0b374a90@resistor.net> <4C2725DA.6000507@isode.com> <4C27F351.9060604@att.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: [yam] Referencing 1652bis and update to RFC 5321/5322
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: Mon, 28 Jun 2010 03:22:53 -0000
--On Sunday, June 27, 2010 20:56 -0400 Tony Hansen <tony@att.com> wrote: > I would call this an excellent agenda item for Maastricht. > > Some of the documents are quite needy of a rev, irrespective > of Russ' document's outcome. Deciding on the set of documents > that make up that list would be one of the tasks for the WG. > One of the interesting thing about using the pre-evaluation > step is that we've forced people to think through the state of > the documents and to get buy-in from the WG for those changes. > None of the pre-eval docs so far have been contentious, but > future ones may be more so. Tony, Per my earlier note, if the WG is going to go down that path, I think it is important to distinguish between: (1) In need of a rev because of specific issues that require clarification. (2) In need of a rev because the document itself is sufficiently defective that it requires a complete revision and replacement. We are treating all documents as if they fall into the second category because the procedures for advancement to Full Standard more or less require that. But, if there were no "advancement" goal, I think some (or most) of the documents would either not need revision at all or would fall into the first category. For it, it should be possible to issue an RFC whose substance is one or more statements of the form "Section N.M of RFC nnnn says "xxxx" but means "yyyy". And that would be a lot less work for all involved than revising the documents. I have to confess to finding myself significantly de-motivated to spend time on 5321bis until the question of its fate (advancements or not and to what) is sorted out, especially since some of the changes that require the most work are in the queue only because we had to promise them to IESG members for the Full Standard version in order to get 5321 signed off. If the IESG makes "Full Standard version" meaningless, there should be no need to do that work. john
- [yam] Referencing 1652bis and update to RFC 5321/… Alexey Melnikov
- Re: [yam] Referencing 1652bis and update to RFC 5… Dave CROCKER
- Re: [yam] Referencing 1652bis and update to RFC 5… Alexey Melnikov
- Re: [yam] Referencing 1652bis and update to RFC 5… Dave CROCKER
- Re: [yam] Referencing 1652bis and update to RFC 5… Alessandro Vesely
- Re: [yam] Referencing 1652bis and update to RFC 5… John C Klensin
- Re: [yam] Referencing 1652bis and update to RFC 5… Tony Hansen
- Re: [yam] Referencing 1652bis and update to RFC 5… John C Klensin
- Re: [yam] Referencing 1652bis and update to RFC 5… S Moonesamy
- Re: [yam] Referencing 1652bis and update to RFC 5… John C Klensin
- Re: [yam] Referencing 1652bis and update to RFC 5… Ned Freed
- Re: [yam] Referencing 1652bis and update to RFC 5… S Moonesamy
- Re: [yam] Referencing 1652bis and update to RFC 5… Jari Arkko
- Re: [yam] Referencing 1652bis and update to RFC 5… Alessandro Vesely
- Re: [yam] Referencing 1652bis and update to RFC 5… Jari Arkko
- Re: [yam] Referencing 1652bis and update to RFC 5… John C Klensin
- Re: [yam] Referencing 1652bis and update to RFC 5… Ned Freed
- Re: [yam] Referencing 1652bis and update to RFC 5… Dave CROCKER
- Re: [yam] Referencing 1652bis and update to RFC 5… Tony Hansen
- Re: [yam] Referencing 1652bis and update to RFC 5… John C Klensin
- Re: [yam] Referencing 1652bis and update to RFC 5… Jari Arkko
- Re: [yam] Referencing 1652bis and update to RFC 5… John C Klensin
- Re: [yam] Referencing 1652bis and update to RFC 5… John C Klensin