[dhcwg] Re: 8415bis

Tim has volunteered to apply these fixes, otherwise the document really is ready to go and shepherd review can occur now, so if any nits (or issues) are found they can be addressed as part of the next version - which is hopefully sent to AD/IESG.

So, I think the ball is really in Suresh’s court … unless he is no longer willing to shepherd and we can search for another. The shepherd work for this document is really to do the shepherd write up document … we will continue to work on this should AD or IESG (last call) issues arrise, so shepherd really isn’t critical for those phases. Though sadly we do move a bit slower than many of us would like!

- Bernie (from iPad)

> On Sep 18, 2024, at 6:37 PM, Michael Richardson <[email protected]> wrote:
> 
> 
> Bernie Volz <[email protected]> wrote:
>> Hi … is it time to work on getting the 8415bis draft moving to
>> publication (close WGLC as still open, do
>> shepherd write-up, …)? It has been 2 weeks since IETF meeting.
> 
>> I did have a few minor nits with the -05 … see
> 
> It seems like we just need to push some buttons.
> 
> Reviews shouldn't be significant, unless reviewers insist on re-opening
> things from 8415.    Who can drive this, if Bernie, as an author, is
> reluctant.  Is Suresh the shepherd? Yes.
> 
> state is: Revised I-D Needed - Issue raised by WG
> 
> are there github issues that I've missed?
> 
> I'm open to a design team meeting to walk through the issues.
> 
> --
> Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> <signature.asc>

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