Re: [yam] [Fwd: RFC 5321, Erratum 1543]

Tony Hansen <tony@att.com> Sat, 12 September 2009 04:17 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 4F26C3A68A6 for <yam@core3.amsl.com>; Fri, 11 Sep 2009 21:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.339
X-Spam-Level:
X-Spam-Status: No, score=-106.339 tagged_above=-999 required=5 tests=[AWL=0.260, 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 PVsUKXy5fldM for <yam@core3.amsl.com>; Fri, 11 Sep 2009 21:17:28 -0700 (PDT)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id 5C3C73A6903 for <yam@ietf.org>; Fri, 11 Sep 2009 21:17:28 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-14.tower-146.messagelabs.com!1252729088!7688234!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [144.160.112.25]
Received: (qmail 3922 invoked from network); 12 Sep 2009 04:18:09 -0000
Received: from sbcsmtp3.sbc.com (HELO tlph064.enaf.dadc.sbc.com) (144.160.112.25) by server-14.tower-146.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Sep 2009 04:18:09 -0000
Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id n8C4I5OC002223 for <yam@ietf.org>; Fri, 11 Sep 2009 23:18:05 -0500
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id n8C4I1lt002195 for <yam@ietf.org>; Fri, 11 Sep 2009 23:18:01 -0500
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 n8C4I1vA024777 for <yam@ietf.org>; Fri, 11 Sep 2009 23:18:01 -0500
Received: from 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 n8C4Hvip024766 for <yam@ietf.org>; Fri, 11 Sep 2009 23:17:57 -0500
Received: from [135.70.252.199] (vpn-135-70-252-199.vpn.east.att.com[135.70.252.199]) by maillennium.att.com (mailgw1) with ESMTP id <20090912041756gw1003ibmte> (Authid: tony); Sat, 12 Sep 2009 04:17:56 +0000
X-Originating-IP: [135.70.252.199]
Message-ID: <4AAB20F4.2070002@att.com>
Date: Sat, 12 Sep 2009 00:17:56 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: yam@ietf.org
References: <4AA4D490.9020700@isode.com> <6c9fcc2a0909070820w6b9fa44rf061ba60d87dad25@mail.gmail.com> <4AA54669.9070001@tana.it> <01NDFXXHFRHQ001ML6@mauve.mrochek.com> <4AA680C6.8000006@tana.it> <01NDHA2D0Z16001ML6@mauve.mrochek.com> <4AA78790.9010904@tana.it> <01NDIHODQ412001ML6@mauve.mrochek.com> <4AA7EC2A.90000@tana.it> <01NDIQVJACHK001ML6@mauve.mrochek.com> <6c9fcc2a0909101104q51340e5dk39612d0164661c7e@mail.gmail.com>
In-Reply-To: <6c9fcc2a0909101104q51340e5dk39612d0164661c7e@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [yam] [Fwd: RFC 5321, Erratum 1543]
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: Sat, 12 Sep 2009 04:17:29 -0000

I missed seeing most of this thread until today. Sorry -- I *really* 
need to get a better MUA.

The *primary* thing that this working group should be considering right 
now is the template that we are going to be sending to the IESG, and 
with it the pre-evaluation for RFC 1652.

The working group should *not* be looking at errata for 5321. It should 
*not* be looking at errata for 3798. It *should* have been looking at 
1652, whose WGLC just finished and hardly anyone deigned to respond to 
the issues that were outstanding there. (See other message coming out 
shortly.)

I am *not* going to declare any consensus on this issue -- 5321 isn't on 
my radar at this point. RFC 5321 is coming up again soon enough in our 
queue -- this topic can be revisited at that point if there is anything 
left to be revisited.

	Tony Hansen
	your usually-friendly neighborhood co-chair

Barry Leiba wrote:
> As I see it, it's clear where the consensus stands on this, and the
> discussion has gone into the realm of wasting the working group's time
> and effort.  I ask the chairs to declare whether they think there's
> consensus on this issue, and, thus, end the discussion, or they think
> more discussion is needed in order to reach consensus.