RFC 5343 on Simple Network Management Protocol (SNMP) Context EngineID Discovery

rfc-editor@rfc-editor.org Fri, 03 June 2011 00:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1AF12E0674; Thu, 2 Jun 2011 17:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.013
X-Spam-Status: No, score=-102.013 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id p1nl4oSJJr1i; Thu, 2 Jun 2011 17:16:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 897DCE07B6; Thu, 2 Jun 2011 17:16:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 845C9E0787; Thu, 2 Jun 2011 17:16:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5343 on Simple Network Management Protocol (SNMP) Context EngineID Discovery
From: rfc-editor@rfc-editor.org
Message-Id: <20110603001624.845C9E0787@rfc-editor.org>
Date: Thu, 02 Jun 2011 17:16:24 -0700
Cc: opsawg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 00:16:29 -0000

This document is now a Draft Standard Protocol.

        RFC 5343

        Title:      Simple Network Management Protocol (SNMP) 
                    Context EngineID Discovery 
        Author:     J. Schoenwaelder
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2008
        Mailbox:    j.schoenwaelder@jacobs-university.de
        Pages:      9
        Characters: 19938
        Updates:    RFC3411

        I-D Tag:    draft-ietf-opsawg-snmp-engineid-discovery-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5343.txt

The Simple Network Management Protocol (SNMP) version three (SNMPv3)
requires that an application know the identifier (snmpEngineID) of
the remote SNMP protocol engine in order to retrieve or manipulate
objects maintained on the remote SNMP entity.

This document introduces a well-known localEngineID and a discovery
mechanism that can be used to learn the snmpEngineID of a remote SNMP
protocol engine.  The proposed mechanism is independent of the
features provided by SNMP security models and may also be used by
other protocol interfaces providing access to managed objects.

This document updates RFC 3411.  [STANDARDS-TRACK]

This document is a product of the Operations and Management Area Working Group Working Group of the IETF.

This is now a Draft Standard Protocol.

STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC