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

Tony Hansen <tony@att.com> Tue, 29 June 2010 21:46 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 F34FB3A6C22 for <yam@core3.amsl.com>; Tue, 29 Jun 2010 14:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.365
X-Spam-Level:
X-Spam-Status: No, score=-106.365 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 tCOLyEgmquFV for <yam@core3.amsl.com>; Tue, 29 Jun 2010 14:46:35 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id F17AF3A6C07 for <yam@ietf.org>; Tue, 29 Jun 2010 14:46:34 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-2.tower-167.messagelabs.com!1277848004!14958259!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 30454 invoked from network); 29 Jun 2010 21:46:45 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-2.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Jun 2010 21:46:45 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o5TLkLth020583 for <yam@ietf.org>; Tue, 29 Jun 2010 17:46:21 -0400
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o5TLkHdb020563 for <yam@ietf.org>; Tue, 29 Jun 2010 17:46:17 -0400
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klpd017.kcdc.att.com (8.14.3/8.14.3) with ESMTP id o5TLkeOV000393 for <yam@ietf.org>; Tue, 29 Jun 2010 16:46:40 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klpd017.kcdc.att.com (8.14.3/8.14.3) with ESMTP id o5TLkZnx032704 for <yam@ietf.org>; Tue, 29 Jun 2010 16:46:35 -0500
Received: from [135.70.25.139] (vpn-135-70-25-139.vpn.west.att.com[135.70.25.139]) by maillennium.att.com (mailgw1) with ESMTP id <20100629214634gw100s4p17e> (Authid: tony); Tue, 29 Jun 2010 21:46:35 +0000
X-Originating-IP: [135.70.25.139]
Message-ID: <4C2A69B9.3070508@att.com>
Date: Tue, 29 Jun 2010 17:46:33 -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: <4C29FEA3.8050800@piuha.net> <4C2A2814.8080007@dcrocker.net>
In-Reply-To: <4C2A2814.8080007@dcrocker.net>
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 21:46:39 -0000

If Russ' two step process goes forward, then the YAM working group's 
current charter will be complete.

At that point, we will have some choices to make such as whether we shut 
down the WG or whether we recharter.

When we started up YAM, we did discuss several possibilities for 
post-Full Standard work, including working on the numerous documents 
sitting in Proposed Standard state.

It will be up to the WG to make a decision when the time comes.

     Tony Hansen
     Your Friendly Neighborhood Co-Chair

On 6/29/2010 1:06 PM, Dave CROCKER wrote:
> On 6/29/2010 7:09 AM, Jari Arkko 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.
>
> Jari,
>
> This might reflect continuing confusion about the purpose of the YAM 
> working group.
>
> In pragmatic terms, as odd as it might seem, that is almost explicitly 
> NOT what
> the working is chartered to do.
>
> "Full" standard is really about community acceptance, rather than 
> being about improving the specifications.  For YAM, the focus in 
> writing the charter was specifically NOT to make any interesting 
> changes.  Anything that seems to call for interesting changes is 
> required to /disqualify/ the specification from further consideration...
>
> d/