[Gen-art] Re: Gen-ART review of draft-ietf-imss-fc-fcs-mib-02.txt

Henrik Levkowetz <henrik@levkowetz.com> Mon, 19 February 2007 17:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJCRw-0003Mm-4E; Mon, 19 Feb 2007 12:37:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJCRu-0003Mg-Uk for gen-art@ietf.org; Mon, 19 Feb 2007 12:37:14 -0500
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJCRt-0005zE-Fc for gen-art@ietf.org; Mon, 19 Feb 2007 12:37:14 -0500
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 938F137EF8; Mon, 19 Feb 2007 18:37:12 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 7568C37EE3; Mon, 19 Feb 2007 18:37:12 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 1D61137E46; Mon, 19 Feb 2007 18:37:12 +0100 (CET)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from <henrik@levkowetz.com>) id 1HJCRr-0006Z4-Eh; Mon, 19 Feb 2007 18:37:11 +0100
Message-ID: <45D9E047.1000607@levkowetz.com>
Date: Mon, 19 Feb 2007 18:37:11 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: Keith McCloghrie <kzm@cisco.com>
References: <200702191643.IAA15790@cisco.com>
In-Reply-To: <200702191643.IAA15790@cisco.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: kzm@cisco.com, suresh.krishnan@ericsson.com, gen-art@ietf.org, dromasca@avaya.com, hvivek@cisco.com, cds@cisco.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: "Romascanu, Dan" <dromasca@avaya.com>, General Area Review Team <gen-art@ietf.org>, hvivek@cisco.com, cds@cisco.com
Subject: [Gen-art] Re: Gen-ART review of draft-ietf-imss-fc-fcs-mib-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org

Removing ietf@ietf.org from the distribution list for comments about
the editorial notes:

on 2007-02-19 17:43 Keith McCloghrie said the following:
...
>> Editorial:
>> ==========
>> 
>> * No expiration date for draft on the first and last pages. According to
>>
>> http://www.ietf.org/ietf/1id-guidelines.txt
>> ===========================================
>> 
>>     A document expiration date should appear on the first and last page
>>     of the Internet-Draft.  The expiration date is 185 days following the
>>     submission of the document as an Internet-Draft.  Use of the phrase
>>     "expires in six months" or "expires in 185 days" is not acceptable.
>  
> The footer (on every page) contains the expiry date.

idnits failed to identify this.  Fixed in version 2.03.2

>> * Intended Status of the document is not specified in the draft. (I 
>> found it is Proposed Standard using the ID Tracker)
>  
> The guidelines say:
> 
>    The Internet-Draft should neither state nor imply that it has any
>    standards status; to do so conflicts with the role of the RFC Editor
>    and the IESG.  The title of the document should not imply a status.
>    Avoid the use of the terms Standard, Proposed, Draft, Experimental,
>    Historic, Required, Recommended, Elective, or Restricted in the title
>    of the Internet-Draft.  Indicating what status the document is aimed
>    for is OK, but should be done with the words "Intended status:
>    <status>".
> 
> Since the I-D neither states nor implies that it has any standards status,
> I believe it complies.

Yes.  But it's certainly easier to know what the intended status is, if the
document is explicit about it.  I understand that the IESG is now trying
hard to not issue Standards Track documents with normative references to
Informational or Experimental RFCs, so it would be helpful to provide that
information up front.  It would also make it easier for readers not intimately
involved in the particular working group to know how to relate to the draft.

That said, the guidelines should probably be updated to a 'should' instead
of 'is OK' regarding this.


	Henrik


_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art