Skip to main content

Last Call Review of draft-ietf-savnet-intra-domain-problem-statement-10
review-ietf-savnet-intra-domain-problem-statement-10-opsdir-lc-banks-2025-01-24-00

Request Review of draft-ietf-savnet-intra-domain-problem-statement
Requested revision No specific revision (document currently at 26)
Type IETF Last Call Review
Team Ops Directorate (opsdir)
Deadline 2025-01-17
Requested 2025-01-03
Requested by Jim Guichard
Authors Lancheng Qin , Dan Li , Jianping Wu , Mingqing(Michael) Huang , Nan Geng
I-D last updated 2026-06-09 (Latest revision 2026-06-01)
Completed reviews Rtgdir IETF Last Call review of -09 by Linda Dunbar (diff)
Secdir IETF Last Call review of -10 by Benjamin M. Schwartz (diff)
Opsdir IETF Last Call review of -10 by Sarah Banks (diff)
Artart IETF Last Call review of -09 by Robert Sparks (diff)
Genart IETF Last Call review of -10 by Tim Evens (diff)
Opsdir IETF Last Call review of -21 by Chongfeng Xie (diff)
Secdir IETF Last Call review of -21 by Benjamin M. Schwartz (diff)
Assignment Reviewer Sarah Banks
State Completed
Request IETF Last Call review on draft-ietf-savnet-intra-domain-problem-statement by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/-qRx4Gvdb_yAwKuUm51nc-wTAa0
Reviewed revision 10 (document currently at 26)
Result Not ready
Completed 2025-01-24
review-ietf-savnet-intra-domain-problem-statement-10-opsdir-lc-banks-2025-01-24-00
Hi authors!
I appreciate that you took the time to think through and write a well written
gap analysis draft. I believe I understand the intent, and I applaud it. That
said, my opinion is that generally, these types of documents are not ones I'd
expect to see as an RFC; they'd either guide the WG into some work stream
doc(s), or roll into one of those docs directly. I can see the case for
exceptions. For example, sometimes issues with requirements and implementation
are thorny enough where having a "discussion" doc could make sense. However,
this draft covers requirements that are somewhat broad, with no consideration
for any of the issues or obstacles to overcome, or tradeoffs in one approach
versus another, where the requirements are potentially OK by themselves, but
without anything else with them, I find it a good discussion point, but not an
informational RFC.