RE: [OPSAWG] [nmrg] draft-irtf-nmrg-snmp-measure-04.txt oid xmlpattern change
"David Harrington" <ietfdbh@comcast.net> Fri, 16 May 2008 14:13 UTC
Received: from QMTA02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by bierator.ibr.cs.tu-bs.de (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id m4GEDnCB014887 for <nmrg@ibr.cs.tu-bs.de>; Fri, 16 May 2008 16:13:55 +0200
Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA02.emeryville.ca.mail.comcast.net with comcast id SAv71Z00216AWCUA20G700; Fri, 16 May 2008 14:13:43 +0000
Received: from Harrington73653 ([24.128.66.199]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id SEDg1Z0044HwxpC8S00000; Fri, 16 May 2008 14:13:43 +0000
X-Authority-Analysis: v=1.0 c=1 a=ISx8kgmK6NcA:10 a=X5CS3wKyBVwA:10 a=j3Z76cjpAAAA:8 a=Jiz0tsSxAAAA:8 a=48vgC7mUAAAA:8 a=cQZuYZh4ME2UarBVmeoA:9 a=blMDACQhUAAelina1AQA:7 a=32j3w6sY7jJCCCOEoydU2Ar3j-0A:4 a=FvgKqOQ44qUA:10 a=JrSEOxZJtCQA:10 a=lZB815dzVvQA:10 a=50e4U0PicR4A:10
From: David Harrington <ietfdbh@comcast.net>
To: "'Natale, Bob'" <RNATALE@mitre.org>, j.schoenwaelder@jacobs-university.de, 'Bert Wijnen' <bertietf@bwijnen.net>
References: <20080516122704.GB19275@elstar.local> <4915F014FDD99049A9C3A8C1B832004F02AEAA46@IMCSRV2.MITRE.ORG>
Subject: RE: [OPSAWG] [nmrg] draft-irtf-nmrg-snmp-measure-04.txt oid xmlpattern change
Date: Fri, 16 May 2008 10:13:40 -0400
Message-ID: <07ef01c8b75f$0c1b7000$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: <4915F014FDD99049A9C3A8C1B832004F02AEAA46@IMCSRV2.MITRE.ORG>
Thread-Index: Aci3UELJ3N6FvxJ6R86avAHLVyYyMgACifDAAADWtXA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-IBRFilter-SpamReport: 3.602 (***) BAYES_50, DNS_FROM_RFC_POST, RCVD_IN_SORBS_DUL
X-Scanned-By: MIMEDefang 2.51 on 134.169.34.9
Cc: opsawg@ietf.org, nmrg@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://mail.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <http://mail.ibr.cs.tu-bs.de/pipermail/nmrg>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Subscribe: <https://mail.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
X-List-Received-Date: Fri, 16 May 2008 14:14:01 -0000
Hi, SMIv2 is based on ASN.1-1988 not ASN.1-2002. XSDMI should maintain fidelity to SMIv2. I would think the snmp-measure document should do so also. We should be liberal in what we accept, and conservative in what we send, of course. I think XSDMI should enforce the 1988 syntax, since one expected use case is validation; it probably will make no difference to the snmp-research document, whose use case is reporting. In practice, I have never seen a 2.X in any SMIv2 MIB module. dbh > -----Original Message----- > From: opsawg-bounces@ietf.org > [mailto:opsawg-bounces@ietf.org] On Behalf Of Natale, Bob > Sent: Friday, May 16, 2008 9:48 AM > To: j.schoenwaelder@jacobs-university.de; Bert Wijnen > Cc: opsawg@ietf.org; nmrg@ibr.cs.tu-bs.de > Subject: Re: [OPSAWG] [nmrg] > draft-irtf-nmrg-snmp-measure-04.txt oid xmlpattern change > > Hi, > > Juergen is correct (per Sec. 8.19 of ITU-T Recommendation X.690, > prepared by ITU-T Study Group 17 and approved on 14 July 2002, > identical text is also published as ISO/IEC 8825-1). > > draft-ietf-opsawg-smi-datatypes-in-xsd-02.txt (to be posted any day > now!) will contain the fix Juergen provides below. > > Cheers, > BobN > > -----Original Message----- > From: nmrg-bounces@ibr.cs.tu-bs.de > [mailto:nmrg-bounces@ibr.cs.tu-bs.de] On Behalf Of Juergen > Schoenwaelder > Sent: Friday, May 16, 2008 8:27 AM > To: nmrg@ibr.cs.tu-bs.de; Bert Wijnen > Subject: [nmrg] draft-irtf-nmrg-snmp-measure-04.txt oid xml pattern > change > > Hi, > > there was recently a discussion on the XSD pattern for object > identifier values and it was pointed out that the pattern we picked up > from the SMI-XSD document is too restrictive by not allowing OIDs of > the format 2.X.* where X is larger than 39. I therefore propose that > we change the pattern used by oid.type from > > "[0-2](\.[1-3]?[0-9])(\.(0|([1-9]\d*))){0,126}" > > to > > "([0-1](\.[1-3]?[0-9]))|(2.(0|([1-9]\d*)))" ~ > "(\.(0|([1-9]\d*))){0,126}" > > Any objections against this change which is really a bugfix? Bert, do > we run into procedural trouble if we fix this or an additional N weeks > delay? (In that case, I would be tempted to go along with the buggy > version of the pattern. ;-) > > /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/> > -- > !! This message is brought to you via the `nmrg' mailing list. > !! Please do not reply to this message to unsubscribe. To unsubscribe > or adjust > !! your settings, send a mail message to > <nmrg-request@ibr.cs.tu-bs.de> > !! or look at https://mail.ibr.cs.tu-bs.de/mailman/listinfo/nmrg. > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg >
- RE: [OPSAWG] [nmrg] draft-irtf-nmrg-snmp-measure-… Natale, Bob
- RE: [OPSAWG] [nmrg] draft-irtf-nmrg-snmp-measure-… David Harrington
- RE: [nmrg] draft-irtf-nmrg-snmp-measure-04.txt oi… Natale, Bob
- [nmrg] draft-irtf-nmrg-snmp-measure-04.txt oid xm… Juergen Schoenwaelder