Re: [yam] Referencing 1652bis and update to RFC 5321/5322
John C Klensin <john-ietf@jck.com> Tue, 29 June 2010 15:47 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 466A93A6BE8 for <yam@core3.amsl.com>; Tue, 29 Jun 2010 08:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.395
X-Spam-Level:
X-Spam-Status: No, score=-0.395 tagged_above=-999 required=5 tests=[AWL=-0.396, BAYES_50=0.001]
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 2AJZOvq5gGfz for <yam@core3.amsl.com>; Tue, 29 Jun 2010 08:47:20 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 1A61C3A6BBD for <yam@ietf.org>; Tue, 29 Jun 2010 08:47:09 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1OTd1n-0009gn-GU; Tue, 29 Jun 2010 11:47:15 -0400
Date: Tue, 29 Jun 2010 11:47:14 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>
Message-ID: <F846AFA19652B24D5C79B099@PST.JCK.COM>
In-Reply-To: <4C29FEA3.8050800@piuha.net>
References: <4C29FEA3.8050800@piuha.net>
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
Cc: Dave Crocker <dcrocker@bbiw.net>, yam@ietf.org
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: Tue, 29 Jun 2010 15:47:28 -0000
--On Tuesday, June 29, 2010 17:09 +0300 Jari Arkko <jari.arkko@piuha.net> wrote: > Dave, > >> If the proposal being promoted by Russ is chosen, then >> there's nothing for this wg to do: everything that is a >> candidate for the wg should automatically already be at the >> final level. No? > > I would hope that the YAM working group exists to improve the > e-mail related RFCs. Actually, the YAM WG exists --I'm inclined say "solely"-- to advance these documents to Full Standard. Quoting the from first two sentences of the charter: "The Yet Another Mail (YAM) WG will revise existing Internet Mail specifications currently at Draft Standard to advance them to Full Standard. YAM will focus strictly on advancing email-related specifications..." > I'm not sure about these specific RFCs, > but in general, I at least see often small issues here and > there, there's usually some filed errata, and we've learned > over the years to understand some issues better. While all of > these issues are small (as evidenced by global deployment of > this technology), I still think they are worthwhile to handle. > In short, while the edits will probably be small, I think it > is our duty at the IETF to maintain our specifications. Sure. The difficulty lies at the intersection of "duty" with "resources", "motivation", and "priorities". Your observations about small issues, errata, and improved understanding can be applied to almost any standards-track RFC. As an extreme example, there are certainly enough small issues, updates, and improved understanding to justify updates/replacements for RFC 768 and/or RFC 793 yet, "duty" aside, we have not done that. > For instance, I looked at > draft-ietf-yam-5321bis-smtp-pre-evaluation and all the > suggested changes make sense to me (irrespective of what > labels we might be using to name the resulting RFCs). Sure. They make sense to me too. Whether they make enough sense to justify the editorial effort, the efforts by the WG to be sure that any changes are made correctly and don't have side-effects, etc., is really the question, not whether the document can be made better with another editing pass (in the case of 5321bis, the third such pass if one counts from 2821 and a somewhat higher number if one goes further back -- there is still some unchanged 821 text in 5321). I note that the thesis of draft-housley-two-... can be interpreted as "one revision after the original spec is worthwhile, but more than one isn't worth the effort". I don't happen to believe that, and I'm keenly aware of the fact that errata, even "approved" errata, do not constitute community consensus documents, but, if the IESG does, then YAM is pretty worthless even though the documents themselves (again, like almost all other documents the IETF has produced) could be improved. 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