IETF Last Call Review of draft-ietf-v6ops-rfc6146-bis-07
review-ietf-v6ops-rfc6146-bis-07-artart-lc-levine-2026-06-28-00
review-ietf-v6ops-rfc6146-bis-07-artart-lc-levine-2026-06-28-00
ARTART last call review of draft-ietf-v6ops-rfc6146-bis Reviewer: John Levine Overall: Ready with Issues Figure 1 is scrambled. It looks like it was intended to be two large boxes representing IPv6 and IPv4 networks connected by smaller boxes for DNS64 and NAT64. But the right edge of the IPv6 box runs through the middle of the small boxes. There is a vertical line under the k in "IPv6 network" that might have been intended to be the right edge of the IPv6 box but isn't. This figure is unchanged from RFC 6146 where it was equally scrambled, which makes me wonder when was the last time somone really looked at it. Both this figure and Figure 2, which appears correct but is complex and confusing, could benefit from being redrawn as real figures using SVG tools. The security considerations should say something about DNS64 and DNSSEC, since the synthesized AAAA records are not and cannot be signed. There are workarounds but none of them are great. RFC 6147 Section 3 discusses this issue so it could refer there. I have looked at Tony Li's review and while I am not as sceptical of IPv6 as he is, I generally agree with the changes he proposed.