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

"Woundy, Richard" <> Sat, 12 July 2014 14:44 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BCD701B2A81 for <>; Sat, 12 Jul 2014 07:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.484
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Si_873CBRQTt for <>; Sat, 12 Jul 2014 07:44:37 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 810CD1B2A80 for <>; Sat, 12 Jul 2014 07:44:37 -0700 (PDT)
Received: from ([]) by with ESMTP id C7WM3M1.143129217; Sat, 12 Jul 2014 08:44:30 -0600
Received: from ([]) by ([fe80::7da6:458a:eadf:dadb%16]) with mapi id 14.03.0181.006; Sat, 12 Jul 2014 10:44:30 -0400
From: "Woundy, Richard" <>
To: Michael StJohns <>, Mark Ellison <>
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: <>
References: <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_4DAB961442244A0C8E681672B0A64572cablecomcastcom_"
MIME-Version: 1.0
Cc: "" <>, "" <>, "" <>, "" <>, "Woundy, Richard" <>, RFC Errata System <>
Subject: Re: [ipcdn] [Technical Errata Reported] RFC3083 (4048)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IP over Cable Data Network <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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 (<>) 12 years ago.

In any case, I agree with this submission.

-- Rich

On Jul 12, 2014, at 9:29 AM, "Michael StJohns" <<>> 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 <<>> 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:  then you will see the comma is clearly omitted from the 'fixed' text:

It should say:

   docsBpiCmAuthState      OBJECT-TYPE
   SYNTAX                  INTEGER {


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



On Fri, Jul 11, 2014 at 7:34 PM, Michael StJohns <<>> 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.


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:
>Type: Technical
>Reported by: Mark Ellison <<>>
>Section: 4
>Original Text
>Corrected Text
>errata # 334 for RFC3083 omits the necessary comma at the end of the inserted line 'start(1)'
>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