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

Alice Russo <arusso@amsl.com> Mon, 14 July 2014 14:01 UTC

Return-Path: <arusso@amsl.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 C4CB61A0454 for <ipcdn@ietfa.amsl.com>; Mon, 14 Jul 2014 07:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 vlW-t6e6SWTG for <ipcdn@ietfa.amsl.com>; Mon, 14 Jul 2014 07:01:17 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4C11A043D for <ipcdn@ietf.org>; Mon, 14 Jul 2014 07:01:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A13241E41C8; Mon, 14 Jul 2014 07:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNKY-jMMXW1y; Mon, 14 Jul 2014 07:00:18 -0700 (PDT)
Received: from alices-mbp.home (pool-68-238-162-118.washdc.fios.verizon.net [68.238.162.118]) by c8a.amsl.com (Postfix) with ESMTPSA id A42841E1890; Mon, 14 Jul 2014 07:00:17 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <4DAB9614-4224-4A0C-8E68-1672B0A64572@cable.comcast.com>
Date: Mon, 14 Jul 2014 10:01:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <553B7724-56A5-4D4D-AAB5-E1953443292A@amsl.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> <4DAB9614-4224-4A0C-8E68-1672B0A64572@cable.comcast.com>
To: Mark Ellison <ellison@ieee.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipcdn/ZjtTpwL9R8V8zaFm0dDIFivxtlc
X-Mailman-Approved-At: Mon, 14 Jul 2014 08:16:22 -0700
Cc: "ipcdn@ietf.org" <ipcdn@ietf.org>, "joelja@bogus.com" <joelja@bogus.com>, "jf.mule@cablelabs.com" <jf.mule@cablelabs.com>, Michael StJohns <mstjohns@comcast.net>, "bclaise@cisco.com" <bclaise@cisco.com>, "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, RFC Editor <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: Mon, 14 Jul 2014 14:01:23 -0000

Greetings,

With AD approval, Errata ID 334 has been corrected as indicated: 
http://www.rfc-editor.org/errata_search.php?eid=334

Errata ID 4048 has been removed from the system because it was an erratum for an erratum. (In the future, please direct corrections to existing errata to rfc-editor@rfc-editor.org.)

Thank you.
RFC Editor/ar

On Jul 12, 2014, at 10:44 AM, Woundy, Richard <Richard_Woundy@cable.comcast.com>; wrote:

> Wow. I don't even remember why I submitted that errata, 13 years ago. And I left Cisco (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>; 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>; 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>; 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>;
>>> >
>>> >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
>>> >https://www.ietf.org/mailman/listinfo/ipcdn
>>> 
>>> 
>>> 
>>> 
>>>