Re: Mac OS X 10.7, still no DHCPv6

[Mark Andrews <marka () isc org>]

In message <CA58D5C5-3826-4DA8-BCC6-5057AB912D5C () delong com>, Owen DeLong writes:
> On Feb 27, 2011, at 2:39 PM, Mark Andrews wrote:
>
> > =20
> > In message <20110227204511.GM27578 () virtual bogons net>, Simon Lockhart =
> writes:
> > > On Mon Feb 28, 2011 at 07:22:08AM +1100, Mark Andrews wrote:
> > > > > This is often required for legislation compliance. DHCP does this =
> well.
> > > > =20
> > > > Does it really matter what address a customer has as long as it =
> comes from
> > > > the /64, /56 or /48 assigned to them?
> > > =20
> > > You are assuming an access technology that lends itself to =
> subnet-per-custome
> > > r.
> > > =20
> > > I run a network with 50,000+ end users using ethernet-based access to =
> the
> > > user's room. In IPv4, I run 1 or more subnets per building (depending =
> on the=20
> > > number of rooms in the build). I use DHCP to assign IPs, and record =
> the=20
> > > DHCP assignments allow me to trace users in the event of abuse =
> complaints. I
> > > use DHCP Option82 to allow me to correlate multiple devices in a =
> user's room.
> > > I feed the DHCP information into my bandwidth management platform to =
> enforce
> > > different levels (i.e. speeds) of service per user depending on what =
> they've
> > > purchased.
> > > =20
> > > I have yet to come up with a viable solution to do all of the above =
> in IPv6
> > > without using DHCPv6. At the moment, that means that OSX users are =
> not going
> > > to get IPv6.
> > =20
> > Have you *asked* your vendors for a alternate solution?
> > =20
> > DHCP kills privacy addresses.
>
> In many environments, this is a feature, not a bug.
>
> > DHCP kills CGAs.
> > =20
> In many environments, this is a feature, not a bug.
>
> I would, in fact, posit that some of the people complaining about the =
> lack of
> DHCP are doing so precisely because of a desire to kill these things in =
> their
> environment.
>
> Owen

Sure there are some envionments where it is a feature.  But in many
you really don't care what address the machine gets.  You are
actually looking for to tie the address(mac) to a accounting record
and DHCP is the only currently available solution and rather than
look for a better solution DHCP is being used.

One could have the machine generate its own addresses and register
them using DHCP.  You get the accounting without throwing out the
ability to do things like privacy addresses and CGA.  The DHCP
server can also prevent the machine using a reserved address for
the few things on the net that need it.  You also get IPv6 reverse
maintenance thrown in for free.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka () isc org