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

mohamed.boucadair@orange.com Wed, 05 May 2021 11:14 UTC

Return-Path: <mohamed.boucadair@orange.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 65D633A10C1 for <teas@ietfa.amsl.com>; Wed, 5 May 2021 04:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level:
X-Spam-Status: No, score=-2.117 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 zX2GNcJnUiV5 for <teas@ietfa.amsl.com>; Wed, 5 May 2021 04:14:36 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (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 17F323A10C5 for <teas@ietf.org>; Wed, 5 May 2021 04:14:35 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 4FZvHZ2dYDz2xms; Wed, 5 May 2021 13:14:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1620213274; bh=uq4iHmVcHHHBbnSuMr2N0gIegPcYRv0+lz+kA6L2TO8=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=lTYPOZctv4EcaQXEbaVKdjD//gP2MAN+ybs/B/XKwhr2SKi2BeqTahs2mvYxWbxot llv1OWiN3/cIwLYSfY/XChe2NlhtZO9Ctp8WjqzMrHsN+O4Yi3PiZS/6U+hdEvqZXy Cnqqlj3zF+T9hh1felg80SxvIOrKty97oejNkC6QsYyoYt6n/7onuuCBKOwzTR0BwL 7EHXkM00/XZb/565vn2GOTHUW80HfcG3r1zS3IJxtsVWMSDv0Jnu6Lbqxj3N6yWhqH iId7Vy90wgEOVLe9A1SUqqsNX6+FqPdmkw0g9iOqJgRGgMVMheOaDGa2uma/SecFYp Dd0uxtIPwcMMQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.76]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 4FZvHZ1YWqzBrLQ; Wed, 5 May 2021 13:14:34 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, '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: AQIxNfjF9qcx9VubDm1D4ubI8og6YwEz+LibAjUMGbABYFA3hqn6hfMAgAACheA=
Date: Wed, 5 May 2021 11:14:33 +0000
Message-ID: <28018_1620213274_60927E1A_28018_67_2_787AE7BB302AE849A7480A190F8B933035376E39@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
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: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/uGM-Cq7plD5gbq1S-dlCGOScxP0>
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:14:41 -0000

Re-,

Works for me. Thanks. 

I have one comment, though: s/IETF Network Slice/IETF Network Slice Service.

Cheers,
Med

> -----Message d'origine-----
> De : Adrian Farrel [mailto:adrian@olddog.co.uk]
> Envoyé : mercredi 5 mai 2021 13:06
> À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>om>; 'Loa
> Andersson' <loa@pi.nu>nu>; teas@ietf.org
> Objet : 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.


_________________________________________________________________________________________________________________________

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.