Re: [yam] Referencing 1652bis and update to RFC 5321/5322
Dave CROCKER <dhc@dcrocker.net> Tue, 29 June 2010 17:06 UTC
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 656CD3A6915 for <yam@core3.amsl.com>; Tue, 29 Jun 2010 10:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 5r2ZWAqlcTL7 for <yam@core3.amsl.com>; Tue, 29 Jun 2010 10:06:25 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 66DBE3A6862 for <yam@ietf.org>; Tue, 29 Jun 2010 10:06:25 -0700 (PDT)
Received: from [192.168.1.18] (ppp-68-122-72-44.dsl.pltn13.pacbell.net [68.122.72.44]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o5TH6SS4013450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jun 2010 10:06:35 -0700
Message-ID: <4C2A2814.8080007@dcrocker.net>
Date: Tue, 29 Jun 2010 10:06:28 -0700
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.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4C29FEA3.8050800@piuha.net>
In-Reply-To: <4C29FEA3.8050800@piuha.net>
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]); Tue, 29 Jun 2010 10:06:36 -0700 (PDT)
Cc: yam@ietf.org
Subject: Re: [yam] Referencing 1652bis and update to RFC 5321/5322
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: Tue, 29 Jun 2010 17:06:26 -0000
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/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- [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