Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router

[David Farmer <[e-mail]>]

On Thu, Sep 6, 2018 at 3:33 PM, Brian E Carpenter <
[e-mail]> wrote:

> On 2018-09-07 02:24, Tim Chown wrote:
> >> On 6 Sep 2018, at 14:01, Lorenzo Colitti <lorenzo=40google.com@dmarc.
> ietf.org> wrote:
> >>
> >> On Wed, Sep 5, 2018 at 11:09 PM Owen DeLong <[e-mail]> wrote:
> >> Further, I don’t believe for one second that ALL enterprises will
> require or use DHCPv6. Perhaps most, but certainly not all.
> >>
> >> +1. Ours doesn't.
> >
> > And the requirement/use of configuration method, especially at a
> university campus, may vary between managed desktops and WiFi/eduroam where
> BYOD is the norm.
>
> If you base admission to the wired network on registered MAC addresses,
> which
> is quite common, there seems to be no particular reason to waste resources
> on DHCPv6 even for managed devices.
>

Well not entirely true. It is common to base admission on registered MAC
addresses. However, if you also want a strong binding between MAC address
and IP address to be enforced with SAVI then DHCPv4 or v6 is still useful.
If you use SLAAC you really only have a First-Come-First-Serve(FCFS)
binding methodology SAVI. FCFS will work in a lot of cases but it is not as
strong of a binding as DHCP.

We have a broad set of tools for a broad set of environments. Some tools
are appropriate in some environments and other tools are not. IPv6 needs to
work in every situation, from wide-open wifi, as in free love wifi, to a
nuclear control room and most networks are someplace in between those two.

-- 
===============================================
David Farmer               Email:[e-mail]
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: [phone]
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================