IETF Logo Mail Archive

Re: ISMS working group and charter problems

Eliot Lear <lear@cisco.com> Tue, 06 September 2005 18:43 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECiQJ-0002WC-O3; Tue, 06 Sep 2005 14:43:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECiQG-0002W5-SV for ietf@megatron.ietf.org; Tue, 06 Sep 2005 14:43:56 -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 OAA12706 for <ietf@ietf.org>; Tue, 6 Sep 2005 14:43:55 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECiTH-0005An-Cw for ietf@ietf.org; Tue, 06 Sep 2005 14:47:04 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 06 Sep 2005 11:43:46 -0700
X-IronPort-AV: i="3.96,172,1122879600"; d="scan'208"; a="658457179:sNHT31620892"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j86Ihh0J004267; Tue, 6 Sep 2005 11:43:44 -0700 (PDT)
Received: from [212.254.247.4] (ams-clip-vpn-dhcp4272.cisco.com [10.61.80.175]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j86IcwEd030106; Tue, 6 Sep 2005 11:38:59 -0700
Message-ID: <431DE35D.5070305@cisco.com>
Date: Tue, 06 Sep 2005 20:43:41 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <431DD3BD.9090108@cisco.com> <3221221C-DBBA-4DE8-AF04-98D3D822644A@muada.com>
In-Reply-To: <3221221C-DBBA-4DE8-AF04-98D3D822644A@muada.com>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=742; t=1126031940; x=1126464140; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=lear@cisco.com; z=Subject:Re=3A=20ISMS=20working=20group=20and=20charter=20problems| From:Eliot=20Lear=20<lear@cisco.com>| Date:Tue,=2006=20Sep=202005=2020=3A43=3A41=20+0200| Content-Type:text/plain=3B=20charset=3DISO-8859-1| Content-Transfer-Encoding:7bit; b=SiHorLg7x2mV6QY1nas5mlTXIDKA8filLmvdT8vGUJJRukinauBmtqoblq2tZXjJbHT/Ws9b +VXINJjpNtrNCiTZDtWrNMKjWupnOFcqbQDDY8jumwolr9gHeTjTmTI5uc/0aeHm4n9HHTiCyFa coIvY44CZFuTu4ix7JnFDgjw=
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: NANOG list <nanog@merit.edu>, 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

Hi Iljitsch,

> On 6-sep-2005, at 19:37, Eliot Lear wrote:
> 
>> I seek a change to the proposed ISMS charter that requests the working
>> group pay attention to firewall and NAT concerns.  The current
>> envisioned approach will not work through firewalls
> 
> 
> I consider the fact that random people across the internet can't  manage
> my equipment a feature rather than a bug.

Use of a well known port that you can block will actually make it EASIER
for you to make use of that "feature".  Today if you leave your PC up
with various forms of commercial software, you have no idea who is
connecting to what.

> The IETF has been doing extensive work on NAT traversal, have a look 
> and see if you can reuse some existing mechanism.

All mechanisms used with the possible exception of an additional SNMP
table will be re-used from existing IETF work (mostly SSH with help from
the fact that it's based on TCP).

Eliot

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

v2.23.0 | Report a Bug | By Email