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

Adrian Farrel <adrian@olddog.co.uk> Wed, 05 May 2021 11:05 UTC

Return-Path: <adrian@olddog.co.uk>
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 0A4643A104A for <teas@ietfa.amsl.com>; Wed, 5 May 2021 04:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.784
X-Spam-Level:
X-Spam-Status: No, score=0.784 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=2.7, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 W6QliREc8K21 for <teas@ietfa.amsl.com>; Wed, 5 May 2021 04:05:51 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02FA13A0FD9 for <teas@ietf.org>; Wed, 5 May 2021 04:05:50 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 145B5mmh024777; Wed, 5 May 2021 12:05:48 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8196F2203C; Wed, 5 May 2021 12:05:48 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id 691D922044; Wed, 5 May 2021 12:05:48 +0100 (BST)
Received: from LAPTOPK7AS653V (74.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.74] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 145B5l2s008741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 May 2021 12:05:47 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mohamed.boucadair@orange.com>, "'Loa Andersson'" <loa@pi.nu>, <teas@ietf.org>
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>
In-Reply-To: <9933_1620212302_60927A4E_9933_344_1_787AE7BB302AE849A7480A190F8B933035376DFA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Wed, 5 May 2021 12:05:46 +0100
Organization: Old Dog Consulting
Message-ID: <00a001d7419e$99e5a040$cdb0e0c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQIxNfjF9qcx9VubDm1D4ubI8og6YwEz+LibAjUMGbABYFA3hqn6hfMA
X-Originating-IP: 81.174.197.74
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-26132.007
X-TM-AS-Result: No--40.078-10.0-31-10
X-imss-scan-details: No--40.078-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-26132.007
X-TMASE-Result: 10--40.078000-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFqyoI+bK8UPQnFPUrVDm6jtmxawpTnIv8ZYbPLopoBzQrru Ujtsr/F2LEm1nQlSFXY+UayYenUbhFRHPXOO8PBcrWPyyJwe0IHYc9kUwzLgM2PK/53RnQ7FvC5 qcZ9b5e6C9FpVQ3HWgPJ6kan/hO9scAI85VuV5+2yBjDX4sGuTQvxMaV6x4s8bIggPfvFwcqrCF pHLL31kKSvjTUx+iaPKARHumklBHe1rSfuT05GphQSKrt8gY5dDIJ2W9wBb2m2a7uAlbKs2LBUp HHLYQpmPY09ws/vuNE8IJjIWPVzqkkfXU45UHTJtGM0cBDUM406En2bnefhoKsoAw12Y1UTtXpx KtGjgZ0HABmd5MFcW8VWt+webelAZU1Z8+q6r0BJHfeHL20/8vNkoMDX+kiuSnVG9A9T8TNz+NW kRQjaNrNATPgcw39DBdUIHYZOnBYam5LR76Ox+R3EEAbn+GRb4FBhMAaXjUx7lDzh8Z+EhgL1h7 7IqX0+vYKC2gleE+w8jF8qoAJJxfKH/YOVPQc03nHtGkYl/Vqy3YhOn/M0MdZd/DOmlnxItNfew smJeFZlFSORUVE4XgRRh1IZA32yljkS1MSR0TlFbfkTOopt/tZ8wL8wmNqsRUWQh4SEhGVJ2FFZ ZjlLDIordEds4OXB9gvyzqAiGUy3Cf840PjT3VkXzeMxWi6Hd1oKD5MO29WhUDAHFcyu8//cZLI rVlNZkZrRwSX45uTjrOv4f0EQHQ52ItB5LgeXrQcmzcV8ovwSDuyLvbnDBrXl40gTGJ5pfNbP1n cYLZA4HFt+vqKGDC38M+247Q7B58mLFF6hQfCeAiCmPx4NwGNn8XPiALIbm5N2YHMD0b8MyrfP9 j+C1d934/rDAK3zUc1+O1X9AzE=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/KD-Af-taymtmT1Ysm_3-tzZ86rE>
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 11:05:56 -0000

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.