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

Adrian Farrel <> Wed, 05 May 2021 09:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F13553A0B68 for <>; Wed, 5 May 2021 02:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.782
X-Spam-Status: No, score=0.782 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=2.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Mf91O2iNi-qO for <>; Wed, 5 May 2021 02:58:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 12F6D3A0B60 for <>; Wed, 5 May 2021 02:58:57 -0700 (PDT)
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id 1459wtb1007497; Wed, 5 May 2021 10:58:55 +0100
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 64A9C22048; Wed, 5 May 2021 10:58:55 +0100 (BST)
Received: from (unknown []) by (Postfix) with ESMTPS id 4F57C22042; Wed, 5 May 2021 10:58:55 +0100 (BST)
Received: from LAPTOPK7AS653V ( [] (may be forged)) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id 1459wsYM003181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 May 2021 10:58:54 +0100
From: Adrian Farrel <>
To: 'Loa Andersson' <>,
References: <037401d740c5$70a9cc30$51fd6490$> <>
In-Reply-To: <>
Date: Wed, 05 May 2021 10:58:53 +0100
Organization: Old Dog Consulting
Message-ID: <009401d74195$41fd70a0$c5f851e0$>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQIxNfjF9qcx9VubDm1D4ubI8og6YwEz+LibqhcYFGA=
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--6.737-10.0-31-10
X-imss-scan-details: No--6.737-10.0-31-10
X-TMASE-Result: 10--6.737500-10.000000
X-TMASE-MatchedRID: 8+bhjh9TQnGyoI+bK8UPQnFPUrVDm6jtC/ExpXrHizzCvo6DOxRiGvrB QG4lHOVdNXbXQqH6D3TXA34IiFg0bckwYM+oZdHX4M3l0EeXvQ305GPBMOUChMI9dI7bfY/ve4/ lQZWR7BJq1r55FCyIt758RPNRRoZDEONKxfrChoLi709uFnkxd6VjgXyvS9c/GUs9b7xvtJqVRz EZ9aTQbfS/9U2/Kffdm4kGJzpzTBBxQamqjayUs9YpUOCigMK3JjoAtfwU0s5QKAQSutQYXMEjo Fgm7EFKFUFBdbv9pv/df9Rgfcas3t/fDBfIC7YyxrcEU94eVgsr9gVlOIN/6myIID37xcHKAbO5 5XKJGy1nHQJ2jUDp71+24nCsUSFN/fTpDjOELgPdB/CxWTRRu4as+d5/8j569NsybRQq/QCU/GP ZZRMXBzMYWWLAXxxhwUpi3DRPGaQLxcqOxVsmNQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <>
Subject: Re: [Teas] Moving forward with draft-ietf-teas-ietf-network-slices
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 05 May 2021 09:59:00 -0000

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?