RE: [midcom] More on new work item

"Christopher A. Martin" <chris@sip1.com> Mon, 26 April 2004 22:47 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01251 for <midcom-archive@odin.ietf.org>; Mon, 26 Apr 2004 18:47:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIEo6-00078J-6t for midcom-archive@odin.ietf.org; Mon, 26 Apr 2004 18:42:34 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3QMgYAx027408 for midcom-archive@odin.ietf.org; Mon, 26 Apr 2004 18:42:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIEhk-0005xy-Q0; Mon, 26 Apr 2004 18:36:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIEbH-0004lG-Jt for midcom@optimus.ietf.org; Mon, 26 Apr 2004 18:29:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00208 for <midcom@ietf.org>; Mon, 26 Apr 2004 18:29:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIEbE-0002iz-IU for midcom@ietf.org; Mon, 26 Apr 2004 18:29:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIEaK-0002ft-00 for midcom@ietf.org; Mon, 26 Apr 2004 18:28:20 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BIEZa-0002cq-00 for midcom@ietf.org; Mon, 26 Apr 2004 18:27:34 -0400
Received: from adsl-64-219-190-5.dsl.rcsntx.swbell.net ([64.219.190.5] helo=voyager.sip1.com) by mx2.foretec.com with esmtp (Exim 4.24) id 1BIEZb-0002gZ-E7 for midcom@ietf.org; Mon, 26 Apr 2004 18:27:35 -0400
Received: from HOME2 (adsl-64-219-190-1.dsl.rcsntx.swbell.net [64.219.190.1]) by voyager.sip1.com (8.12.8/8.12.8) with ESMTP id i3QNWdw9007638; Mon, 26 Apr 2004 18:32:40 -0500
Reply-To: Chris@sip1.com
From: "Christopher A. Martin" <chris@sip1.com>
To: 'Jonathan Rosenberg' <jdrosen@dynamicsoft.com>, 'Melinda Shore' <mshore@cisco.com>
Cc: midcom@ietf.org
Subject: RE: [midcom] More on new work item
Date: Mon, 26 Apr 2004 17:26:44 -0500
Organization: SIP1 Information Services
Message-ID: <009901c42bdd$8ea7b9a0$6402a8c0@HOME2>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <408D754C.5080708@dynamicsoft.com>
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I totally agree with Jonathan's position on the scope of DHCP as
outlined below. 

Either way though, IMHO, MIDCOM does not appear to be useful for
anything other than a carrier deployment or in a large enterprise
deployment that controls all aspects of a MIDCOM deployment, just from a
business/security policy perspective. I say this due to the very points
brought up in Jonathans last sentence WRT configuring the NAT IP.

Chris

-----Original Message-----
From: midcom-admin@ietf.org [mailto:midcom-admin@ietf.org] On Behalf Of
Jonathan Rosenberg
Sent: Monday, April 26, 2004 3:47 PM
To: Melinda Shore
Cc: midcom@ietf.org
Subject: Re: [midcom] More on new work item

I'm not sure we should take on these work items. My concerns are mostly 
practical.

I think we agree that DHCP applicability is only in very, very limited 
topologies - only in simple stub networks where an end user client would

normally directly talk to a nat. This would really be limited to 
consumers with home nats, or to enterprises. I think its unlikely that 
an enterprise would actually allow end clients to control the nat, due 
to the serious potential for abuse (imagine a virus infecting a PC, 
causing it to ask the middlebox to open all ports to all addresses). As 
such, I dont think this is workable in enterprise.

That leaves home NAT. However, do we think that manufacturers of such 
devices are likely to support midcom? I'd like to hear from one on this 
list. If not, this work item would be useful only in theory. Even if 
they did, how would we expect the clients to be configured with the 
security credentials needed to exercise midcom control over their nat? 
If such information is manually configured into the client, why can't 
you manually configure the IP of the home NAT as well?

Thanks,
Jonathan R.

Melinda Shore wrote:

> There's been no feedback on the proposed charter change, which
concerns
> me.  I hope that people will speak up regardless of whether they think
> the proposed work item is a good idea or a bad idea.
> 
> I don't think getting the work done would be an issue - there are
> always people willing to author documents.  However, getting people
> to *review* documents is far more difficult, and I don't think we can
> allow work to go forward if we don't have a reasonable expectation
> that people with subject area expertise - in this case, the midcom
> working group - are willing to take the time to provide expert review
> as the document is progressed.  I don't want to make any assumptions
> about what the lack of feedback means, so even a simple "yes" or "no"
> on the proposed work item would be much appreciated.
> 
> Thanks,
> 
> Melinda
> 
> 
> _______________________________________________
> midcom mailing list
> midcom@ietf.org
> https://www1.ietf.org/mailman/listinfo/midcom
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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


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