Re: [OPSAWG] [Technical Errata Reported] RFC5935 (2477)
Mark Ellison <ellison@ieee.org> Sat, 21 August 2010 15:45 UTC
Return-Path: <mark@ellisonsoftware.com>
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 D3C953A6808 for <opsawg@core3.amsl.com>; Sat, 21 Aug 2010 08:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.976
X-Spam-Level:
X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 wkemlvYRWcnS for <opsawg@core3.amsl.com>; Sat, 21 Aug 2010 08:45:04 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 01DAC3A687E for <opsawg@ietf.org>; Sat, 21 Aug 2010 08:45:03 -0700 (PDT)
Received: by vws10 with SMTP id 10so4357748vws.31 for <opsawg@ietf.org>; Sat, 21 Aug 2010 08:45:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.88.84 with SMTP id z20mr1787871vcl.92.1282405537480; Sat, 21 Aug 2010 08:45:37 -0700 (PDT)
Sender: mark@ellisonsoftware.com
Received: by 10.220.202.13 with HTTP; Sat, 21 Aug 2010 08:45:37 -0700 (PDT)
In-Reply-To: <20100819105540.5F394E0656@rfc-editor.org>
References: <20100819105540.5F394E0656@rfc-editor.org>
Date: Sat, 21 Aug 2010 11:45:37 -0400
X-Google-Sender-Auth: AdYSFKANxs0LfNIq6kweRi2IVL4
Message-ID: <AANLkTi=w8EXnLZA-yeUz+ap4fazNc4j_VxbXcK+6T+L-@mail.gmail.com>
From: Mark Ellison <ellison@ieee.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="0016e6441efe84ff1c048e574e24"
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)
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: Sat, 21 Aug 2010 15:45:09 -0000
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&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 >
- [OPSAWG] [Technical Errata Reported] RFC5935 (247… RFC Errata System
- Re: [OPSAWG] [Technical Errata Reported] RFC5935 … Mark Ellison
- Re: [OPSAWG] [Technical Errata Reported] RFC5935 … Romascanu, Dan (Dan)
- Re: [OPSAWG] [Technical Errata Reported] RFC5935 … David Harrington
- Re: [OPSAWG] [Technical Errata Reported] RFC5935 … Mark Ellison