[dhcwg] Mirja Kühlewind's No Objection on draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Wed, 15 February 2017 10:03 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148715302215.17389.14651452070558302618.idtracker@ietfa.amsl.com>
Date: Wed, 15 Feb 2017 02:03:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/ArFKZkghbC_DIIyRPzg6GLMWrN0>
Cc: dhc-chairs@ietf.org, volz@cisco.com, dhcwg@ietf.org, draft-ietf-dhc-dhcpv6-prefix-length-hint-issue@ietf.org
Subject: [dhcwg] Mirja Kühlewind's No Objection on draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05: (with COMMENT)

Mirja Kühlewind has entered the following ballot position for
draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-prefix-length-hint-issue/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I think it would make sense if this doc updates RFC 3633 because someone
who (newly) implements RFC 3633 should really also read this document and
hance needs this pointer.

Also, I would move section 3.6 to the beginning but that doesn't really
matter.

[dhcwg] Mirja Kühlewind's No Objection on draft-i… Mirja Kuehlewind
Re: [dhcwg] Mirja Kühlewind's No Objection on dra… tianxiang li