RFC 2574 on USM for SNMPv3

RFC Editor <rfc-ed@ISI.EDU> Wed, 12 May 1999 16:25 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id MAA01120 for ietf-123-outbound.10@ietf.org; Wed, 12 May 1999 12:25:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29570 for <all-ietf@ietf.org>; Wed, 12 May 1999 11:50:03 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id IAA13629; Wed, 12 May 1999 08:50:05 -0700 (PDT)
Message-Id: <199905121550.IAA13629@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2574 on USM for SNMPv3
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 12 May 1999 08:50:04 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.

	RFC 2574: 

        Title:	    User-based Security Model (USM) for version 3 of
		    the Simple Network Management Protocol (SNMPv3)
	Author(s):  U. Blumenthal, B. Wijnen
        Status:     Draft Standard
	Date:       April 1999
        Mailbox:    uri@watson.ibm.com, wijnen@vnet.ibm.com
        Pages:      86
        Characters: 190755
        Obsoletes:  2274
        I-D Tag:    draft-ietf-snmpv3-usm-v2-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2574.txt


This document describes the User-based Security Model (USM) for SNMP
version 3 for use in the SNMP architecture [RFC2571].  It defines the
Elements of Procedure for providing SNMP message level security.  This
document also includes a MIB for remotely monitoring/managing the
configuration parameters for this Security Model.
 
This is now a Draft Standard Protocol.
 
This document is a product of the SNMP Version 3 Working Group of the
IETF.
 
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2574.txt"><ftp://ftp.isi.edu/in-notes/rfc2574.txt>