Re: [yam] Issue #4

SM <sm@resistor.net> Sat, 05 December 2009 22:02 UTC

Return-Path: <sm@resistor.net>
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 006153A6956 for <yam@core3.amsl.com>; Sat, 5 Dec 2009 14:02:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level:
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 vyVXg-O986g1 for <yam@core3.amsl.com>; Sat, 5 Dec 2009 14:02:40 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 39D673A6892 for <yam@ietf.org>; Sat, 5 Dec 2009 14:02:40 -0800 (PST)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4.Beta0/8.14.4.Beta0) with ESMTP id nB5M2A4F010073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Dec 2009 14:02:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1260050549; x=1260136949; bh=IUv8tdmYAln09tuo1BsP8S8LaIMQKZRgt+rQps9ylmo=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=kNLI7v9Bq0rYvmWUpe9HtErErPtA6laosL5d2cjkouc7HiG3XK3GlEYGlLS05641U q0Jo2OdlsI3Ioz0jDhMGq9FI3HBH/VThB/2DszKbTsm18o+rw6Xx/ml5iqR1YySSe3 SHHqmy0cBlfvSotg4AtEp7UnC1A9ivk4l909fn9c=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=eTybfNl6VvlhDbf35hXibcRPSe0FOQD2BtVEJiJefwpRdRvtABXuTxraV0E7lYzjH t14aY60WV3jxDnHik4LJ3hDdBHZBWV8goPbUiN0+g+W8m2tWveKB+uW+gLbLZ6OYmie a2pdqpL1cV04fTTQC3/VuLNDA/TEB/oNTTFPUa8=
Message-Id: <6.2.5.6.2.20091205132616.030c4420@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 05 Dec 2009 13:46:28 -0800
To: Alexey Melnikov <alexey.melnikov@isode.com>
From: SM <sm@resistor.net>
In-Reply-To: <4B1AC04A.5050204@isode.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Ned Freed <ned.freed@mrochek.com>, 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: Sat, 05 Dec 2009 22:02:41 -0000

Hi Alexey,
At 12:19 05-12-2009, Alexey Melnikov wrote:
>Collecting all changes in one place, this is my recommendation:
>
>All existing References become Normative.

Agreed.

>A normative reference to RFC 2119 needs to be added, as the document 
>is using MAYs

There is only one "MAY" in the document (Section 3).  I prefer not to 
have the reference to RFC 2119 to avoid getting into a discussion 
about requirement levels.

>[1] RFC 821 --> 5321 (Draft) - downref, but in scope for YAM
>
>[2] RFC 822 --> RFC 5234 (Full)
>
>[3] RFC 1521 --> RFC 2045 (Draft) - downref, but in scope for YAM
>
>[4] - remove as unused
>
>[5] RFC 1651 --> RFC 5321 (Draft). Same as [1], so can be replaced with [1]
>
>[6] - remove as unused.

Agreed.

Regards,
-sm