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

Igor Bryskin <i_bryskin@yahoo.com> Thu, 06 May 2021 14:25 UTC

Return-Path: <i_bryskin@yahoo.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD623A2402 for <teas@ietfa.amsl.com>; Thu, 6 May 2021 07:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N4A5q96GOwbj for <teas@ietfa.amsl.com>; Thu, 6 May 2021 07:25:50 -0700 (PDT)
Received: from sonic311-23.consmr.mail.ne1.yahoo.com (sonic311-23.consmr.mail.ne1.yahoo.com [66.163.188.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 017C03A240C for <teas@ietf.org>; Thu, 6 May 2021 07:25:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1620311148; bh=HeDDrlw2Fx+ekaiARlQbfl/fmXK1zZVhQH/DNZzetNQ=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=tbxPaExIraX4k6Im+2jk8sbz3BgYt42jFsOcEemj6BqGPRkbGfZvgIiR5I6PvRKPoq987rjrgCcEXMptlXY/ytyDGt2eDXk7cAfYUeIm8ppg5IA98VewllBY2EvqaBaldqdEcS5cRXH9T/khwHzzLlwxxqvtw7brAlCWcvROwmxyWmmARuN057JstjJkLcmqc07B2ZOmnHLVtYk+FDEqd4rfl28Qp15yo2hCQ8NwFdY6RJd91QR1ygf7GX6+Y+T/tsj2YaqpnytTrPnX7ibaKRFWDGLK8EpFD3NCk5NtTl9SEiGYxf9GQtjdNZdeQYoLQMhYHGlJqjVWzMV3oEtOOg==
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1620311148; bh=ecLWzMmvPec5Wju/PwnXRPlDitF3cuGlT/Ea1OerYHu=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=TBkJey+nu6tHxZ5jfhWIfa6X9C7cNq3+EKCAg6fe2JMPbWegEYbT3tqBQnObPqWd6CQo9HCnw1kZBDrOZThLVXqCSWahguxH2EJ2p/rnI9YpzGhgSq+uSMoQRw3vHUJvk4OAIbpiQ9LZW/P6HN3jWifrbjZtI5UckqUhd0Z8zciADY1wOVnO9KZkaTo08PSd51PQyKQo0VXTqoQ2rOxWfyH3i6emexw5UJa7geKgILtdfgRbE+NVO2lR9eQ8RBi0AK6HqIq91TuQsA0tZIKFwQ8q9WqKIYE1Dl57JzR+1TiUIQqAFh4s4LOLaE4we5AKiYoxBzKWfWrT08HUmh/Kcw==
X-YMail-OSG: xqs9r3MVM1k_ygq.PbsRIG67726fdfSV4c8gj5zyV2lrwo.G2uoR6702tXSpRpq dZ7r5rJge0Vc4qLS4JQNMWGexU7bnBkxAIkJU.5RgEUn8C6eTT64L3hoGtqsnEdGzrqizFl5M.EX qPPv.XqhBApVZ_6_UBVHxYcv.j4VBanObhk8_n3qspQWG15k5.htlsEYRpZ2QbK8LYVA7K2Ck5JQ sSYaWEgFGrhZQgzoq0TaOZHyKEb3YKk_0zLCUzhRD3Gylq6BJwHUzQmWBu6ZN8Ofdg9wt7j1aPTq LyhS1TkdUTfzoYy.I45ILMfZXLdFOwknKhy94bqykVzYtXnltTT3XPsuywuLyGmFiPK8xFT9mtL. 36skFEyecXK30.l7uMdQqDh1QNSU7wSmyiG7RLU8vojNCsmdhhdWXz7.4X09p8uKVnPDRq5te3py 8Sx37biKlKD4RdgIFo8UluMQJ8YGaV3_BhHzBynAEZk_30udtX6jsyzo8UcavKJ2og2aG6GEpE61 JZYoSdQwYQxUZS9Hml1Zpa29TpmBqTjkrFhvyooW1.p2VOLTJxIyaqrk7m0bKeCBCfnJZ2ujgDD3 ktEWj3eVmwuN53iAlXWkVXTrUwqvdgb2H81SlppNP4UuMKj4MvDqmTXZj.2mAiq6MEodwQhztwb7 h3I4o6nP.zJxQjMefOi7R.S8uEfbZBP1Oatym81T.kVCnbOjFQxz6nFCd9pnDwkY7od.8oKFpqIG h4Mb5x0dlbQ5PvNMlnCBQGD1w57N3Q87tz58AqU6Z_at7zPGaaa.EglQpOfeOpQXbBO7YrVAt3cx lpP_GqS6rCHZcjJrB.GYpiG948JLILq7OPyT7Rn1fluo2E2K0gZDOmExwfrXZDNlI4wONY1HEeOY S7uYbGoKNqSBmmRAYrregyuq9zw6Y3lbxChDDwnH2ggkySGvrOApbz5Xj3xT0mcndvodiEFHKfUt oN5aU_msXWk_TA_gIA4glxOKXJ2FLFt3vBpriqGuGV2s9hJ5umwYXv4HZFocNhirJipInBtIjj3H yUW9mi9V6XklSxIPxdMYGfpNqv8SJtgKiiuhqZ3b5gdyTuAd0AjndX8whXevfVd7gwes9qGfVVVE 81UpB4VmEQ5ra38SW_KGJuFdpxBxt9.3oxnoD_a.PecTtn8Se3Pgozt.12uHFAs9RQLbD6N3bvn8 Hy0.Smpk0xNa.9TS7OGaldL5NlcceIot6p04KEIqcsRmh5ydfCKbZVJK5.AYcaNRL8yw.PMeORcv NZDvOlqZMzosCVFDoQgTeCZOburXA07CWMdYug3XzuW7XYowlPUY4ch3gHeHTpVKj9OfSdn0pGBw dexWKkvZsUUXs8w.Wdh5MpuJxOnJUE4Osc77qm84vkD89x4rXSShlHXbdcjLcJyBJCcHXrdKW_Ur xAWnnkrdZGZehtg8gcrFj.YTAzCxnqPCHfBvn.LkMM1QtsNp3upK3xlDOyFOHwirlvryFzO8z3dC mgNAlt8Sn8GJ3UK3LQR_2NeZzVhXY13KD72uR84Y4sBBK2nsVTtj9FRVK38w6yIza7Jzy3yQABPF CTkogadZbO5.jRnKxMIqg5JfKrwmxoLv6jxGHYONLf0vbrWkMJkoT2TKy4wmeoV2OylGZixcIsOe P4.7rMFtenZiQwAkwhDH.XNcbQR5YM0iv_.1R3wTdtRTGU0lp7OLzuR1fSBL5ZL5vjHSZs73I1mK 7DGX7PoTULeIk9ZbEHcuzXaVI0VsZen_s_Gy9pgtpj7t2YgG1y1E15a5MqrJyeuwZQJxEgiFbsHy PBcqiPftG6RLOo.fvx8n7SucGDKONraaI0aH2z8dWb3vtjNTr5HxFuvK3F7Fp4AypineQoImj0WR JBfgu0ayKpSp0JMan1yWxoR5dfZfWBEimc7yGfNP72IgKBiC2_kCc.He8XDnG7x3puhwgYJXM4ll MjjC7tMzMqzMHM27.PNYXAwg_Am_5P5gamOfuJJcthcDxtPcC0d9RL7qt_x9V4eVfPhJCanVkm8. gGNMIoOdCggOY8OpfZ2RWuv4fGrXKPZRn8vmRIgINscjkvnsBc0COmMXAOV1KjLCe5rJ1bMTmNXo bxmxbLb_.LjWslp39rwZDEKPNvlwgEBx9GTbxw1vdZp_vsv2bWdESw4BRHAwVQwWKYHkvdxbE3Wh Kdy_uEap2pCDH0YRTuTUOpQuOddim4sq5rfypOlWE9c5gWBjXLmIlBunKmfnIOffN2OnK_HD2Z8E jza8ETv3eb5Mhm3xZYvvU_pdo65dhAPvEW4a1RmG370km9qvdz0zMDtJg36SrpNrtpSYU9TjkZVJ M1yMBgwMiWSTFAZU7LMnEdFn62e61GWZM_akuhyBN2L5x5M2I1MiwqsVYw5oRqfi6yxmsZEOopIx vNRewHdZ6I34rI9tHlmi6DcI75B3o7icWT6mCjotAtByNsr_OZWtUyLfGDU0OMC85zTYHc8G9f6W q81vHQTG4AcNXLhJvdeVLmmPpEy9Yv6SCH7quMAKKOEL0kmW6PCCBB6WmK8dnbnVzPrLR.fexHD9 agg2s3i7FbnQ786fCiiVu8VuxKFVaL431pgg5l26lLukFNBtU2peYjL9BWfWUsQbBbCLoCyGQJti UdCS_G3MIZB9.62e9R1uSf4S1EiNjANvqbgJEPQdKfT7MXKjDggK8B4UqZnffdEgrh9TddsTbCaf w_rf1bMvTTWHf0t.C1z0bVrfUTjT6
X-Sonic-MF: <i_bryskin@yahoo.com>
Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.ne1.yahoo.com with HTTP; Thu, 6 May 2021 14:25:48 +0000
Date: Thu, 6 May 2021 14:25:46 +0000 (UTC)
From: Igor Bryskin <i_bryskin@yahoo.com>
To: Loa Andersson <loa@pi.nu>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "teas@ietf.org" <teas@ietf.org>, =?UTF-8?Q?Oscar_Gonz=C3=A1lez_de_Dios?= <oscar.gonzalezdedios@telefonica.com>
Message-ID: <914297092.1179550.1620311146249@mail.yahoo.com>
In-Reply-To: <PAXPR06MB7872B2DEF299B15988966A9DFD589@PAXPR06MB7872.eurprd06.prod.outlook.com>
References: <037401d740c5$70a9cc30$51fd6490$@olddog.co.uk> <3ea262cf-e4c0-5ec0-9736-aedaf6d5d4d8@pi.nu> <009401d74195$41fd70a0$c5f851e0$@olddog.co.uk> <9933_1620212302_60927A4E_9933_344_1_787AE7BB302AE849A7480A190F8B933035376DFA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <00a001d7419e$99e5a040$cdb0e0c0$@olddog.co.uk> <03cf404d-59a7-0ec5-e18f-0a98bf638c0f@pi.nu> <PAXPR06MB7872B2DEF299B15988966A9DFD589@PAXPR06MB7872.eurprd06.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_1179549_1471559124.1620311146246"
X-Mailer: WebService/1.1.18231 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36 Edg/90.0.818.51
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/m1Yl-o6RviKaqEDoWlf-8945ICQ>
Subject: Re: [Teas] Moving forward with draft-ietf-teas-ietf-network-slices
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 14:25:55 -0000

 Hi Adrian,
I probably missed the discussion, but how do we reconcile  two IETF stories - network slicing and SFCs? Surely, at some point a network slice client will ask the provider not just only to deliver its traffic from A to B with delay no worse than D, but also to do something else with the data (e.g. DPI). On the other hand, when we talk about SFCs we cannot assume I think any longer the context of a physical (not sliced) network. I do not suppose we can simply mandate the SF placement at network slice end points or somewhere outside network slices - this approach would probably not scale well. 
So, the question is how SFs relate to network slices, in particular, to their SLAs, SLOs and topologies?
Thanks,Igor
    On Thursday, May 6, 2021, 07:53:32 AM EDT, Oscar González de Dios <oscar.gonzalezdedios@telefonica.com> wrote:  
 
 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 <teas-bounces@ietf.org> En nombre de Loa Andersson
Enviado el: jueves, 6 de mayo de 2021 9:31
Para: adrian@olddog.co.uk; mohamed.boucadair@orange.com; teas@ietf.org
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: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> Sent: 05 May 2021 11:58
> To: adrian@olddog.co.uk; 'Loa Andersson' <loa@pi.nu>nu>; teas@ietf.org
> 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:teas-bounces@ietf.org] De la part de Adrian Farrel
>> Envoyé : mercredi 5 mai 2021 11:59 À : 'Loa Andersson' <loa@pi.nu>nu>;
>> teas@ietf.org 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
>> Teas@ietf.org
>> 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
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>

--

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting            phone: +46 739 81 21 64

_______________________________________________
Teas mailing list
Teas@ietf.org
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
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas