Re: [Teas] WG Last Call: draft-ietf-teas-applicability-actn-slicing-05

[[e-mail]]

Hi all,

Here are some few comments:


* References: I would list both the slice and actn frameworks as normative references

* Nit: s/ [I-D.ietf-teas-ietf-network-slices] Section 6.2/ Section 6.2 of [I-D.ietf-teas-ietf-network-slices]

* wrong section: : s/as "isolation" in (Section 7.1 of [I-D.ietf-teas-ietf-network-slices])/ as "isolation" in (Section 8 of [I-D.ietf-teas-ietf-network-slices])

* nit: s/Layer 3 Service Model (L3SM) [RFC8299], Layer 2 Service Model (L2SM) [RFC8466]/ L3VPN Service Model (L3SM) [RFC8299], L2VPN Service Model (L2SM) [RFC8466]



* More details about mapping/example: Shouldn't Section 4.1 or 4.2 mentions that a service mapping for slicing is described in draft-dhody-teas-ietf-network-slice-mapping? Otherwise, we need to explain how the mapping is done. Ideally, an example to illustrate the mapping between the NSSM and VN would be great to have.



* Network Slice Service vs. Network Service:

OLD:

   The YANG model defined in

   [I-D.ietf-teas-ietf-network-slice-nbi-yang] provides a suitable basis

   for requesting, controlling, and deletion, of network slices.



NEW:

    The YANG model defined in

   [I-D.ietf-teas-ietf-network-slice-nbi-yang] provides a suitable basis

   for requesting, controlling, and deletion, of Network Slice Service.

* nit: Please update I-D.ietf-teas-rfc3272bis to RFC 9522.

Cheers,
Med

De : Teas <[e-mail]> De la part de Vishnu Pavan Beeram
Envoyé : samedi 17 février 2024 18:37
À : TEAS WG <[e-mail]>
Cc : TEAS WG Chairs <[e-mail]>
Objet : [Teas] WG Last Call: draft-ietf-teas-applicability-actn-slicing-05

All,

This starts a two-week working group last call on
https://datatracker.ietf.org/doc/draft-ietf-teas-applicability-actn-slicing/

The working group last call ends on March 2nd 2024.
Please send your comments to the working group mailing list.

Positive comments, e.g., "I've reviewed this document
and believe it is ready for publication", are welcome!
This is useful and important, even from authors.
Thank you,
Pavan, Lou and Oscar
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.