Re: Status of SNMPv2 Documents
"michael (m.) sam chee" <mschee@bnr.ca> Thu, 16 November 1995 22:31 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24103; 16 Nov 95 17:31 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa24098; 16 Nov 95 17:31 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa29602; 16 Nov 95 17:31 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24087; 16 Nov 95 17:31 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23997; 16 Nov 95 17:28 EST
Received: from x400gate.bnr.ca by CNRI.Reston.VA.US id aa29403; 16 Nov 95 17:28 EST
X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Thu, 16 Nov 1995 17:15:07 -0500
X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Thu, 16 Nov 1995 17:14:34 -0500
X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Thu, 16 Nov 1995 10:17:00 -0500
Date: Thu, 16 Nov 1995 10:17:00 -0500
X400-Originator: "/dd.id=1664568/g=michael/i=m/s=sam chee/"@bnr.ca
X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; bcars735.b.388:16.10.95.22.14.34]
X400-Content-Type: P2-1984 (2)
Content-Identifier: Re: Status of...
X-Orig-Sender: ietf-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "michael (m.) sam chee" <mschee@bnr.ca>
X-Orig-Sender: "michael (m.) sam chee" <mschee@bnr.ca>
Message-ID: <"22398 Thu Nov 16 17:14:37 1995"@bnr.ca>
To: romanov@nacto.lkg.dec.com
Cc: "joey (j.h.) de wiele" <joey@bnr.ca>, snmpv2@tis.com, ietf@CNRI.Reston.VA.US
Subject: Re: Status of SNMPv2 Documents
In message "Status of SNMPv2 Documents", romanov@nacto.lkg.dec.com writes: > It is possible that SNMPv2 will never to be a standard, Let me surmise to say, and I hope I am wrong, that the SNMP community is slowly but surely losing faith in the SNMP Working Group. The original SNMPv2 was perceived as being proposed by a set of highly qualified persons, so many people took this at face value and faithfully went ahead and implemented the proposed standard. Today, new proposals are probably not likely to receive the same warm reception as before because of what became of the original SNMPv2 proposal. We may be putting ourselves deeper in a catch 22 situation - no one implements till it becomes a draft/full standard, but this is not possible until there are implementations. IMHO, I think we need to pick up the pieces, put all interpersonal conflicts aside, come to grips with what had went wrong and how we can improve on it, so we can regain the thrust of the SNMP community and move forward. Just a thought. --- Michael Sam Chee LAN Communications Protocol Development mschee@bnr.ca Bell-Northern Research, Ltd. Voice (613)763-9650 P.O. Box 3511, Station C FAX (613)763-8312 Ottawa, Ontario, Canada K1Y 4H7 #include <standard_disclaimer.h>
- Status of SNMPv2 Documents Deirdre Kostick
- Re: Status of SNMPv2 Documents Marshall Rose
- Re: Status of SNMPv2 Documents romanov
- Re: Status of SNMPv2 Documents Bob Natale
- Re: Status of SNMPv2 Documents romanov
- Re: Status of SNMPv2 Documents Steve Waldbusser
- Re: Status of SNMPv2 Documents Marshall Rose
- Re: Status of SNMPv2 Documents Steve Waldbusser
- Re: Status of SNMPv2 Documents Marshall Rose
- Re: Status of SNMPv2 Documents Steve Waldbusser
- Re: Status of SNMPv2 Documents Deirdre Kostick
- Re: Status of SNMPv2 Documents Michael L. Kornegay
- Re: Status of SNMPv2 Documents Marshall Rose
- Re: Status of SNMPv2 Documents Steve Waldbusser
- Re: Status of SNMPv2 Documents Marshall Rose
- Re: Status of SNMPv2 Documents Brian O'Keefe
- Re: Status of SNMPv2 Documents Marshall Rose
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents Brian O'Keefe
- Re: Status of SNMPv2 Documents romanov
- Re: Status of SNMPv2 Documents Brian O'Keefe
- Re: Status of SNMPv2 Documents Aleksey Y Romanov
- Re: Status of SNMPv2 Documents michael (m.) sam chee
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents Peter J M Polkinghorne
- re: Status of SNMPv2 Documents glenn (g.) waters
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents John W Riley/OSI
- Re: Status of SNMPv2 Documents Kim Laraqui Sfp-han