Re: [Technical Errata Reported] RFC3083 (4048)
Mark Ellison <[email protected]> Sat, 12 Jul 2014 07:55:50 -0400
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <CABfCB8qoiuAY144E_Vb91y=izfOdifP_9JcRrtQ=ovqw3w3B3g@mail.gmail.com> |
--===============2288238519268143318==
Content-Type: multipart/alternative; boundary=001a11330bea3b03c804fdfdbdfc
--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 <[email protected]>
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 <[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
>
>
>
--001a11330bea3b03c804fdfdbdfc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>Hi Guys,<br><br></div>Thanks for your reply=
.<br><br>My submission is in regard to the docsBpiCmAuthState object.=C2=A0=
If you look at the technical errata submitted here: <a href=3D"http://www.=
rfc-editor.org/errata_search.php?rfc=3D3083">http://www.rfc-editor.org/erra=
ta_search.php?rfc=3D3083</a>=C2=A0 then you will see the comma is clearly o=
mitted from the 'fixed' text:<br>
<br><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb=
(204,204,204);padding-left:1ex" class=3D"gmail_quote">It should say:<br><br=
>=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 {<br>
<br>=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)<br>=
=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),<br>=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),<br>=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),<br>=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)<br>
</blockquote><br><br></div>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!<br><br></div>Regards,<br><br>Mark<br><div class=3D"gmail_ext=
ra">
<br><br><div class=3D"gmail_quote">On Fri, Jul 11, 2014 at 7:34 PM, Michael=
StJohns <span dir=3D"ltr"><<a href=3D"mailto:[email protected]" targ=
et=3D"_blank">[email protected]</a>></span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
What a blast from the past.<br>
<br>
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.<br>
<br>
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.=
<br>
<br>
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.<br>
<br>
Mike<br>
<div><div class=3D"h5"><br>
<br>
<br>
At 11:02 AM 7/11/2014, RFC Errata System wrote:<br>
>The following errata report has been submitted for RFC3083,<br>
>"Baseline Privacy Interface Management Information Base for DOCSIS=
Compliant Cable Modems and Cable Modem Termination Systems".<br>
><br>
>--------------------------------------<br>
>You may review the report below and at:<br>
><a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D3083&e=
id=3D4048" target=3D"_blank">http://www.rfc-editor.org/errata_search.php?rf=
c=3D3083&eid=3D4048</a><br>
><br>
>--------------------------------------<br>
>Type: Technical<br>
>Reported by: Mark Ellison <<a href=3D"mailto:[email protected]">ellis=
[email protected]</a>><br>
><br>
>Section: 4<br>
><br>
>Original Text<br>
>-------------<br>
>start(1)<br>
><br>
>Corrected Text<br>
>--------------<br>
>start(1),<br>
><br>
>Notes<br>
>-----<br>
>errata # 334 for RFC3083 omits the necessary comma at the end of the in=
serted line 'start(1)'<br>
><br>
>Instructions:<br>
>-------------<br>
>This errata is currently posted as "Reported". If necessary, =
please<br>
>use "Reply All" to discuss whether it should be verified or<b=
r>
>rejected. When a decision is reached, the verifying party (IESG)<br>
>can log in to change the status and edit the report, if necessary.<br>
><br>
>--------------------------------------<br>
>RFC3083 (draft-ietf-ipcdn-mcns-bpi-mib-02)<br>
>--------------------------------------<br>
>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<br>
>Publication Date =C2=A0 =C2=A0: March 2001<br>
>Author(s) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : R. Woundy<br>
>Category =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: INFORMATIONAL<br>
>Source =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IP over Cable =
Data Network<br>
>Area =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Operation=
s and Management<br>
>Stream =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IETF<br>
>Verifying Party =C2=A0 =C2=A0 : IESG<br>
><br>
</div></div>>_______________________________________________<br>
>IPCDN mailing list<br>
><a href=3D"mailto:[email protected]">[email protected]</a><br>
><a href=3D"https://www.ietf.org/mailman/listinfo/ipcdn" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ipcdn</a><br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><br></div></div>
--001a11330bea3b03c804fdfdbdfc--
--===============2288238519268143318==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
IPCDN mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipcdn
--===============2288238519268143318==--