IETF Logo Mail Archive

Re: [yam] Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard

S Moonesamy <sm+ietf@elandsys.com> Mon, 22 August 2011 23:44 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: yam@ietfa.amsl.com
Delivered-To: yam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 159A321F8BDE for <yam@ietfa.amsl.com>; Mon, 22 Aug 2011 16:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level:
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KemNcCEOCpoi for <yam@ietfa.amsl.com>; Mon, 22 Aug 2011 16:44:26 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by ietfa.amsl.com (Postfix) with ESMTP id 4519721F8BD7 for <yam@ietf.org>; Mon, 22 Aug 2011 16:44:25 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.235.242]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p7MNjKvA019506; Mon, 22 Aug 2011 16:45:29 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1314056731; bh=Hsgjopic8KP1GmCpYVStzlOUOE4=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=wZOvrveVAiJi8krgGBD2THzbrrOYIZnVAhamB7gB68tmRob6p7fRd8MPPSjPrku0g rqMIlEAWEL5Iw2axc0MDrgU+1q4BngeBYjDTCdS+ez/niEDkEHFsDq6+xHVQqnj/Bs N1hv2il/JqnBuc/f8p9nBT0F2qz102uywXffzk7M=
Message-Id: <6.2.5.6.2.20110822155503.0b5ba2f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 22 Aug 2011 16:45:14 -0700
To: Alexey Melnikov <alexey.melnikov@isode.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <4E4FF3AF.6070006@isode.com>
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E44A5BE.3050008@att.com> <F5833273385BB34F99288B3648C4F06F13512DF6E3@EXCH-C2.corp.cloudmark.com> <4E4FF3AF.6070006@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: yam@ietf.org
Subject: Re: [yam] Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 22 Aug 2011 23:44:27 -0000

Hi Alexey,

Thanks for the review.  I am following up on the YAM mailing list.

At 10:49 20-08-2011, Alexey Melnikov wrote:
>One pedantic nit:
>
>8.4.  Transfer Encode
>
>   The MSA MAY apply transfer encoding to the message according to MIME
>   conventions, if needed and not harmful to the MIME type.
>
>Shouldn't this be "media type"?

That text is in RFC 4409.  From what I gathered, the term "MIME type" 
was used previously and "media type" is used nowadays.

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email