Re: [ipcdn] [Technical Errata Reported] RFC3083 (4048)

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Sat, 12 July 2014 14:44 UTC

Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: ipcdn@ietfa.amsl.com
Delivered-To: ipcdn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD701B2A81 for <ipcdn@ietfa.amsl.com>; Sat, 12 Jul 2014 07:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.484
X-Spam-Level:
X-Spam-Status: No, score=-3.484 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Si_873CBRQTt for <ipcdn@ietfa.amsl.com>; Sat, 12 Jul 2014 07:44:37 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 810CD1B2A80 for <ipcdn@ietf.org>; Sat, 12 Jul 2014 07:44:37 -0700 (PDT)
Received: from ([24.40.56.116]) by copdcavout01.cable.comcast.com with ESMTP id C7WM3M1.143129217; Sat, 12 Jul 2014 08:44:30 -0600
Received: from PACDCEXMB01.cable.comcast.com ([169.254.1.114]) by PACDCEXHUB03.cable.comcast.com ([fe80::7da6:458a:eadf:dadb%16]) with mapi id 14.03.0181.006; Sat, 12 Jul 2014 10:44:30 -0400
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: Michael StJohns <mstjohns@comcast.net>, Mark Ellison <ellison@ieee.org>
Thread-Topic: [ipcdn] [Technical Errata Reported] RFC3083 (4048)
Thread-Index: AQHPncg5/PmoJihoXEubxsy/wm+7IZucsg+A///R8lE=
Date: Sat, 12 Jul 2014 14:44:29 +0000
Message-ID: <4DAB9614-4224-4A0C-8E68-1672B0A64572@cable.comcast.com>
References: <20140711150259.3A1F7180201@rfc-editor.org> <53c07499.e149320a.1e0e.2b68SMTPIN_ADDED_MISSING@mx.google.com> <CABfCB8qoiuAY144E_Vb91y=izfOdifP_9JcRrtQ=ovqw3w3B3g@mail.gmail.com>, <8721294E-3582-48B7-B725-C411BB2D321A@comcast.net>
In-Reply-To: <8721294E-3582-48B7-B725-C411BB2D321A@comcast.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_4DAB961442244A0C8E681672B0A64572cablecomcastcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipcdn/AXqPl3Wh8kwDYz1ZHp_2t8v0bJs
Cc: "ipcdn@ietf.org" <ipcdn@ietf.org>, "joelja@bogus.com" <joelja@bogus.com>, "jf.mule@cablelabs.com" <jf.mule@cablelabs.com>, "bclaise@cisco.com" <bclaise@cisco.com>, "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [ipcdn] [Technical Errata Reported] RFC3083 (4048)
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipcdn/>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jul 2014 14:44:41 -0000

Wow. I don't even remember why I submitted that errata, 13 years ago. And I left Cisco (rwoundy@cisco.com<mailto:rwoundy@cisco.com>) 12 years ago.

In any case, I agree with this submission.

-- Rich

On Jul 12, 2014, at 9:29 AM, "Michael StJohns" <mstjohns@comcast.net<mailto:mstjohns@comcast.net>> wrote:

Ok.  That makes sense.  I didn't realize Rich had posted an errata.  The "start" is extraneous but harmless, but does need the comma if present.  Mike

Sent from my iPad

On Jul 12, 2014, at 7:55, Mark Ellison <ellison@ieee.org<mailto:ellison@ieee.org>> wrote:

Hi Guys,

Thanks for your reply.

My submission is in regard to the docsBpiCmAuthState object.  If you look at the technical errata submitted here: http://www.rfc-editor.org/errata_search.php?rfc=3083  then you will see the comma is clearly omitted from the 'fixed' text:

It should say:

   docsBpiCmAuthState      OBJECT-TYPE
   SYNTAX                  INTEGER {

                                   start(1)
                                   authWait(2),
                                   authorized(3),
                                   reauthWait(4),
                                   authRejectWait(5)


Maybe what you are saying is that the above fix is not required?  If so, it is misleading...and either way, syntactically incorrect!

Regards,

Mark


On Fri, Jul 11, 2014 at 7:34 PM, Michael StJohns <mstjohns@comcast.net<mailto:mstjohns@comcast.net>> wrote:
What a blast from the past.

This is "not an error" , at least as reported.  Three are two places this error might have been reported from - the definition of  docsBpiCmAuthState and  the definition o fdocsBpiCmTEKState.  The former -  I believe correctly -does not include "start (1)" as one of its states.  The latter has "start (1),"  - e.g. including the comma.  So I'm not sure where he's actually seeing the error.

The  MIB  was verified at submission.  I would be surprised if there are any obvious syntactic errors like this in the body of the MIB.

If I remember correctly, the reason the "start" state was excluded from the docsBpiCmAuthState enums is that its never a visible state - the state machine doesn't actually exist until docsIfCmStatusValue is at least todEstablished - (RFC4546) and the state would always be later than "start" so any query about baseline privacy will not necessarily give you valid information prior to todEstablished.

Mike



At 11:02 AM 7/11/2014, RFC Errata System wrote:
>The following errata report has been submitted for RFC3083,
>"Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems".
>
>--------------------------------------
>You may review the report below and at:
>http://www.rfc-editor.org/errata_search.php?rfc=3083&eid=4048
>
>--------------------------------------
>Type: Technical
>Reported by: Mark Ellison <ellison@ieee.org<mailto:ellison@ieee.org>>
>
>Section: 4
>
>Original Text
>-------------
>start(1)
>
>Corrected Text
>--------------
>start(1),
>
>Notes
>-----
>errata # 334 for RFC3083 omits the necessary comma at the end of the inserted line 'start(1)'
>
>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.
>
>--------------------------------------
>RFC3083 (draft-ietf-ipcdn-mcns-bpi-mib-02)
>--------------------------------------
>Title               : Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems
>Publication Date    : March 2001
>Author(s)           : R. Woundy
>Category            : INFORMATIONAL
>Source              : IP over Cable Data Network
>Area                : Operations and Management
>Stream              : IETF
>Verifying Party     : IESG
>
>_______________________________________________
>IPCDN mailing list
>IPCDN@ietf.org<mailto:IPCDN@ietf.org>
>https://www.ietf.org/mailman/listinfo/ipcdn