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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 06 May 2021 03:52 UTC

Return-Path: <jie.dong@huawei.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 900893A2E8B for <teas@ietfa.amsl.com>; Wed, 5 May 2021 20:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 S0nvJ80dh2r8 for <teas@ietfa.amsl.com>; Wed, 5 May 2021 20:52:46 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF1F03A2E88 for <teas@ietf.org>; Wed, 5 May 2021 20:52:45 -0700 (PDT)
Received: from fraeml736-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FbKBZ656Xz72fV8 for <teas@ietf.org>; Thu, 6 May 2021 11:41:42 +0800 (CST)
Received: from dggeme753-chm.china.huawei.com (10.3.19.99) by fraeml736-chm.china.huawei.com (10.206.15.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Thu, 6 May 2021 05:52:41 +0200
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme753-chm.china.huawei.com (10.3.19.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Thu, 6 May 2021 11:52:39 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2176.012; Thu, 6 May 2021 11:52:39 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "'Loa Andersson'" <loa@pi.nu>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] Moving forward with draft-ietf-teas-ietf-network-slices
Thread-Index: AddAxWjITt1c7iy5R82GjNJUuT9irQAgunSAAAJ4G4AAAhOtgAAAQk8AADNb5kA=
Date: Thu, 6 May 2021 03:52:39 +0000
Message-ID: <d1458825956f48ffa417f07707cba535@huawei.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>
In-Reply-To: <00a001d7419e$99e5a040$cdb0e0c0$@olddog.co.uk>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.143]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/UkzR3BvsP7KLqfzX4kW9NgfJNGI>
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 03:52:51 -0000

Hi Adrian,

My feeling is in this context "customer" is better than "consumer". When talking about the customers of network services, there is also another term: tenant. Sometimes customer and tenant may be considered interchangeable, while as you said customer can be generic covering either an individual, an entity, or a physical or logical component.

Best regards,
Jie

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: Wednesday, May 5, 2021 7:06 PM
> To: mohamed.boucadair@orange.com; 'Loa Andersson' <loa@pi.nu>nu>;
> teas@ietf.org
> Subject: Re: [Teas] Moving forward with draft-ietf-teas-ietf-network-slices
> 
> 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