Re: [yam] RFC5322 reference in RFC1652bis?

Tony Hansen <tony@att.com> Fri, 19 February 2010 05:19 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 5880E28C150 for <yam@core3.amsl.com>; Thu, 18 Feb 2010 21:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.61
X-Spam-Level:
X-Spam-Status: No, score=-105.61 tagged_above=-999 required=5 tests=[AWL=-0.303, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 XQJ-IUtAj+Bp for <yam@core3.amsl.com>; Thu, 18 Feb 2010 21:19:21 -0800 (PST)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id 65C2E28C142 for <yam@ietf.org>; Thu, 18 Feb 2010 21:19:21 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-15.tower-167.messagelabs.com!1266556864!18834387!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 29904 invoked from network); 19 Feb 2010 05:21:05 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-15.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Feb 2010 05:21:05 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o1J5Ku3A028765 for <yam@ietf.org>; Fri, 19 Feb 2010 00:20:56 -0500
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o1J5Kpcc028744 for <yam@ietf.org>; Fri, 19 Feb 2010 00:20:52 -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 o1J5KxrR014021 for <yam@ietf.org>; Thu, 18 Feb 2010 23:20:59 -0600
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 o1J5KuWD014006 for <yam@ietf.org>; Thu, 18 Feb 2010 23:20:57 -0600
Received: from [135.70.148.221] (vpn-135-70-148-221.vpn.mwst.att.com[135.70.148.221]) by maillennium.att.com (mailgw1) with ESMTP id <20100219052056gw100m6bd1e> (Authid: tony); Fri, 19 Feb 2010 05:20:56 +0000
X-Originating-IP: [135.70.148.221]
Message-ID: <4B7E1FB7.6000307@att.com>
Date: Fri, 19 Feb 2010 00:20:55 -0500
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
CC: Yet Another Mail Working Group <yam@ietf.org>
References: <4B7D819E.2000704@dcrocker.net>
In-Reply-To: <4B7D819E.2000704@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [yam] RFC5322 reference in RFC1652bis?
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, 19 Feb 2010 05:19:23 -0000

Wearing my technical hat, I see no problem with this.

	Tony

On 2/18/2010 1:06 PM, Dave CROCKER wrote:
> Folks,
>
> The technical details of RFC1652bis must cite MIME AND SMTP, of course.
> However it happens that the details do not absolutlely need to cite
> RFC5322.
>
> However it strikes me as too strange to have a standard that pertains to
> message objects not cite the /message/ standard.
>
> I'd like to have RFC5322 cited at the time MIME is cited, as Ned
> suggested privately:
>
>
> In
> particular, a significant portion of the Internet community wishes to
> exchange messages in which the content body consists of a MIME
> message [RFC2045][RFC2046][RFC 5322] containing arbitrary octet-aligned
> material.
>
>
> Does anyone object?
>
> d/