[Isms] RFC 6353 on Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)

rfc-editor@rfc-editor.org Wed, 20 July 2011 22:59 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: isms@ietfa.amsl.com
Delivered-To: isms@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1A36021F8AED; Wed, 20 Jul 2011 15:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.155
X-Spam-Status: No, score=-102.155 tagged_above=-999 required=5 tests=[AWL=-0.155, 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 5UmT1veKhYkd; Wed, 20 Jul 2011 15:59:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id E57B621F8B09; Wed, 20 Jul 2011 15:59:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E0DEC98C518; Wed, 20 Jul 2011 15:59:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110720225943.E0DEC98C518@rfc-editor.org>
Date: Wed, 20 Jul 2011 15:59:43 -0700 (PDT)
Cc: isms@ietf.org, rfc-editor@rfc-editor.org
Subject: [Isms] RFC 6353 on Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 22:59:48 -0000

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

        RFC 6353

        Title:      Transport Layer Security (TLS) Transport 
                    Model for the Simple Network Management 
                    Protocol (SNMP) 
        Author:     W. Hardaker
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2011
        Mailbox:    ietf@hardakers.net
        Pages:      65
        Characters: 148571
        Obsoletes:  RFC5953

        I-D Tag:    RFC 5953

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

This document describes a Transport Model for the Simple Network
Management Protocol (SNMP), that uses either the Transport Layer
Security protocol or the Datagram Transport Layer Security (DTLS)
protocol.  The TLS and DTLS protocols provide authentication and
privacy services for SNMP applications.  This document describes how
the TLS Transport Model (TLSTM) implements the needed features of an
SNMP Transport Subsystem to make this protection possible in an
interoperable way.

This Transport Model is designed to meet the security and operational
needs of network administrators.  It supports the sending of SNMP
messages over TLS/TCP and DTLS/UDP.  The TLS mode can make use of
TCP's improved support for larger packet sizes and the DTLS mode
provides potentially superior operation in environments where a
connectionless (e.g., UDP) transport is preferred.  Both TLS and DTLS
integrate well into existing public keying infrastructures.

This document also defines a portion of the Management Information
Base (MIB) for use with network management protocols.  In particular,
it defines objects for managing the TLS Transport Model for SNMP. 

This document is a product of the Integrated Security Model for SNMP 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