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

Michael StJohns <> Fri, 11 July 2014 23:34 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id EB5D81A0070 for <>; Fri, 11 Jul 2014 16:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.154
X-Spam-Status: No, score=-2.154 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MISSING_MID=0.497, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dUOhv12g66Vu for <>; Fri, 11 Jul 2014 16:34:49 -0700 (PDT)
Received: from ( [IPv6:2001:558:fe14:43:76:96:62:48]) by (Postfix) with ESMTP id 237D81A005B for <>; Fri, 11 Jul 2014 16:34:49 -0700 (PDT)
Received: from ([]) by with comcast id RBM51o0061ap0As55Baonr; Fri, 11 Jul 2014 23:34:48 +0000
Received: from ([]) by with comcast id RBao1o0064D0RQL3iBaowf; Fri, 11 Jul 2014 23:34:48 +0000
X-Mailer: QUALCOMM Windows Eudora Version
Date: Fri, 11 Jul 2014 19:34:58 -0400
To: RFC Errata System <>,,,,,
From: Michael StJohns <>
In-Reply-To: <>
References: <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=q20140121; t=1405121688; bh=VFmJ/2JP9SJLe0XH8Bm5/9gIaliNtWkeGIkxH6JE4uE=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=Meat+SCGfhnoNije/4cuVa+B24Jhxp593PZOtfcBNVXk7FCagC/tSiqEbQ3+EvCyN NXwNfi/D49R91eAzEWcsYRYaZhUrUuNGGJniDA6vve4Q16c3k60R7ohIYyZPhHThnQ tl0UJY7tbnF63hBj+jQm25pfmkYKxaaAa5UYJlmTwjyw26piWEB0hZEmk8T+WwIXOn 7rG1DgsrNWB9vkfl2T3aceS0u+lfc03D0X9ahjRCe3vRdb8/LflTG8nb8BEdPL3Udt DWpmIxaEPXRhFdyWRND9GL9wVq14NGrHoaMzjjDVFsHZILQxde8fUsT06mIDpZ65sd yLnIHqGNlwy2A==
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: Fri, 11 Jul 2014 23:34:51 -0000
Message-ID: <>

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