Skip to main content

IETF Last Call Review of draft-ietf-dmm-tn-aware-mobility-25
review-ietf-dmm-tn-aware-mobility-25-genart-lc-dunbar-2026-05-12-00

Request Review of draft-ietf-dmm-tn-aware-mobility
Requested revision No specific revision (document currently at 27)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2026-05-13
Requested 2026-04-29
Authors Uma Chunduri , John Kaippallimalil , Sridhar Bhaskaran , Jeff Tantsura , Luis M. Contreras
I-D last updated 2026-07-06 (Latest revision 2026-07-06)
Completed reviews Genart IETF Last Call review of -25 by Linda Dunbar (diff)
Secdir IETF Last Call review of -26 by Jon Geater (diff)
Intdir Telechat review of -27 by Wassim Haddad
Assignment Reviewer Linda Dunbar
State Completed
Request IETF Last Call review on draft-ietf-dmm-tn-aware-mobility by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/GEhH8SYnouuZfI7WO09ki5-0o_c
Reviewed revision 25 (document currently at 27)
Result Ready w/nits
Completed 2026-05-12
review-ietf-dmm-tn-aware-mobility-25-genart-lc-dunbar-2026-05-12-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-dmm-tn-aware-mobility-25
Reviewer: Linda Dunbar
Review Date: 2026-05-12
IETF LC End Date: 2026-05-13
IESG Telechat date: Not scheduled for a telechat

Summary: This document describes a way to map 5G user-plane traffic for a given
3GPP slice to the appropriate transport-network slice by using the GTP-U outer
UDP source port, including across mobility and handover.

Major issues: None

Minor issues: None

Nits/editorial comments:
- In the Introduction, “F-U” appears to be used where “F1-U” is probably
intended. - In Section 1, “UDP source port ranges in TN underlays for slice
mapping is described in Section 4” should be “are described in Section 4”. -
There are a few places where “to setup” should be “to set up,” for example in
Section 2 and Section 3.3. - In Section 3.2, “maybe realized in an NSS” should
be “may be realized in an NSS.” - The text says the solution does not depend on
VLANs, but Figure 3 includes VLAN matching prominently. A short note in the
figure caption or text saying VLAN is only illustrative would improve clarity.

Best Regards,

Linda Dunbar