Re: [yam] Referencing 1652bis and update to RFC 5321/5322

Tony Hansen <tony@att.com> Mon, 28 June 2010 00:56 UTC

Return-Path: <tony@att.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 AC3D63A68B7 for <yam@core3.amsl.com>; Sun, 27 Jun 2010 17:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.573
X-Spam-Level:
X-Spam-Status: No, score=-105.573 tagged_above=-999 required=5 tests=[AWL=-0.593, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4, SARE_RMML_Stock10=0.13, USER_IN_WHITELIST=-100]
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 NOwYjKwe8398 for <yam@core3.amsl.com>; Sun, 27 Jun 2010 17:56:48 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id BA3F03A688C for <yam@ietf.org>; Sun, 27 Jun 2010 17:56:47 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-8.tower-121.messagelabs.com!1277686616!28524593!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 3930 invoked from network); 28 Jun 2010 00:56:56 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-8.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Jun 2010 00:56:56 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o5S0vBNB027417 for <yam@ietf.org>; Sun, 27 Jun 2010 20:57:11 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o5S0v8ge027408 for <yam@ietf.org>; Sun, 27 Jun 2010 20:57:08 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.3/8.14.3) with ESMTP id o5S0urHB002296 for <yam@ietf.org>; Sun, 27 Jun 2010 20:56:53 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.3/8.14.3) with ESMTP id o5S0ungh002227 for <yam@ietf.org>; Sun, 27 Jun 2010 20:56:50 -0400
Received: from [135.70.220.37] (vpn-135-70-220-37.vpn.east.att.com[135.70.220.37]) by maillennium.att.com (mailgw1) with ESMTP id <20100628005649gw100s4pohe> (Authid: tony); Mon, 28 Jun 2010 00:56:49 +0000
X-Originating-IP: [135.70.220.37]
Message-ID: <4C27F351.9060604@att.com>
Date: Sun, 27 Jun 2010 20:56:49 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: yam@ietf.org
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>
In-Reply-To: <4C2725DA.6000507@isode.com>
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: Mon, 28 Jun 2010 00:56:48 -0000

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

On 6/27/2010 6:20 AM, Alexey Melnikov wrote:
> [Moving this discussion to YAM and changing the subject.]
>
> I have a more fundamental question for this WG: are people still going 
> to be interested in updating various email specs if 3 muturity levels 
> are replaced with 1 or 2?
> (I understand that that would mean rechartering, but that is a 
> relatively minor point.)