IETF Logo Mail Archive

Re: [yam] Issue #4

S Moonesamy <sm+ietf@elandsys.com> Thu, 10 December 2009 18:22 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 172AD3A6850 for <yam@core3.amsl.com>; Thu, 10 Dec 2009 10:22:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level:
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[AWL=0.268, 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 wzzAazuvzTmI for <yam@core3.amsl.com>; Thu, 10 Dec 2009 10:22:18 -0800 (PST)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id D03313A68A6 for <yam@ietf.org>; Thu, 10 Dec 2009 10:22:17 -0800 (PST)
Received: from subman.elandsys.com ([41.136.232.185]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id nBAILwIK011807; Thu, 10 Dec 2009 10:22:04 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=elandsys.com; s=mail; t=1260469325; x=1260555725; bh=zJtPIqluJu9xL6X/UQRp/v6Smf4=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=N7EEz7A+nvTgdUOL1hlvVFNJW5b8o8q8LUcGgdj5CU8t2dLvnQ654UbYooXEtFVsT V91f3EySZYnrQrQGGxNkIK0tCPUEzLFv/R5pGNBzGExZwmP6AktWWxLilfNouBjQpZ MtYmi35WGXbuth+OTRHCG7slN83ft5L9KktZF48E=
Message-Id: <6.2.5.6.2.20091210100121.02d15068@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Dec 2009 10:18:19 -0800
To: Ned Freed <ned.freed@mrochek.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <01NH27CJI5KK0002QL@mauve.mrochek.com>
References: <6.2.5.6.2.20091031115845.03fdeaa8@elandnews.com> <01NFMC338P960000BI@mauve.mrochek.com> <6.2.5.6.2.20091202190648.032612b0@elandnews.com> <4B1AC04A.5050204@isode.com> <6.2.5.6.2.20091205132616.030c4420@resistor.net> <6.2.5.6.2.20091209153400.033118d8@resistor.net> <01NH27CJI5KK0002QL@mauve.mrochek.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: yam@ietf.org
Subject: Re: [yam] Issue #4
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: Thu, 10 Dec 2009 18:22:19 -0000

Hi Ned,
At 17:09 09-12-2009, Ned Freed wrote:
>It doesn't look right to me... First of all, reference [4], to RFC 
>1522, should
>simply be dropped since it isn't referred to in the text. And the 
>update to RFC
>1522 is RFC 2047, so it makes no sense to update this reference to one to RFC
>2046. And I see no reason to retain the reference to RFC 1521. The less people
>look back to RFC 1521 the better off we will be.
>
>What needs to happen is:

I'm leaving Issue #4 open. I updated the tracker with your comments 
about the references.

>The text involving the capitalized MAY needs to be replaced along the lines of
>what I provided in my previous email on this topic.
>
>And finally, an IANA considerations section needs to be added containing
>a registration for this extension.

I'll track the above as a separate issue with a pointer to 
http://www.ietf.org/mail-archive/web/yam/current/msg00260.html

Regards,
S. Moonesamy
YAM WG Secretary

v2.23.0 | Report a Bug | By Email