Re: [yam] Referencing 1652bis and update to RFC 5321/5322
Alessandro Vesely <vesely@tana.it> Sun, 27 June 2010 17:32 UTC
Return-Path: <vesely@tana.it>
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 F2E053A693A for <yam@core3.amsl.com>; Sun, 27 Jun 2010 10:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level:
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=1.190, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 6memE7SvlbiD for <yam@core3.amsl.com>; Sun, 27 Jun 2010 10:31:54 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 934243A6878 for <yam@ietf.org>; Sun, 27 Jun 2010 10:31:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1277659903; bh=92pnUJNvQXNH+E7+qIHO3SanhxXFZ7yoFUQUulXnKCA=; l=883; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=WFJ3UB5pRAcDFHmKYEOGAP01dEiE7LcTfgz6Ce5UQ1QYKV9btbsqx2UZRImI2EyvZ LKKkh+21j1iGNLDtcC6prxUhv2Lb5xePYrIGiY3he9jZTwEiObkL8qp//H88XTH35l tKA7aa0yI1mcsijU2AO9JZG92HTWiMvhZWYVmmyg=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Sun, 27 Jun 2010 19:31:43 +0200 id 00000000005DC02B.000000004C278AFF.00003504
Message-ID: <4C278AFD.6080804@tana.it>
Date: Sun, 27 Jun 2010 19:31:41 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
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> <4C272C75.8060407@dcrocker.net> <4C272D60.9000703@isode.com> <4C272E8A.8000505@dcrocker.net>
In-Reply-To: <4C272E8A.8000505@dcrocker.net>
Content-Type: text/plain; charset="us-ascii"; 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: Sun, 27 Jun 2010 17:32:02 -0000
On 27/Jun/10 12:57, Dave CROCKER wrote: > On 6/27/2010 11:52 AM, Alexey Melnikov wrote: >> This is not the question I've asked ;-). "Are people interested in >> updating documents" and "are people interested in moving from Draft to >> Full" are not quite the same. > > Strictly speaking, the task of this working group, as I understand it, > is to move docs from Draft to Full. The editing is in the service of > that goal rather than being a goal of its own. Although that's correct, some documents really deserve a revision. I, for one, would be interested in completing the work defined by the existing issues. Documents that need no editing need no advancement, /if/ that proposal passes. For those cases, it is possible that the IESG has to actually work more than the WG in order to produce an advancement, so the decision could be left with them...
- [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