that is making sense to clients under isp, DNS, mail, dhcpv6 and, ... dhcpv4 ranges domains crazily being used widely , none a little tendency to stop at the may 2020 when ietf.org claimed THE IPV6 ONLY at the day, it is may 15 2020.
would the IPv6.Only is auto, forced , willing way or else may please let know ?
Sincerely
Li HUANG
On Tue, May 12, 2020, 14:50 Roni Even via Datatracker <noreply@xxxxxxxx> wrote:
Reviewer: Roni Even
Review result: Ready with Nits
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more information, please see the FAQ at
<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
Document: draft-ietf-dhc-mac-assign-??
Reviewer: Roni Even
Review Date: 2020-05-11
IETF LC End Date: 2020-05-19
IESG Telechat date: Not scheduled for a telechat
Summary:
The document is ready for publication as a standard track RFC with nits
Major issues:
Minor issues:
Nits/editorial comments:
1. In the terminology section I was wondering why the client is a device while
the server is a software. Any reason for this distinction.
2. The server can allocate a smaller size chunk and not the requested size. The
allocation policy is up to the server. Should it be required from the server to
allocate the largest chunk that is closer to the requested size.
_______________________________________________
dhcwg mailing list
dhcwg@xxxxxxxx
https://www.ietf.org/mailman/listinfo/dhcwg
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
