Re: [dhcwg] DHCPv6 Stateful Issues

Hi Tim:

I too would have expected just the IA_NA (IAADDR) to be declined. You don't mention what the clients are doing in this case (sending a Decline with both the IA_NA and IA_PD or sending a Release with both - or sending a Decline for the IA_NA and Release for the IA_PD)?

A DAD conflict should result in a Decline. So, it would seem to me that the added step of sending a Release for the IA_PD (IAPREFIX) is extra effort and not necessary/warranted. And I would hope these clients aren't sending a Decline for the IA_PD (IAPREFIX).

Also, did the routers doing the IA_PD Release earlier request the IA_NA and IA_PD in the same packet (transaction) or different ones?

Be nice if you had a packet trace available to see what the interaction here is?

This does sound like a candidate for discussion in the draft, but we need a bit more information before considering to add it.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Timothy Winters
Sent: Monday, February 03, 2014 12:07 PM
To: dhcwg@ietf.org WG
Subject: [dhcwg] DHCPv6 Stateful Issues

Hi Bernie,
	While testing some IPv6 CE Router I've noticed an issue that this draft might want to address.  When a DHCP Client receives both the IA_NA and IA_PD in the reply, the Client performs DAD on the IA_NA.   If DAD fails some implementations keep the IA_PD and try for a different IA_NA.   Other IPv6 CE Routers will Release the IA_PD in this scenario.  

	 I would think the proper thing to do would be to keep the IA_PD so your LAN as addressing.   Is something that we can talk about in this document?

~Tim

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg