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

RFC Editor <rfc-editor@rfc-editor.org> Thu, 08 May 2014 20:47 UTC

Return-Path: <rfc-ed@rfc-editor.org>
X-Original-To: isms@ietfa.amsl.com
Delivered-To: isms@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17BE1A00BA; Thu, 8 May 2014 13:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H7pHESId4dFz; Thu, 8 May 2014 13:47:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4841A00B7; Thu, 8 May 2014 13:47:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 6000) id 9DACB1801C2; Thu, 8 May 2014 13:47:11 -0700 (PDT)
Date: Thu, 8 May 2014 13:47:11 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Message-ID: <20140508204711.GF14585@rfc-editor.org>
References: <20140508204607.GE14585@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140508204607.GE14585@rfc-editor.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/isms/RoanxM9vJJAEFgDH1w5mRHLH81c
Cc: Pearl Liang <drafts-update-ref@icann.org>, isms@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Isms] STD 78, RFC 5590 on Transport Subsystem for the Simple Network Management Protocol (SNMP)
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 08 May 2014 20:48:00 -0000

       STD 78
       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:    RFC 3411, RFC 3412, RFC 3414, RFC 3417
       See Also:   STD 78

       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.

This document is a product of the Integrated Security Model for SNMP
Working Group of the IETF.

This is now an Internet Standard.

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/search/rfc_search.php
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