From isms-bounces@lists.ietf.org Tue Nov 08 14:54:44 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZZYK-0000BO-BX; Tue, 08 Nov 2005 14:54:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZZYI-0000B9-QP for isms@megatron.ietf.org; Tue, 08 Nov 2005 14:54:42 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29721 for ; Tue, 8 Nov 2005 14:54:15 -0500 (EST) Received: from hosting.revelstone.com ([66.36.242.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZZo9-0006Zm-L3 for isms@ietf.org; Tue, 08 Nov 2005 15:11:06 -0500 Received: from localhost ([127.0.0.1] helo=aud) by hosting.revelstone.com with smtp (Exim 4.52) id 1EZZYA-00014S-Il; Tue, 08 Nov 2005 14:54:34 -0500 Date: Tue, 8 Nov 2005 14:54:50 -0500 From: Robert Story To: ietfdbh@comcast.net Subject: Re: [Isms] #3: we need some text contributed to discuss theimplications of sessions on SNMP. Message-ID: <20051108145450.6eb4afb3@aud> In-Reply-To: <200510132223.SAA21940@ietf.org> References: <200510132147.RAA19727@ietf.org> <200510132223.SAA21940@ietf.org> X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.4.14; powerpc-yellowdog-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hosting.revelstone.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - revelstone.com X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Cc: isms@ietf.org X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org On Thu, 13 Oct 2005 18:23:42 -0400 David wrote: DBH> SNMP was originally designed with certain assumptions in mind. Some DBH> assumptions may no longer be valid if we use sessions. One issue that was discussed early on, I think in one of the BOFs, was about the security level of the session, and how that affected what PDUs could be sent over the session. IMHO, the security level used to initiate the session should be considered the maximum security level, with no minimum. eg an authNoPriv pdu could be sent over an authPriv session. The rational being that we should not require additional sessions for varying security levels. A user is free to create another session if they want to avoid the overhead of encryption for authNoPriv messages, but if their goal is to avoid session setup overhead, they re-use an existing session of a higher level. _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Tue Nov 08 14:58:39 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZZc7-00023K-Q3; Tue, 08 Nov 2005 14:58:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZZc5-00020z-Sz for isms@megatron.ietf.org; Tue, 08 Nov 2005 14:58:37 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29931 for ; Tue, 8 Nov 2005 14:58:10 -0500 (EST) Received: from hosting.revelstone.com ([66.36.242.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZZry-0006g8-6p for isms@ietf.org; Tue, 08 Nov 2005 15:15:02 -0500 Received: from localhost ([127.0.0.1] helo=aud) by hosting.revelstone.com with smtp (Exim 4.52) id 1EZZc3-00015N-0r; Tue, 08 Nov 2005 14:58:35 -0500 Date: Tue, 8 Nov 2005 14:58:51 -0500 From: Robert Story To: "Randy Presuhn" Subject: Re: [Isms] #6: Are there are any wrinkles to coexistence withSNMPv1/v2c/USM? Message-ID: <20051108145851.71e30655@aud> In-Reply-To: <001a01c5d0f8$453b2ce0$7f1afea9@oemcomputer> References: <200510132149.RAA19807@ietf.org> <001a01c5d0f8$453b2ce0$7f1afea9@oemcomputer> X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.4.14; powerpc-yellowdog-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hosting.revelstone.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - revelstone.com X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: 7bit Cc: isms@ietf.org X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org On Fri, 14 Oct 2005 12:48:37 -0700 Randy wrote: RP> Someone should think through how proxy would work, or whether it would be RP> simpler to just say "don't do that". It would be simpler, but I don't think we should do that. I can definitely envision people wanting to put an SSHSM enabled device at/near the border of their network and have it proxy for their legacy v1/v2c/v3 devices inside the network. _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Tue Nov 08 15:47:57 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZaNp-0006ot-39; Tue, 08 Nov 2005 15:47:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZaNo-0006oo-K4 for isms@megatron.ietf.org; Tue, 08 Nov 2005 15:47:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02700 for ; Tue, 8 Nov 2005 15:47:29 -0500 (EST) Received: from hosting.revelstone.com ([66.36.242.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZadg-00086x-BT for isms@ietf.org; Tue, 08 Nov 2005 16:04:21 -0500 Received: from localhost ([127.0.0.1] helo=aud) by hosting.revelstone.com with smtp (Exim 4.52) id 1EZaNg-0001Ep-Mi; Tue, 08 Nov 2005 15:47:49 -0500 Date: Tue, 8 Nov 2005 15:48:03 -0500 From: Robert Story To: "Randy Presuhn" Subject: Re: [Isms] #1: is it important to support anonymous user accesstoSNMP? Message-ID: <20051108154803.155595a2@aud> In-Reply-To: <000e01c5d936$5e3c5200$7f1afea9@oemcomputer> References: <474EEBD229DF754FB83D256004D02108BBCA17@XCH-NW-6V1.nw.nos.boeing.com> <000e01c5d936$5e3c5200$7f1afea9@oemcomputer> X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.4.14; powerpc-yellowdog-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hosting.revelstone.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - revelstone.com X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: 7bit Cc: isms@ietf.org X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org On Tue, 25 Oct 2005 00:33:17 -0700 Randy wrote: RP> To make it really concrete, if we assume the security adminstrator is RP> reasonably sane, the permissions granted to "anonymous" would probably RP> be identical to those given to "public". The difference (with respect to RP> using "public" with USM or SNMPv1 or SNMPv2) is that the user could RP> have reasonable assurance that the data being retrieved was not tampered RP> with or spoofed, and, optionally, was protected from evesdroppers. This is exactly how I'd envision this being done, and I think it would be useful. _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Tue Nov 08 16:46:01 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZbI1-0001j4-PJ; Tue, 08 Nov 2005 16:46:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZbHy-0001hr-8a for isms@megatron.ietf.org; Tue, 08 Nov 2005 16:46:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07946 for ; Tue, 8 Nov 2005 16:45:30 -0500 (EST) Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZbXp-0001vq-Ro for isms@ietf.org; Tue, 08 Nov 2005 17:02:23 -0500 Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id jA8LjkCO027901; Tue, 8 Nov 2005 13:45:46 -0800 Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id jA8Ljct8018064; Tue, 8 Nov 2005 13:45:38 -0800 Received: from localhost (dperkins@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id jA8LjcBB018024; Tue, 8 Nov 2005 13:45:38 -0800 X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs Date: Tue, 8 Nov 2005 13:45:38 -0800 (PST) From: "David T. Perkins" X-Sender: dperkins@shell4.bayarea.net To: Robert Story Subject: Re: [Isms] #6: Are there are any wrinkles to coexistence withSNMPv1/v2c/USM? In-Reply-To: <20051108145851.71e30655@aud> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: isms@ietf.org X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org HI, In the past (which seems to repeat) when new SNMP technology is made available, then it is implemented first in managed devices, and only later in managers. And of course, there will always be managed devices that will never be updated. So, I believe that it is required that the following be supported: Manager<--SNMPv1,SNMPv2c,SNMPv3/USM-->PROXY<---SNMPv3/ISMS-->device On Tue, 8 Nov 2005, Robert Story wrote: > On Fri, 14 Oct 2005 12:48:37 -0700 Randy wrote: > RP> Someone should think through how proxy would work, or whether it would be > RP> simpler to just say "don't do that". > > It would be simpler, but I don't think we should do that. I can definitely > envision people wanting to put an SSHSM enabled device at/near the border of > their network and have it proxy for their legacy v1/v2c/v3 devices inside the > network. > Regards, /david t. perkins _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Tue Nov 08 18:09:22 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZcag-0002jY-9a; Tue, 08 Nov 2005 18:09:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZcaf-0002jQ-0Y for isms@megatron.ietf.org; Tue, 08 Nov 2005 18:09:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12463 for ; Tue, 8 Nov 2005 18:08:54 -0500 (EST) Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZcqX-00044H-Pq for isms@ietf.org; Tue, 08 Nov 2005 18:25:47 -0500 Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id jA8N9DCO019844 for ; Tue, 8 Nov 2005 15:09:13 -0800 Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id jA8N95pW011979 for ; Tue, 8 Nov 2005 15:09:05 -0800 Received: from localhost (dperkins@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id jA8N95H4011976 for ; Tue, 8 Nov 2005 15:09:05 -0800 X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs Date: Tue, 8 Nov 2005 15:09:05 -0800 (PST) From: "David T. Perkins" X-Sender: dperkins@shell4.bayarea.net To: isms@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: Subject: [Isms] Solution for "arch needs context engineID" X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org HI, Background: In SNMPv3, all messages include a "context engineID" field that specifies the "location" of management information identified by the variables in the varBindList of an SNMP message. When receiving an SNMP request, the value of the context engineID is used to determine if the receiving SNMP entity can process the message, or if the message is to be forwarded to another SNMP entity. (When an SNMP entity forwards a message, that entity is called an SNMP proxy agent. The SNMP entity that finally processes the message is called an SNMP target agent.) In most (if not all) SNMPv3/USM managers, managed systems have an associated set of attributes, which include: 1) transport address, 2) SNMPv3/USM user name, 3) security level (noAuthNoPriv, authNoPriv, authPriv) 4) the "authentication protocol" (such as "MD5" or "SHA") 5) the "privacy protocol" (such as "DES" or "AES") 6) the pass phrase _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Wed Nov 09 12:17:51 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZtVH-0002E4-TB; Wed, 09 Nov 2005 12:12:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZtVG-0002Dr-AZ for isms@megatron.ietf.org; Wed, 09 Nov 2005 12:12:54 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22583 for ; Wed, 9 Nov 2005 12:12:25 -0500 (EST) Resent-From: j.schoenwaelder@iu-bremen.de Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZtlH-0002Lm-9A for isms@ietf.org; Wed, 09 Nov 2005 12:29:29 -0500 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 72B674C138 for ; Wed, 9 Nov 2005 18:12:30 +0100 (CET) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 14309-02 for ; Wed, 9 Nov 2005 18:12:29 +0100 (CET) Received: from pp111-212.bctel.ca (unknown [10.222.1.1]) by hermes.iu-bremen.de (Postfix) with ESMTP id 070DB4C25F for ; Wed, 9 Nov 2005 18:12:29 +0100 (CET) Received: by pp111-212.bctel.ca (Postfix, from userid 501) id F38205277C6; Wed, 9 Nov 2005 18:12:25 +0100 (CET) Resent-Date: Wed, 9 Nov 2005 18:12:25 +0100 Resent-Message-ID: <20051109171225.GA5322@boskop.local> Resent-To: isms@ietf.org Received: from merkur.iu-bremen.de ([unix socket]) by merkur (Cyrus v2.2.12) with LMTPA; Wed, 09 Nov 2005 18:08:49 +0100 X-Sieve: CMU Sieve 2.2 Received: from hermes.iu-bremen.de (hermes.iu-bremen.de [212.201.44.23]) by merkur.iu-bremen.de (Postfix) with ESMTP id B96CC79E96E24 for ; Wed, 9 Nov 2005 18:08:49 +0100 (CET) Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id B65064C248 for ; Wed, 9 Nov 2005 18:08:49 +0100 (CET) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 13795-08 for ; Wed, 9 Nov 2005 18:08:48 +0100 (CET) Received: from boskop.local (pp111-212.bctel.ca [209.52.111.212]) by hermes.iu-bremen.de (Postfix) with ESMTP id 917F64C206 for ; Wed, 9 Nov 2005 18:08:47 +0100 (CET) Received: by boskop.local (Postfix, from userid 501) id 97D4B527782; Wed, 9 Nov 2005 18:08:22 +0100 (CET) Date: Wed, 9 Nov 2005 18:08:21 +0100 From: Juergen Schoenwaelder To: isms@ietf.org Message-ID: <20051109170821.GA5247@boskop.local> Mail-Followup-To: isms@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.10i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Status: No, hits=-4.9 tagged_above=-30.0 required=5.0 tests=BAYES_00 X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.1 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: Subject: [Isms] isms discussion/editing meeting on thursday X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: j.schoenwaelder@iu-bremen.de List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org Hi! The ISMS WG meeting yesterday has been useful in making progress on several open issues. However, there are still many issues we did not manage to discuss due to time contraints. To make some more progress, we have organized an editing/discussion meeting to take place on Thursday in the morning time slot 09:00 - 11:30 in room Capilano. We will open the isms@ietf.xmpp.org jabber room to take notes and we will report a summary of the conclusions reached in the meeting back to the mailing list. Those who are interested in ISMS and who are available on Thursday morning and hereby invited to join in and to help us move forward. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Wed Nov 09 13:33:30 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZulG-0001Lm-1A; Wed, 09 Nov 2005 13:33:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZulD-0001KX-Ul for isms@megatron.ietf.org; Wed, 09 Nov 2005 13:33:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28454 for ; Wed, 9 Nov 2005 13:32:59 -0500 (EST) Received: from sccrmhc14.comcast.net ([63.240.77.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZv1F-000586-SR for isms@ietf.org; Wed, 09 Nov 2005 13:50:03 -0500 Received: from djyxpy41 (pp105-206.bctel.ca[209.52.105.206]) by comcast.net (sccrmhc14) with SMTP id <20051109183310014002d88se>; Wed, 9 Nov 2005 18:33:16 +0000 From: "David B Harrington" To: , Subject: RE: [Isms] isms discussion/editing meeting on thursday Date: Wed, 9 Nov 2005 10:32:47 -0800 Message-ID: <001901c5e55c$070bc150$ce6934d1@DJYXPY41> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcXlUYn7nWafVPFpQAaO3sZUW83fhwACksHQ In-reply-to: <20051109170821.GA5247@boskop.local> X-Spam-Score: 0.1 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietfdbh@comcast.net List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org Hi, Note that this is an editing meeting. I request everybody to bring a copy of the SSHSM draft with them, since we will be discussing specific sections of the document. dbh > -----Original Message----- > From: isms-bounces@lists.ietf.org > [mailto:isms-bounces@lists.ietf.org] On Behalf Of Juergen > Schoenwaelder > Sent: Wednesday, November 09, 2005 9:08 AM > To: isms@ietf.org > Subject: [Isms] isms discussion/editing meeting on thursday > > Hi! > > The ISMS WG meeting yesterday has been useful in making progress on > several open issues. However, there are still many issues we did not > manage to discuss due to time contraints. > > To make some more progress, we have organized an editing/discussion > meeting to take place on Thursday in the morning time slot 09:00 - > 11:30 in room Capilano. We will open the isms@ietf.xmpp.org jabber > room to take notes and we will report a summary of the conclusions > reached in the meeting back to the mailing list. > > Those who are interested in ISMS and who are available on Thursday > morning and hereby invited to join in and to help us move forward. > > /js > > -- > Juergen Schoenwaelder International University Bremen > P.O. Box 750 561, > 28725 Bremen, Germany > > _______________________________________________ > Isms mailing list > Isms@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/isms > _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Sat Nov 19 12:43:30 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EdWkM-0005to-2Q; Sat, 19 Nov 2005 12:43:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EdWkK-0005tg-K3 for isms@megatron.ietf.org; Sat, 19 Nov 2005 12:43:28 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08865 for ; Sat, 19 Nov 2005 12:42:53 -0500 (EST) Received: from keymaster.sharplabs.com ([216.65.151.107] helo=sharplabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EdX2O-0007gN-Ss for isms@ietf.org; Sat, 19 Nov 2005 13:02:10 -0500 Received: from admsrvnt02.enet.sharplabs.com (admsrvnt02.enet.sharplabs.com [172.29.225.253]) by sharplabs.com (8.13.1/8.13.1) with ESMTP id jAJHh8Zx013636 for ; Sat, 19 Nov 2005 09:43:08 -0800 (PST) Received: by admsrvnt02.enet.sharplabs.com with Internet Mail Service (5.5.2657.72) id ; Sat, 19 Nov 2005 09:45:16 -0800 Message-ID: From: "McDonald, Ira" To: isms@ietf.org Date: Sat, 19 Nov 2005 09:45:14 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: Subject: [Isms] Info on compound authentication method problems X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org Hi, Below is a link to an expired I-D which contains a detailed discussion of the problems with using compound authentication methods, e.g., creation of a one-way authenticated tunnel (TLS, ISAKMP, etc.) with server-only authentication followed by use of any legacy client authentication method. http://www.watersprings.org/pub/id/draft-puthenkulam-eap-binding-04.txt Which is referenced by the new RFC 4169 "HTTP Digest Authentication Using AKAv2", which fixes the problems in Digest-AKAv1 (RFC 3310). ftp://ftp.isi.edu/in-notes/rfc4169.txt Recommended reading. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Sun Nov 20 16:00:45 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EdwIn-0006Ft-BV; Sun, 20 Nov 2005 16:00:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EdwIm-0006Fo-7L for isms@megatron.ietf.org; Sun, 20 Nov 2005 16:00:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13014 for ; Sun, 20 Nov 2005 16:00:07 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Edwb5-0004UA-0Z for isms@ietf.org; Sun, 20 Nov 2005 16:19:40 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-3.cisco.com with ESMTP; 20 Nov 2005 13:00:33 -0800 X-IronPort-AV: i="3.97,355,1125903600"; d="scan'208"; a="367882578:sNHT25082138" Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jAKL0XCJ028447; Sun, 20 Nov 2005 13:00:33 -0800 (PST) Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 20 Nov 2005 13:00:33 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Isms] Info on compound authentication method problems Date: Sun, 20 Nov 2005 13:00:32 -0800 Message-ID: <4C0FAAC489C8B74F96BEAD85EAEB2625010D35D4@xmb-sjc-215.amer.cisco.com> Thread-Topic: [Isms] Info on compound authentication method problems Thread-Index: AcXtMOTGH41DGs3oQmiFWQBn+ff7FwA4//DA From: "Glen Zorn \(gwz\)" To: "McDonald, Ira" , X-OriginalArrivalTime: 20 Nov 2005 21:00:33.0124 (UTC) FILETIME=[726A9A40:01C5EE15] X-Spam-Score: 2.2 (++) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org McDonald, Ira <> supposedly scribbled: > Hi, >=20 > Below is a link to an expired I-D which contains a detailed > discussion of the problems with using compound authentication > methods, e.g., creation of a one-way authenticated tunnel (TLS, > ISAKMP, etc.) with server-only authentication followed by use of any > legacy client authentication method. =20 >=20 > =20 > = http://www.watersprings.org/pub/id/draft-puthenkulam-eap-binding-04.txt >=20 > Which is referenced by the new RFC 4169 "HTTP Digest Authentication > Using AKAv2", which fixes the problems in Digest-AKAv1 (RFC 3310).=20 >=20 > ftp://ftp.isi.edu/in-notes/rfc4169.txt >=20 > Recommended reading. The former should be "recommended meeting" only if you like your = thinking fuzzy and your analysis flawed. >=20 > Cheers, > - Ira >=20 >=20 > Ira McDonald (Musician / Software Architect) Blue Roof Music / High > North Inc PO Box 221 Grand Marais, MI 49839=20 > phone: +1-906-494-2434 > email: imcdonald@sharplabs.com >=20 > _______________________________________________ > Isms mailing list > Isms@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/isms _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms From isms-bounces@lists.ietf.org Tue Nov 22 12:44:08 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EecBF-0004oO-ES; Tue, 22 Nov 2005 12:43:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EecBE-0004nE-4v for isms@megatron.ietf.org; Tue, 22 Nov 2005 12:43:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17299 for ; Tue, 22 Nov 2005 12:43:00 -0500 (EST) Received: from keymaster.sharplabs.com ([216.65.151.107] helo=sharplabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EecJ6-0007fv-Bm for isms@ietf.org; Tue, 22 Nov 2005 12:51:53 -0500 Received: from admsrvnt02.enet.sharplabs.com (admsrvnt02.enet.sharplabs.com [172.29.225.253]) by sharplabs.com (8.13.1/8.13.1) with ESMTP id jAMHVF8U008055; Tue, 22 Nov 2005 09:31:15 -0800 (PST) Received: by admsrvnt02.enet.sharplabs.com with Internet Mail Service (5.5.2657.72) id ; Tue, 22 Nov 2005 09:33:28 -0800 Message-ID: From: "McDonald, Ira" To: "'Glen Zorn (gwz)'" , "McDonald, Ira" , isms@ietf.org Subject: RE: [Isms] Info on compound authentication method problems Date: Tue, 22 Nov 2005 09:33:17 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Cc: X-BeenThere: isms@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the ISMS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isms-bounces@lists.ietf.org Errors-To: isms-bounces@lists.ietf.org Hi Glen, So, would you care to indicate _what_ is wrong with this analysis? I'm happy to be labelled a fool, but I'd be happier to know why. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com > -----Original Message----- > From: Glen Zorn (gwz) [mailto:gwz@cisco.com] > Sent: Sunday, November 20, 2005 4:01 PM > To: McDonald, Ira; isms@ietf.org > Subject: RE: [Isms] Info on compound authentication method problems > > > McDonald, Ira <> supposedly scribbled: > > > Hi, > > > > Below is a link to an expired I-D which contains a detailed > > discussion of the problems with using compound authentication > > methods, e.g., creation of a one-way authenticated tunnel (TLS, > > ISAKMP, etc.) with server-only authentication followed by use of any > > legacy client authentication method. > > > > > > > http://www.watersprings.org/pub/id/draft-puthenkulam-eap-bindi > ng-04.txt > > > > Which is referenced by the new RFC 4169 "HTTP Digest Authentication > > Using AKAv2", which fixes the problems in Digest-AKAv1 (RFC 3310). > > > > ftp://ftp.isi.edu/in-notes/rfc4169.txt > > > > Recommended reading. > > The former should be "recommended meeting" only if you like > your thinking fuzzy and your analysis flawed. > > > > > Cheers, > > - Ira > > > > > > Ira McDonald (Musician / Software Architect) Blue Roof Music / High > > North Inc PO Box 221 Grand Marais, MI 49839 > > phone: +1-906-494-2434 > > email: imcdonald@sharplabs.com > > > > _______________________________________________ > > Isms mailing list > > Isms@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/isms > _______________________________________________ Isms mailing list Isms@lists.ietf.org https://www1.ietf.org/mailman/listinfo/isms