From turners@ieca.com Wed Jun 1 08:33:30 2011 Return-Path: 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 055B7E08E8 for ; Wed, 1 Jun 2011 08:33:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.389 X-Spam-Level: X-Spam-Status: No, score=-101.389 tagged_above=-999 required=5 tests=[AWL=-0.751, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, UNPARSEABLE_RELAY=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 QaKnFTkyNHLp for ; Wed, 1 Jun 2011 08:33:29 -0700 (PDT) Received: from nm23-vm0.bullet.mail.sp2.yahoo.com (nm23-vm0.bullet.mail.sp2.yahoo.com [98.139.91.224]) by ietfa.amsl.com (Postfix) with SMTP id 19389E08E4 for ; Wed, 1 Jun 2011 08:33:29 -0700 (PDT) Received: from [98.139.91.62] by nm23.bullet.mail.sp2.yahoo.com with NNFMP; 01 Jun 2011 15:33:29 -0000 Received: from [98.139.91.44] by tm2.bullet.mail.sp2.yahoo.com with NNFMP; 01 Jun 2011 15:33:29 -0000 Received: from [127.0.0.1] by omp1044.mail.sp2.yahoo.com with NNFMP; 01 Jun 2011 15:33:29 -0000 X-Yahoo-Newman-Id: 7060.6781.bm@omp1044.mail.sp2.yahoo.com Received: (qmail 44098 invoked from network); 1 Jun 2011 15:33:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1306942408; bh=y3XMMG5YcP4RgyXhSBhxHjOwLAitbh7VhHKWTViT05A=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=y7iGG5UoZR4xtewERt2HGPr0EoG1DCl3fLyL14gDH6vf5YX/6p4xMrDEFVcDyqgFzclP0vlxwHTbzZQ8sWvgdJc9VUuebwn6cfymlUNi3/MweC3cuJ9thKFL7CdPstHaEbe5JuwmOfhtPMbo4KFzrPfRKBcE/nWvvyfn685XCiI= Received: from thunderfish.local (turners@71.191.10.67 with plain) by smtp115.biz.mail.sp1.yahoo.com with SMTP; 01 Jun 2011 08:33:27 -0700 PDT X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ X-YMail-OSG: aaHSZpUVM1lSVgSUnjMHkhsknBpQdGmii2Y289A_wfGeiLH 3q8O7O.L.2CLOAycJRd6JJ6UWs3VNgj8UJGNVLaxifZf8w4iXsW8k9HS1bq0 JyTyc70jU_vm28Ik4WF..a5ziYPn_fT8fvSg9i9mA5Y5pexG0AA3jZtbc8sd Rc0HMK2rXSwE2QHCSrcWyPi5ORTsWheyTxiG82gAxjE_5aXmiNtvZ4ILtV2v xCINlVOYgosfEgVOwmevaNL6bG99hJntaXA.7hX0g7uiwUsF65Ewm._darnl 2.fnXeYbUMfXQPKbN1GFjmqX.ZLDzHg05tDyDFltigrl1DulKkM5MzlbIDcO No9Tk3a2v5PVsxH05qlQiGVmckxN75yJvP3.TlEWY X-Yahoo-Newman-Property: ymail-3 Message-ID: <4DE65BC6.6050603@ieca.com> Date: Wed, 01 Jun 2011 11:33:26 -0400 From: Sean Turner User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: isms@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Isms] Fwd: Protocol Action: 'Simple Network Management Protocol (SNMP) Context EngineID Discovery' to Draft Standard X-BeenThere: isms@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 15:33:30 -0000 FYI ... -------- Original Message -------- Subject: Protocol Action: 'Simple Network Management Protocol (SNMP) Context EngineID Discovery' to Draft Standard Date: Tue, 31 May 2011 13:31:35 -0700 (PDT) From: IESG Secretary To: IETF Announcement list CC: iab@iab.org, rfc-editor@rfc-editor.org The IESG has approved the following document: - 'Simple Network Management Protocol (SNMP) Context EngineID Discovery ' RFC 5343 as a Draft Standard This document is the product of the Operations and Management Area Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this RFC is: http://www.ietf.org/rfc/rfc5343.txt Technical Summary 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. Working Group Summary The document is being advanced from Proposed Standard to Draft Standard together with RFC 5590, RFC 5591, and RFC 5953. Document Quality Two independent implementations of SNMP Context EngineID Discovery have been developed, tested, and found to be interoperable. The developers of both implementation agree that RFC 5343 is sufficiently clear to allow for interoperable implementations. The implementation report is available at http://www.ietf.org/iesg/implementation/report-rfc5343-5590-5591-5953.txt Personnel Dan Romascanu is the responsible Area Director. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From wwwrun@rfc-editor.org Thu Jun 2 17:13:14 2011 Return-Path: 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 28FE8E07B6; Thu, 2 Jun 2011 17:13:14 -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 bRVgq0MvAHqR; Thu, 2 Jun 2011 17:13:13 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id EA1BEE0870; Thu, 2 Jun 2011 17:12:55 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id DD6E4E074F; Thu, 2 Jun 2011 17:12:55 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20110603001255.DD6E4E074F@rfc-editor.org> Date: Thu, 2 Jun 2011 17:12:55 -0700 (PDT) Cc: isms@ietf.org, rfc-editor@rfc-editor.org Subject: [Isms] RFC 5591 on Transport Security 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 00:13:14 -0000 This document is now a Draft Standard Protocol. RFC 5591 Title: Transport Security Model for the Simple Network Management Protocol (SNMP) Author: D. Harrington, W. Hardaker Status: Standards Track Stream: IETF Date: June 2009 Mailbox: ietfdbh@comcast.net, ietf@hardakers.net Pages: 28 Characters: 61747 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isms-transport-security-model-14.txt URL: http://www.rfc-editor.org/rfc/rfc5591.txt This memo describes a Transport Security Model for the Simple Network Management Protocol (SNMP). This memo also defines a portion of the Management Information Base (MIB) for monitoring and managing the Transport Security 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 From wwwrun@rfc-editor.org Thu Jun 2 17:14:55 2011 Return-Path: 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, 2 Jun 2011 17:14:55 -0700 (PDT) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From wjhns1@hardakers.net Thu Jun 2 17:16:01 2011 Return-Path: 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 CCE51E0674 for ; Thu, 2 Jun 2011 17:16:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 hqu6Oy4UhVKa for ; Thu, 2 Jun 2011 17:16:01 -0700 (PDT) Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id 66306E0848 for ; Thu, 2 Jun 2011 17:16:00 -0700 (PDT) Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 96CAA29C for ; Thu, 2 Jun 2011 17:15:28 -0700 (PDT) From: Wes Hardaker To: isms@ietf.org References: <20110603001255.DD6E4E074F@rfc-editor.org> Date: Thu, 02 Jun 2011 17:15:27 -0700 In-Reply-To: <20110603001255.DD6E4E074F@rfc-editor.org> (rfc-editor@rfc-editor.org's message of "Thu, 2 Jun 2011 17:12:55 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Isms] IsmsRFC 5591 on Transport Security 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 00:16:01 -0000 >>>>> On Thu, 2 Jun 2011 17:12:55 -0700 (PDT), rfc-editor@rfc-editor.org said: r> This document is now a Draft Standard Protocol. Excellent news! Thanks to everyone who helped make this possible, through implementation reports and interoperability testing and document reviews of the original document and design and ... It takes a lot of work to get here :-) -- Wes Hardaker Cobham Analytic Solutions From wwwrun@ietfa.amsl.com Mon Jun 6 14:47:23 2011 Return-Path: X-Original-To: isms@ietf.org Delivered-To: isms@ietfa.amsl.com Received: by ietfa.amsl.com (Postfix, from userid 30) id 9FF3221F848E; Mon, 6 Jun 2011 14:47:23 -0700 (PDT) From: The IESG To: IETF Announcement list Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20110606214723.9FF3221F848E@ietfa.amsl.com> Date: Mon, 6 Jun 2011 14:47:23 -0700 (PDT) X-Mailman-Approved-At: Thu, 16 Jun 2011 10:14:12 -0700 Cc: isms@ietf.org, isms-chairs@tools.ietf.org, rfc-editor@rfc-editor.org Subject: [Isms] Protocol Action: 'Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)' to Draft Standard X-BeenThere: isms@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 21:47:23 -0000 The IESG has approved the following document: - 'Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) ' RFC 5953 as a Draft Standard This document is the product of the Integrated Security Model for SNMP Working Group. The IESG contact persons are Sean Turner and Stephen Farrell. A URL of this RFC is: http://www.ietf.org/rfc/rfc5953.txt Technical Summary RFC 5953 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. Working Group Summary Only two issues were raised during the 1st IETF LC: 1) references to RFC 1033 need to be replaced with references to RFC 1123; and, 2) references to RFC 3490 need to be updated to RFC 5890. The second also required some textual changes, but in the changes would not force this document to recycle. Document Quality An implementations report can be found at: http://www.ietf.org/iesg/implementation/report-rfc5343-5590-5591-5953.txt Personnel Juergen Schoenwaelder is the Shepherd. Sean Turner in the responsible AD. RFC Editor Note Please note the original "plan" was to progress RFC 5953 from PS to DS as is. During IETF LC there were two changes that were identified, so that plan is out the window. Please incorporate the following in to the published version: 1) Please ensure the published RFC indicates that it obsoletes 5953: Obsoletes: 5953 2) Section 7: Change the top of the MIB's LAST-UPDATED clause: OLD: LAST-UPDATED "201005070000Z" NEW: LAST-UPDATED "201105260000Z" 3) Section 7: Change the MIB's copyright date: OLD: Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. NEW: Copyright (c) 2010-2011 IETF Trust and the persons identified as the document authors. All rights reserved. 4) Section 7: Add a new REVISION clause *ABOVE* the previous one OLD: REVISION "201005070000Z" DESCRIPTION "This version of this MIB module is part of RFC 5953; see the RFC itself for full legal notices." NEW: REVISION "201105260000Z" DESCRIPTION "This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices. The only change was to introduce new wording to reflect require changes for IDNA addresses in the SnmpTLSAddress TC." REVISION "201005070000Z" DESCRIPTION "This version of this MIB module is part of RFC 5953; see the RFC itself for full legal notices." ** Note replace XXXX with the appropriate RFC #. 5) Section 7 OLD: A hostname is always in US-ASCII (as per [RFC1033]); internationalized hostnames are encoded in US-ASCII as domain names after transformation via the ToASCII operation specified in [RFC3490]. The ToASCII operation MUST be performed with the UseSTD3ASCIIRules flag set. The hostname is followed by a colon ':' (US-ASCII character 0x3A) and a decimal port number in US-ASCII. The name SHOULD be fully qualified whenever possible. NEW: A hostname is always in US-ASCII (as per [RFC1123]); internationalized hostnames are encoded as A-labels as specified in [RFC5890]. The hostname is followed by a colon ':' (US-ASCII character 0x3A) and a decimal port number in US-ASCII. The name SHOULD be fully qualified whenever possible. 6) Section 7 OLD: REFERENCE "RFC 1033: DOMAIN ADMINISTRATORS OPERATIONS GUIDE RFC 3490: Internationalizing Domain Names in Applications RFC 5952: A Recommendation for IPv6 Address Text Representation " NEW: REFERENCE "RFC 1123: Requirements for Internet Hosts - Application and Support RFC 5890: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework RFC 5952: A Recommendation for IPv6 Address Text Representation " 7) Section 12 Add RFC 5953 as an informative reference. Replace references to RFC 1033 and RFC 3490 with references to RFC 1123 and RFC 5890, respectively. Move RFC 5890 to the informative references. 8) Incorporate the following errata: 8a) Section A.1 OLD snmpTargetParamsRowStatus = 4 (createAndGo0 NEW: snmpTargetParamsRowStatus = 4 (createAndGo) 8b) Section A.1 OLD: snmpTargetAddrColumnStatus = 4 (createAndGo) NEW: snmpTargetAddrRowStatus = 4 (createAndGo) 9) Add the following new section to highlight these changes: 1.2 Changes Since RFC 5953 This document obsoletes [RFC5953]. Since the publication of RFC 5953, a few editorial errata have been noted. These errata are posted on the RFC Editor web site. These errors have been corrected in this document. This document updates the references to RFC 3490 (IDNA 2003) to to RFC 5890 (IDNA 2008), because RFC 3490 was obsoleted by RFC 5890. References to RFC 1033 were replaced with references to RFC 1123. Added informative reference to 5953. Updated MIB dates and revision date.