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

Loa Andersson <loa@pi.nu> Wed, 05 May 2021 08:48 UTC

Return-Path: <loa@pi.nu>
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 E37BC3A15E1 for <teas@ietfa.amsl.com>; Wed, 5 May 2021 01:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 gXUFb6S_oYqa for <teas@ietfa.amsl.com>; Wed, 5 May 2021 01:48:22 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E4963A188A for <teas@ietf.org>; Wed, 5 May 2021 01:48:21 -0700 (PDT)
Received: from [192.168.0.7] (c83-250-136-37.bredband.comhem.se [83.250.136.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id C59C82FD165; Wed, 5 May 2021 10:48:16 +0200 (CEST)
To: adrian@olddog.co.uk, teas@ietf.org
References: <037401d740c5$70a9cc30$51fd6490$@olddog.co.uk>
From: Loa Andersson <loa@pi.nu>
Message-ID: <3ea262cf-e4c0-5ec0-9736-aedaf6d5d4d8@pi.nu>
Date: Wed, 5 May 2021 10:48:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <037401d740c5$70a9cc30$51fd6490$@olddog.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/EYsxrjqMDccTpzV303bSuWDNbd8>
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 08:48:27 -0000

Adrian, WG,

On customer vs. consumer Adrian says:


On 04/05/2021 11:11, Adrian Farrel wrote:
>     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.

I don't know if it is too late to bring this 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 eatss what i bought at your shop).

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?

/Loa

-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64