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

 -----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