Re: Gen-ART review of draft-ietf-imss-fc-fcs-mib-02.txt
Keith McCloghrie <kzm@cisco.com> Mon, 19 February 2007 16:44 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJBcZ-0000uA-Nl; Mon, 19 Feb 2007 11:44:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJBcY-0000tp-G3; Mon, 19 Feb 2007 11:44:10 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJBcW-0003AY-3l; Mon, 19 Feb 2007 11:44:10 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-5.cisco.com with ESMTP; 19 Feb 2007 08:44:07 -0800
X-IronPort-AV: i="4.14,191,1170662400"; d="scan'208"; a="390719321:sNHT46913764"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l1JGi7mL013937; Mon, 19 Feb 2007 08:44:07 -0800
Received: from cisco.com (pita.cisco.com [171.71.177.199]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l1JGi7Gk024725; Mon, 19 Feb 2007 08:44:07 -0800 (PST)
Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id IAA15790; Mon, 19 Feb 2007 08:43:41 -0800 (PST)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200702191643.IAA15790@cisco.com>
To: suresh.krishnan@ericsson.com
Date: Mon, 19 Feb 2007 08:43:41 -0800
In-Reply-To: <no.id> from "Suresh Krishnan" at Feb 19, 2007 11:19:32 AM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2601; t=1171903447; x=1172767447; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kzm@cisco.com; z=From:=20Keith=20McCloghrie=20<kzm@cisco.com> |Subject:=20Re=3A=20Gen-ART=20review=20of=20draft-ietf-imss-fc-fcs-mib-02 .txt |Sender:=20; bh=jEUrTmeILPJpplDkPygDf9zyvKgxiki3ugVepBTN4yg=; b=P1XhK1MaivuXE6bO893S1njvMjJ0DU5BQfW2SM7fSs5aoJF2YEzPpZHZLDUFU76bkDgXHJ2H KI+MtqZqJoUB8OdLvEHdiXg6ibcTYCOZ8ykDPQnE4RThSBDO81bgnmhm;
Authentication-Results: sj-dkim-3; header.From=kzm@cisco.com; dkim=pass (sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: ietf@ietf.org, General Area Review Team <gen-art@ietf.org>, kzm@cisco.com, "\"Romascanu, Dan Dan" <dromasca@avaya.com>, hvivek@cisco.com, cds@cisco.com
Subject: Re: Gen-ART review of draft-ietf-imss-fc-fcs-mib-02.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
> I am the assigned Gen-ART reviewer for > draft-ietf-imss-fc-fcs-mib-02.txt Thanks for your review. > For background on Gen-ART, please see the FAQ at > <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>. > > Please resolve these comments along with any other Last Call comments > you may receive. > > Summary: This draft is basically ready for publication, but has nits > that should be fixed before publication. > > Comments: > > Minor: > ====== > > * Section 1: Introduction > > I found this sentence strange. Is there any reason to keep it? > > This memo includes boilerplate which uses only one of the following > terms, but is nevertheless required to mention all of the keywords in > the following statement: > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL > NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" > in this document are to be interpreted as described in BCP 14, RFC > 2119 [RFC2119]. Without this sentence, the boilerplate implies that all of the listed keywords are present in the document. Since the boilerplate cannot be changed, the sentence was included to avoid the erroneous implication. > 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. > * 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. Keith. _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: complex extensions attacking IETF protocols Masataka Ohta
- Re: complex extensions attacking IETF protocols Bob Stewart
- Re: complex extensions attacking IETF protocols Karl Denninger
- Re: ISMS working group and charter problems Keith McCloghrie
- Re: ISMS working group and charter problems Dave Crocker
- Re: ISMS working group and charter problems Tom Petch
- Re: ISMS working group and charter problems Sam Hartman
- Re: ISMS working group and charter problems Juergen Schoenwaelder
- Re: ISMS working group and charter problems Sam Hartman
- Re: ISMS working group and charter problems Juergen Schoenwaelder
- Re: ISMS working group and charter problems Keith McCloghrie
- Re: ISMS working group and charter problems Jeffrey Hutzelman
- Re: ISMS working group and charter problems Eliot Lear
- Re: ISMS working group and charter problems Eliot Lear
- Re: ISMS working group and charter problems Juergen Schoenwaelder
- Re: ISMS working group and charter problems Eliot Lear
- Re: ISMS working group and charter problems Juergen Schoenwaelder
- Re: ISMS working group and charter problems Eliot Lear
- Re: ISMS working group Keith McCloghrie
- Re: [Isms] ISMS charter broken- onus should be on… Keith McCloghrie
- Re: Gen-ART review of draft-ietf-imss-fc-fcs-mib-… Keith McCloghrie
- Re: Gen-ART review of draft-ietf-imss-fc-fcs-mib-… Suresh Krishnan
- Re: IETF MAILING: REGISTERED ATTENDEES: December … Masataka Ohta
- Re: IETF MAILING: REGISTERED ATTENDEES: December … Theodore Y. Ts'o
- Re: Last Call: Classical IP and ARP over ATM to P… Brian Carpenter CERN-CN
- Re: IAB/IETF standardization process Masataka Ohta
- Last Call: Classical IP and ARP over ATM to Propo… IESG Secretary
- Re: IETF MAILING: REGISTERED ATTENDEES: December … Masataka Ohta
- Copyright Confusion (was Re: IAB/IETF standardiza… Donald E. Eastlake 3rd (Beast)
- Re: Last Call: Classical IP and ARP over ATM to P… Masataka Ohta
- Re: Copyright Confusion (was Re: IAB/IETF standar… Masataka Ohta
- Re: Copyright Confusion (was Re: IAB/IETF standar… carl
- Re: Last Call: Classical IP and ARP over ATM to P… vincent birritteri ee stnt
- Re: IAB/IETF standardization process Simon E Spero
- Re: IETF MAILING: REGISTERED ATTENDEES: December … Masataka Ohta
- Re: IAB/IETF standardization process Masataka Ohta
- Re: IETF MAILING: REGISTERED ATTENDEES: December … Masataka Ohta
- Re: Last Call: Classical IP and ARP over ATM to P… Masataka Ohta
- Re: Last Call: Classical IP and ARP over ATM to P… Mark Laubach
- Re: Last Call: Classical IP and ARP over ATM to P… Masataka Ohta
- Re: IAB/IETF standardization process Mark Crispin
- Re: IAB/IETF standardization process Theodore Ts'o
- Re: Last Call: Classical IP and ARP over ATM to P… Masataka Ohta
- Last Call: Classical IP and ARP over ATM to Propo… The IESG