
From alexey.melnikov@isode.com  Wed Feb  9 10:35:31 2011
Return-Path: <alexey.melnikov@isode.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 38C4F3A67BD for <yam@core3.amsl.com>; Wed,  9 Feb 2011 10:35:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 vjfn53r42mss for <yam@core3.amsl.com>; Wed,  9 Feb 2011 10:35:30 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id EBE8D3A67AB for <yam@ietf.org>; Wed,  9 Feb 2011 10:35:29 -0800 (PST)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TVLeewADLzeA@rufus.isode.com>; Wed, 9 Feb 2011 18:35:39 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D52DE4D.8090805@isode.com>
Date: Wed, 09 Feb 2011 18:34:53 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: John C Klensin <john-ietf@jck.com>
References: <4D2F4A3D.7070107@att.com> <C4234C2D4D4B9B3A1F9227E7@PST.JCK.COM>
In-Reply-To: <C4234C2D4D4B9B3A1F9227E7@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] whither YAM?
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: Wed, 09 Feb 2011 18:35:31 -0000

Hi John,

John C Klensin wrote:

>Tony,
>
>I'd rather make this reappraisal after we see the composition of
>the IESG that should be seated in Prague.  It seems to me that
>the key question is whether the IESG is going to be willing to
>process the documents as originally intended and that might give
>us a clue.  Or not, but certainly we will not have less
>information.
>
>In theory, we should have that information in well under a
>month.  If we do not, I think I'd suggest going ahead and asking
>for a meeting slot on the theory that meetings are much more
>easily cancelled (should that be necessary) than scheduled.
>  
>
I am sorry for not picking up this thread earlier, but let me say I was 
distracted by activities in a couple of my other WGs.

But anyway, now that the new IESG membership is known, I think the poll 
needs to be restarted.

>I certainly wouldn't object to modifying the charter to include
>your item C.
>
That part should be no problems.

>Finding out whether the IESG would be willing to
>approve a revised charter that included them but also included
>the preapproval model for documents that might go from
>Draft->Full would be another way to get some information.
>  
>
I can ask IESG about keeping the old charter, but my personal opinion is 
that the process documented in the charter is more work for both the WG 
and for IESG.

>   john
>
>
>--On Thursday, January 13, 2011 13:53 -0500 Tony Hansen
><tony@att.com> wrote:
>  
>
>>Folks, the time has come to start deciding what to do with the
>>YAM working group. I've been discussing this with my co-chair
>>and our AD, and I see several ways forward:
>>
>>     1) stay on hold -- keep the group in hiatus for another X
>>months
>>         a) we would need to decide on what X is
>>
>>     2) restart work as originally chartered. This means going
>>back and
>>         picking up where we left off on 5321bis, 5322bis and
>>4409bis.
>>
>>     3) shut down
>>
>>     4) recharter (see below)
>>
>>There are several ways we could recharter.
>>
>>     A) We could eliminate or modify the "process experiment"
>>we've been
>>	using (where we publish an I-D that indicates what needs to
>>	change, get IESG approval, and *then* proceed with revising
>>the
>>	RFC).
>>
>>     B) We could review the documents that were in the
>>original YAM
>>	charter. For any that we feel need to be revved no matter what
>>	(for example, 3798 MDN (one of my documents) is in this list),
>>	we can proceed with revising them.
>>
>>     C) We start taking a look at the Proposed Standard
>>mail-related
>>	standards and see what they need to moved forward to the next
>>	status.
>>
>>     D) Do something else.
>>
>>     E) Any combination of the above.
>>
>>Please provide your input. We have exactly one month to come
>>to a consensus, after which it will be too late to schedule a
>>meeting in Prague (should we decide we need one).
>>
>>         Tony Hansen
>>         YAM co-chair
>>


From alexey.melnikov@isode.com  Wed Feb  9 10:50:08 2011
Return-Path: <alexey.melnikov@isode.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 BB1473A69E7 for <yam@core3.amsl.com>; Wed,  9 Feb 2011 10:50:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 hvYNXLhikqEq for <yam@core3.amsl.com>; Wed,  9 Feb 2011 10:50:06 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 00A793A69E6 for <yam@ietf.org>; Wed,  9 Feb 2011 10:50:06 -0800 (PST)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TVLh5wADLwfz@rufus.isode.com>; Wed, 9 Feb 2011 18:50:15 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D52E1B5.4020409@isode.com>
Date: Wed, 09 Feb 2011 18:49:25 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Tony Hansen <tony@att.com>
References: <4D2F4A3D.7070107@att.com>
In-Reply-To: <4D2F4A3D.7070107@att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] whither YAM?
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: Wed, 09 Feb 2011 18:50:08 -0000

Hi Tony,
With my AD hat on:

Tony Hansen wrote:

> Folks, the time has come to start deciding what to do with the YAM 
> working group. I've been discussing this with my co-chair and our AD, 
> and I see several ways forward:
>
>     1) stay on hold -- keep the group in hiatus for another X months
>         a) we would need to decide on what X is

I am very uncomfortable with letting this WG stay on hold for an 
extended period of time.
I think it is my duty as the outgoing AD to get rid of dead wood and 
simplify life for my successor.

>     2) restart work as originally chartered. This means going back and
>         picking up where we left off on 5321bis, 5322bis and 4409bis.

I suppose the WG can do that, but my personal opinion is that the 
process experiment has failed. IESG is not actually as much of a problem 
as people think it is, and I believe this is going to stay the same 
after March 2011.

>     3) shut down
>
>     4) recharter (see below)

These are my two preferred choices. Details of the new charter don't 
matter to me that much, as long as the process experiment part is removed.
My personal (not-as-an-AD) preferences are to do some combination of B) 
and C).

> There are several ways we could recharter.
>
>     A) We could eliminate or modify the "process experiment" we've been
>     using (where we publish an I-D that indicates what needs to
>     change, get IESG approval, and *then* proceed with revising the
>     RFC).
>
>     B) We could review the documents that were in the original YAM
>     charter. For any that we feel need to be revved no matter what
>     (for example, 3798 MDN (one of my documents) is in this list),
>     we can proceed with revising them.
>
>     C) We start taking a look at the Proposed Standard mail-related
>     standards and see what they need to moved forward to the next
>     status.
>
>     D) Do something else.
>
>     E) Any combination of the above.
>
> Please provide your input. We have exactly one month to come to a 
> consensus, after which it will be too late to schedule a meeting in 
> Prague (should we decide we need one).
>
>         Tony Hansen
>         YAM co-chair

Best Regards,
Alexey

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address


From tony@att.com  Wed Feb  9 10:58:42 2011
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 EF60D3A67A4 for <yam@core3.amsl.com>; Wed,  9 Feb 2011 10:58:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.338
X-Spam-Level: 
X-Spam-Status: No, score=-106.338 tagged_above=-999 required=5 tests=[AWL=0.261, 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 yR8fHT-Sdwps for <yam@core3.amsl.com>; Wed,  9 Feb 2011 10:58:42 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id 0AE933A6768 for <yam@ietf.org>; Wed,  9 Feb 2011 10:58:41 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-11.tower-119.messagelabs.com!1297277931!4715902!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 7457 invoked from network); 9 Feb 2011 18:58:51 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-11.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Feb 2011 18:58:51 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p19IxEce015115 for <yam@ietf.org>; Wed, 9 Feb 2011 13:59:14 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p19Ix9R4014994 for <yam@ietf.org>; Wed, 9 Feb 2011 13:59:10 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p19Iwkk7017002 for <yam@ietf.org>; Wed, 9 Feb 2011 13:58:46 -0500
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p19IwgUc016858 for <yam@ietf.org>; Wed, 9 Feb 2011 13:58:42 -0500
Received: from [135.91.118.213] (dn135-91-118-213.dhcpn.ugn.att.com[135.91.118.213]) by maillennium.att.com (mailgw1) with ESMTP id <20110209185842gw100e4llve> (Authid: tony); Wed, 9 Feb 2011 18:58:42 +0000
X-Originating-IP: [135.91.118.213]
Message-ID: <4D52E3E2.1050804@att.com>
Date: Wed, 09 Feb 2011 13:58:42 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Yet Another Mail Working Group <yam@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [yam] YAM meeting in Prague?
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: Wed, 09 Feb 2011 18:58:43 -0000

Should YAM meet in Prague?

The cutoff for deciding is this coming Monday.

If so, what other WG meetings do we want to avoid conflicts with?

     Tony Hansen
     YAM co-chair

From barryleiba.mailing.lists@gmail.com  Wed Feb  9 11:17:11 2011
Return-Path: <barryleiba.mailing.lists@gmail.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 6F49A3A6839 for <yam@core3.amsl.com>; Wed,  9 Feb 2011 11:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 Icjq4RSFqDvz for <yam@core3.amsl.com>; Wed,  9 Feb 2011 11:17:10 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 731433A672F for <yam@ietf.org>; Wed,  9 Feb 2011 11:17:10 -0800 (PST)
Received: by iwc10 with SMTP id 10so494432iwc.31 for <yam@ietf.org>; Wed, 09 Feb 2011 11:17:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hhy7+mevNiiOpjYLfmC68Vi0OrDAUWoBdFBX2e/JhZk=; b=MsJ6Nz89oeJuWxKOiQDAuMQ+4Uxitaw4BkgsXER98C6fqPCvJO7doj31X4d0GUsXRS iWdrdduVBn8O2WSD8URoWs0sjPNd4yqBLcT/l+CIV6bp+bbUFLc6gBGF6wXqP9haGL9e /h4ERgUOCr2imtM+XQirf7kCbYvUxBZjoYuRc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=wQn3JGFs0vPYWXxZLmx9gO2Zat2lBAKNKo11GeN54N1PyfM7nxS2Ty4tt6B4T8wDmE dvQWRmluNacG3kemEzv97ipkW2Sfxb/oFy0WbkF9+mlwRnJUtr5GvgZ+gLunebxKpNKy a6EhG4W3zxMxf5TF8dbtd9swTgCbrhkTEsnTM=
MIME-Version: 1.0
Received: by 10.42.219.136 with SMTP id hu8mr22242484icb.357.1297279040336; Wed, 09 Feb 2011 11:17:20 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.228.74 with HTTP; Wed, 9 Feb 2011 11:17:20 -0800 (PST)
In-Reply-To: <4D52E3E2.1050804@att.com>
References: <4D52E3E2.1050804@att.com>
Date: Wed, 9 Feb 2011 14:17:20 -0500
X-Google-Sender-Auth: 9WqCjMkAOufoV1K9-l2ef71RkdM
Message-ID: <AANLkTimTDXUrpEcaW4HeMkBJ9Kcfih6eFHTSwwrdmqX3@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Tony Hansen <tony@att.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] YAM meeting in Prague?
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: Wed, 09 Feb 2011 19:17:11 -0000

> Should YAM meet in Prague?

I think not.  But I think we should know more about two-track by QC.

Barry

From dhc@dcrocker.net  Wed Feb  9 11:21:40 2011
Return-Path: <dhc@dcrocker.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 8E16C3A69C3 for <yam@core3.amsl.com>; Wed,  9 Feb 2011 11:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.166
X-Spam-Level: 
X-Spam-Status: No, score=-6.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 z2HhHKSs1SrV for <yam@core3.amsl.com>; Wed,  9 Feb 2011 11:21:39 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 60DD63A67AE for <yam@ietf.org>; Wed,  9 Feb 2011 11:21:39 -0800 (PST)
Received: from [192.168.1.4] (adsl-68-122-35-253.dsl.pltn13.pacbell.net [68.122.35.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p19JLfxp011648 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 9 Feb 2011 11:21:46 -0800
Message-ID: <4D52E943.6090304@dcrocker.net>
Date: Wed, 09 Feb 2011 11:21:39 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <4D52E3E2.1050804@att.com> <AANLkTimTDXUrpEcaW4HeMkBJ9Kcfih6eFHTSwwrdmqX3@mail.gmail.com>
In-Reply-To: <AANLkTimTDXUrpEcaW4HeMkBJ9Kcfih6eFHTSwwrdmqX3@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 09 Feb 2011 11:21:46 -0800 (PST)
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] YAM meeting in Prague?
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 09 Feb 2011 19:21:40 -0000

On 2/9/2011 11:17 AM, Barry Leiba wrote:
>> Should YAM meet in Prague?
>
> I think not.  But I think we should know more about two-track by QC.

+1

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc@dcrocker.net  Wed Feb  9 12:23:55 2011
Return-Path: <dhc@dcrocker.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 92FF83A67AB for <yam@core3.amsl.com>; Wed,  9 Feb 2011 12:23:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.274
X-Spam-Level: 
X-Spam-Status: No, score=-6.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 IAZU9Nwd6gXf for <yam@core3.amsl.com>; Wed,  9 Feb 2011 12:23:54 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 2D6D23A67AA for <yam@ietf.org>; Wed,  9 Feb 2011 12:23:54 -0800 (PST)
Received: from [192.168.1.4] (adsl-68-122-35-253.dsl.pltn13.pacbell.net [68.122.35.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p19KNxbV014049 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <yam@ietf.org>; Wed, 9 Feb 2011 12:24:04 -0800
Message-ID: <4D52F7DD.3020803@dcrocker.net>
Date: Wed, 09 Feb 2011 12:23:57 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Yet Another Mail Working Group <yam@ietf.org>
References: <4D2F4A3D.7070107@att.com> <4D52E1B5.4020409@isode.com>
In-Reply-To: <4D52E1B5.4020409@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 09 Feb 2011 12:24:04 -0800 (PST)
Subject: Re: [yam] whither YAM?
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 09 Feb 2011 20:23:55 -0000

On 2/9/2011 10:49 AM, Alexey Melnikov wrote:
> I am very uncomfortable with letting this WG stay on hold for an extended period
> of time.
> I think it is my duty as the outgoing AD to get rid of dead wood and simplify
> life for my successor.
>
>> 2) restart work as originally chartered. This means going back and
>> picking up where we left off on 5321bis, 5322bis and 4409bis.
>
> I suppose the WG can do that, but my personal opinion is that the process
> experiment has failed. IESG is not actually as much of a problem as people think
> it is, and I believe this is going to stay the same after March 2011.


Russ Housley has recruited Eric Burger and me to help produce a new version of 
the two-stage maturity specification.  (It is within epsilon of being issued.)

That causes me to think it highly likely that some form of two-stage model will 
proceed to be adopted.

As such, I do not see any need for YAM.  We should shut down.

I agree that the effort be classed as a failure.  I disagree about the role of 
the IESG.  But that's rendered moot, of course.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From john-ietf@jck.com  Fri Feb 11 11:24:05 2011
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 5FC393A69D2 for <yam@core3.amsl.com>; Fri, 11 Feb 2011 11:24:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Jn5VK0IojpaL for <yam@core3.amsl.com>; Fri, 11 Feb 2011 11:24:05 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 166C23A659A for <yam@ietf.org>; Fri, 11 Feb 2011 11:24:05 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PnybL-000GBO-41; Fri, 11 Feb 2011 14:24:19 -0500
Date: Fri, 11 Feb 2011 14:24:18 -0500
From: John C Klensin <john-ietf@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Tony Hansen <tony@att.com>
Message-ID: <4341A78A523DF81A49A67F09@PST.JCK.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
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] whither YAM?
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: Fri, 11 Feb 2011 19:24:05 -0000

--On Wednesday, February 09, 2011 18:49 +0000 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

>...
> These are my two preferred choices. Details of the new charter
> don't matter to me that much, as long as the process
> experiment part is removed.
> My personal (not-as-an-AD) preferences are to do some
> combination of B) and C).
> 
>...
>>     B) We could review the documents that were in the
>>     original YAM charter. For any that we feel need to be
>>     revved no matter what (for example, 3798 MDN (one of my
>>     documents) is in this list), we can proceed with revising
>>     them.
>> 
>>     C) We start taking a look at the Proposed Standard
>>     mail-related standards and see what they need to moved
>>     forward to the next status.

For whatever my opinion is worth, I think it would be worth
taking a look at (C).  If there are documents at Proposed that
would benefit from a review of features and interoperability,
that is useful work regardless of what happens with the
standards process.  For anything else, it would be good to have
two-step sufficiently resolved that we knew what the targets
were that we had to meet (of course, the intent of the process
experiment was precisely to resolve that on a per-document
basis, so, while the experiment may be dead, the need for it is
not... unless we are to conclude that the IESG simply isn't
interested in advancing documents other than on a "guess what we
are likely to want" basis).

   john


From john-lame@jck.com  Fri Feb 11 11:22:53 2011
Return-Path: <john-lame@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 121EB3A69D2 for <yam@core3.amsl.com>; Fri, 11 Feb 2011 11:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 uoOLVSTaRqnk for <yam@core3.amsl.com>; Fri, 11 Feb 2011 11:22:52 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 97B903A659A for <yam@ietf.org>; Fri, 11 Feb 2011 11:22:51 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Pnya8-000G9b-GZ; Fri, 11 Feb 2011 14:23:04 -0500
Date: Fri, 11 Feb 2011 14:23:03 -0500
From: John C Klensin <john-lame@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Tony Hansen <tony@att.com>
Message-ID: <AD5ADEF2CD7AC8ED6ED69542@PST.JCK.COM>
In-Reply-To: <4D52E1B5.4020409@isode.com>
References: <4D2F4A3D.7070107@att.com> <4D52E1B5.4020409@isode.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
X-Mailman-Approved-At: Fri, 11 Feb 2011 12:15:55 -0800
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] whither YAM?
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: Fri, 11 Feb 2011 19:22:53 -0000

--On Wednesday, February 09, 2011 18:49 +0000 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

>...
> These are my two preferred choices. Details of the new charter
> don't matter to me that much, as long as the process
> experiment part is removed.
> My personal (not-as-an-AD) preferences are to do some
> combination of B) and C).
> 
>...
>>     B) We could review the documents that were in the
>>     original YAM charter. For any that we feel need to be
>>     revved no matter what (for example, 3798 MDN (one of my
>>     documents) is in this list), we can proceed with revising
>>     them.
>> 
>>     C) We start taking a look at the Proposed Standard
>>     mail-related standards and see what they need to moved
>>     forward to the next status.

For whatever my opinion is worth, I think it would be worth
taking a look at (C).  If there are documents at Proposed that
would benefit from a review of features and interoperability,
that is useful work regardless of what happens with the
standards process.  For anything else, it would be good to have
two-step sufficiently resolved that we knew what the targets
were that we had to meet (of course, the intent of the process
experiment was precisely to resolve that on a per-document
basis, so, while the experiment may be dead, the need for it is
not... unless we are to conclude that the IESG simply isn't
interested in advancing documents other than on a "guess what we
are likely to want" basis).

   john


From ned.freed@mrochek.com  Sun Feb 13 10:02:05 2011
Return-Path: <ned.freed@mrochek.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 02EF13A67BD for <yam@core3.amsl.com>; Sun, 13 Feb 2011 10:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 nklSte-qwNt2 for <yam@core3.amsl.com>; Sun, 13 Feb 2011 10:02:04 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id E66103A6A00 for <yam@ietf.org>; Sun, 13 Feb 2011 10:02:03 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NXRVDEWLPS00KPR4@mauve.mrochek.com> for yam@ietf.org; Sun, 13 Feb 2011 10:02:21 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NXPN84OCUO007FL5@mauve.mrochek.com>; Sun, 13 Feb 2011 10:02:18 -0800 (PST)
Message-id: <01NXRVDDV5YC007FL5@mauve.mrochek.com>
Date: Sun, 13 Feb 2011 10:01:57 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 11 Feb 2011 14:23:03 -0500" <AD5ADEF2CD7AC8ED6ED69542@PST.JCK.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <4D2F4A3D.7070107@att.com> <4D52E1B5.4020409@isode.com> <AD5ADEF2CD7AC8ED6ED69542@PST.JCK.COM>
To: John C Klensin <john-lame@jck.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1297616572; bh=iHwezeV6kO/HMBXa5Lgaffw2IrT0ba6ay1gJgHnZhms=; h=Cc:Message-id:Date:From:Subject:In-reply-to:MIME-version: Content-type:References:To; b=n1qd1J0e5BnfVc5KKkDs22OzDz7mafKstjllMr53N/lMsbY9QV5FbmwJIDOKuYhiv uCXK4zsZL2cyuP4YCt5UNrS3z8AK08Ou/ooDZjcm6JSqY8HrQX4W9HnXmUwY5+oM8/ t+SA754BJFay0/K75kGupt5EQgRC+odCjx/SZ0+c=
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] whither YAM?
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: Sun, 13 Feb 2011 18:02:05 -0000

> --On Wednesday, February 09, 2011 18:49 +0000 Alexey Melnikov
> <alexey.melnikov@isode.com> wrote:

> >...
> > These are my two preferred choices. Details of the new charter
> > don't matter to me that much, as long as the process
> > experiment part is removed.
> > My personal (not-as-an-AD) preferences are to do some
> > combination of B) and C).
> >
> >...
> >>     B) We could review the documents that were in the
> >>     original YAM charter. For any that we feel need to be
> >>     revved no matter what (for example, 3798 MDN (one of my
> >>     documents) is in this list), we can proceed with revising
> >>     them.
> >>
> >>     C) We start taking a look at the Proposed Standard
> >>     mail-related standards and see what they need to moved
> >>     forward to the next status.

> For whatever my opinion is worth, I think it would be worth
> taking a look at (C).  If there are documents at Proposed that
> would benefit from a review of features and interoperability,
> that is useful work regardless of what happens with the
> standards process.  For anything else, it would be good to have
> two-step sufficiently resolved that we knew what the targets
> were that we had to meet (of course, the intent of the process
> experiment was precisely to resolve that on a per-document
> basis, so, while the experiment may be dead, the need for it is
> not... unless we are to conclude that the IESG simply isn't
> interested in advancing documents other than on a "guess what we
> are likely to want" basis).

+1

				Ned
