Hi As a co-author, I support its adoption. We (DT) are currently testing an implementation of DHCPv4oDHCPv6 which includes the Source Address option with a plan to deploy. As this draft is predominantly concerned with changes to DHCPv4o6 client and server implementations, it seems logical to progress this in DHC.
Thanks, Ian > On 22 Feb 2017, at 18:37, Tomek Mrugalski <tomasz.mrugal...@gmail.com> wrote: > > Hi, > > This message initiates a two weeks long DHC WG adoption call on: > > Title: DHCPv4 over DHCPv6 Source Address Option > Pages: 9 > Date: 2017-02-01 > Document: draft-fsc-softwire-dhcp4o6-saddr-opt-07 > Link: tools.ietf.org/html/draft-fsc-softwire-dhcp4o6-saddr-opt-07 > > This document initially started as work intended to be adopted in > Softwires, but after a discussion with chairs, responsible AD (Suresh) > and presenting this work in DHC, the conclusion is to aim for DHC > adoption, not Softwires. Therefore this is a DHC adoption call. > > This message is cross-posted to Softwires to let Softwire experts weigh > in their opinion. Please be sure to post your comments to DHC list, > though. Comments sent by end of March 8th, 2017 are much appreciated. > > Bernie & Tomek > > _______________________________________________ > Softwires mailing list > Softwires@ietf.org > https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
