IETF Logo Mail Archive

RE: RE : RE : [midcom] More on new work item

"Christian Huitema" <huitema@windows.microsoft.com> Mon, 03 May 2004 17:05 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14051 for <midcom-archive@odin.ietf.org>; Mon, 3 May 2004 13:05:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKght-0004DW-Uq for midcom-archive@odin.ietf.org; Mon, 03 May 2004 12:54:18 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i43GsHHa016187 for midcom-archive@odin.ietf.org; Mon, 3 May 2004 12:54:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKgZv-0001LU-HO; Mon, 03 May 2004 12:46:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKgPA-00072m-0Q for midcom@optimus.ietf.org; Mon, 03 May 2004 12:34:56 -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 MAA11652 for <midcom@ietf.org>; Mon, 3 May 2004 12:34:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKgP8-0005ii-Dp for midcom@ietf.org; Mon, 03 May 2004 12:34:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKgOI-0005db-00 for midcom@ietf.org; Mon, 03 May 2004 12:34:03 -0400
Received: from mail4.microsoft.com ([131.107.3.122]) by ietf-mx with esmtp (Exim 4.12) id 1BKgNC-0005TX-00 for midcom@ietf.org; Mon, 03 May 2004 12:32:54 -0400
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 3 May 2004 09:32:21 -0700
Received: from 157.54.8.155 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 03 May 2004 09:32:23 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 3 May 2004 09:31:33 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 3 May 2004 09:32:33 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069); Mon, 3 May 2004 09:32:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RE : RE : [midcom] More on new work item
Date: Mon, 03 May 2004 09:32:14 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA08CB3AE8@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: RE : RE : [midcom] More on new work item
Thread-Index: AcQxJPcdUfzKOeaHTLetzWz6JwjN1gABu97Q
From: Christian Huitema <huitema@windows.microsoft.com>
To: Joel Tran <joel.tran@USherbrooke.ca>, Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: midcom@ietf.org, Melinda Shore <mshore@cisco.com>
X-OriginalArrivalTime: 03 May 2004 16:32:11.0084 (UTC) FILETIME=[2F0BC8C0:01C4312C]
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
Content-Transfer-Encoding: quoted-printable
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: quoted-printable

> I think now we are at a turn point in the discussion where we have do
> decide whatever we need or not DHCP or another mechanism for midcom.

Based on the discussion so far, I believe the answer is: No. The domains
of applicability of DHCP and Midcom have an almost empty intersection,
and adding another standard to the mix is not going to help.

-- Christian Huitema

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

v2.23.0 | Report a Bug | By Email