Subject: Re: [Teas] WG adoption poll: draft-contreras-teas-slice-controller-models-05

From: LUIS MIGUEL CONTRERAS MURILLO <[email-masked]>
Date: Sat, 22 Jul 2023 18:19:41 +0000

Hi Kiran

Thanks so much for your comments.

Not answering to the internal interface comment since I have responded in that respect to Swamy and Adrian's comments, please, check.

Regarding your comment on the realizer building block. The reason for considering such building block was to enable the transition from an IETF Network Slice service request which is technology-agnostic, up to the point of being able to use existing (or augmented) network models being supported by network controllers (please, see draft-barguil-teas-network-slices-instantation for reference). That was the rationale of dividing the actions in those two building blocks of mapper and realizer. For sure, some other options are possible, and the approach followed in this draft does not have the purpose of standardizing or constraining the implementation the IETF Network Slice Controller. It only tries to describe a way of going from technology-abstracted request received by the NSC up to technology-specific network model supported by a network controller.

Respect to your reference to section 6.3, do you refer to the framework document? Not clear to me.

Thanks again,

Best regards

Luis

De: Teas <[email-masked]> En nombre de Kiran Makhijani
Enviado el: martes, 11 de julio de 2023 13:05
Para: Vishnu Pavan Beeram <[email-masked]>; TEAS WG <[email-masked]>
CC: TEAS WG Chairs <[email-masked]>
Asunto: Re: [Teas] WG adoption poll: draft-contreras-teas-slice-controller-models-05

I quickly skimmed through the document and like that how it connects different pieces of work being done in the WG about network slices, we need something like this. Therefore, I support this document's adoption.  It will help with designing NSC interfaces in a standard way.

Fair point raised that internal interface, should not be exposed. At the same time - perhaps my information is outdated, I always thought that NSC should be technology agnostic and inclusion of realizer in NSC is not entirely clear ( it could be anywhere - maybe with the network controller). In 6.3 section of slices... we say a lot about mapping but nothing about the realizer.

Perhaps, when the document is adopted - we can clarify these aspects.
Cheers,
Kiran

From: Teas <[email-masked]<mailto:[email-masked]>> on behalf of Vishnu Pavan Beeram <[email-masked]<mailto:[email-masked]>>
Date: Tuesday, July 4, 2023 at 12:42 PM
To: TEAS WG <[email-masked]<mailto:[email-masked]>>
Cc: TEAS WG Chairs <[email-masked]<mailto:[email-masked]>>
Subject: [Teas] WG adoption poll: draft-contreras-teas-slice-controller-models-05
All,

This is start of a *two* week poll on making
draft-contreras-teas-slice-controller-models-05 a TEAS working group document
[https://datatracker.ietf.org/doc/html/draft-contreras-teas-slice-controller-models-05].

Please send email to the list indicating "yes/support" or "no/do not support".
If indicating no, please state your reservations with the document. If
yes, please also feel free to provide comments you'd like to see
addressed once the document is a WG document.

The poll ends July 19th.

Thank you,
Pavan, Lou and Oscar

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener informaci?n privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destrui??o
________________________________

Le informamos de que el responsable del tratamiento de sus datos es la entidad del Grupo Telef?nica vinculada al remitente, con la finalidad de mantener el contacto profesional y gestionar la relaci?n establecida con el destinatario o con la entidad a la que est? vinculado. Puede contactar con el responsable del tratamiento y ejercitar sus derechos escribiendo a [email-masked]<mailto:[email-masked]>. Puede consultar informaci?n adicional sobre el tratamiento de sus datos en nuestra Pol?tica de Privacidad<https://www.telefonica.com/es/telefonica-politica-de-privacidad-de-terceros/>.

We inform you that the data controller is the Telef?nica Group entity linked to the sender, for the purpose of maintaining professional contact and managing the relationship established with the recipient or with the entity to which it is linked. You may contact the data controller and exercise your rights by writing to [email-masked]<mailto:[email-masked]>. You may consult additional information on the processing of your data in our Privacy Policy<https://www.telefonica.com/en/wp-content/uploads/sites/5/2022/12/Telefonica-Third-data-subjects-Privacy-Policy.pdf>.

Informamos que o respons?vel pelo tratamento dos seus dados ? a entidade do Grupo Telef?nica vinculada ao remetente, a fim de manter o contato professional e administrar a rela??o estabelecida com o destinat?rio ou com a entidade ? qual esteja vinculado. Voc? pode entrar em contato com o respons?vel do tratamento de dados e exercer os seus direitos escrevendo a [email-masked]<mailto:[email-masked]>. Voc? pode consultar informa??o adicional sobre o tratamento do seus dados na nossa Pol?tica de Privacidade<https://www.telefonica.com/es/politica-de-privacidade-de-terceiros/>.