Re: [Call-home] draft now posted; BoF?

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Tue, 27 September 2005 16:29 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKIKX-0006JC-6M; Tue, 27 Sep 2005 12:29:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKIKV-0006If-HI for call-home@megatron.ietf.org; Tue, 27 Sep 2005 12:29:19 -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 MAA24409 for <call-home@ietf.org>; Tue, 27 Sep 2005 12:29:17 -0400 (EDT)
Received: from ia53e.i.pppool.de ([85.73.165.62] helo=boskop.local) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKIRm-0002XP-5A for call-home@ietf.org; Tue, 27 Sep 2005 12:36:51 -0400
Received: by boskop.local (Postfix, from userid 501) id 8D072408731; Tue, 27 Sep 2005 11:58:33 +0200 (CEST)
Date: Tue, 27 Sep 2005 11:58:33 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Eliot Lear <lear@cisco.com>
Subject: Re: [Call-home] draft now posted; BoF?
Message-ID: <20050927095833.GB488@boskop.local>
References: <4337FBB5.4010701@cisco.com> <20050926210654.GA3067@boskop.local> <43391200.1020806@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43391200.1020806@cisco.com>
User-Agent: Mutt/1.5.10i
X-Spam-Score: 0.6 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: call-home@ietf.org
X-BeenThere: call-home@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: "Discussion of issues relating to &quot; call home&quot; functionality and firewall traversal" <call-home.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/call-home>, <mailto:call-home-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/call-home>
List-Post: <mailto:call-home@ietf.org>
List-Help: <mailto:call-home-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/call-home>, <mailto:call-home-request@ietf.org?subject=subscribe>
Sender: call-home-bounces@ietf.org
Errors-To: call-home-bounces@ietf.org

On Tue, Sep 27, 2005 at 11:33:52AM +0200, Eliot Lear wrote:
 
> I'm not quite sure what you're asking for.  Are you suggesting, for
> instance, that the initiator have a host key and the listener make use
> of a user key?

I am asking for a solution which gives me the same authenticated
identities regardless how the connection was established. In SNMP
terms, I assume that an engine hosting a command generator identifies
itself as a user on the engine hosting the command responder and I
like to leverage this user identity which does exist on the device
across multiple management interfaces, whether that is a CLI, NETCONF
or even an HTTP interface.

Looking at the real-world networking devices I have access to, they
all have a notion of a user identity and they all are able to talk
RADIUS to outsource the authentication decision, which is typically
then password based. I like to leverage that and if call home can be
made to work without changing the premise I am operating on, I am
fine.

/js

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

_______________________________________________
Call-home mailing list
Call-home@ietf.org
https://www1.ietf.org/mailman/listinfo/call-home