IETF Logo Mail Archive

Re: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt

"Natale, Bob" <RNATALE@mitre.org> Mon, 02 February 2009 17:41 UTC

Return-Path: <opsawg-bounces@ietf.org>
X-Original-To: opsawg-archive@optimus.ietf.org
Delivered-To: ietfarch-opsawg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B951D3A692A; Mon, 2 Feb 2009 09:41:53 -0800 (PST)
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 269B43A67F4 for <opsawg@core3.amsl.com>; Mon, 2 Feb 2009 09:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vVvXTxgrvNyx for <opsawg@core3.amsl.com>; Mon, 2 Feb 2009 09:41:52 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id A12FF3A6929 for <opsawg@ietf.org>; Mon, 2 Feb 2009 09:41:28 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n12Hf8hP008149 for <opsawg@ietf.org>; Mon, 2 Feb 2009 12:41:08 -0500
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n12Hf8Sk008131; Mon, 2 Feb 2009 12:41:08 -0500
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Mon, 2 Feb 2009 12:41:08 -0500
From: "Natale, Bob" <RNATALE@mitre.org>
To: "j.schoenwaelder@jacobs-university.de" <j.schoenwaelder@jacobs-university.de>
Date: Mon, 02 Feb 2009 12:41:06 -0500
Thread-Topic: [OPSAWG] start WGLC on draft-ietf-opsawg-smi-datatypes-in-xsd-04.txt
Thread-Index: AcmFNkku0ATXcJWcTxqz/UeNTnZgzQAJkt2g
Message-ID: <17969D855F28964C88D177D45B6CDF11F2296C61@IMCMBX2.MITRE.ORG>
References: <20090130021022.B4DA312DC3E3@newdev.eecs.harvard.edu> <EDC652A26FB23C4EB6384A4584434A04013632CC@307622ANEX5.global.avaya.com> <20090202130044.GC3897@elstar.iuhb02.iu-bremen.de>
In-Reply-To: <20090202130044.GC3897@elstar.iuhb02.iu-bremen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] start 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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsawg-bounces@ietf.org
Errors-To: opsawg-bounces@ietf.org

Hi Juergen,

I have no problem removing the text that gives rise to your "meta-issue" as part of a revision for transmittal to the IESG, but I don't think it should require another round of WGLC...?

We had specific substantive inputs from a fair number of people during earlier drafts -- as is to be desired -- and all of those inputs have been incorporated or otherwise adjudicated, to the best of my knowledge.

Cheers,
BobN

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
Sent: Monday, February 02, 2009 8:01 AM
To: Romascanu, Dan (Dan)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] start WGLC ondraft-ietf-opsawg-smi-datatypes-in-xsd-04.txt

On Mon, Feb 02, 2009 at 01:39:58PM +0100, Romascanu, Dan (Dan) wrote:

> Answers like - 'I have read the document and I believe it's important
> enough and good enough to be submitted to the IESG' are also acceptable.

I have read the revised version and I still have a meta issue with the
following statement:

:   This memo is the first in a set of three related and (logically)
:   ordered specifications:
:
:      1.  SMI Base Datatypes [RFC2578] in XSD
:      2.  SMI MIB Structure [RFC2578] in XSD
:      3.  SNMP Textual Conventions [RFC2579] in XSD

We have a discussion at the IETF in Dublin the scope of this work and
I think the chairs got a task to sort this out, which as far as I can
tell did not happen. For some details, please see the meeting minutes.

Since I have not seen any documents for items 2. and 3., I am somewhat
unsure that the scope defined in this document is correct and that it
should be there in the first place, especially since there are no
working documents nor is it clear that the charter covers 2. and 3.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

v2.23.0 | Report a Bug | By Email