Re: [OPSAWG] [Technical Errata Reported] RFC5935 (2477)

"David Harrington" <ietfdbh@comcast.net> Tue, 28 September 2010 15:31 UTC

Return-Path: <ietfdbh@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 B7F2F3A6C34 for <opsawg@core3.amsl.com>; Tue, 28 Sep 2010 08:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.293
X-Spam-Level:
X-Spam-Status: No, score=-102.293 tagged_above=-999 required=5 tests=[AWL=0.305, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 UdiWREqb2fko for <opsawg@core3.amsl.com>; Tue, 28 Sep 2010 08:31:47 -0700 (PDT)
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 9839B3A6D49 for <opsawg@ietf.org>; Tue, 28 Sep 2010 08:31:47 -0700 (PDT)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta01.westchester.pa.mail.comcast.net with comcast id CADB1f0051HzFnQ51FYVYR; Tue, 28 Sep 2010 15:32:29 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta14.westchester.pa.mail.comcast.net with comcast id CFYT1f0072JQnJT3aFYT0J; Tue, 28 Sep 2010 15:32:29 +0000
From: David Harrington <ietfdbh@comcast.net>
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, 'Mark Ellison' <ellison@ieee.org>, 'RFC Errata System' <rfc-editor@rfc-editor.org>
References: <20100819105540.5F394E0656@rfc-editor.org><AANLkTi=w8EXnLZA-yeUz+ap4fazNc4j_VxbXcK+6T+L-@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A040246D1FB@307622ANEX5.global.avaya.com>
Date: Tue, 28 Sep 2010 11:31:44 -0400
Message-ID: <92C71A4C60234BA0AD8185E0F38E8108@23FX1C1>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0E3C_01CB5F00.BBD46A10"
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-index: ActBR+iYpwb78qd8Q/mGSRoRr+kqRQAxwdEAB0TMpEA=
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040246D1FB@307622ANEX5.global.avaya.com>
Cc: rnatale@mitre.org, ah@tr-sys.de, ietf@ellisonsoftware.com, opsawg@ietf.org, chris@cw.net
Subject: Re: [OPSAWG] [Technical Errata Reported] RFC5935 (2477)
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: Tue, 28 Sep 2010 15:31:52 -0000

Hi,
 
does this modify an IANA request?
If so, make sure IANA modifies the regsitry to match.
 
dbh


  _____  

From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On
Behalf Of Romascanu, Dan (Dan)
Sent: Sunday, August 22, 2010 11:31 AM
To: Mark Ellison; RFC Errata System
Cc: ah@tr-sys.de; ietf@ellisonsoftware.com; rnatale@mitre.org;
opsawg@ietf.org; chris@cw.net
Subject: Re: [OPSAWG] [Technical Errata Reported] RFC5935 (2477)


Looks OK to me. Unless somebody objects on the opsawg list in the next
few days I will approve this resolution. 
 
Thanks and Regards,
 
Dan
 


  _____  

From: mark@ellisonsoftware.com [mailto:mark@ellisonsoftware.com] On
Behalf Of Mark Ellison
Sent: Saturday, August 21, 2010 6:46 PM
To: RFC Errata System
Cc: ietf@ellisonsoftware.com; rnatale@mitre.org; Romascanu, Dan (Dan);
rbonica@juniper.net; sob@harvard.edu; chris@cw.net; ah@tr-sys.de;
opsawg@ietf.org
Subject: Re: [Technical Errata Reported] RFC5935 (2477)


Hi Alfred,

Thank you for calling this errata on RFC 5935 to our attention.  As
one of the authors of this RFC, I concur with your suggested change to
Section 7, page 11.

If there are no objections from others, I recommend transitioning this
errata submission to 'verified'.

Regards,

Mark


On Thu, Aug 19, 2010 at 6:55 AM, RFC Errata System
<rfc-editor@rfc-editor.org> wrote:



The following errata report has been submitted for RFC5935,
"Expressing SNMP SMI Datatypes in XML Schema Definition Language".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5935
<http://www.rfc-editor.org/errata_search.php?rfc=5935&eid=2477>
&eid=2477

--------------------------------------
Type: Technical
Reported by: Alfred Hoenes <ah@TR-Sys.de>

Section: 7, pg.11

Original Text
-------------
  In accordance with RFC 3688 [RFC3688], the IANA XML registry has
been
  updated with the following namespace and schema registrations
  associated with this document:

  o  urn:ietf:params:xml:ns:smi:base:1.0

|  o  urn:ietf:params:xml:schema:base:1.0

Corrected Text
--------------
  In accordance with RFC 3688 [RFC3688], the IANA XML registry has
been
  updated with the following namespace and schema registrations
  associated with this document:

  o  urn:ietf:params:xml:ns:smi:base:1.0

|  o  urn:ietf:params:xml:schema:smi:base:1.0


Notes
-----
Rationale: "smi:" component missing in schema registration;
 Section 7.2 provides the correct URI.
 The registry entry at IANA is correct as well.

Remark:
 Also, the ASCII transliteration of the last name of the submitter
 of this note is misspelled in the last paragraph of Section 8.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC5935 (draft-ietf-opsawg-smi-datatypes-in-xsd-06)
--------------------------------------
Title               : Expressing SNMP SMI Datatypes in XML Schema
Definition Language
Publication Date    : August 2010
Author(s)           : M. Ellison, B. Natale
Category            : PROPOSED STANDARD
Source              : Operations and Management Area Working Group
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG