Re: [Technical Errata Reported] RFC3083 (4048)

Michael StJohns <[email protected]> Fri, 11 Jul 2014 19:34:58 -0400
Newsgroups gmane.ietf.ipcdn
Message-ID <[email protected]>
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 <[email protected]>
>
>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
>[email protected]
>https://www.ietf.org/mailman/listinfo/ipcdn