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

Mark Ellison <ellison@ieee.org> Sat, 12 July 2014 11:55 UTC

Return-Path: <mark@ellisonsoftware.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 22F651B285A for <ipcdn@ietfa.amsl.com>; Sat, 12 Jul 2014 04:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 hHAHHteN9UYe for <ipcdn@ietfa.amsl.com>; Sat, 12 Jul 2014 04:55:51 -0700 (PDT)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0386C1B2854 for <ipcdn@ietf.org>; Sat, 12 Jul 2014 04:55:50 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id uy5so2169225obc.11 for <ipcdn@ietf.org>; Sat, 12 Jul 2014 04:55:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellisonsoftware.com; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2V3ftgZQwNAe8Cvhkuo/+zoqmxllOwgUcmzad6m4Sxc=; b=aZrD/y3Ge4W3ZZIqqty+YN6oNh5RFp+HCCZUpSptsdo1QL5tpiD3hijqrgvb9C98zJ 0C95rUo9EvS4UNptbDcJ6WTYKFetT855pkBtlTRJeAdwjfuqBY8SxqeV4jogYiwbYnuL 9ghxZi0Kz/RDCAYKR4V3Jyl1n0Gh4onliydvw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=2V3ftgZQwNAe8Cvhkuo/+zoqmxllOwgUcmzad6m4Sxc=; b=EXxd667D3fYCQlj0Wd0h7Yrfva05X1XTmG775Kuh8pQs8N2bTeOR8CinwQZvHDpqdE 5gOywEOKzbPRi9VEpzsdptnV3QYDluYcg4b+wOV0LA736xiVgw9AhW6IH1ixxywaqZNS vpYYKfLqzGTuqkvP4MO7WSDkoQf99kyS+saDEN9lhOX3bkz+c/uJyxio+tzkV1ADuRPD e9Z0HUnJiK68+effxwa7VcbYGWzk/O6y0s11oOCWVbfXfjFOYhrMWmJs/5CJ/cEAgkxN xfeksy0uUruBOplzxLa9vZO6oywi9mXl3SSYWc2x/LUk98zSR6VbGR3BapU9DogPqjDi GnIw==
X-Gm-Message-State: ALoCoQn9TAjGF386bpZ6YF3ZUkUNQD8CI4GC9POqNYcHQ2B44eOFy5otRs4dsT6LuOZ2cDcnWCVz
MIME-Version: 1.0
X-Received: by 10.60.52.35 with SMTP id q3mr5508789oeo.79.1405166150150; Sat, 12 Jul 2014 04:55:50 -0700 (PDT)
Sender: mark@ellisonsoftware.com
Received: by 10.202.54.7 with HTTP; Sat, 12 Jul 2014 04:55:50 -0700 (PDT)
In-Reply-To: <53c07499.e149320a.1e0e.2b68SMTPIN_ADDED_MISSING@mx.google.com>
References: <20140711150259.3A1F7180201@rfc-editor.org> <53c07499.e149320a.1e0e.2b68SMTPIN_ADDED_MISSING@mx.google.com>
Date: Sat, 12 Jul 2014 07:55:50 -0400
X-Google-Sender-Auth: 2WULcvkIye8Cqr19PCNPdFOP3N4
Message-ID: <CABfCB8qoiuAY144E_Vb91y=izfOdifP_9JcRrtQ=ovqw3w3B3g@mail.gmail.com>
From: Mark Ellison <ellison@ieee.org>
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: multipart/alternative; boundary=001a11330bea3b03c804fdfdbdfc
Archived-At: http://mailarchive.ietf.org/arch/msg/ipcdn/nathuQyb8BWE0qjYmgKliDPJ008
Cc: ipcdn@ietf.org, joelja@bogus.com, jf.mule@cablelabs.com, rwoundy@cisco.com, bclaise@cisco.com, 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 11:55:53 -0000

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
>
>
>