From nobody Fri Jul 11 08:04:00 2014 Return-Path: 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 488BE1B2B51 for ; Fri, 11 Jul 2014 08:03:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.553 X-Spam-Level: X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 bp5iUn8J8TpZ for ; Fri, 11 Jul 2014 08:03:35 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id EB5B31B2B6A for ; Fri, 11 Jul 2014 08:03:35 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 3A1F7180201; Fri, 11 Jul 2014 08:02:59 -0700 (PDT) To: rwoundy@cisco.com, bclaise@cisco.com, joelja@bogus.com, jf.mule@cablelabs.com, Richard_Woundy@cable.comcast.com X-PHP-Originating-Script: 6000:errata_mail_lib.php From: RFC Errata System Message-Id: <20140711150259.3A1F7180201@rfc-editor.org> Date: Fri, 11 Jul 2014 08:02:59 -0700 (PDT) Archived-At: http://mailarchive.ietf.org/arch/msg/ipcdn/U_D2Gj_W5uVnNOKHo5YHWStTwvg Cc: ipcdn@ietf.org, ellison@ieee.org, rfc-editor@rfc-editor.org Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2014 15:03:55 -0000 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 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 From nobody Fri Jul 11 16:34:53 2014 Return-Path: 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 EB5D81A0070 for ; Fri, 11 Jul 2014 16:34:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.154 X-Spam-Level: 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dUOhv12g66Vu for ; Fri, 11 Jul 2014 16:34:49 -0700 (PDT) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 237D81A005B for ; Fri, 11 Jul 2014 16:34:49 -0700 (PDT) Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta05.westchester.pa.mail.comcast.net with comcast id RBM51o0061ap0As55Baonr; Fri, 11 Jul 2014 23:34:48 +0000 Received: from Mike-T530ssd.comcast.net ([68.34.113.195]) by omta22.westchester.pa.mail.comcast.net with comcast id RBao1o0064D0RQL3iBaowf; Fri, 11 Jul 2014 23:34:48 +0000 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 11 Jul 2014 19:34:58 -0400 To: RFC Errata System ,rwoundy@cisco.com, bclaise@cisco.com,joelja@bogus.com,jf.mule@cablelabs.com, Richard_Woundy@cable.comcast.com From: Michael StJohns In-Reply-To: <20140711150259.3A1F7180201@rfc-editor.org> References: <20140711150259.3A1F7180201@rfc-editor.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; 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== Archived-At: http://mailarchive.ietf.org/arch/msg/ipcdn/aj2O4UETZ-o1c0eYsanNan5J4rE Cc: ipcdn@ietf.org, ellison@ieee.org, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2014 23:34:51 -0000 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 > >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 From nobody Sat Jul 12 04:55:54 2014 Return-Path: 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 ; 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 ; 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 ; Sat, 12 Jul 2014 04:55:50 -0700 (PDT) Received: by mail-ob0-f180.google.com with SMTP id uy5so2169225obc.11 for ; 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: From: Mark Ellison To: Michael StJohns 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2014 11:55:53 -0000 --001a11330bea3b03c804fdfdbdfc Content-Type: text/plain; charset=UTF-8 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 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 > > > >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 > > > --001a11330bea3b03c804fdfdbdfc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Guys,

Thanks for your reply= .

My submission is in regard to the docsBpiCmAuthState object.=C2=A0= If you look at the technical errata submitted here: http://www.rfc-editor.org/erra= ta_search.php?rfc=3D3083=C2=A0 then you will see the comma is clearly o= mitted from the 'fixed' text:

It should say:
=C2=A0=C2=A0 docsBpiCmAuthState=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 OBJECT-TYPE<= br>=C2=A0=C2=A0 SYNTAX=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 INTEGER {

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


Maybe what you are saying is that the above fix = is not required?=C2=A0 If so, it is misleading...and either way, syntactica= lly 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. =C2=A0Three are tw= o places this error might have been reported from - the definition of =C2= =A0docsBpiCmAuthState and =C2=A0the definition o fdocsBpiCmTEKState. =C2=A0= The former - =C2=A0I believe correctly -does not include "start (1)&qu= ot; as one of its states. =C2=A0The latter has "start (1)," =C2= =A0- e.g. including the comma. =C2=A0So I'm not sure where he's act= ually seeing the error.

The =C2=A0MIB =C2=A0was verified at submission. =C2=A0I 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 exclude= d from the docsBpiCmAuthState enums is that its never a visible state - the= state machine doesn't actually exist until docsIfCmStatusValue is at l= east todEstablished - (RFC4546) and the state would always be later than &q= uot;start" so any query about baseline privacy will not necessarily gi= ve 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?rf= c=3D3083&eid=3D4048
>
>--------------------------------------
>Type: Technical
>Reported by: Mark Ellison <ellis= on@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 in= serted 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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Baseline Priva= cy Interface Management Information Base for DOCSIS Compliant Cable Modems = and Cable Modem Termination Systems
>Publication Date =C2=A0 =C2=A0: March 2001
>Author(s) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : R. Woundy
>Category =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: INFORMATIONAL
>Source =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IP over Cable = Data Network
>Area =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Operation= s and Management
>Stream =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IETF
>Verifying Party =C2=A0 =C2=A0 : IESG
>
>_______________________________________________
>IPCDN mailing list
>IPCDN@ietf.org
>https://www.ietf.org/mailman/listinfo/ipcdn





--001a11330bea3b03c804fdfdbdfc-- From nobody Sat Jul 12 06:29:26 2014 Return-Path: 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 6F0311B2880 for ; Sat, 12 Jul 2014 06:29:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.649 X-Spam-Level: X-Spam-Status: No, score=-2.649 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 XESp-4Ncxzaq for ; Sat, 12 Jul 2014 06:29:23 -0700 (PDT) Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA2B1B2876 for ; Sat, 12 Jul 2014 06:29:23 -0700 (PDT) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta04.westchester.pa.mail.comcast.net with comcast id RRNL1o0011HzFnQ54RVNxv; Sat, 12 Jul 2014 13:29:22 +0000 Received: from [192.168.1.105] ([68.34.113.195]) by omta14.westchester.pa.mail.comcast.net with comcast id RRVK1o00m4D0RQL3aRVLYR; Sat, 12 Jul 2014 13:29:22 +0000 References: <20140711150259.3A1F7180201@rfc-editor.org> <53c07499.e149320a.1e0e.2b68SMTPIN_ADDED_MISSING@mx.google.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-8D77D726-CA02-4E97-9127-E058BCFB799E Content-Transfer-Encoding: 7bit Message-Id: <8721294E-3582-48B7-B725-C411BB2D321A@comcast.net> X-Mailer: iPad Mail (11D257) From: Michael StJohns Date: Sat, 12 Jul 2014 09:29:19 -0400 To: Mark Ellison DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1405171762; bh=9iVwZ1cFv0HlzM4E1FkxnJzbNHUUzxtlfBOSC+1QGDo=; h=Received:Received:Mime-Version:Content-Type:Message-Id:From: Subject:Date:To; b=dGnZVpjOGVWVzDZGQjHYSCZKxUM5Ipra3beD29YB0LRYRnB7EPVopZJRmpop4hnqv YV8himbiOC0jvyPTXM4B67LauhBPLVeDtCmx9z5sZensfTI3006tsvUofcIaF2gC4Z StU6oVQKKOwvY0eAGbWfl6TUHoeKiU28Np9vuKP2Sby8gBhaOLPOSovw0lhVrvdjGh BImhNM4YlpGsxkEfIU7PbhHSxav2SnbPTHN3NswZ3cPqzL7NoHPdZw+wwlGqCsHMHM C1gdA2YWGe1D9f0WWZzUbPQtPkOH65wQTDHOOa2mmMTNzgTzZWVaC1bP0OgZ0OsZ9N 807yIWKQ938FA== Archived-At: http://mailarchive.ietf.org/arch/msg/ipcdn/Uxgbq01OmMFxlOkm7J5kcIOI1Hk 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2014 13:29:25 -0000 --Apple-Mail-8D77D726-CA02-4E97-9127-E058BCFB799E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Ok. That makes sense. I didn't realize Rich had posted an errata. The "st= art" 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: >=20 > Hi Guys, >=20 > Thanks for your reply. >=20 > My submission is in regard to the docsBpiCmAuthState object. If you look a= t the technical errata submitted here: http://www.rfc-editor.org/errata_sear= ch.php?rfc=3D3083 then you will see the comma is clearly omitted from the '= fixed' text: >=20 >> It should say: >>=20 >> docsBpiCmAuthState OBJECT-TYPE >> SYNTAX INTEGER { >>=20 >> start(1) >> authWait(2), >> authorized(3), >> reauthWait(4), >> authRejectWait(5) >=20 >=20 > Maybe what you are saying is that the above fix is not required? If so, i= t is misleading...and either way, syntactically incorrect! >=20 > Regards, >=20 > Mark >=20 >=20 >> On Fri, Jul 11, 2014 at 7:34 PM, Michael StJohns w= rote: >> What a blast from the past. >>=20 >> 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 correctl= y -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 see= ing the error. >>=20 >> The MIB was verified at submission. I would be surprised if there are a= ny obvious syntactic errors like this in the body of the MIB. >>=20 >> If I remember correctly, the reason the "start" state was excluded from t= he docsBpiCmAuthState enums is that its never a visible state - the state ma= chine doesn't actually exist until docsIfCmStatusValue is at least todEstabl= ished - (RFC4546) and the state would always be later than "start" so any qu= ery about baseline privacy will not necessarily give you valid information p= rior to todEstablished. >>=20 >> Mike >>=20 >>=20 >>=20 >> 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 Compl= iant Cable Modems and Cable Modem Termination Systems". >> > >> >-------------------------------------- >> >You may review the report below and at: >> >http://www.rfc-editor.org/errata_search.php?rfc=3D3083&eid=3D4048 >> > >> >-------------------------------------- >> >Type: Technical >> >Reported by: Mark Ellison >> > >> >Section: 4 >> > >> >Original Text >> >------------- >> >start(1) >> > >> >Corrected Text >> >-------------- >> >start(1), >> > >> >Notes >> >----- >> >errata # 334 for RFC3083 omits the necessary comma at the end of the ins= erted 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 B= ase 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 >=20 >=20 >=20 --Apple-Mail-8D77D726-CA02-4E97-9127-E058BCFB799E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Ok.  That makes sense.  I di= dn't realize Rich had posted an errata.  The "start" is extraneous but h= armless, but does need the comma if present.  Mike

Sent from my i= Pad

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

Hi Guys,

T= hanks for your reply.

My submission is in regard to the docsBpiCmAuth= State object.  If you look at the technical errata submitted here: http://www.rf= c-editor.org/errata_search.php?rfc=3D3083  then you will see the co= mma is clearly omitted from the 'fixed' text:

It should say:

&= nbsp;  docsBpiCmAuthState      OBJECT-TYPE
=    SYNTAX         &nb= sp;        INTEGER {

            =             &nbs= p;          start(1)
 &= nbsp;            = ;            &nb= sp;        authWait(2),
  &n= bsp;            =             &nbs= p;       authorized(3),
   &= nbsp;            = ;            &nb= sp;      reauthWait(4),
    =             &nbs= p;            &n= bsp;     authRejectWait(5)


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

Regards,

Mark


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

This is "not an error" , at least as reported.  Three are two places th= is error might have been reported from - the definition of  docsBpiCmAu= thState and  the definition o fdocsBpiCmTEKState.  The former - &n= bsp;I believe correctly -does not include "start (1)" as one of its states. &= nbsp;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 i= f 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 d= ocsBpiCmAuthState enums is that its never a visible state - the state machin= e doesn't actually exist until docsIfCmStatusValue is at least todEstablishe= d - (RFC4546) and the state would always be later than "start" so any query a= bout baseline privacy will not necessarily give you valid information prior t= o 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 Compl= iant Cable Modems and Cable Modem Termination Systems".
>
>--------------------------------------
>You may review the report below and at:
>http://www.rfc-editor.org/errata_search.php?rfc=3D= 3083&eid=3D4048
>
>--------------------------------------
>Type: Technical
>Reported by: Mark Ellison <elliso= n@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 ins= erted 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 Privac= y Interface Management Information Base for DOCSIS Compliant Cable Modems an= d Cable Modem Termination Systems
>Publication Date    : March 2001
>Author(s)           : R. Woundy
>Category            : INFORMATIONAL
>Source              : IP over Cable D= ata Network
>Area                : Operations= and Management
>Stream              : IETF
>Verifying Party     : IESG
>
>_______________________________________________
>IPCDN mailing list
>IPCDN@ietf.org
>https://www.ietf.org/mailman/listinfo/ipcdn





= --Apple-Mail-8D77D726-CA02-4E97-9127-E058BCFB799E-- From nobody Sat Jul 12 07:44:42 2014 Return-Path: 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 ; 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 ; 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 ; 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" 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: <4DAB9614-4224-4A0C-8E68-1672B0A64572@cable.comcast.com> References: <20140711150259.3A1F7180201@rfc-editor.org> <53c07499.e149320a.1e0e.2b68SMTPIN_ADDED_MISSING@mx.google.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" , "joelja@bogus.com" , "jf.mule@cablelabs.com" , "bclaise@cisco.com" , "Woundy, Richard" , RFC Errata System 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2014 14:44:41 -0000 --_000_4DAB961442244A0C8E681672B0A64572cablecomcastcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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" > wrote: Ok. That makes sense. I didn't realize Rich had posted an errata. The "s= tart" 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 a= t the technical errata submitted here: http://www.rfc-editor.org/errata_sea= rch.php?rfc=3D3083 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 > wrote: What a blast from the past. This is "not an error" , at least as reported. Three are two places this e= rror might have been reported from - the definition of docsBpiCmAuthState = and the definition o fdocsBpiCmTEKState. The former - I believe correctl= y -does not include "start (1)" as one of its states. The latter has "star= t (1)," - e.g. including the comma. So I'm not sure where he's actually s= eeing the error. The MIB was verified at submission. I would be surprised if there are an= y 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 mac= hine doesn't actually exist until docsIfCmStatusValue is at least todEstabl= ished - (RFC4546) and the state would always be later than "start" so any q= uery 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 Complia= nt Cable Modems and Cable Modem Termination Systems". > >-------------------------------------- >You may review the report below and at: >http://www.rfc-editor.org/errata_search.php?rfc=3D3083&eid=3D4048 > >-------------------------------------- >Type: Technical >Reported by: Mark Ellison > > >Section: 4 > >Original Text >------------- >start(1) > >Corrected Text >-------------- >start(1), > >Notes >----- >errata # 334 for RFC3083 omits the necessary comma at the end of the inser= ted 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 Ba= se 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 --_000_4DAB961442244A0C8E681672B0A64572cablecomcastcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
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
Ok.  That makes sense.  I didn't realize Rich had posted an = errata.  The "start" is extraneous but harmless, but does ne= ed 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 l= ook at the technical errata submitted here: http://w= ww.rfc-editor.org/errata_search.php?rfc=3D3083  then you will see = the comma is clearly omitted from the 'fixed' text:

It should say:

   docsBpiCmAuthState      OBJECT-TYPE    SYNTAX         &n= bsp;        INTEGER {

            &nb= sp;            =           start(1)
            &nb= sp;            =           authWait(2),
            &nb= sp;            =           authorized(3),
            &nb= sp;            =           reauthWait(4),
            &nb= sp;            =           authRejectWait(5)


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

Regards,

Mark


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

This is "not an error" , at least as reported.  Three are tw= o places this error might have been reported from - the definition of  = ;docsBpiCmAuthState and  the definition o fdocsBpiCmTEKState.  Th= e 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 exclude= d 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 p= rivacy will not necessarily give you valid information prior to todEstablis= hed.

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?rf= c=3D3083&eid=3D4048
>
>--------------------------------------
>Type: Technical
>Reported by: Mark Ellison <ellis= on@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 in= serted 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 Priva= cy 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                : Operation= s and Management
>Stream              : IETF
>Verifying Party     : IESG
>
>_______________________________________________
>IPCDN mailing list
>IPCDN@ietf.org
>https://www.ietf.org/mailman/listinfo/ipcdn





--_000_4DAB961442244A0C8E681672B0A64572cablecomcastcom_-- From nobody Mon Jul 14 08:16:25 2014 Return-Path: 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 ; 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 ; 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 ; 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 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> , <8721294E-3582-48B7-B725-C411BB2D321A@comcast.net> <4DAB9614-4224-4A0C-8E68-1672B0A64572@cable.comcast.com> To: Mark Ellison 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" , "joelja@bogus.com" , "jf.mule@cablelabs.com" , Michael StJohns , "bclaise@cisco.com" , "Woundy, Richard" , RFC Editor 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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:=20 http://www.rfc-editor.org/errata_search.php?eid=3D334 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 = 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. >=20 > In any case, I agree with this submission. >=20 > -- Rich >=20 > On Jul 12, 2014, at 9:29 AM, "Michael StJohns" = wrote: >=20 >> 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 >>=20 >> Sent from my iPad >>=20 >> On Jul 12, 2014, at 7:55, Mark Ellison wrote: >>=20 >>> Hi Guys, >>>=20 >>> Thanks for your reply. >>>=20 >>> 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=3D3083 then you will = see the comma is clearly omitted from the 'fixed' text: >>>=20 >>> It should say: >>>=20 >>> docsBpiCmAuthState OBJECT-TYPE >>> SYNTAX INTEGER { >>>=20 >>> start(1) >>> authWait(2), >>> authorized(3), >>> reauthWait(4), >>> authRejectWait(5) >>>=20 >>>=20 >>> Maybe what you are saying is that the above fix is not required? If = so, it is misleading...and either way, syntactically incorrect! >>>=20 >>> Regards, >>>=20 >>> Mark >>>=20 >>>=20 >>> On Fri, Jul 11, 2014 at 7:34 PM, Michael StJohns = wrote: >>> What a blast from the past. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> Mike >>>=20 >>>=20 >>>=20 >>> 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=3D3083&eid=3D4048 >>> > >>> >-------------------------------------- >>> >Type: Technical >>> >Reported by: Mark Ellison >>> > >>> >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 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20