Article View: comp.protocols.time.ntp
Article #871Re: MIB for ntp
From: Randall Atkinson
Date: Sun, 22 Nov 1992 15:39
Date: Sun, 22 Nov 1992 15:39
16 lines
1266 bytes
1266 bytes
In article <1emjakINNmcn@ni.umd.edu> louie@sayshell.umd.edu (Louis A. Mamakos) writes: >There are, of course, a number of design decisions to make; one of the >more obvious is how to represent 64 bit NTP timestamps in the MIB. >Two 32 bit integers? Octet string? Hmm.. That is a good question. The notion of adding a 64-bit entity as part of the SNMP v2 (aka SMP) work seems to have been discarded if I recall my mailing list traffic correctly. If such a MIB were read-write, someone would need to look at the security implications since NTP already has its own security and SNMP has its own. It would be undesirable if a compromised SNMP could be used to undermine an uncompromised NTP or vice versa. Ran atkinson@itd.nrl.navy.mil
Technical Details
Message-ID:
<By4JHo.rD@ra.nrl.navy.mil>Path:
arc1-ca.pugleaf.net!sparky!uunet!ornl!rsg1.er.usgs.gov!darwin.sura.net!ra!atkinsonReferences:
<1992Nov20.154239.27827@den.mmc.com> <1emjakINNmcn@ni.umd.edu> <2B0F17FD.22593@news.service.uci.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.protocols.time.ntp Path: arc1-ca.pugleaf.net!sparky!uunet!ornl!rsg1.er.usgs.gov!darwin.sura.net!ra!atkinson From: atkinson@itd.nrl.navy.mil (Randall Atkinson) Subject: Re: MIB for ntp Message-ID: <By4JHo.rD@ra.nrl.navy.mil> Keywords: MIB SNMP Sender: usenet@ra.nrl.navy.mil Organization: Naval Research Laboratory, DC References: <1992Nov20.154239.27827@den.mmc.com> <1emjakINNmcn@ni.umd.edu> <2B0F17FD.22593@news.service.uci.edu> Distribution: inet Date: Sun, 22 Nov 1992 15:39:24 GMT Lines: 16