[OPSAWG] WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt
"David B Harrington" <dbharrington@comcast.net> Wed, 04 February 2009 22:16 UTC
Return-Path: <dbharrington@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 616623A6934 for <opsawg@core3.amsl.com>; Wed, 4 Feb 2009 14:16:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, 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 SC3ZckZ8VlWp for <opsawg@core3.amsl.com>; Wed, 4 Feb 2009 14:16:57 -0800 (PST)
Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id 66D693A6921 for <opsawg@ietf.org>; Wed, 4 Feb 2009 14:16:57 -0800 (PST)
Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA01.westchester.pa.mail.comcast.net with comcast id BnQD1b0031HzFnQ51yG4mx; Wed, 04 Feb 2009 22:16:04 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA14.westchester.pa.mail.comcast.net with comcast id ByGe1b00K0UQ6dC3ayGecE; Wed, 04 Feb 2009 22:16:38 +0000
From: David B Harrington <dbharrington@comcast.net>
To: opsawg@ietf.org, "'Natale, Bob'" <RNATALE@mitre.org>
References: <20090130021022.B4DA312DC3E3@newdev.eecs.harvard.edu> <EDC652A26FB23C4EB6384A4584434A04013632CC@307622ANEX5.global.avaya.com> <17969D855F28964C88D177D45B6CDF11F2296C7C@IMCMBX2.MITRE.ORG> <17969D855F28964C88D177D45B6CDF11F2296C82@IMCMBX2.MITRE.ORG> <17969D855F28964C88D177D45B6CDF11F2296C8E@IMCMBX2.MITRE.ORG> <035601c98566$2e94ec80$0600a8c0@china.huawei.com>
Date: Wed, 04 Feb 2009 17:16:36 -0500
Message-ID: <058001c98716$3f329680$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <035601c98566$2e94ec80$0600a8c0@china.huawei.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcmCf+6Dw0EjDHCoReukukGWp0iR7ACspMxgAArzYzAAAGcj0AAAFHfAAAFle2AAal8+YA==
Subject: [OPSAWG] WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 22:16:58 -0000
Hi, I have reviewed the -04- revision and believe it is in good shape, with the following recommended changes. I think it should be published as a standards track RFC. Recommended changes: 1) Abstract s/(when approved as a standards-track RFC)// 2) Introduction I recommend dropping the part about three documents unless you actually publish initial versions of the other documents. I do recommend against creating a tarball of the three documents, which would hold up all three until all are complete. So dropping the text makes the most sense to me. On the other hand, this document alone is insufficient. Users of this document may also need the other two documents, depending on their purpose. You could say that the other two documents may be needed for complete reuse of existing MIB modules in an XML environment, but those documents have not been written at the time of this writing. 3) section 4 The paragraph about "BITS" needs to be modified: s/will be defined/????/ 4) IANA Considerations The document registers namespaces and schemas for three documents. This should be changed to only register one set. 5) Acknowledgements check the spelling of Alfred HInes. you or the RFC editor should remove the note to notify the editor. 6) References I think RFC3584 might be Normative, and 2579 Informational. 7) Open Issues remove this section 8) Change Log you or the RFC editor should remove the change log 9) copyrights need to be 2009, and must meet the new IPR rules. 10) Since this schema might be used separately from the enclosing document, should it contain information, similar to the description in a MIB module, such as organization, contact person, address, phone, email, last updated, the RFC in which it was published, etc.? David Harrington dbharrington@comcast.net ietfdbh@comcast.net dharrington@huawei.com
- [OPSAWG] start WGLC on draft-ietf-opsawg-smi-data… Scott O. Bradner
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Scott O. Bradner
- Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-d… Romascanu, Dan (Dan)
- Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-d… Juergen Schoenwaelder
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Natale, Bob
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Mark Ellison
- Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-d… Bert Wijnen (IETF)
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Natale, Bob
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Mark Ellison
- Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-… Natale, Bob
- [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-datat… Ersue, Mehmet (NSN - DE/Munich)
- [OPSAWG] WGLC on draft-ietf-opsawg-smi-datatypes-… David B Harrington
- Re: [OPSAWG] WGLC on draft-ietf-opsawg-smi-dataty… Natale, Bob