[dhcwg] Re: DHC Agenda for IETF122 in Bangkok

Hi Michael,

Currently we do not have any specific suggestions for RFC8415bis as a
result of our plugfest--most of the issues we observed resulted from a lack
of support from the implementations, rather than issues we found with the
draft itself. That being said, there were some instances of seemingly
undefined behavior that we will touch on during our presentation; perhaps
this will motivate specific draft suggestions after discussions with the
rest of the group.

DHCPv6-PD was in the original scope for the plugfest, but like many other
specific features/configurations, there was a significant lack of support
that caused us to omit these test cases from our results.
draft-ietf-v6ops-cpe-lan-pd-06 was not included in this plugfest.

Of course, we will provide much more information during our presentation,
but let us know if there are any other specific questions we can answer
beforehand.

Thanks,
Spencer

On Thu, Mar 6, 2025 at 1:24 PM Michael Richardson <[email protected]> wrote:

> > Virtual DHCPv6 (8415) Plugfest Results 10 mins
> > UNH-IOL
>
> I'm excited to hear about this.
> Is there anything that RFC8415bis needs to do?
>
> Are there further things that did not work that we ought to, in this
> transition to IS, obsolete, or at least caution against?
>
> (Does this plugfest include DHCPv6-PD?  What about
> draft-ietf-v6ops-cpe-lan-pd-06 ??)
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT
> architect   [
> ]     [email protected]  http://www.sandelman.ca/        |   ruby on
> rails    [
>
> _______________________________________________
> dhcwg mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>


-- 

Spencer Couture UNH InterOperability Laboratory 21 Madbury Rd, Suite 100,
Durham, NH 03824 [email protected]

_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]