[dhcwg] RE: mboned: draft-jdurand-assign-addr-ipv6-multicast-dhcpv6-00 comments

"Dave Thaler" <dthaler@windows.microsoft.com> Wed, 04 August 2004 22:26 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14681; Wed, 4 Aug 2004 18:26:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BsU4o-0002cx-F0; Wed, 04 Aug 2004 18:17:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BsTv4-0005iM-TM for dhcwg@megatron.ietf.org; Wed, 04 Aug 2004 18:07:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12455 for <dhcwg@ietf.org>; Wed, 4 Aug 2004 18:07:32 -0400 (EDT)
Received: from mail1.microsoft.com ([131.107.3.125]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsTyR-0001JA-Jp for dhcwg@ietf.org; Wed, 04 Aug 2004 18:11:03 -0400
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.196); Wed, 4 Aug 2004 15:05:14 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 4 Aug 2004 15:05:13 -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); Wed, 4 Aug 2004 15:05:03 -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); Wed, 4 Aug 2004 15:04:42 -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
Date: Wed, 4 Aug 2004 15:03:10 -0700
Message-ID: <C9588551DE135A41AA2626CB645309370A77212E@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: mboned: draft-jdurand-assign-addr-ipv6-multicast-dhcpv6-00 comments
thread-index: AcR6blEdPChd+JtyS1yNAR0ROWUZ4AAAEL+w
From: "Dave Thaler" <dthaler@windows.microsoft.com>
To: "Jerome Durand" <jdurand@renater.fr>
X-OriginalArrivalTime: 04 Aug 2004 22:04:42.0317 (UTC) FILETIME=[0B5317D0:01C47A6F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable
Cc: dhcwg@ietf.org, mboned@lists.uoregon.edu
Subject: [dhcwg] RE: mboned: draft-jdurand-assign-addr-ipv6-multicast-dhcpv6-00 comments
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

 -----Original Message-----
> From: Jerome Durand [mailto:jdurand@renater.fr]
> Sent: Wednesday, August 04, 2004 6:01 AM
> To: Dave Thaler
> Cc: dhcwg@ietf.org; mboned@lists.uoregon.edu
> Subject: Re: mboned:
draft-jdurand-assign-addr-ipv6-multicast-dhcpv6-00
> comments
> 
> > 1) One of the things that both the API and the MADCAP protocol
provide
> > is
> > allocation of ranges (not "several", but a large number of
addresses,
> > like
> > a block of 400).  This requirement came from applications which want
a
> > larger range to use with things like
> > a) hashing resource ids into groups (I can't remember the specific
> > examples here, but IANA often gets requests for blocks of space, and
I
> > believe many of them are for this reason.  Dave Meyer can probably
> > correct me :),
> > b) assignment to areas inside virtual worlds (from customers in the
DIS
> > industry),
> 
> I don't beleive we really need this feature. A company that wants
plenty
> of addresses can be allocated manually for example a block. But can be
> added to the specs. (prefix delegation for IPv6 multicast address
could
> be the answer)

To be clear, this has nothing to do with company requests.
This was about _application_ requests from the server's address space.

-Dave

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