Administrative Model for Version 2 of the Simple Network Management Protocol (SNMPv2)
draft-various-snmpv2-adminv2-syn-01

Document Type Expired Internet-Draft (individual)
Last updated 1995-12-22
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-various-snmpv2-adminv2-syn-01.txt

Abstract

This document is a submission to the SNMPv2 Working Group of the IETF. Computer security systems can be usually be understood as being composed of two or more logically distinct components. There is often a privacy service that protects data from disclosure, an authentication service that validates the identity of the entity requesting service, and an access control service which, given an authorized entity, restricts the data and operations to which that entity has access. The SNMPv2 Administrative Model makes these distinctions. It specifies the data and protocols that a compliant SNMPv2 entity must implement in order to provide an access control service. However, it does not say anything about how authentication, privacy, timeliness, and the like ought to be implemented. Rather, it leaves the hooks in place for these services to be implemented in a variety of ways. Henceforth, this collection of unspecified services will be collectively referred to as 'the authentication and privacy services'. Consequently, the SNMPv2 Administrative Model provides an architecture that realizes an access control service, and provides the means for integrating authentication

Authors

Jeff Case (case@snmp.com)
James Davin (davin@psi.com)
Marshall Rose (mrose+mtr.mxcomp@dbc.mtview.ca.us)
Steven Waldbusser (waldbusser@nextbeacon.com)
Keith McCloghrie (kzm@cisco.com)
James Galvin (galvin+ietf@elistx.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)