Re: [Dhcpv6bis] WGLC review of draft-ietf-dhc-rfc3315bis-08

Fred:

We (a few of the coauthors) decided to leave this be.

Our reason was that in most cases, the network between clients and servers are not the Internet and so there's much more (administrative) control over this. And, to our knowledge, there hasn't been any report of problems.

- Bernie

-----Original Message-----
From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] 
Sent: Tuesday, June 20, 2017 2:01 PM
To: Bernie Volz (volz) <volz@cisco.com>; Ralph Droms <rdroms.ietf@gmail.com>
Cc: Timothy Winters <twinters@iol.unh.edu>; dhcpv6bis@ietf.org
Subject: RE: [Dhcpv6bis] WGLC review of draft-ietf-dhc-rfc3315bis-08

Hi Bernie,

In my on-list WGLC post, I said:

> I read the entire document, and have only one comment. In section 
> 18.3, the
> sentence:
> 
>   “The server must be aware of the recommendations on packet sizes and the
>     use of fragmentation in Section 5 of [RFC2460].”
>
> Suggest changing this to:
>
>   “The server must honor the recommendations on packet sizes and the
>     use of fragmentation in Section 5 of [RFC2460].”

However, I think an even more appropriate phrasing would be:

  “The server must observe the recommendations on packet sizes and the
    use of fragmentation in Section 5 of [RFC2460].”

My rationale is that "must be aware of" is too weak, and an implication could choose to "be aware" of the recommendations but then ignore them with no fears that something bad might happen. Conversely, the phrase "must observe" strongly implies that the recommendations are there to be followed, and bad things can happen if they are not followed.

Thanks - Fred

> -----Original Message-----
> From: Dhcpv6bis [mailto:dhcpv6bis-bounces@ietf.org] On Behalf Of 
> Bernie Volz (volz)
> Sent: Wednesday, June 14, 2017 7:54 PM
> To: Ralph Droms <rdroms.ietf@gmail.com>
> Cc: Timothy Winters <twinters@iol.unh.edu>; dhcpv6bis@ietf.org
> Subject: Re: [Dhcpv6bis] WGLC review of draft-ietf-dhc-rfc3315bis-08
> 
> See 
> https://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis-08#section-1.1 
> and https://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis-
> 08#appendix-A.
> 
> On 6/14/17, 6:41 PM, "Ralph Droms" <rdroms.ietf@gmail.com> wrote:
> 
>     Asking for any opinions - can you characterize the changes in 
> rfc3315bis?  For example, integration of RFCs published after RFC 3315, fixes to bugs in RFC 3315, editorial improvements, ???
> 
>     - Ralph
> 
>     > On Jun 14, 2017, at 9:08 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
>     >
>     > Tomek, Ralph, and I met to review the open issues 
> (seehttps://docs.google.com/spreadsheets/d/10e00zAlqlR58NSsZfmxshv5tr7
> 6Ea3pyGyDpll8eDLA/edit?usp=sharing). We ran out of time for the last 
> few (row 25 and up), but Tomek will take a look at this and update the 
> sheet with comments. Input on these (25 and
> up) or comments about earlier ones we evaluated if you have a difference of opinion are welcome.
>     >
>     > The plan is to get the 09 out shortly (definitely before the IETF-99 deadline, July 3rd) and Ralph will do the WGLC consensus call.
>     >
>     > (If anyone wants write access to the document, let me know and I will set you up to have write access.)
>     >
>     > 	• Bernie
>     >
>     > From: Dhcpv6bis <dhcpv6bis-bounces@ietf.org> on behalf of Timothy Winters <twinters@iol.unh.edu>
>     > Date: Wednesday, June 14, 2017 at 8:12 AM
>     > To: "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>
>     > Subject: Re: [Dhcpv6bis] WGLC review of draft-ietf-dhc-rfc3315bis-08
>     >
>     > I'm trapped in a customer emergency (IPv6 testing over 4G)!   Let me know if you need anything from me.
>     >
>     > ~Tim
>     >
>     > On Wed, Jun 7, 2017 at 2:54 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
>     >> Hi:
>     >>
>     >> There were 4 WGLC responses with comments (as I write this). 
> While we can skip the typos and other simple corrections, there may be a few issues worth discussing.
>     >>
>     >> Therefore, Tomek and I propose to use our old Wednesday 0800 
> EDT (1200 UT) time slot to review those issues worth discussing to finalize the set of changes for an -09.
>     >>
>     >> We request Ralph to attend as he needs to provide a consensus 
> call (since another WGLC was done) – I will send him a note under separate cover.
>     >>
>     >> I plan to make many of the minor edits (as I already have 
> started a few) and also pull together an open issues list and distribute before the meeting. But, it is a PLAN not a certainty.
>     >>
>     >> To assist you, here are I believe the links to the emails with comments:
>     >> ·         Re: [dhcwg] WGLC for draft-ietf-dhc-rfc3315bis-08 - Respond by June 6th, 2017, Templin, Fred L
>     >> ·         Re: [dhcwg] WGLC for draft-ietf-dhc-rfc3315bis-08 - Respond by May 30th, 2017, kkinnear
>     >> ·         Re: [dhcwg] WGLC for draft-ietf-dhc-rfc3315bis-08 - Respond by May 30th, 2017, 神明達哉
>     >> ·         Re: [dhcwg] WGLC for draft-ietf-dhc-rfc3315bis-08 - Respond by May 30th, 2017, Bernie Volz (volz)
>     >> ·         Re: [dhcwg] WGLC for draft-ietf-dhc-rfc3315bis-08 - Respond by May 30th, 2017, 神明達哉
>     >> ·         Re: [dhcwg] WGLC for draft-ietf-dhc-rfc3315bis-08 - Respond by May 30th, 2017, Bernie Volz (volz)
>     >> ·         Tomek & Bernie
>     >>
>     >>
>     >> -- Do not delete or change any of the following text. --
>     >>
>     >>
>     >> Join WebEx meeting
>     >> Meeting number: 204 592 394
>     >> Meeting password: M5kZiPci (65594724 from phones)
>     >>
>     >>
>     >> Join from a video conferencing system or application
>     >> Dial 204592394@cisco.webex.com
>     >> From the Cisco internal network, dial *267* and the 9-digit meeting number. If you are the host, enter your PIN when prompted.
>     >>
>     >>
>     >> If you are a host, go here to view host information.
>     >>
>     >> Join by phone
>     >> +1-866-432-9903 Call-in toll-free number (US/Canada)
>     >> +1-408-525-6800 Call-in toll number (US/Canada)
>     >> Access code: 204 592 394
>     >> Global call-in numbers  |  Toll-free calling restrictions
>     >>
>     >>
>     >> Can't join the meeting? Contact support.
>     >>
>     >> IMPORTANT NOTICE: Please note that this WebEx service allows 
> audio and other information sent during the session to be recorded, 
> which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session..
>     >> ·
>     >> ·
>     >>
>     >> _______________________________________________
>     >> Dhcpv6bis mailing list
>     >> Dhcpv6bis@ietf.org
>     >> https://www.ietf.org/mailman/listinfo/dhcpv6bis
>     >>
>     >
>     >
>     >
>     > --
>     > Now offering testing for SDN applications and controllers in our SDN switch test bed. Learn more today http://bit.ly/SDN_IOLPR
>     >
>     > _______________________________________________
>     > Dhcpv6bis mailing list
>     > Dhcpv6bis@ietf.org
>     > https://www.ietf.org/mailman/listinfo/dhcpv6bis
> 
> 
> 
> _______________________________________________
> Dhcpv6bis mailing list
> Dhcpv6bis@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcpv6bis