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

Shunsuke Homma <shunsuke.homma.ietf@gmail.com> Wed, 05 May 2021 13:23 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 8AEAF3A08ED for <teas@ietfa.amsl.com>; Wed, 5 May 2021 06:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_BLOCKED=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=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 AKY8uRcxt8kM for <teas@ietfa.amsl.com>; Wed, 5 May 2021 06:23:17 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 2E4BA3A08F9 for <teas@ietf.org>; Wed, 5 May 2021 06:23:17 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id x19so2565056lfa.2 for <teas@ietf.org>; Wed, 05 May 2021 06:23:16 -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=OI9KDt39H4+4qPHZkmnaOxlBjZu3C9U+G8j/uz2H1E0=; b=IwoywmBuF5HJBuizUNi/sMQmQEN0hpP27ckj3Myp4ozeQdCQsLgV43OqChLxdQHgQO K+ywrxpD40hFFGi0aVEsEHglcUArkWfHqFCHpFCc8BPfvB+If7ZC0YmgByHv/fgCH5Y/ uoHCLq3Y/LcpCAVgnncwAxaOgtux718BMO5AYxsxHQeo8tdf/fUSoULJoBT0Szv/nAqf cqfwbyDtQZqp1Ays6ABYQH1v2dNp5ziSX50kKToo+xxFGvJJ1Qpw/xLytnsI3A0GpSg+ MjLWaB8seOpf4aHYUzJwxlJZbXOl2owCxfdpJpRKUsbYM1SUF+K0FLyq/DGrCgSh+F8W jHKQ==
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=OI9KDt39H4+4qPHZkmnaOxlBjZu3C9U+G8j/uz2H1E0=; b=QyDCO0E/qZa6Ye/Bud8Qgb8ghsQLMiKItxgFyU0Rk2/KMaWFMlTwB2JKtffuB3/1/N eRB91Gehw4Y/UfwdHYmoTyh/Zu5VLsjHdpL0Y0tjp0RZsNvj8Xo0lxqmzTGb329CSozq awxKqpt6KUbjS/9znz8/ysgit/L2su2hinm2t9iJg4PkVE9M3I+IzD/dNc4jd4Oh+K49 sVGRBbgv9CIYRhU1bL3ebS7tTSJakXOALw//uyejkVKQmXy4+R57bWLMhwxYvsmf9CRa 6xZ2cAAm66PMGj4WIIIQPU55FtaXI+0/BUWe7kN/wXGFwbLuYOeby8Qc7G+9u5OKnBsL uhCA==
X-Gm-Message-State: AOAM533aROAUgVqOrcsagBsz5KyT+FTDXoHMvtGwSXZLDqWG/VGPEjXs VTAwLApDFXO/lLOjpicggN+cyqXsnYfT9g3yj3s=
X-Google-Smtp-Source: ABdhPJzTWkPMrvf//oF7dSvjZ+uG4aUMBUKih+TvZaYScr85syA+jArv2JSAhejB0DBESTXiyu9PxjWO/HMHu4r4j78=
X-Received: by 2002:a05:6512:308d:: with SMTP id z13mr21432472lfd.130.1620220994473; Wed, 05 May 2021 06:23:14 -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> <B31A661C-FED6-4005-813C-E87EF6D5E98B@nokia.com> <AM0PR07MB5490DC3EC59D021F6460E7A091599@AM0PR07MB5490.eurprd07.prod.outlook.com>
In-Reply-To: <AM0PR07MB5490DC3EC59D021F6460E7A091599@AM0PR07MB5490.eurprd07.prod.outlook.com>
From: Shunsuke Homma <shunsuke.homma.ietf@gmail.com>
Date: Wed, 5 May 2021 22:23:02 +0900
Message-ID: <CAKr2Fb_swXG49R9T1_ASL58zUuGLdsSad9rvyNWS-gDbKuQWgA@mail.gmail.com>
To: "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>
Cc: Loa Andersson <loa@pi.nu>, "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>, "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="000000000000d5549b05c19518ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/aKiFzlxoz9jGlA6eSGa7hFuxPnY>
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: Wed, 05 May 2021 13:23:23 -0000

Hi,


Sorry for cutting in...


I’m not a native English speaker and I’m not sure if my understanding on
the words is correct, but I think “consumer” would be more appropriate,
because I feel that “consumer” implies people rend a slice from a slice
provider with “paying fee”. (On the other hand, in my understanding,
“consumer” means a user of a service and it is independent of whether
he/she pays fee or not.)


As you know, network slice concept generally allows hierarchical structure
(of course, the current IETF network slice definition allows it). For
example, an IETF network slice may be used to provide connectivity (and
some functionalities) to other slices, such as 5G slices, which are under
the same provider, for creating an E2E slice. In such case, can other
slices or a higher orchestrator coordinating these slices be called
“customer”? (In this case, there would not be any payments.)


I’m sorry if my understanding on “customer” is incorrect and it can be
applied to such cases.


Regards,


Shunsuke

2021年5月5日(水) 21:18 Belotti, Sergio (Nokia - IT/Vimercate) <
sergio.belotti@nokia.com>gt;:

> Hi Adrian,
> +1
>
> Thanks
> Sergio
>
> > -----Original Message-----
> > From: Teas <teas-bounces@ietf.org> On Behalf Of Rokui, Reza (Nokia -
> > CA/Ottawa)
> > Sent: Wednesday, May 5, 2021 1:13 PM
> > To: adrian@olddog.co.uk
> > Cc: mohamed.boucadair@orange.com; teas@ietf.org; Loa Andersson
> > <loa@pi.nu>
> > Subject: Re: [Teas] Moving forward with
> draft-ietf-teas-ietf-network-slices
> >
> > Hi Adrian,
> >
> > I am fine with the definition of “Customer” provided below.
> >
> > Reza
> >
> > > On May 5, 2021, at 7:06 AM, Adrian Farrel <adrian@olddog.co.uk> 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
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>