<div dir="ltr">The real problem is there are distinct use cases for both SLAAC and DHCPv6 and the people in charge of DHCPv6 keep screwing up. It should be possible to run either SLAAC/RA or DHCPv6 and have each offering provide the required information without having to run additional services just to get basic feature parity to IPv4. This is slowing implementation in enterprise networks.<div><br></div><div>james<br><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 31, 2020 at 3:24 PM Brian E Carpenter <<a href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 31-Mar-20 23:17, Mark Tinka wrote:<br>
> <br>
> <br>
> On 31/Mar/20 12:09, <a href="mailto:sthaug@nethelp.no" target="_blank">sthaug@nethelp.no</a> wrote:<br>
> <br>
>> Note that there have been multiple requests for DHCPv6 to do this but<br>
>> every attempt has been shot down.<br>
> <br>
> Yep - thankfully, we have an option.<br>
> <br>
> Operating two address assignment protocols is just silly.<br>
> <br>
> At my house, I don't even bother with DHCPv6 for DNS. I just use the<br>
> IPv4 ones and let SLAAC assign IPv6 addresses to my devices. Just about<br>
> done with the purist madness around this.<br>
<br>
There's purism (which I don't understand) and there's also historical<br>
baggage that is incredibly hard to get rid of. As I have reminded from<br>
time to time, SLAAC was designed and implemented for IPv6 *before* DHCP<br>
became a proven technology for IPv4 (i.e. many of us were still running<br>
around manually assigning IPv4 addresses to newly installed Suns and<br>
NCDs and the like). DHCPv6 was an afterthought.<br>
<br>
Unfortunately, the purism has made it impossible to have a rational<br>
discussion about engineering our way out of this historical duplication.<br>
<br>
On 01-Apr-20 05:01, Gert Doering wrote:<br>
<br>
...<br>
> As soon as you have a larger routed network, mDNS falls short, and <br>
> (unless you have a windows domain) there are no existing mechanisms<br>
> to put a SLAAC v6 address into DNS...<br>
<br>
I think there's no *deployed* mechanism. DynDNS is said to work in the<br>
lab. There's also some hope that DNS-SD will alleviate this problem, <br>
but only if it gets deployed.<br>
<br>
> Yes, thanks, IETF. Well done.<br>
<br>
It's not because nobody has tried. But the bridge between theory and<br>
operations seems to be hard to cross.<br>
<br>
On 01-Apr-20 07:21, James R Cutler wrote:<br>
<br>
...<br>
> Wouldn’t it be more cost effect in the long term to simply make SLAAC and DHCPv6 cooperative and complementary attributes of end-to-end networking? <br>
<br>
Well, duh. What we need is more people with real operational smarts<br>
able to spend a lot of time and patience in the IETF. Yes, I know<br>
why that is hard. (I had operation smarts once; no longer.) But that<br>
is the only way we we can get a pragmatic approach into RFC text.<br>
<br>
Don't worry about the travel budget, because the IETF is going to<br>
have to do much more of its work remotely for the next couple of years<br>
anyway. But the time and patience investment is substantial.<br>
<br>
Stay well,<br>
Brian Carpenter<br>
<br>
<br>
<br>
</blockquote></div>