RE: [ipcdn] Problems in XML source of Cable Device MIB, Draft 09
"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Wed, 06 July 2005 21:26 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqHPM-00025G-46; Wed, 06 Jul 2005 17:26:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqHPK-000214-CQ for ipcdn@megatron.ietf.org; Wed, 06 Jul 2005 17:26:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00271 for <ipcdn@ietf.org>; Wed, 6 Jul 2005 17:26:12 -0400 (EDT)
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqHqN-0006ox-TQ for ipcdn@ietf.org; Wed, 06 Jul 2005 17:54:12 -0400
Received: from ([10.20.9.174]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH3.11989345; Wed, 06 Jul 2005 17:25:52 -0400
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by PACDCEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 6 Jul 2005 17:25:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ipcdn] Problems in XML source of Cable Device MIB, Draft 09
Date: Wed, 06 Jul 2005 17:25:51 -0400
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73807325@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: [ipcdn] Problems in XML source of Cable Device MIB, Draft 09
Thread-Index: AcV5RRg16zTj90DAThaLfqdedj3OTQJJ2CHg
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, Marez Kevin-MGI1375 <Kevin.Marez@motorola.com>
X-OriginalArrivalTime: 06 Jul 2005 21:25:51.0637 (UTC) FILETIME=[48ED8C50:01C58271]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1c0c3d540ad9f95212b1c2a9a2cc2595
Content-Transfer-Encoding: quoted-printable
Cc: ipcdn@ietf.org
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=subscribe>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org
Randy, The comments in your six emails (below is the first one I received) look very reasonable. I would like to post a revised draft that addresses all of your comments before the July 18th cut-off. Kevin, can we talk about how we would do this in an offline discussion? I think the WG needs to discuss which deprecated groups should be included in the docsDevCmCompliance and docsDevCmtsCompliance statement (if any). In my opinion, some (if not all) of the deprecated groups need to be implemented on CMs and CMTSs for backwards compatibility with various cable OSS systems... but maybe cable operators are ready to drop support for some of these deprecated groups, and this draft should reflect that. I have oonly a few minor reactions to your other comments, that I will address over the next few days. For example, with respect to docsDevNmAccessTable, according to DOCSIS a cable modem may boot in a mode where SNMP Coexistence mode is disabled, but the same cable modem may boot in a mode where SNMP Coexistance mode or SNMPv3 management is enabled, depending on the boot parameters received. -- Rich -----Original Message----- From: ipcdn-bounces@ietf.org [mailto:ipcdn-bounces@ietf.org] On Behalf Of Randy Presuhn Sent: Saturday, June 25, 2005 1:15 AM To: Ipcdn (E-mail) Subject: [ipcdn] Problems in XML source of Cable Device MIB, Draft 09 Hi Rich - > From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com> > To: "Randy Presuhn" <randy_presuhn@mindspring.com> > Sent: Friday, June 24, 2005 11:51 AM > Subject: RE: [ipcdn] Cable Device MIB, Draft 09 released > > Thanks! I attached the XML version, which might help slightly. ... I tried Bill Fenner's tool on it, and got quite a few diagnostics. Background by Bill: Another tool that is worth running on the xml source before using xml2rfc on it is at http://rtg.ietf.org/~fenner/ietf/xml2rfc-valid/ ; it will check that the source is well-formed and valid according to the DTD (XML generated outside of a validating editor is often not valid, and sometimes even not well-formed, even though xml2rfc creates a fine-looking document from it), and also checks for various other errors including the IPR requested. The warnings are mostly due to inappropriate characters (like spaces or periods) in things like xref targets and anchors. Clear those up, and you'll know whether the complaints about unreferenced references are real. These aren't terribly critical, as far as I'm concerned, but it's probably good housekeeping to take care of them now, since it would be one less potential source of error during final RFC editing. The messages I received were: Validation results for C:\My Documents\draft-ietf-ipcdn-device-mibv2-09.xml Processing... Validating document... 193: element xref: validity error : Syntax of value for attribute target of xref is not valid 192: "Data-Over-Cable Service Interface Specification". A term referring to the 193: ITU-T J.112 <xref target="ITU-T J.112" /> 194: Annex B standard for cable modem systems. <xref target="RFI1.0" /> 212: element section: validity error : Syntax of value for attribute anchor of section is not valid 211: 212: <section anchor="mac packet" title="Media Access Control (MAC) Packet"> 213: <t> 4061: element reference: validity error : Syntax of value for attribute anchor of reference is not valid 4060: 4061: <reference anchor="ITU-T J.112" target="http://www.itu.int/ITU-T/studygroups/com09/"> 4062: <front> ...validation failed Performing additional checks... 142: fyi: anchor framework not referenced 141: 142: <section anchor="framework" title="The Internet-Standard Management Framework"> 143: <t> 159: fyi: anchor glossary not referenced 158: 159: <section anchor="glossary" title="Glossary"> 160: <t> 165: fyi: anchor catv not referenced 164: </t> 165: <section anchor="catv" title="CATV"> 166: <t> 173: fyi: anchor cm not referenced 172: 173: <section anchor="cm" title="CM or Cable Modem"> 174: <t> 180: fyi: anchor cmts not referenced 179: 180: <section anchor="cmts" title="CMTS or Cable Modem Termination System"> 181: <t> 190: fyi: anchor docsis not referenced 189: 190: <section anchor="docsis" title="DOCSIS or Data-Over-Cable Service Interface Specification"> 191: <t> 199: fyi: anchor downstream not referenced 198: 199: <section anchor="downstream" title="Downstream"> 200: <t> 205: fyi: anchor head-end not referenced 204: 205: <section anchor="head-end" title="Head-end"> 206: <t> 212: fyi: anchor mac packet not referenced 211: 212: <section anchor="mac packet" title="Media Access Control (MAC) Packet"> 213: <t> 218: fyi: anchor rf not referenced 217: 218: <section anchor="rf" title="RF"> 219: <t> 224: fyi: anchor snmp not referenced 223: 224: <section anchor="snmp" title="Simple Network Management Protocol (SNMP)"> 225: <t> 232: fyi: anchor upstream not referenced 231: 232: <section anchor="upstream" title="Upstream"> 233: <t> 240: fyi: anchor introduction not referenced 239: 240: <section anchor="introduction" title="Introduction"> 241: <t> 263: fyi: anchor mibstructure not referenced 262: 263: <section anchor="mibstructure" title="Structure of the MIB"> 264: <t> 308: fyi: anchor ipv4 not referenced 307: 308: <section anchor="ipv4" title="IPv4 Compliance"> 309: <t> 321: fyi: anchor management not referenced 320: 321: <section anchor="management" title="Management requirements"> 322: 323: fyi: anchor upgrades not referenced 322: 323: <section anchor="upgrades" title="Handling of Software upgrades"> 324: <t> 366: fyi: anchor events not referenced 365: 366: <section anchor="events" title="Events and Notifications"> 367: <t> 380: fyi: anchor throttling not referenced 379: 380: <section anchor="throttling" title="Notification Throttling"> 381: <t> 388: fyi: anchor ratethrottling not referenced 387: 388: <section anchor="ratethrottling" title="Notification rate throttling"> 389: <t> 409: fyi: anchor limitingrate not referenced 408: 409: <section anchor="limitingrate" title="Limiting the notification rate"> 410: <t> 430: fyi: anchor protocolfilters not referenced 429: 430: <section anchor="protocolfilters" title="Protocol Filters"> 431: <t> 451: error: <figure> inside <t> is deprecated by rfc2629bis 450: filters. 451: <figure anchor="filterfigure"> 452: <artwork> 491: fyi: anchor inboundllcfilters not referenced 490: 491: <section anchor="inboundllcfilters" title="Inbound LLC Filters - docsDevFilterLLCTable"> 492: <t> 506: fyi: anchor specialfilters not referenced 505: 506: <section anchor="specialfilters" title="Special Filters"> 507: <t> 513: fyi: anchor spoofingfilters not referenced 512: 513: <section anchor="spoofingfilters" title="IP Spoofing Filters - docsDevCpeTable, docsDevCpeInetTable"> 514: <t> 540: fyi: anchor snmpfilters not referenced 539: 540: <section anchor="snmpfilters" title="SNMP Access Filters - docsDevNmAccessTable"> 541: <t> 559: fyi: anchor ipfilters not referenced 558: 559: <section anchor="ipfilters" title="IP Filtering - docsDevFilterIpTable"> 560: <t> 609: fyi: anchor outboundllcfilters not referenced 608: 609: <section anchor="outboundllcfilters" title="Outbound LLC Filters"> 610: <t> 624: fyi: anchor definitions not referenced 623: 624: <section anchor="definitions" title="Definitions"> 625: <t> 626: error: <figure> inside <t> is deprecated by rfc2629bis 625: <t> 626: <figure> 627: <artwork><![CDATA[ 3776: fyi: anchor acknowledgments not referenced 3775: 3776: <section anchor="acknowledgments" title="Acknowledgments"> 3777: <t> 3790: fyi: anchor revisions not referenced 3789: 3790: <section anchor="revisions" title="Revision Descriptions"> 3791: <t> 3829: fyi: anchor securityconsiderations not referenced 3828: 3829: <section anchor="securityconsiderations" title="Security Considerations"> 3830: <t> 3: warning: anchor RFC2863 not referenced 2: <?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?> 3: <?rfc toc="yes" ?> 4: <?rfc symrefs="yes" ?> 3: fyi: anchor RFC3014 referred to in plain text as [RFC3014] 2: <?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?> 3: <?rfc toc="yes" ?> 4: <?rfc symrefs="yes" ?> 3: warning: anchor RFC3411 not referenced 2: <?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?> 3: <?rfc toc="yes" ?> 4: <?rfc symrefs="yes" ?> 3: fyi: anchor RFC3413 referred to in plain text as [RFC3413] 2: <?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?> 3: <?rfc toc="yes" ?> 4: <?rfc symrefs="yes" ?> 3: warning: anchor RFC3617 not referenced 2: <?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?> 3: <?rfc toc="yes" ?> 4: <?rfc symrefs="yes" ?> 4084: warning: anchor OSSI1.1 not referenced 4083: 4084: <reference anchor="OSSI1.1" target="http://www.cablemodem.com/specifications/"> 4085: <front> 4095: warning: anchor OSSI2.0 not referenced 4094: 4095: <reference anchor="OSSI2.0" target="http://www.cablemodem.com/specifications/"> 4096: <front> ...done Randy _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn
- [ipcdn] Problems in XML source of Cable Device MI… Randy Presuhn
- [ipcdn] idnits and smilint on Cable Device MIB Dr… Randy Presuhn
- RE: [ipcdn] Problems in XML source of Cable Devic… Woundy, Richard
- Re: [ipcdn] Problems in XML source of Cable Devic… Randy Presuhn
- RE: [ipcdn] Problems in XML source of Cable Devic… Woundy, Richard
- Re: [ipcdn] Problems in XML source of Cable Devic… Randy Presuhn