Re: [Isms] ISMS charter broken- onus should be on WG to fix it

Sam Hartman <hartmans-ietf@mit.edu> Tue, 13 September 2005 19:34 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFGYG-0005in-Sg; Tue, 13 Sep 2005 15:34:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFFZk-0003ck-8P; Tue, 13 Sep 2005 14:32:16 -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 OAA05456; Tue, 13 Sep 2005 14:31:59 -0400 (EDT)
Received: from carter-zimmerman.mit.edu ([18.18.3.197]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFFe0-00015T-5b; Tue, 13 Sep 2005 14:36:37 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id 49DF2E0049; Tue, 13 Sep 2005 14:31:54 -0400 (EDT)
To: <ietfdbh@comcast.net>
References: <200509131506.j8DF664A016810@pacific-carrier-annex.mit.edu>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Tue, 13 Sep 2005 14:31:54 -0400
In-Reply-To: <200509131506.j8DF664A016810@pacific-carrier-annex.mit.edu> (David B. Harrington's message of "Tue, 13 Sep 2005 11:05:49 -0400")
Message-ID: <tslhdcokeed.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: d6b246023072368de71562c0ab503126
Cc: david.kessens@nokia.com, isms@ietf.org, iesg@ietf.org, 'Eliot Lear' <lear@cisco.com>, 'IETF Discussion' <ietf@ietf.org>
Subject: Re: [Isms] ISMS charter broken- onus should be on WG to fix it
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

>>>>> "David" == David B Harrington <ietfdbh@comcast.net> writes:

    David> Hi, Personally, I'd rather see the issue of working through
    David> NATs and firewalls solved at the SSH level, and then SNMP
    David> and other SSH-using applications, such as Netconf and CLI,
    David> could use the solution in a consistent manner.


I think that the ssh connection application already has a fairly
reasonable story for NATs and firewalls, so I don't see much of a need
for ssh itself to advance in this area.  

For the most part people who block port 22 really do intend to block
ssh and so having standard facilities to get around that would not be
appropriate.  The port forwarding support in ssh seems to be an
adequate solution for NATs.

SNMP can use these facilities certainly.  However you may want/need a
more automated solution.

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