Re: ISMS working group and charter problems

Sam Hartman <hartmans-ietf@mit.edu> Thu, 08 September 2005 19:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDS6Y-0000rA-JU; Thu, 08 Sep 2005 15:30:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDS6V-0000pX-VR for ietf@megatron.ietf.org; Thu, 08 Sep 2005 15:30:36 -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 PAA13759 for <ietf@ietf.org>; Thu, 8 Sep 2005 15:30:33 -0400 (EDT)
Received: from carter-zimmerman.dyn.mit.edu ([18.188.3.148] helo=carter-zimmerman.mit.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDS9x-0005ok-5g for ietf@ietf.org; Thu, 08 Sep 2005 15:34:09 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id B3E97E0049; Thu, 8 Sep 2005 15:30:28 -0400 (EDT)
To: Tom Petch <nwnetworks@dial.pipex.com>
References: <200509081520.IAA02206@cisco.com> <00a101c5b49c$5e913680$0601a8c0@pc6>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 08 Sep 2005 15:30:28 -0400
In-Reply-To: <00a101c5b49c$5e913680$0601a8c0@pc6> (Tom Petch's message of "Thu, 8 Sep 2005 19:39:04 +0200")
Message-ID: <tslirxbnyqz.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Keith McCloghrie <kzm@cisco.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: ISMS working group and charter problems
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>>>>> "Tom" == Tom Petch <nwnetworks@dial.pipex.com> writes:

    Tom> I think that there is subtext that is missing here.

    Tom> Call Home was declared out of scope, more or less, for isms
    Tom> before the decision to use SSH was taken (the suggestion was
    Tom> made on the isms list to set up a BOF in the Operations Area
    Tom> to explore Call Home).  

I'm not sure this is accurate, but I don't think it matters.

    Tom> The significance is that SSH is not
    Tom> perceived as a good fit for Call Home, whereas a different
    Tom> protocol, seen as less suitable in other regards, might be.
    Tom> So if the community at large comes to regard Call Home as a
    Tom> mandatory requirement, then that would be construed as saying
    Tom> that SSH is the wrong protocol (which may be what this
    Tom> discussion is really about:-).

I don't believe that it is true that ssh is not perceived as a good
fit for call home.  I think the strongest statement I've seen in that
regard is that ssh is not the solution netconf chose for call home, so
we might end up with incompatible solutions if ISMS chooses a
different solution than netconf.

Note that the mandatory to implement solution for netconf is based on
ssh and does not support call home.


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf