Re: [dhcwg] Reminder - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 22nd

[Kim Kinnear <[e-mail]>]

I have read this document, and reviewed it lightly (minor comments below).
I commend the folks that worked on it for their efforts, and strongly
support its moving forward in the standards process.

My comments:

1.2 Seems odd that v4 should be used for v4, not v6, but then RFC7341 is quoted.
Left up to the reader to decide what to do?  Some guidance might be useful here.
 
5.2 First sentence.  Perhaps "... and is the "stateful address autnconfiguration protocol"  
for IPv6 which is discussed in [RFC2462]." would better
   
5.4 Figure 1.  I would replace "DSL to subscriber..." with "Network link to subscriber...". 
Or someething like that.  I think DSL isn't going to aid understanding now or into the
future.
 
13.1  First paragraph.  "This loops can repeat ..." -> "This loop can repeat..."
 
13.2 "Client MUST choose..." -> "Clients MUST choose ..."
 
15. I think that "A server MUST discard any Solicit ..." should be "A server SHOULD discard ..."
MUST seems overly restrictive to me, despite being in RFC3315. Not that I expect anyone to
change it based on this comment...

17. Second paragraph after the list. "... solicitation process to obtain the bindings from a..."
-> "... solictation process to obtain the same bindings from a ..."

17.1  I would remove "DISCUSSION:" and just make this a regular paragraph.

17.1.1 "The client MUST include an Option Request option ..." but section 20.7 says
"MAY" include an Option Request option.  The implication in 17.1.1 is that you
have to have an ORO with SOL_MAX_RT in it, or ... what, exactly, will happen?   
Packet dropped?  Seems like either MUST -> MAY, or some additional clarity would
be good here.  This is in 17.1.2 as well.

17.1.11 Here the "DISCUSSION" seems appropriate.  Not clear why that seems to be
the case, as opposed to 17.1.

20.7 "... or the will not ..." -> "... or they will not ..."

Regards -- Kim


> On Aug 15, 2016, at 9:26 AM, Bernie Volz (volz) <[e-mail]> wrote:
> 
> Hi:
> 
> Just a friendly reminder that this (extended) WGLC is scheduled to end in a week (August 22nd).
> 
> Thanks much to all those that have responded so far!!
> 
> - Bernie
> 
> -----Original Message-----
> From: dhcwg [mailto:[e-mail]] On Behalf Of Bernie Volz (volz)
> Sent: Monday, August 08, 2016 9:38 AM
> To: dhcwg <[e-mail]>
> Subject: [dhcwg] Extended - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 22nd
> 
> Hi:
> 
> In discussions with Ralph and Tomek, we have decided to extend the WGLC for this document by 2 weeks. So comments are due Monday 8/22.
> 
> Thanks to all those that have sent review comments so far!!!
> 
> - Bernie (for Ralph and Tomek)
> 
> -----Original Message-----
> From: dhcwg [mailto:[e-mail]] On Behalf Of Bernie Volz (volz)
> Sent: Thursday, July 28, 2016 11:14 AM
> To: dhcwg <[e-mail]>
> Subject: [dhcwg] Reminder - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 8th
> 
> Hi:
> 
> Just a reminder about this WGLC ... please review and respond by August 8th. For a reminder as to the goals and key areas of change, please see https://www.ietf.org/proceedings/96/slides/slides-96-dhc-2.pdf.
> 
> As a reminder, the following people agreed to review during WGLC:
> 
>> From https://www.ietf.org/proceedings/95/minutes/minutes-95-dhc:
> 
>    Volunteers for review: Ted Lemon, Bernie Volz, Mohammed Boucadair, Tim Winters, 
>    Tim Chown, Francis Dupont, Paul Ebersman
>    Co-authors (who are supposed to review without explicitly voluneering): Bernie Volz,
>    Sheng Jiang, Marcin Siodelski,
>    Ian - I also volunteered to review
> 
> And, at IETF-96:
> 
>   Yogendra Pal volunteered to review the draft.
> 
> Thanks much!
> 
> - Bernie
> 
> -----Original Message-----
> From: dhcwg [mailto:[e-mail]] On Behalf Of Tomek Mrugalski
> Sent: Friday, July 08, 2016 1:03 PM
> To: dhcwg <[e-mail]>
> Subject: [dhcwg] WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 8th
> 
> Hi all,
> 
> So the day finally has come. Authors working on RFC3315bis believe that after over two years of work, this document is ready for working group last call. This call initiates the working group last call on
> draft-ietf-dhc-rfc3315bis-05 [1]. Since this is a large document (130+ pages), there's upcoming meeting and a holiday period, chairs decided to do an extended last call that will last 4 weeks. Please post your comments by August 8th.
> 
> We do have a slot reserved for this work in Berlin. We will present the overview of the document (some areas are organized differently than original 3315), go over the most important changes and will discuss any comments raised to date.
> 
> If you would like to review more important changes, looking at appendices A anb B seems like a good place to start. If you like to see the list of tickets addressed, see [2]. Many smaller issues were discussed on dhcpv6bis mailing list [3].
> 
> This is the most important document the DHC working group is currently working on. Please review it thoroughly. Since both co-chairs are also co-authors, our shepherd, Ralph Droms, will determine consensus and wrap up the WGLC. Thank you Ralph for stepping up and helping with this!
> 
> 1. https://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis-05
> 2. https://tools.ietf.org/group/dhcpv6bis/
> 3. https://www.ietf.org/mailman/listinfo/dhcpv6bis
> 
> Cheers,
> Bernie & Tomek
> 
> _______________________________________________
> dhcwg mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dhcwg