IETF Logo Mail Archive

Re: ISMS working group and charter problems

Eliot Lear <lear@cisco.com> Mon, 12 September 2005 10:52 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EElvc-00068F-I4; Mon, 12 Sep 2005 06:52:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EElvV-00066l-8f for ietf@megatron.ietf.org; Mon, 12 Sep 2005 06:52:46 -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 GAA10186 for <ietf@ietf.org>; Mon, 12 Sep 2005 06:52:30 -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 1EElzY-0007vG-Gy for ietf@ietf.org; Mon, 12 Sep 2005 06:56:52 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 12 Sep 2005 03:52:24 -0700
X-IronPort-AV: i="3.97,99,1125903600"; d="scan'208"; a="659252915:sNHT32043888"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8CAqHKC007355; Mon, 12 Sep 2005 03:52:18 -0700 (PDT)
Received: from [212.254.247.4] (ams-clip-vpn-dhcp377.cisco.com [10.61.65.121]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j8CB50uH012464; Mon, 12 Sep 2005 04:05:02 -0700
Message-ID: <43255DE1.2030405@cisco.com>
Date: Mon, 12 Sep 2005 12:52:17 +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: Brian E Carpenter <brc@zurich.ibm.com>
References: <431DD3BD.9090108@cisco.com> <431DD94C.8070907@dcrocker.net> <261A1E9D259E6FA3B9203B61@B50854F0A9192E8EC6CDA126> <431EB020.8090101@zurich.ibm.com>
In-Reply-To: <431EB020.8090101@zurich.ibm.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=616; t=1126523103; x=1126955303; 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:Mon,=2012=20Sep=202005=2012=3A52=3A17=20+0200| Content-Type:text/plain=3B=20charset=3DISO-8859-1| Content-Transfer-Encoding:7bit; b=EEbUrahXCxBEMlXx2dce7IAVJFRctOaa8ivRt32iw/w/HNjOkLRLy9r3QMUO8AfuqaxcNlQJ GVL5P6piWIKfg4PVJTL0Asf7LaAQfEuBpiAT8vEetmZg0CoU2GKlTkBYpz2c+j1MRaw7rjVWlsL 5kZ7winuNoqn3AaOmTD6wLpM=
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: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, dcrocker@bbiw.net, 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

Brian,

> "Call home" is IMHO a fairly radical departure for SNMP and
> raises trust model questions that I don't find easy to get
> hold of. It seems quite distinct from both firewall traversal
> and NAT traversal, conceptually, even if they might be
> a side-effect of calling home.

I do not believe - nor have I seen document demonstrating that - you can
practicably achieve the two classic functional goals of query/response
and unsolicited notification without implementing CH in the face of a
firewall/NAT.

Another way of putting it is that if firewalls are to be dealt with (and
in this day and age we should presume this), this functionality has been
prematurely ruled out of scope and must be considered in order to that
need ANYWAY.

Eliot

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

v2.23.0 | Report a Bug | By Email