Reply to OPS directorate comments from Juergen Schoenwaelder

[George Jones <gmj@pobox.com>]

js> ----------------
js> Comments from Juergen Schoenwaelder:
js>
js> With my SNMP background, I was of course puzzled about the requirement
js> to be able to reset counters. I would personally like to have one or
js> two sentences added that such a reset means the display of counters in
js> e.g. a CLI interface but not necessarily the reset of the real
js> physical counters. (In other words, I expect that the CLI takes a
js> snapshot of a counter C at time t and then later displays C(now)-C(t)
js> on the CLI or whatever interface (this is basically what a management
js> application running on top of SNMP would do).)

Does this do it ?

04>      For the purposes of this requirement it would be acceptable for
04>      the system to maintain two counters: an "absolute counter",
04>      C[now], and a "reset" counter, C[reset].  The absolute counter
04>      would maintain counts that increase monotonically until they
04>      wrap or overflow the counter.  The reset counter would receive a
04>      copy of the current value of the absolute counter when the reset
04>      function was issued for that counter. Functions that display or
04>      retrieve the counter could then display the delta (C[now] -
04>      C[reset]).

js>
js> Below are the other comments I wrote down last night - most of them
js> (except the one referring to page 38) are purely editorial and may
js> have already been observed by others.
js>
js> Page 15: RS2323 -> RS232

Fixed.

js>
js> Page 16: I am not really sure that RS 232 interfaces do not need
js> additional software. In fact, without a modem/terminal program, using
js> RS 232 interfaces is kind of hard (of course depends on your OS).

Name me an common OS that does not ship with a terminal program,
or for which 1 (10?) are not easily available ?

js>
js> Page 26: The following sentence does not read well: "This requirement
js> makes it possible restrict access to management services using
js> routing."

s/possible/possible to/

done.

js>
js> Page 29: "support to to rate-limit" -> "support to rate-limit"

Already fixed.

js>
js> Page 36: Reset of counter requirement should probably explain how this
js>         relates to SNMP. I hope the idea is that the displayed counter
js>         is reset, not the real counter underneath it.

Yes.  That is fine.   See above.   Thanks for catching that.

js>
js> Page 38: The warning concerning syslog are interesting and the current
js>         best solution concerns me (since it just says that there is no
js>         deployable secure syslog solution at the moment, more than two
js>         years after publication of RFC 3195). This should probably
js>         make the IESG think about the question whether RFC 3195 is
js>         going to be the right solution...

I'd love to be shown wrong here or that good things are "just over the
horizon" (Chris ?).  3195 is a fine document.  I don't see the
implementations, so it's hard to call it a "best practice".  Other
reliable delivery solutions would be fine by me too...as long as there
implmentations.

js>
js> Page 41: "... the address a reliable for ..." ->
js>         "... the address reliable for ..."

s/ a / more /

js>
js> Page 51: "... will may leave the operator ..." ->
js> "... may leave the operator ..."

s/will//

Thanks,
George M. Jones    |  Resolve to be honest in all events; and if in your own
                   |  judgment you cannot be an honest lawyer, resolve to be
                   |  honest without being a lawyer.
                   |      A. Lincoln
gmj@pobox.com