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

Fred Baker <fred@cisco.com> Wed, 25 May 2005 17:20 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 NAA02092 for <wgchairs-archive@lists.ietf.org>; Wed, 25 May 2005 13:20:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DazWr-0001QT-6f; Wed, 25 May 2005 13:18:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DazWn-0001Q8-AQ for wgchairs@megatron.ietf.org; Wed, 25 May 2005 13:18:47 -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 NAA01923 for <wgchairs@ietf.org>; Wed, 25 May 2005 13:18:42 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DazpB-0003Tw-Q2 for wgchairs@ietf.org; Wed, 25 May 2005 13:37:48 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 25 May 2005 10:18:32 -0700
X-IronPort-AV: i="3.93,137,1115017200"; d="scan'208"; a="269557084:sNHT31235752"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j4PHIQbw012521; Wed, 25 May 2005 10:18:27 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com [10.32.244.218]) by imail.cisco.com (8.12.11/8.12.10) with SMTP id j4PH7NhX028765; Wed, 25 May 2005 10:07:23 -0700
In-Reply-To: <42949165.4050907@qualcomm.com>
References: <4292F2CD.9050507@zurich.ibm.com> <42949165.4050907@qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <42d087d10e076548b6e90ce46f11e577@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Date: Wed, 25 May 2005 10:18:28 -0700
To: ldondeti@qualcomm.com
X-Mailer: Apple Mail (2.622)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs"; t:"1117040843.595832"; x:"432200"; a:"rsa-sha1"; b:"nofws:2526"; e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p" "XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC" "50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc="; s:"WEePmQ1fcs4z5FCP8jeQnjYTZDnWb5OsxFh5IFH/zgZ3Ws170YhHt+5bLz99Dm0RimSsNjfu" "CcW96MfDJbNlkdMfQjr7Xere26DN+OlwFOYmOHKjwjb1jW1YfGlO6mTh5eoa8Nv8EF6rAcABBf2" "UJWn6NHni2KQ1Js9nra0ifJg="; c:"From: Fred Baker <fred@cisco.com>"; c:"Subject: Re: [Fwd: I-D ACTION:draft-iesg-info-exp-00.txt]"; c:"Date: Wed, 25 May 2005 10:18:28 -0700"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com"; c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org, Brian E Carpenter <brc@zurich.ibm.com>
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
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

imho, a requirements document is never standards track, and the words  
in 2119 only belong in documents that say what an implementation or  
solution must or must not do.

On May 25, 2005, at 7:53 AM, Lakshminath Dondeti wrote:

> 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
>>
>>
>