Skip to main content

IETF Last Call Review of draft-ietf-v6ops-framework-md-ipv6only-underlay-23
review-ietf-v6ops-framework-md-ipv6only-underlay-23-genart-lc-bryant-2026-06-24-00

Request Review of draft-ietf-v6ops-framework-md-ipv6only-underlay
Requested revision No specific revision (document currently at 24)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2026-06-22
Requested 2026-06-08
Authors Chongfeng Xie , Chenhao Ma , Xing Li , Gyan Mishra , Thomas Graf
I-D last updated 2026-07-01 (Latest revision 2026-07-01)
Completed reviews Opsdir Early review of -23 by Tim Chown (diff)
Secdir Early review of -22 by Chris M. Lonvick (diff)
Intdir Early review of -23 by Tatuya Jinmei (diff)
Tsvart IETF Last Call review of -23 by Brian Trammell (diff)
Genart IETF Last Call review of -23 by Stewart Bryant (diff)
Assignment Reviewer Stewart Bryant
State Completed
Request IETF Last Call review on draft-ietf-v6ops-framework-md-ipv6only-underlay by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/i_Y31d5IjmXxA3o1j5qTfECxx_0
Reviewed revision 23 (document currently at 24)
Result Ready w/issues
Completed 2026-06-24
review-ietf-v6ops-framework-md-ipv6only-underlay-23-genart-lc-bryant-2026-06-24-00
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://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-v6ops-framework-md-ipv6only-underlay-23
Reviewer: Stewart Bryant
Review Date: 2026-06-24
IETF LC End Date: 2026-06-22
IESG Telechat date: Not scheduled for a telechat

Summary: I am reviewing from a GENART perspective and with this perspective I
think the text of the draft should reassure me that this unconditionally works
for any legitimate IPv4 protocol stack and any legitimate operation of that
protocol stack.

The draft adequately describes how an IPv4 packet is sent and delivered over an
IPv6 network at the network layer but IPv4/6 hosts have assumptions about the
network they are using at other layers of the protocol stack and there is no
in-depth exploration of the wider considerations. Hopefully these are addressed
in other similar mechanisms that I did not have time to explore, but I think
the general reader should be reassured in the body of the text.

Major issues:The draft has covered ICMP by asserting the presence of a
stateless translator, but I cannot but worry that the are a lot of other
assumptions built into an IPv4 protocol stack that may surface during
deployment. For example IPv6 has the assumption (for integrity reasons) that
UDP will have a checksum. IPv4 is acrostic on that and frequently sets CS = 0
and yet the draft seems to be silent on the consequences. I wonder if the draft
needs to be experimental until there is operational experience with the method.

Minor issues: None

Nits/editorial comments:There seems to be a minor confusion between Network
Operator and Network Provider in the text that needs examining. "service
continuity after IPv4 address exhaustion, network operators (NPs). I assume
this is just a typo.