Last Call Review of draft-ietf-teas-ietf-network-slice-nbi-yang-17
review-ietf-teas-ietf-network-slice-nbi-yang-17-genart-lc-robles-2025-01-10-00

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-teas-ietf-network-slice-nbi-yang-17
Reviewer: Ines Robles
Review Date: 2025-01-10
IETF LC End Date: 2025-01-10
IESG Telechat date: Not scheduled for a telechat

Summary:

The document defines a YANG data model for the RFC 9543 Network Slice Service.
The model can be used in the Network Slice Service interface between a customer
and a provider offering RFC 9543 Network Slice Services.

The document is comprehensive and includes good examples, particularly in the
appendices.

I have the following questions/comments:

1- Section 4: The document mentions dynamic Network Slice management for 5G but
does not specify what "dynamic" entails in this context. It would be helpful to
clarify what dynamic management means, perhaps by providing examples of dynamic
changes, such as modifying service objectives.

2- Section 5.2.3: The draft defines precedence rules for SLO/SLE policies. It
would be helpful to explain what happens if policies conflict or are ambiguous.

3 -Section 5.2.6: In "compute-only" mode, the document mentions feasibility
checks. It would be helpful to describe what happens if the checks fail.

4- Does the YANG model support compute-only mode in multi-domain setups, and if
so, are there any constraints or limitations that need to be addressed?

5- How does the model scale with an increasing number of slices or handle
frequent modifications to existing slices? It would be helpful to include a
sentence addressing this.

Thank you for this document,

Ines