RE: [midcom] Possible new work item

"Harrington, David" <dbh@enterasys.com> Tue, 04 May 2004 21:20 UTC

Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00210 for <midcom-archive@odin.ietf.org>; Tue, 4 May 2004 17:20:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7HN-0000yT-Cq for midcom-archive@odin.ietf.org; Tue, 04 May 2004 17:16:41 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i44LGfK0003745 for midcom-archive@odin.ietf.org; Tue, 4 May 2004 17:16:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL786-0006lJ-Fs; Tue, 04 May 2004 17:07:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL74F-0005jf-Jv for midcom@optimus.ietf.org; Tue, 04 May 2004 17:03:07 -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 RAA29127 for <midcom@ietf.org>; Tue, 4 May 2004 17:03:04 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL74D-0007Uy-EN for midcom@ietf.org; Tue, 04 May 2004 17:03:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL73I-0007Nj-00 for midcom@ietf.org; Tue, 04 May 2004 17:02:08 -0400
Received: from gtfw2.enterasys.com ([12.25.1.128] ident=firewall-user) by ietf-mx with esmtp (Exim 4.12) id 1BL72s-0007GO-00 for midcom@ietf.org; Tue, 04 May 2004 17:01:42 -0400
Received: from NHROCAVG2.ets.enterasys.com (nhrocavg2.enterasys.com [134.141.79.124]) by gtfw2.enterasys.com (0.25.1/8.12.6) with ESMTP id i44L1eTm003804 for <midcom@ietf.org>; Tue, 4 May 2004 17:01:41 -0400 (EDT)
Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.124]) by 134.141.79.124 with InterScan Messaging Security Suite; Tue, 04 May 2004 17:01:41 -0400
Received: from source ([134.141.79.122]) by host ([134.141.79.124]) with SMTP; Tue, 04 May 2004 17:01:41 -0400
Received: from nhrocmbx1 ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 4 May 2004 17:01:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.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: [midcom] Possible new work item
Date: Tue, 04 May 2004 17:01:35 -0400
Message-ID: <6D745637A7E0F94DA070743C55CDA9BA01977678@NHROCMBX1.ets.enterasys.com>
Thread-Topic: [midcom] Possible new work item
Thread-Index: AcQopCWIkMzoMjH3ScmhXL+uagyCUwJdmdrA
From: "Harrington, David" <dbh@enterasys.com>
To: Melinda Shore <mshore@cisco.com>, midcom@ietf.org
Cc: rdroms@cisco.com
X-OriginalArrivalTime: 04 May 2004 21:01:41.0813 (UTC) FILETIME=[FFF6F650:01C4321A]
X-pstn-version: pmps:sps_win32_1_1_0c1 pase:2.5
X-pstn-levels: (C:84.0661 M:98.8113 P:95.9108 R:95.9108 S:99.9000 )
X-pstn-settings: 4 (0.2500:0.7500) p:13 m:13 C:14 r:13
X-pstn-addresses: from <dbh@enterasys.com> forward (org good)
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

Hi Melinda,

I'd be more supportive if one or more persons had actually done an
implementation and found it useful in practice (you know, rough
consensus and running code). Otherwise this is purely speculation that
it might be useable and useful to somebody sometime. That doesn't sound
like a good justification to me.

dbh

> -----Original Message-----
> From: midcom-admin@ietf.org [mailto:midcom-admin@ietf.org] On 
> Behalf Of Melinda Shore
> Sent: Thursday, April 22, 2004 3:04 PM
> To: midcom@ietf.org
> Cc: rdroms@cisco.com
> Subject: [midcom] Possible new work item
> 
> As was discussed here several weeks ago, there's a proposal for midcom
> to add new deliverables - DHCP and DHCPv6 options to 
> configure middlebox
> addresses into endpoints.  If we were to undertake the work, we'd be
> working with the dhc working group (expert review) and ideally we'd
> be able to get a volunteer from that group to work with the editor of 
> the
> deliverable.  I've appended some proposed charter text.  The two
> questions are:
> 
> 1) do we want to take on the work, and
> 2) is the proposed charter paragraph okay?
> 
> Thanks,
> 
> Melinda
> 
> 
> The working group will also produce documents describing DHCP and
> DHCPv6 options for configuring middlebox addresses into endpoints.
> These are not a replacement for a more sophisticated routing or
> discovery mechanism, but may prove useful in simple network topologies
> where network endpoints are making requests directly of middleboxes
> rather than relying on third parties, such as call control servers, to
> make middlebox requests on their behalf.
> 
> 
> _______________________________________________
> 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