Skip to main content

Last Call Review of draft-ietf-teas-applicability-actn-slicing-07
review-ietf-teas-applicability-actn-slicing-07-rtgdir-lc-retana-2024-08-12-00

Request Review of draft-ietf-teas-applicability-actn-slicing
Requested revision No specific revision (document currently at 10)
Type Last Call Review
Team Routing Area Directorate (rtgdir)
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 2024-08-12
Completed reviews Rtgdir Early review of -06 by Tony Przygienda (diff)
Rtgdir Last Call review of -07 by Alvaro Retana (diff)
Secdir Last Call review of -07 by Linda Dunbar (diff)
Opsdir Last Call review of -07 by Joe Clarke (diff)
Genart Last Call review of -07 by Peter E. Yee (diff)
Assignment Reviewer Alvaro Retana
State Completed
Request Last Call review on draft-ietf-teas-applicability-actn-slicing by Routing Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/bZ7_tCBIXO3IRa3G90Y3yQynY3I
Reviewed revision 07 (document currently at 10)
Result Ready
Completed 2024-08-12
review-ietf-teas-applicability-actn-slicing-07-rtgdir-lc-retana-2024-08-12-00
Hi!

I have been selected as the Routing Directorate reviewer for this
draft. The Routing Directorate seeks to review all routing or
routing-related drafts as they pass through IETF last call and IESG
review, and sometimes on special request. The purpose of the review is
to provide assistance to the Routing ADs. For more information about
the Routing Directorate, please see
https://wiki.ietf.org/en/group/rtg/RtgDir

Although these comments are primarily for the use of the Routing ADs,
it would be helpful if you could consider them along with any other
comments that you receive, and strive to resolve them through
discussion or by updating the draft.

Document: draft-ietf-teas-applicability-actn-slicing-07
Reviewer: Alvaro Retana
Review Date: August 12, 2024.
Intended Status: Informational

Summary: This document is basically ready for publication but I have
some concerns that I think should be resolved before publication.

Comments:

The document is well structured and easy to read.

I have two concerns:

(1) Security Considerations

The text in §6 is good.  For completeness, it would benefit from a
pointer to the Security Considerations in rfc8453 and rfc9543, as well
as the Privacy Considerations in that last document.

(2) References

Based on the definitions from the IESG Statement on Normative and
Informative References [1], I believe some of the Informative
references should be Normative because they refer to "documents that
must be read to understand or implement the technology" in this
document.

The terminology from I-D.ietf-teas-enhanced-vpn is used.

Unless the text in §4 is used as an example of the applicability (but
that was not mentioned), the drafts/RFCs mentioned there as specifics
on how the ACTN framework is applied to network slicing should be
Normative: I-D.ietf-teas-actn-pm-telemetry-autonomics,
I-D.ietf-teas-actn-vn-yang, I-D.ietf-teas-ietf-network-slice-nbi-yang,
I-D.ietf-teas-te-service-mapping-yang, I-D.ietf-teas-yang-te, RFC8299,
and RFC8466.

[1]
https://datatracker.ietf.org/doc/statement-iesg-iesg-statement-normative-and-informative-references

Alvaro.