Re: [Teas] Moving forward with draft-ietf-teas-ietf-network-slices

[Igor Bryskin <[e-mail]>]

 Hi Joel,
     As far as I can tell, the client should not be trying to control the
details of which instance is used to fill the service function
requirements.IB>> But is not possible that in  the chain:AccessPoint 1 -> SF1->SF2->...-> AccessPoint2 the client cares about SF1->SF2 delay more than  about AccessPoint1 to AccessPoint2 delay ?
      Constraints like "stay out of a certain country", or
"stay within a given country" would be expressed in terms of the
properties the slice is to meet (service level expectations).  Not by
controlling particular aspects of the service.
IB>> What if I want to stay away, say, from a particular DC? Would it be easier and more flexible to express such exclusions/inclusions in terms of an abstract topology nodes representing countries, DCs, internal networks, etc.?

Igor

    On Thursday, May 6, 2021, 11:14:07 PM EDT, Shunsuke Homma <[e-mail]> wrote:  
 
 Hi,
Firstly, I also follow the WG consensus, and I’m ok to use “customer” if WG prefers it.
I assume there are mainly two types of use cases on (IETF) network slices:1. Providing slices to externals(customers) as a network service 2. Operating some internal network resources with the same slice system with case1
As far as I read other comments on the terms, most of people seem to focuses on use cases where IETF network slices are provided as a type of network services (i.g., case1), and I’d like to confirm if case2 is also in our scope and “customer” can cover both cases. (I personally want to avoid using different terms depending on assumed use cases).


Btw, I agree with that slice management would be important, and we’ll need to clarify what “customers” and “providers” can do on slice managements. In my memory, the NS-DT’s study was started with an assumption that resources should be abstracted from several reasons, such as usability, scalability, security, etc. In this assumption, in my understanding, who controls network resources will be always slice provider (i.e., the owner of NSC). In other words, customers never manage resources structuring a slice directly, and a customer will send a service request to a slice provider/NSC when he/she wants to create/change/delete a slice. (I think this is fit to operation models considered in other SDOs such as TMF.) 




What can be done via service request will depend on design of slice service, and the current definition part provides just minimal sets of selectable parameters as SLOs. More details are provided in NBI drafts.




Regards,




Shunsuke 

2021年5月6日(木) 20:53 Oscar González de Dios <[e-mail]>:

Hi Adrian,

        I think what is really relevant is to have a clear definition on the chosen term to avoid misunderstandings. Unfortunately today customer/consumer/client are used also in other contexts that might bring extra implications.

          Said that, I am fine with the term customer. There are still a couple of places in the document where the term "service customer" is used. Please change those to "IETF Network Slice customer" to be coherent.

        One argument in favor of the term customer is that the "IETF Network slice customer" makes use of the slice to fulfill its needs (can be carry the traffic from a to b with a set of SLOs) and manage the granted slice (that is, it can rearrange the resources it is allowed to).  The term consumer misses the management part, which is a key differentiator of a slice.

        In the definition of customer, Can we just say: " A customer may manage the granted IETF Network Slice.

        Also, I'd like to clarify between the management of the IETF Network slice that the customer can do and the management the provider can do. The customer can "play" within the allocated resources, but may have some limitations. One question, the ability to manage the slice, is part of an SLO? Or should be defined separately with a different term? It would be interesting to have the possibility to indicate what the slice customer can manage and what not...

        I support moving earlier in the document the definition of the IETF Network Slice Customer and, also, add a definition for the IETF Network Slice Provider (although only "provider" is used thought the text).

        Best Regards,

                Oscar


-----Mensaje original-----
De: Teas <[e-mail]> En nombre de Loa Andersson
Enviado el: jueves, 6 de mayo de 2021 9:31
Para: [e-mail]; [e-mail]; [e-mail]
Asunto: Re: [Teas] Moving forward with draft-ietf-teas-ietf-network-slices

Adrian,

That is acceptable.

As you said it is late in the document, and really not in a definitions section. I don't know if we can we place something in Section "2.  Terms and Abbreviations", but there seems to be only abbreviations.

Your wholesale example:

I think you forget about wholesale. What do you call the school that buys food at the shop to provide to the children? Do you call the school the customer, or do you refer to the cook who buys the food as the customer? The contract is with the school, negotiated by the cook, signed by the bursar.

I think "the school! is the customer, which is OK in this context. The cook and the school kids could be viewed as consumers", one removed from the system.

It strikes me that "Customer System" and "IETF Slice" are somewhat similar, the risk is that we talk about "customer" (even if we change it), and "slice" (even though if is really "IETF Slice)",

Having said that, though it is not my task to call consensus, I think we have a enough support to use "customer".

I rest my case.

/Loa


On 05/05/2021 13:05, Adrian Farrel wrote:
> We currently have (in section 5.1, which may be a bit late in the
> document)
>
>     Customer:  A customer is the requester of an IETF Network Slice.
>        Customers may request monitoring of SLOs.  A customer may manage
>        the IETF Network Slice service directly by interfacing with the
>        IETF NSC or indirectly through an orchestrator.
>
> We could add "A customer may be an entity such as an enterprise
> network or a network operator, an individual working at such an
> entity, a private individual contracting for a service, or an
> application or software component."
>
> Cheers,
> Adrian
>
> -----Original Message-----
> From: [e-mail] <[e-mail]>
> Sent: 05 May 2021 11:58
> To: [e-mail]; 'Loa Andersson' <[e-mail]>; [e-mail]
> Subject: RE: [Teas] Moving forward with
> draft-ietf-teas-ietf-network-slices
>
> Hi all,
>
>> Anyone else got anything to say on the topic?
>
> I would simply use "customer" and make sure the definition is generic
> enough to denote a role/entity.
>
> Thanks.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : Teas [mailto:[e-mail]] De la part de Adrian Farrel
>> Envoyé : mercredi 5 mai 2021 11:59 À : 'Loa Andersson' <[e-mail]>;
>> [e-mail] Objet : Re: [Teas] Moving forward with
>> draft-ietf-teas-ietf-network- slices
>>
>> Hi Loa,
>>
>>> On customer vs. consumer Adrian says:
>>>
>>>>    c. "Consumer" vs "customer". I have made this consistent (we
>> only need to
>>>>         use one term). I selected "Customer" because that seemed
>> best, but I
>>>>         know some people prefer "consumer". Please discuss if you
>> are not
>>>>         happy.
>>>
>>> If the choice is between customer vs. consumer, I prefer customer.
>>
>> OK. So I made an improvement, but...
>>
>>> I don't know if it is too late to bring this up.
>>
>> It's never too late to bring things up.
>>
>>> But I really don't like either, normal language has a strong
>>> indication that that that a customer is a person (a person that
>> walks
>>> inte to your
>>> shop) and consumer is also a person /that eats what I bought at
>> your shop).
>>
>> I think you forget about wholesale. What do you call the school that
>> buys food at the shop to provide to the children? Do you call the
>> school the customer, or do you refer to the cook who buys the food as
>> the customer? The contract is with the school, negotiated by the
>> cook, signed by the bursar.
>>
>>> IETF specifies "systems", including what goes into SW and HW, but
>> we
>>> don't specify normative rules for human behavior.
>>>
>>> I don't know if we can talk about Customer System?
>>
>> I'm afraid of this getting heavy for the reader. There are 73
>> instances of "customer" in the document, and "customer system" may
>> become tiresome to read.
>>
>> Anyone else got anything to say on the topic?
>>
>> Cheers,
>> Adrian
>>
>> _______________________________________________
>> Teas mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/teas
>
> ______________________________________________________________________
> ______ _____________________________________________
>
> 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.
>
> _______________________________________________
> Teas mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/teas
>

--

Loa Andersson                        email: [e-mail]
Senior MPLS Expert                          [e-mail]
Bronze Dragon Consulting             phone: [phone]

_______________________________________________
Teas mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/teas

________________________________

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 privileged and confidential 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
_______________________________________________
Teas mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/teas

_______________________________________________
Teas mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/teas