Last Call Review of draft-ietf-teas-applicability-actn-slicing-07
review-ietf-teas-applicability-actn-slicing-07-opsdir-lc-clarke-2024-08-13-00

Request Review of draft-ietf-teas-applicability-actn-slicing
Requested revision No specific revision (document currently at 10)
Type IETF Last Call Review
Team Ops Directorate (opsdir)
Deadline 2024-08-13
Requested 2024-07-25
Requested by Jim Guichard
Authors Daniel King , John Drake , Haomian Zheng , Adrian Farrel
I-D last updated 2026-05-20 (Latest revision 2024-08-28)
Completed reviews Rtgdir Early review of -06 by Tony Przygienda (diff)
Rtgdir IETF Last Call review of -07 by Alvaro Retana (diff)
Secdir IETF Last Call review of -07 by Linda Dunbar (diff)
Opsdir IETF Last Call review of -07 by Joe Clarke (diff)
Genart IETF Last Call review of -07 by Peter E. Yee (diff)
Assignment Reviewer Joe Clarke
State Completed
Request IETF Last Call review on draft-ietf-teas-applicability-actn-slicing by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/PE_w7t75I0EHziSfIfEwQ2dW-Zk
Reviewed revision 07 (document currently at 10)
Result Ready
Completed 2024-08-13
review-ietf-teas-applicability-actn-slicing-07-opsdir-lc-clarke-2024-08-13-00
I have been asked to review this document on behalf of the OPS Directorate. 
This document is an informational description of applicability of ACTN to
network slicing.  I found the document very informative and clear on both the
ACTN and network slicing fronts.  Admittedly, there are a lot of moving parts
in TEAS that are referenced by this document, and I'm sure many operational
items when it comes to implementations (the excellent examples in this document
highlight these complexities).

In terms of this document, I have one question.  When I look at how the other
work with augment the service-level YANG modules and specifically figure 6, why
aren't the network models (e.g., L2NM and L3NM) referenced?  I'd think they
might be more useful in figure 6 than a direct approach to the physical device
interface.