Re: [Isms] charter proposal

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Tue, 02 August 2005 20:01 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E02we-0008QA-3F; Tue, 02 Aug 2005 16:01:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E02wc-0008NJ-P7 for isms@megatron.ietf.org; Tue, 02 Aug 2005 16:00:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14805 for <isms@ietf.org>; Tue, 2 Aug 2005 16:00:56 -0400 (EDT)
Received: from tui75-2-82-229-178-125.fbx.proxad.net ([82.229.178.125] helo=boskop.local) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E03TA-0000JR-Ke for isms@ietf.org; Tue, 02 Aug 2005 16:34:36 -0400
Received: by boskop.local (Postfix, from userid 501) id 34C253A1DA8; Tue, 2 Aug 2005 22:00:43 +0200 (CEST)
Date: Tue, 02 Aug 2005 22:00:42 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Kaushik Narayan <kaushik@cisco.com>
Subject: Re: [Isms] charter proposal
Message-ID: <20050802200042.GC7546@boskop.local>
Mail-Followup-To: Kaushik Narayan <kaushik@cisco.com>, ietfdbh@comcast.net, isms@ietf.org
References: <20050802170625.GA7466@open-31-253.ietf63.ietf.org> <200508021721.NAA06692@ietf.org> <6.2.0.14.0.20050802102835.0360c218@email.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.2.0.14.0.20050802102835.0360c218@email.cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: isms@ietf.org
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 <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>
Sender: isms-bounces@lists.ietf.org
Errors-To: isms-bounces@lists.ietf.org

On Tue, Aug 02, 2005 at 10:52:03AM -0700, Kaushik Narayan wrote:

> I am not sure we need elaborate AAA work in order to allow for
> linkages between ISMS authentication and SNMPv3 VACM.
> Ideally the RADIUS work for this should happen in RADEXT
> and I believe Dave Nelson and Greg Weber already have an
> ID that would be relevant.
> 
> http://www.ietf.org/internet-drafts/draft-nelson-radius-management-authorization-01.txt

This is indeed interesting and highly relevant work. I do, however,
believe that (if we go down this road) we need to specify when exactly
such authorization information is retrieved, how long it is valid and
how such an external source of authorization information fits into the
RFC 3411 model.

I am also not sure the implementation specific textual formats
described in the ID cited above which convey authorization information
are particularily useful for interoperability, but that might be a
less important detail at this point in time.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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