Re: [yam] RFC5322 reference in RFC1652bis?
S Moonesamy <sm+ietf@elandsys.com> Fri, 19 February 2010 17:09 UTC
Return-Path: <sm@elandsys.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 D4D563A76B7 for <yam@core3.amsl.com>; Fri, 19 Feb 2010 09:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[AWL=0.288, 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 RhLlfKCEqchw for <yam@core3.amsl.com>; Fri, 19 Feb 2010 09:09:06 -0800 (PST)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id 2667328C2A8 for <yam@ietf.org>; Fri, 19 Feb 2010 09:09:00 -0800 (PST)
Received: from SUBMAN.elandsys.com ([41.136.238.150]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id o1JHASlY031610; Fri, 19 Feb 2010 09:10:38 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=elandsys.com; s=mail; t=1266599440; x=1266685840; bh=rzo/FIYYZAqjea91vR25CmXJBRI=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=kucASdOwWW12zfBak/cu0BN4uRbw5zAIIZou7mLUzS2h1BxPNefOEUWgkRWsr+eCQ yxODiV5vVH4JS4eUK5BVS54M+Od/dNwFdt9COdpNWtsRX+Pxi0Dh/ckxNBRr6PjduL xV4PeUdJSe7OSi0szUdR3SkfL0of+2Ju4qxd0thU=
Message-Id: <6.2.5.6.2.20100219090025.082bdef0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 19 Feb 2010 09:09:50 -0800
To: dcrocker@bbiw.net
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <4B7D819E.2000704@dcrocker.net>
References: <4B7D819E.2000704@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Yet Another Mail Working Group <yam@ietf.org>
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 17:09:07 -0000
Hi Dave, All the issues for draft-ietf-yam-rfc1652bis have been addressed. I closed all the related tickets in the tracker. At 10:06 18-02-10, Dave CROCKER wrote: >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. Please submit a new I-D. Regards, S. Moonesamy YAM WG Secretary
- [yam] RFC5322 reference in RFC1652bis? Dave CROCKER
- Re: [yam] RFC5322 reference in RFC1652bis? Tony Hansen
- Re: [yam] RFC5322 reference in RFC1652bis? S Moonesamy
- Re: [yam] RFC5322 reference in RFC1652bis? Dave CROCKER