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 1EKIKW-0006In-Uq; Tue, 27 Sep 2005 12:29:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKIKV-0006Ia-2J 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 MAA24404 for <call-home@ietf.org>; Tue, 27 Sep 2005 12:29:16 -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-0002XO-73 for call-home@ietf.org; Tue, 27 Sep 2005 12:36:50 -0400
Received: by boskop.local (Postfix, from userid 501) id 66931408A3A; Tue, 27 Sep 2005 16:32:10 +0200 (CEST)
Date: Tue, 27 Sep 2005 16:32:10 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Wes Hardaker <wjhns1@hardakers.net>
Subject: Re: [Call-home] draft now posted; BoF?
Message-ID: <20050927143210.GB1586@boskop.local>
References: <4337FBB5.4010701@cisco.com> <20050926210654.GA3067@boskop.local> <43391200.1020806@cisco.com> <sdy85iocsw.fsf@wes.hardakers.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <sdy85iocsw.fsf@wes.hardakers.net>
User-Agent: Mutt/1.5.10i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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 06:33:35AM -0700, Wes Hardaker wrote:

> [...] but the current protocols (SSH, TLS) don't do this.  They are
> designed with a particular order of sending the credentials and they
> all expect the model above.  Whether you can trigger them to do the
> reverse is subject to a huge debate with their authors I'd think.

My understanding of SSH is that both parties send an identification
string after connection establishment. Once that has happened, both
parties start the key exchange process by sending SSH_MSG_KEXINIT and
they both know their client/server role due to the way the TCP
connection was established. What I like to know is whether something
would break (and what) if the client/server role was not necessarily
bound to the TCP connection setup.

I am not saying SSH people will like this or that this whole idea is
worth anything at this point in time - I am just trying to explore the
solution space. On the other hand, if the call home feature could be
supported by a rather small change to SSH, then all SSH based
management interfaces could benefit from this and the only thing to be
dealt with is to identify the transport enpoints to which to call home.

/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