Re: [Fwd: I-D ACTION:draft-iesg-info-exp-00.txt]

Lakshminath Dondeti <ldondeti@qualcomm.com> Wed, 25 May 2005 14:54 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18627 for <wgchairs-archive@lists.ietf.org>; Wed, 25 May 2005 10:54:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaxGV-0007R9-4e; Wed, 25 May 2005 10:53:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaxGT-0007R4-6B for wgchairs@megatron.ietf.org; Wed, 25 May 2005 10:53:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18423 for <wgchairs@ietf.org>; Wed, 25 May 2005 10:53:43 -0400 (EDT)
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaxYr-00085A-Bh for wgchairs@ietf.org; Wed, 25 May 2005 11:12:46 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j4PErVdv027307; Wed, 25 May 2005 07:53:31 -0700 (PDT)
Received: from [10.4.42.144] (ldondeti.qualcomm.com [10.4.42.144]) by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j4PErQJ9001601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 25 May 2005 07:53:27 -0700 (PDT)
Message-ID: <42949165.4050907@qualcomm.com>
Date: Wed, 25 May 2005 10:53:25 -0400
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
Organization: Qualcomm
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <4292F2CD.9050507@zurich.ibm.com>
In-Reply-To: <4292F2CD.9050507@zurich.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
Subject: Re: [Fwd: I-D ACTION:draft-iesg-info-exp-00.txt]
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ldondeti@qualcomm.com
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
Sender: wgchairs-bounces@ietf.org
Errors-To: wgchairs-bounces@ietf.org
Content-Transfer-Encoding: 7bit

I have a related question:  RFC 2119 says that the keywords "MUST" and 
so forth are for standards track use.  In fact 2119 is very succinct 
(which is generally good, but I think 2119 is perhaps too succinct).  It 
starts out with an Abstract:

"In many standards track documents several words are used to signify the requirements in the specification ...", There is nothing else in
the main text: the document starts out with what appears to be a numbered list, which in fact are section numbers.  I would like to see 
some additional text in an Introduction section with detailed guidance on proper use of the keywords.

Specifically, I would like to see it address whether RFC 2119 words are "allowed" in documents of other category.  To me it makes 
sense to use them in Experimental track, but not in informational.  In RFC 4046 that I co-wrote  (MSEC group), we were forced to 
make all our MUSTs lowercase (i.e., they are the English language must, not the 2119 keyword).  A quick search in a few 
crypto-related informational RFCs reveals that the keywords are in fact used quite frequently in non-standards track documents.


I am looking for some guidance.  As I note above, perhaps the guidance 
should be documented in BCP 14.

(If it makes sense to use the keywords in Experimental RFCs, then the 
info-exp I-D might discuss that.)

thanks and regards,
Lakshminath

Brian E Carpenter wrote:

> Comments welcome (here, or on the ietf list if you think that is
> more appropriate).
>
>     Brian
>
> -------- Original Message --------
> Subject: I-D ACTION:draft-iesg-info-exp-00.txt
> Date: Mon, 23 May 2005 15:42:02 -0400
> From: Internet-Drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> CC: iesg@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Internet Engineering Steering Group 
> Working Group of the IETF.
>
>     Title        : Choosing between Informational and Experimental Status
>     Author(s)    : B. Carpenter
>     Filename    : draft-iesg-info-exp-00.txt
>     Pages        : 6
>     Date        : 2005-5-23
>     
> This document reproduces the rules for classifying documents as
>    Informational and Experimental from RFC 2026, and amplifies those
>    rules with guidelines relevant to ongoing IESG evaluations.  It is
>    not intended to change any of the underlying principles.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-iesg-info-exp-00.txt
>
>------------------------------------------------------------------------
>
>_______________________________________________
>I-D-Announce mailing list
>I-D-Announce@ietf.org
>https://www1.ietf.org/mailman/listinfo/i-d-announce
>
>  
>