[Pwg-Announce] Fwd: [Isms] RFC 5953 - TLS Transport Model for SNMP
Ira McDonald <blueroofmusic@gmail.com> Fri, 20 August 2010 20:52 UTC
Return-Path: <pwg-announce-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 931D33A693A for <ietfarch-ipp-archive@core3.amsl.com>; Fri, 20 Aug 2010 13:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level:
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[AWL=0.311, BAYES_00=-2.599, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q+2TwHEu9NQr for <ietfarch-ipp-archive@core3.amsl.com>; Fri, 20 Aug 2010 13:52:39 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 62EBD3A6881 for <ipp-archive@lists.ietf.org>; Fri, 20 Aug 2010 13:52:39 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E36A07931F; Fri, 20 Aug 2010 16:53:07 -0400 (EDT)
X-Original-To: pwg-announce@pwg.org
Delivered-To: pwg-announce@pwg.org
Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 160407919E for <pwg-announce@pwg.org>; Fri, 20 Aug 2010 16:53:03 -0400 (EDT)
Received: by vws3 with SMTP id 3so3536576vws.5 for <pwg-announce@pwg.org>; Fri, 20 Aug 2010 13:53:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=F/XX2n0BOnc93jGFTChTrTjtjBJqfo+OqZR/uPGEMvg=; b=dzya+I74eDd8KmDUp4W2rQ0iXCrfJEXW6sVX3lI/v2PtIGDLba2ZxibtoQmYB2zNGb ogg7LVbvT+iA7hw5FbS2IHxG5GMS5zQA8dY5RiUhcQXQY/GP06lFe7X6h1GnUcEeGWI+ cVhnlyuHWuEEvRwfhJKq5NAW2McelrDITQ9Ps=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=wYLXydNeUbFfv8NE2IuppRRmcAMHwVn5ldd9g1SoPiCfV0mkZk6LccGkdVujp50wub yQKd1OshktsDHEzVy8ub8E/PK4daRSaqk8XjfJdDvZIAacewikMiHTHTt6Y4NgRmZj+G hijHb0o8wWpA5IssQiLtmzwOI7DGmNaxlVlEQ=
MIME-Version: 1.0
Received: by 10.220.62.136 with SMTP id x8mr1152653vch.177.1282337583194; Fri, 20 Aug 2010 13:53:03 -0700 (PDT)
Received: by 10.220.199.204 with HTTP; Fri, 20 Aug 2010 13:53:03 -0700 (PDT)
Date: Fri, 20 Aug 2010 16:53:03 -0400
Message-ID: <AANLkTimiX1E9eay6La9R3muRVTkuJQ2VW02VuJ14iyJ4@mail.gmail.com>
From: Ira McDonald <blueroofmusic@gmail.com>
To: pwg-announce@pwg.org, Ira McDonald <blueroofmusic@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-pwg-MailScanner: Found to be clean, Found to be clean
Cc:
Subject: [Pwg-Announce] Fwd: [Isms] RFC 5953 - TLS Transport Model for SNMP
X-BeenThere: pwg-announce@pwg.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Printer Working Group Announcement List <pwg-announce.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/listinfo/pwg-announce>, <mailto:pwg-announce-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/archives/pwg-announce>
List-Post: <mailto:pwg-announce@pwg.org>
List-Help: <mailto:pwg-announce-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/pwg-announce>, <mailto:pwg-announce-request@pwg.org?subject=subscribe>
Sender: pwg-announce-bounces@pwg.org
Errors-To: pwg-announce-bounces@pwg.org
X-pwg-MailScanner-Information: Please contact the ISP for more information
X-pwg-MailScanner-ID: E36A07931F.ACAC5
X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org
Hi, The long-awaited enterprise network-friendly way to deploy SNMP authentication and security using TLS and DTLS. Recommended reading. Cheers, - Ira ---------- Forwarded message ---------- From: <rfc-editor@rfc-editor.org> Date: Fri, Aug 20, 2010 at 2:14 PM Subject: [Isms] RFC 5953 on Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Cc: isms@ietf.org, rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 5953 Title: Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) Author: W. Hardaker Status: Standards Track Stream: IETF Date: August 2010 Mailbox: ietf@hardakers.net Pages: 65 Characters: 147393 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isms-dtls-tm-14.txt URL: http://www.rfc-editor.org/rfc/rfc5953.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 a 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. [STANDARDS TRACK] This document is a product of the Integrated Security Model for SNMP Working Group of the IETF. This is now a Proposed 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 _______________________________________________ Isms mailing list Isms@ietf.org https://www.ietf.org/mailman/listinfo/isms -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce
- [Pwg-Announce] Fwd: [Isms] RFC 5953 - TLS Transpo… Ira McDonald
- Re: [Pwg-Announce] Fwd: [Isms] RFC 5953 - TLS Tra… Randy Turner