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

Shunsuke Homma <shunsuke.homma.ietf@gmail.com> Fri, 07 May 2021 03:14 UTC

Return-Path: <shunsuke.homma.ietf@gmail.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 478303A1101 for <teas@ietfa.amsl.com>; Thu, 6 May 2021 20:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_DNSWL_NONE=-0.0001, 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=gmail.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 uTOXsR-MqHcl for <teas@ietfa.amsl.com>; Thu, 6 May 2021 20:13:54 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 25D203A1107 for <teas@ietf.org>; Thu, 6 May 2021 20:13:54 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id o16so9761734ljp.3 for <teas@ietf.org>; Thu, 06 May 2021 20:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lh9rYQVx2fRelp8+72v6Rrj8BA3h6/BcmzQvzFmFQfU=; b=lQKJVzyGFjQVAoDrqe7b+rGXV1KTf7nktPmVndp4l8O3lNXfQEuuOipIy1TqetHiKA SH+WsVOhx/Or0ziCI4A9My/TA7oBK/icMyG/kCgtGk5Phyx5qq5+4dwXmWf0vHVni9yE N2doMpxv0cUisOZpUVMvTT1GDITSxEZDlT+Xw3eqtabXhkQBsNvzekien9s0s8gvWd8H cfj4AGzTIz/n+vtCQ+RVFAaGLkaaeESXyZg9GB5jKXOmlgc+8Lj2zD2x4rqyEMIDo1cD 6qbJg+z9pP8HeEJJ7pdAcO6DfSNfevQnElah4uLxRCvLN4oYBcejJ37iUaT8qnXkJ7cl JuDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lh9rYQVx2fRelp8+72v6Rrj8BA3h6/BcmzQvzFmFQfU=; b=fqrxId3Lqn+zt+ORIJMU2br9qfCQ3XKR9tXMThKPjeLjgW6vW4f4cmLrnQ9pbklQ8T YL6umeTnTQF2LFgoZOYvP1A2msKct7XJAiYy9poTJkW/MQGKvVUaKGUdLyyoSMxVWCof 3d4CtIl8CMnEh1tQ8RFHVVdHCtK5kVTfhF5C/txfTnMI2K/hNh9t/hUbRr0WS8WNYme2 eX/P8a6Sq1QVkn8jDhIcVJ8SRCwbJxeJGcrSJUHjXOTWRQB9xX9AUuBAW9wzIPXXTv8T Tl4K6j5iyWhcEQCWjiRefINSNQT6LCzK+jYswOuF33gJKDMhLWtfI4HALYjdSVSidU6z 5YWw==
X-Gm-Message-State: AOAM533LCDOCCV70r0YWy8Sr5x5x/z/LeW4zwrJpI2qWYm7jnzBCwuao NO2XZ0cdAS2Zng0XwWbcw5Qj7yTrlS+fJRmvEA8=
X-Google-Smtp-Source: ABdhPJwZoTzLextYTd7Q4co/d5SM4DPRINCvvC3fPHWkF7waTFMMwqD9AjulJLHpw7PeB6UWYpvcxtCaCkV16XbAvHE=
X-Received: by 2002:a2e:9e88:: with SMTP id f8mr5953711ljk.88.1620357231645; Thu, 06 May 2021 20:13:51 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <PAXPR06MB7872B2DEF299B15988966A9DFD589@PAXPR06MB7872.eurprd06.prod.outlook.com>
From: Shunsuke Homma <shunsuke.homma.ietf@gmail.com>
Date: Fri, 7 May 2021 11:53:08 +0900
Message-ID: <CAKr2Fb9Krrqe7SWB4Zxyp8y8q1S1-jR2=Z3KkoF89cwhOEV4bg@mail.gmail.com>
To: =?UTF-8?Q?Oscar_Gonz=C3=A1lez_de_Dios?= <oscar.gonzalezdedios@telefonica.com>
Cc: 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>
Content-Type: multipart/alternative; boundary="00000000000033978605c1b4d1dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/4fPKzh7X2PVXdcK12N2cYfb79Eg>
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: Fri, 07 May 2021 03:14:00 -0000

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 <
oscar.gonzalezdedios@telefonica.com>gt;:

> 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
>