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

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 19 August 2010 10:55 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 19A623A6814 for <opsawg@core3.amsl.com>; Thu, 19 Aug 2010 03:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.35
X-Spam-Level:
X-Spam-Status: No, score=-102.35 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, NO_RELAYS=-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 l-g1eDEVqegb for <opsawg@core3.amsl.com>; Thu, 19 Aug 2010 03:55:05 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 4731E3A6784 for <opsawg@ietf.org>; Thu, 19 Aug 2010 03:55:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5F394E0656; Thu, 19 Aug 2010 03:55:40 -0700 (PDT)
To: ietf@ellisonsoftware.com, rnatale@mitre.org, dromasca@avaya.com, rbonica@juniper.net, sob@harvard.edu, chris@cw.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20100819105540.5F394E0656@rfc-editor.org>
Date: Thu, 19 Aug 2010 03:55:40 -0700
X-Mailman-Approved-At: Thu, 19 Aug 2010 03:57:11 -0700
Cc: ah@TR-Sys.de, opsawg@ietf.org, rfc-editor@rfc-editor.org
Subject: [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: Thu, 19 Aug 2010 10:55:07 -0000

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&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