Skip to main content

IETF Last Call Review of draft-ietf-netmod-sub-intf-vlan-model-17
review-ietf-netmod-sub-intf-vlan-model-17-genart-lc-hares-2025-10-14-00

Request Review of draft-ietf-netmod-sub-intf-vlan-model
Requested revision No specific revision (document currently at 17)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2025-10-23
Requested 2025-10-09
Authors Robert Wilton , Scott Mansfield
I-D last updated 2025-10-29 (Latest revision 2025-10-08)
Completed reviews Yangdoctors Early review of -14 by Per Andersson (diff)
Opsdir Early review of -17 by Linda Dunbar
Genart IETF Last Call review of -17 by Susan Hares
Secdir Early review of -17 by Dave Thaler
Intdir Early review of -17 by Darren Dukes
Assignment Reviewer Susan Hares
State Completed
Request IETF Last Call review on draft-ietf-netmod-sub-intf-vlan-model by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/v3fSHVpXinIEZ68op8_HnPTdghA
Reviewed revision 17
Result Ready w/issues
Completed 2025-10-14
review-ietf-netmod-sub-intf-vlan-model-17-genart-lc-hares-2025-10-14-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-netmod-sub-intf-vlan-model-??
Reviewer: Sue
Review Date: 2025-10-14
IETF LC End Date: 2025-10-23
IESG Telechat date: Not scheduled for a telechat

Summary:

Major issues: none

Minor issues: Security section paragraph 3, the last sentence makes one wonder
if there are missing sensitivities/vulnerabilities.  If there are, please fill
this in so the operators have a warning. If this is an editorial NIT, please
just respond with completed text.

Nits/editorial comments:

1. Abstract - use of the ";" in the third sentence is confusing.  Consider
rewriting to remove ";".  The sentences do not follow grammatical rules for ";"
as parallel sentences.

2. use if "i.e." in sections 4, paragraph 3, sentence 3, should be considered
for rewriting.  The sentence becomes very confusing.

3. page 14, Yang text, case dotq-priority-tagged, leaft tag-type, description
needs to end with "." according to yang rules.

4. page 17, container dot1q-tag-rewrite, description, "E.g." would be better
replaced by "For example,"

5. page 18, container rewrite, case symetrical, container symmetrical,
description, "E.g." would be better replaced by "For example,"

6. page 25, Security Considerations section, paragraph 3, last sentence does
not list "subtress and data nodes with sensitivities". Last sentence is unclear
and uses incorrect English format.