RE : [midcom] More on new work item
"Joel Tran" <joel.tran@USherbrooke.ca> Thu, 29 April 2004 15:47 UTC
Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10080 for <midcom-archive@odin.ietf.org>; Thu, 29 Apr 2004 11:47:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJDaG-00013l-HG for midcom-archive@odin.ietf.org; Thu, 29 Apr 2004 11:36:20 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3TFaKvN004073 for midcom-archive@odin.ietf.org; Thu, 29 Apr 2004 11:36:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJDMU-00062u-JZ; Thu, 29 Apr 2004 11:22:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJDEQ-00045a-UA for midcom@optimus.ietf.org; Thu, 29 Apr 2004 11:13:46 -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 LAA08468 for <midcom@ietf.org>; Thu, 29 Apr 2004 11:13:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BJDEM-00033z-Pd for midcom@ietf.org; Thu, 29 Apr 2004 11:13:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BJDDM-0002mL-00 for midcom@ietf.org; Thu, 29 Apr 2004 11:12:41 -0400
Received: from smtpi1.usherbrooke.ca ([132.210.244.92]) by ietf-mx with esmtp (Exim 4.12) id 1BJDCa-0002RX-00 for midcom@ietf.org; Thu, 29 Apr 2004 11:11:52 -0400
Received: from kamel (traj1901.gel.usherb.ca [132.210.72.178]) by smtpi1.usherbrooke.ca (8.12.10/8.12.10) with ESMTP id i3TF5b8R012587; Thu, 29 Apr 2004 11:05:37 -0400
From: Joel Tran <joel.tran@USherbrooke.ca>
To: 'Jonathan Rosenberg' <jdrosen@dynamicsoft.com>, 'Melinda Shore' <mshore@cisco.com>
Cc: midcom@ietf.org
Subject: RE : [midcom] More on new work item
Date: Thu, 29 Apr 2004 11:05:21 -0400
Message-ID: <000601c42dfb$648eae10$b248d284@kamel>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <408D754C.5080708@dynamicsoft.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-UdeS-i-MailScanner-Information: Veuillez consulter le http://www.usherbrooke.ca/vers/virus-courriel
X-UdeS-i-MailScanner: Aucun code suspect détecté
X-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.9, requis 5, autolearn=not spam, BAYES_00 -4.90)
X-MailScanner-From: joel.tran@usherbrooke.ca
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
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>
Jonathan Rosenberg, you raised a good point. There are however some ISPs that are deploying NAT/Firewall (i.e. China, Europe, Africa). In such case, DHCP might be useful. The ISP might do some load balancing. Thus, DHCP method will provide a mean for the ISP to configure dynamically third-end party devices. As for the security information, this might be entered by the user to the third-end party device (ex: same id/password as for the ADSL authentication). ...J > -----Message d'origine----- > De : midcom-admin@ietf.org [mailto:midcom-admin@ietf.org] De > la part de Jonathan Rosenberg > Envoyé : 26 avril, 2004 16:47 > À : Melinda Shore > Cc : midcom@ietf.org > Objet : 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
- [midcom] More on new work item Melinda Shore
- Re: [midcom] More on new work item Jonathan Rosenberg
- RE: [midcom] More on new work item Christopher A. Martin
- Re: [midcom] More on new work item Melinda Shore
- RE : [midcom] More on new work item Joel Tran
- Re: RE : [midcom] More on new work item Jonathan Rosenberg
- Re: RE : [midcom] More on new work item Joel Tran
- Re: RE : [midcom] More on new work item Jonathan Rosenberg
- Re: RE : [midcom] More on new work item Joel Tran
- Re: RE : [midcom] More on new work item Melinda Shore
- Re: RE : [midcom] More on new work item Jonathan Rosenberg
- RE : RE : [midcom] More on new work item Joel Tran
- Re: RE : RE : [midcom] More on new work item Melinda Shore
- RE: RE : RE : [midcom] More on new work item Christian Huitema
- RE : RE : [midcom] More on new work item Joel Tran
- Re: RE : RE : [midcom] More on new work item Jonathan Rosenberg