[rfc-dist] RFC 3826 on The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Thu Jun 17 16:13:00 PDT 2004

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

        RFC 3826

        Title:      The Advanced Encryption Standard (AES) Cipher
                    Algorithm in the SNMP User-based Security Model
        Author(s):  U. Blumenthal, F. Maino, K. McCloghrie
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    uri at bell-labs.com, fmaino at andiamo.com,
                    kzm at cisco.com
        Pages:      16
        Characters: 32821
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-blumenthal-aes-usm-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3826.txt

This document describes a symmetric encryption protocol that
supplements the protocols described in the User-based Security Model
(USM), which is a Security Subsystem for version 3 of the Simple
Network Management Protocol for use in the SNMP Architecture.  The
symmetric encryption protocol described in this document is based on
the Advanced Encryption Standard (AES) cipher algorithm used in Cipher
FeedBack Mode (CFB), with a key size of 128 bits.

This is now a Proposed Standard Protocol.

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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

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

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
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.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list