[Isms] RFC 5590 on Transport Subsystem for the Simple Network Management Protocol (SNMP)

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

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: isms@ietfa.amsl.com
Delivered-To: isms@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B09E0674; Thu, 2 Jun 2011 17:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.014
X-Spam-Level:
X-Spam-Status: No, score=-102.014 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CImsvmL3qLws; Thu, 2 Jun 2011 17:14:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 832BAE07B6; Thu, 2 Jun 2011 17:14:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7E29AE0785; Thu, 2 Jun 2011 17:14:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110603001455.7E29AE0785@rfc-editor.org>
Date: Thu, 02 Jun 2011 17:14:55 -0700
Cc: isms@ietf.org, rfc-editor@rfc-editor.org
Subject: [Isms] RFC 5590 on Transport Subsystem 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: Fri, 03 Jun 2011 00:14:56 -0000

This document is now a Draft Standard Protocol.

        
        RFC 5590

        Title:      Transport Subsystem for the Simple 
                    Network Management Protocol (SNMP) 
        Author:     D. Harrington, J. Schoenwaelder
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2009
        Mailbox:    ietfdbh@comcast.net, 
                    j.schoenwaelder@jacobs-university.de
        Pages:      34
        Characters: 84513
        Updates:    RFC3411, RFC3412, RFC3414, RFC3417

        I-D Tag:    draft-ietf-isms-tmsm-18.txt

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

This document defines a Transport Subsystem, extending the Simple
Network Management Protocol (SNMP) architecture defined in RFC 3411.
This document defines a subsystem to contain Transport Models that is
comparable to other subsystems in the RFC 3411 architecture.  As work
is being done to expand the transports to include secure transports,
such as the Secure Shell (SSH) Protocol and Transport Layer Security
(TLS), using a subsystem will enable consistent design and modularity
of such Transport Models.  This document identifies and describes
some key aspects that need to be considered for any Transport Model
for SNMP.  [STANDARDS-TRACK]

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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