Sign in
Version 5.13.0, 2015-03-25
Report a bug

Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)
RFC 5907

No Objection
(was Discuss)
(was Discuss)
(was Discuss)
(was Discuss)
(was No Record, Discuss)

Note: This ballot was opened for revision 05 and is now closed.

Summary: Needs a YES. Needs 10 more YES or NO OBJECTION positions to pass.

[Adrian Farrel]

Comment (2009-10-24 for -07)

Thanks, looks like you took care of all my Comments.

[Cullen Jennings]

Comment (2009-04-06 for -07)

Support Discuss from several other ADs.

[Dan Romascanu]

Comment (2010-02-11 for -)

1. Most DisplayString objects have been changed into Utf8String objects, but
there are still a few objects where they use DisplayString.I understand that in
these cases there will (most probably) never be international text, so we can
live with this. On the other hand, I do not see what the problem would be to
also make those utf8 based. If the content is ASCII, then basically that is
exactly the same, no matter if it is repreented in UTF8 or ASCII.

2. Now that they use Utf8String (from RFC 2287), I think that RFC2287 should be
added as a normative reference.

3. It would be nice to acknowledge the contribution of the MIB Doctor Bert

[Robert Sparks]

Comment (2009-04-07 for -)

Support Adrian's and Dan's discusses

[Ron Bonica]

Comment (2009-04-07 for -)

Supporting Dan's discuss