Re: [yam] Referencing 1652bis and update to RFC 5321/5322
Jari Arkko <jari.arkko@piuha.net> Tue, 29 June 2010 14:09 UTC
Return-Path: <jari.arkko@piuha.net>
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 9CD393A6C0D for <yam@core3.amsl.com>; Tue, 29 Jun 2010 07:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.794
X-Spam-Level:
X-Spam-Status: No, score=-1.794 tagged_above=-999 required=5 tests=[AWL=0.805, 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 NsyR3FA5XJHw for <yam@core3.amsl.com>; Tue, 29 Jun 2010 07:09:30 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id A97A33A6BB7 for <yam@ietf.org>; Tue, 29 Jun 2010 07:09:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 745F32CED3; Tue, 29 Jun 2010 17:09:40 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XoRJ3Z2arHHW; Tue, 29 Jun 2010 17:09:40 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DE3CB2CC62; Tue, 29 Jun 2010 17:09:39 +0300 (EEST)
Message-ID: <4C29FEA3.8050800@piuha.net>
Date: Tue, 29 Jun 2010 17:09:39 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>, yam@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 14:09:31 -0000
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. 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. 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). Just my view point on this, of course. Jari
- [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