RE: [Isms]SSHSMRADIUSIntegrationdraft(draft-narayan-isms-sshsm-radius-01.txt)submitted

"Fleischman, Eric" <eric.fleischman@boeing.com> Tue, 20 March 2007 16:09 UTC

Return-path: <isms-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTgtl-0002gM-2x; Tue, 20 Mar 2007 12:09:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTgtk-0002ct-2P for isms@ietf.org; Tue, 20 Mar 2007 12:09:20 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56] helo=stl-smtpout-01.ns.cs.boeing.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTgtf-0006yR-EW for isms@ietf.org; Tue, 20 Mar 2007 12:09:19 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id l2KG99ks006796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 20 Mar 2007 11:09:09 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_RELAY) with ESMTP id l2KG99Ph028295; Tue, 20 Mar 2007 11:09:09 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id l2KG97Hf028226; Tue, 20 Mar 2007 11:09:08 -0500 (CDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Mar 2007 09:09:07 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Isms]SSHSMRADIUSIntegrationdraft(draft-narayan-isms-sshsm-radius-01.txt)submitted
Date: Tue, 20 Mar 2007 09:09:06 -0700
Message-ID: <474EEBD229DF754FB83D256004D0210802584E4C@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <618694EF0B657246A4D55A97E38274C3032CD04D@xmb-sjc-22d.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Isms]SSHSMRADIUSIntegrationdraft(draft-narayan-isms-sshsm-radius-01.txt)submitted
Thread-Index: AcdoBKMk4CxSVF/VRwKmI+D+3apyWQCReg0gAAqh8jAAJNAeQA==
References: <474EEBD229DF754FB83D256004D0210802584E3C@XCH-NW-6V1.nw.nos.boeing.com> <618694EF0B657246A4D55A97E38274C3032CD04D@xmb-sjc-22d.amer.cisco.com>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: kaushik@cisco.com, j.schoenwaelder@iu-bremen.de
X-OriginalArrivalTime: 20 Mar 2007 16:09:07.0208 (UTC) FILETIME=[16585080:01C76B0A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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 <isms.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/isms>
List-Post: <mailto:isms@lists.ietf.org>
List-Help: <mailto:isms-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=subscribe>
Errors-To: isms-bounces@lists.ietf.org

Kaushik,

Yes, I am aware that my suggestions for a default PKI and
username/password authentication basis correlates well with a SSHv2
transport (and RADIUS) and that there are O/S implications to source
code. 

However, the itch that I want scratched is that I want ISMS to include a
viable default solution to key management so that the currently onerous
problem with key distribution in large SNMPv3 deployments would be
solved for ISMS. It's not enough to provide RFCs offering theoretical
solutions. The specs themselves need to create default interoperable
products that adequately (i.e., securely, scalably) handle key
distribution issues. [By "key distribution" I am not solely considering
symmetric and asymmetric keys, but also include the issue of secure
username/password distribution.]

--Eric


_______________________________________________
Isms mailing list
Isms@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/isms