Re: [Fwd: I-D Action: draft-carpenter-6man-why64-00.txt]

[Ray Hunter <[e-mail]>]

> Tim Chown <mailto:[e-mail]>
> 9 January 2014 17:32
>
> I;m not sure you're defining what your problem is fully enough here.
>
> What's wrong with polling network devices to maintain a database of 
> IP/MAC/port bindings? Some reasonably sized campuses with IPv6 
> deployed do just that, on the assumption devices can effectively pick 
> their own addresses and/or change them over time.
>
> Tim

I'd also probably consider that on a campus, which is geographically 
limited, there's no latency, network devices are uniform, there's a 
single management vendor, SNMP access is allowed, and bandwidth is free.

DHCP (which is effectively a form of event-triggered central 
registration) works pretty well today. Two people can support all global 
IPAM, DHCP, and DNS for 100K users in 50 countries. All you need is the 
lowest common denominator of a DHCP proxy on any LAN equipment pointing 
at your regional servers, and a DHCP client on end user devices, which 
is basically universally supported. And you can lever that information 
up in all sorts of ways. DHCPv6 would not be cost impacting (part of 
licensing on existing kit). Anything else would be. You're not going to 
be able to get any less than 2 support people for this sort of 
enterprise critical infra. Off topic for this ID, but just saying.

The bottom line is that sparse addressing in IPv6, as implemented today, 
also has a down side for enterprise operations; but perhaps that 
discussion should be held in v6ops.

-- 
Regards,
RayH