Skip to main content

Telechat Review of draft-ietf-intarea-proxy-config-11
review-ietf-intarea-proxy-config-11-tsvart-telechat-eddy-2026-03-27-00

Request Review of draft-ietf-intarea-proxy-config
Requested revision No specific revision (document currently at 14)
Type Telechat Review
Team Transport Area Review Team (tsvart)
Deadline 2026-03-31
Requested 2026-03-14
Requested by Gorry Fairhurst
Authors Tommy Pauly , Dragana Damjanovic , Yaroslav Rosomakho
I-D last updated 2026-06-02 (Latest revision 2026-05-19)
Completed reviews Dnsdir IETF Last Call review of -11 by Florian Obser (diff)
Genart IETF Last Call review of -11 by Dale R. Worley (diff)
Secdir IETF Last Call review of -11 by Chris M. Lonvick (diff)
Tsvart Telechat review of -11 by Wesley Eddy (diff)
Opsdir IETF Last Call review of -13 by Daniele Ceccarelli (diff)
Comments
Please review, e.g., with respect to usage by MASQUE.
Assignment Reviewer Wesley Eddy
State Completed
Request Telechat review on draft-ietf-intarea-proxy-config by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/H4nV_CNF1GO-M3lu0qdJ577OcxQ
Reviewed revision 11 (document currently at 14)
Result Ready
Completed 2026-03-27
review-ietf-intarea-proxy-config-11-tsvart-telechat-eddy-2026-03-27-00
This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

This document seems pretty clear and well-written.  I didn't find any real
transport / WIT concerns to note.

In Table 3, the examples in the the "subnets" row (["2001:db8::1",
"192.0.2.0/24"] made me wonder if the description of this should be specified
better, in order to avoid some possible bugs/incompatibilities.  The paragraph
describing the format just says "written using CIDR notation", which matches
the example IPv4 subnet, but the example also includes an IPv6 address (which
doesn't have a "/N", etc.).  For IPv6, I think RFC 4291, section 2.3 might be
the right thing to reference, and that the example might not actually be
correct if this is really supposed to be "subnets", otherwise the description
should say it's subnets as well as specific IP addresses.