Skip to main content

IETF Last Call Review of draft-ietf-intarea-v4-via-v6-07
review-ietf-intarea-v4-via-v6-07-opsdir-lc-graf-2026-04-13-00

Request Review of draft-ietf-intarea-v4-via-v6
Requested revision No specific revision (document currently at 08)
Type IETF Last Call Review
Team Ops Directorate (opsdir)
Deadline 2026-04-14
Requested 2026-03-23
Requested by Mohamed Boucadair
Authors Juliusz Chroboczek , Warren Kumari , Toke Høiland-Jørgensen
I-D last updated 2026-04-24 (Latest revision 2026-04-17)
Completed reviews Genart IETF Last Call review of -07 by Linda Dunbar (diff)
Artart IETF Last Call review of -07 by Barry Leiba (diff)
Opsdir IETF Last Call review of -07 by Thomas Graf (diff)
Secdir IETF Last Call review of -07 by Karen O'Donoghue (diff)
Tsvart IETF Last Call review of -07 by David L. Black (diff)
Rtgdir IETF Last Call review of -08 by Emmanuel Baccelli
Assignment Reviewer Thomas Graf
State Completed
Request IETF Last Call review on draft-ietf-intarea-v4-via-v6 by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/YvCyCzhMMJYN3w8lfwk2FAvJFw0
Reviewed revision 07 (document currently at 08)
Result Has issues
Completed 2026-04-13
review-ietf-intarea-v4-via-v6-07-opsdir-lc-graf-2026-04-13-00
Hi,

I have been selected as the Operational Directorate (opsdir) reviewer for this
Internet-Draft.

The Operational Directorate reviews all operational and management-related
Internet-Drafts to ensure alignment with operational best practices and that
adequate operational considerations are covered.

A complete set of _"Guidelines for Considering Operations and Management in
IETF Specifications"_ can be found at
https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5706bis/.

While these comments are primarily for the Operations and Management Area
Directors (Ops ADs), the authors should consider them alongside other feedback
received.

- Document: [draft-ietf-intarea-v4-via-v6-07]

- Reviewer: [Thomas Graf]

- Review Date: [13-04-2026]

- Intended Status: [Proposed Status, e.g., Standards Track]

---

## Summary

Choose one:

- Has Issues: I have some minor concerns about this document that I think
should be resolved before publication.

## General Operational Comments Alignment with RFC 5706bis

I welcome that the document has an operational consideration section. However,
besides traceroute other OAM considerations such as for IPFIX should be
considered as well.

---

## Minor Issues

I suggest to adjust the second paragraph in the operational considerations
section as following to:

Just like any other extension to an already deployed technology, it requires
changes how it is being operated as well. Even though v4-via-v6 routes are
similar in structure to traditional next-hop routes, some monitoring protocols
and management tools require adjustment. To take IPFIX [RFC7011] as example for
monitoring forward and data plane. Each IPFIX data and template record for IPv4
flows should contain IE62 ipNextHopIPv6Address to describe IPv6 next hop.
Deployment of v4-via-v6 routing in a network requires testing and potentially
updating of all tools and scripts that manipulate or examine routes.

---

## Nits

For anything else, please consider the nits described in here:

DOCX:
https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/document-review/draft-ietf-intarea-v4-via-v6-07.pdf
PDF:
https://github.com/network-analytics/ietf-network-analytics-document-status/blob/main/document-review/draft-ietf-intarea-v4-via-v6-07.docx

---