Re: [Teas] Why term transport slice? WG adoption - draft-nsdt-teas-transport-slice-definition

LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com> Sat, 05 September 2020 17:00 UTC

Return-Path: <luismiguel.contrerasmurillo@telefonica.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 182C53A0DF4; Sat, 5 Sep 2020 10:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.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 Z0X_jsslGkpG; Sat, 5 Sep 2020 10:00:03 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2135.outbound.protection.outlook.com [40.107.22.135]) (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 DA5A03A0DEA; Sat, 5 Sep 2020 10:00:02 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jUIQsR/h+TVWFcjbih0RW38nOX62cdQjDcjB9hMroMngohIX8Jf6/kIqWF/GjDip8z2+HGX9oAveNn0AJhIv5L1mctNdUHgVUzxUKEBU1WJF2aPghHoapq1Gcp2IkBK+0oX59/Nc/VA/63QWl04oDfziSt2wrtM/fpkVVLAYByngyHRLgMv2VJB6493cSstmOXA0eOk+qMz17SKGGG4rLr6hd1tHBqGptIwLdbwtudiNG9HcxgxGHTdOrbuWJSM8CwCarSzYiQRsJp8YHvfbHTLWxvl7pnhURedEwa6d4AmA3B4KgwLryby0lMTQ7aWXd4BNxaAh223mRLn4jOENag==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UscgGaZNIDJCFkRRUI8ztgwElLfzH5bNq4j7FmitEhY=; b=EomDhlPovBqfJHRXS9bOIYdGpDKh1KZlyWGx362Ki9HJ9LWnRR74yhs456zKJoHRs2vrE7SBwQ3F3zjJzs+NyR80r8gSMOFjRc/HEdQNJlv7bvShM7OMgarrwZs6UscNUY2Zc1PXdI0EgsnormjRD1vcaV2rSZY8s01XH6Z1fy1Oj4BaG6A0Ee6EUICFcg/6Dwj2TfVANk/SomlRkhdlq8u+2cIlh7dDE63bF/rD+KiM5jozrwGU8CLDKOUFTaJ39R8hmUI4Ygl2XNtrLOFWWzsV11+Jmb93ZMChEqyuJAaGxYdadARgWPC6FH5He5MRjQAKkqkpin6NK3YsP0YYGg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telefonica.com; dmarc=pass action=none header.from=telefonica.com; dkim=pass header.d=telefonica.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UscgGaZNIDJCFkRRUI8ztgwElLfzH5bNq4j7FmitEhY=; b=ic9m6x+/PeEwjQDQ8AYUHD58add5mN814DEl4ZNn5+/AjLyGnB7QKTFtorZ2yPmcuso9PwqfjfgSGtKBRS+xoCNxXrYUpzeTgoMlPo7pKSqEG6hbIBMRAolK9grIMbEgcgC7gubr8UK09Le31wSYnlMUxRJJeHDDYrvj/IPxjMU=
Received: from DB6PR0601MB2150.eurprd06.prod.outlook.com (2603:10a6:4:4d::13) by DB8PR06MB6235.eurprd06.prod.outlook.com (2603:10a6:10:108::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.15; Sat, 5 Sep 2020 16:59:58 +0000
Received: from DB6PR0601MB2150.eurprd06.prod.outlook.com ([fe80::8808:fc2e:6731:22c9]) by DB6PR0601MB2150.eurprd06.prod.outlook.com ([fe80::8808:fc2e:6731:22c9%11]) with mapi id 15.20.3348.018; Sat, 5 Sep 2020 16:59:58 +0000
From: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>
To: Young Lee <younglee.tx@gmail.com>, John E Drake <jdrake=40juniper.net@dmarc.ietf.org>
CC: "BRUNGARD, DEBORAH A" <db3546@att.com>, Kiran Makhijani <kiranm@futurewei.com>, TEAS WG Chairs <teas-chairs@ietf.org>, TEAS WG <teas@ietf.org>, Eric Gray <ewgray2k@gmail.com>, Igor Bryskin <i_bryskin=40yahoo.com@dmarc.ietf.org>, "EXT-vishnupavan@gmail.com" <vishnupavan@gmail.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
Thread-Topic: [Teas] Why term transport slice? WG adoption - draft-nsdt-teas-transport-slice-definition
Thread-Index: AQHWgsX63GErIr9JAECVKqmtq/XJj6lYjNjQgADphICAAMrq0A==
Date: Sat, 5 Sep 2020 16:59:57 +0000
Message-ID: <DB6PR0601MB2150EB1EA28A5A767D1A54C59E2A0@DB6PR0601MB2150.eurprd06.prod.outlook.com>
References: <EBB5115F-1EF4-4F07-88FB-C5598A640D74@nokia.com> <DM5PR05MB33881A3CE266B2B38A6D29C0C72D0@DM5PR05MB3388.namprd05.prod.outlook.com> <CAGHSPWM0fvoh_vKWsKGtaCkc11UHgysi2_oSJ95UqKv7S785+Q@mail.gmail.com>
In-Reply-To: <CAGHSPWM0fvoh_vKWsKGtaCkc11UHgysi2_oSJ95UqKv7S785+Q@mail.gmail.com>
Accept-Language: es-ES, en-US
Content-Language: es-ES
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=telefonica.com;
x-originating-ip: [83.55.117.152]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 13ba29ee-4ee7-49ab-db29-08d851bd1ed2
x-ms-traffictypediagnostic: DB8PR06MB6235:
x-microsoft-antispam-prvs: <DB8PR06MB6235DA6AB21D34E75FED36919E2A0@DB8PR06MB6235.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: i24E93m+xlDeT2SC4/mxy5vOg9+6UVPeVM/ODekobJ9K9SRAmpD7ZIt01Nl7GMlx/f2dmcdUSJPsjwswIpO0RSKNWernBPI01skOBAGjSEPwH+bgGhi9+ACvZcdEyWcg80X8ypIYwmfEaUSQ7TzZSPqowsIP2RtFCh+X9Ok8KdBGpz/kIsXp+eMHBKqF+vhuWbmJRaHlzIO1NMlM2UZIBkoHGwdu1GU8szQPcH8RwHyFc5G3aksVhGYJi35dVe0f5N8ESJsY9Ox+bvx2B5mtkTv2AJWOBc9y93r0IiFhbb0TrtQOT64yMoHPVuuz2Iioz+8sgJluiNAl4VQUu6xaE+oVnIyLPN9u8yhK/RVzlgd+GSKYXAHuFnjyMl0edkcaflCbpWicsx1f5q1hrwvZdZmYaicEQ6Bi4O5llEkR+HnR86UAF/yRMYfat+/HUTOtNpwZDN151D1f/xX21K7VhA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB6PR0601MB2150.eurprd06.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(396003)(39860400002)(366004)(136003)(346002)(53546011)(19627235002)(66574015)(66476007)(9326002)(76116006)(4326008)(66946007)(5660300002)(9686003)(33656002)(2906002)(66556008)(86362001)(8676002)(8936002)(26005)(186003)(966005)(786003)(7416002)(64756008)(66446008)(71200400001)(478600001)(316002)(6506007)(52536014)(166002)(83380400001)(55016002)(7696005)(110136005)(54906003)(9010500006)(579004); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: 2PEiKYeJlwKpuBvrhijdCe40cxzKvM0wwzVQBuLelRdHD8zl/9uvItOErTyflBuFekuNfYzf0WNkKK1dHXohJfoBPkSH9nSkNeGK6s9A791Mw7/PKByt7png4zt9CEL4XKoT1NA3CBBxyKu+mzwGdwCCPYBvoWweYlGmSctX8DHEOkHK9rl1pahANlHlbiBvFz3Osnsejh0e7Qw7vKgsHC2MgY8VOjvqwamgHPqTBjaXCUFT6AJfhCR2ejTnMEWLhM55FXJ94nwDoZ2IOsmoRk4jm4mpiGzO3pRQ291tQxKirlFHkhlD4Oq4gUS+/JXA+NW7cV/Nw0OUc3/0swsBqs0+8aamteYUGekon36vfdNViwh/ZS74jh5Nvuu6mNKv8VOcRjuTc6WbIlSmSf3EmtvYs6KPwMVfdP5itbF0iRNVFhU+fYL1Q+SSU+XpWllBCHne2/r0vc2dnc5+24OpPGTGnZPhuAFOncV3nuis1l2qQ06GSyQ2wVn+HuQ4DHzrCsObozf/QxC/++ciT5B2BPdAOaV78Ide6R8r3NdzRpcboRlbMLe3v8FD+T2aDYVSoRQlySmA0fUfRAsVAk9G1dMZQGl8Mb5+p4BZ6j2rrqc6GRsAU8g8yXCci9jv/xoiyW2G+SMpt32qQNKpUGkX1g==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DB6PR0601MB2150EB1EA28A5A767D1A54C59E2A0DB6PR0601MB2150_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB6PR0601MB2150.eurprd06.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 13ba29ee-4ee7-49ab-db29-08d851bd1ed2
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Sep 2020 16:59:57.8480 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: gw/IArPFohm4FDLs1aYblXnAEKTU94qdFTCtCbC/u+oQpoC1xPy9kXAuPeXV+2aNY1s2EJDEe0fWB8nN1orJQMVh2B9F12g9aIgykglmxd/GXmCn3IAWt3bDBq4lOSNiA7BtDuewhga3rqCYsQxzCQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR06MB6235
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/agfFcXPD__agWtn3Su3z92hxZZc>
Subject: Re: [Teas] Why term transport slice? WG adoption - draft-nsdt-teas-transport-slice-definition
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: Sat, 05 Sep 2020 17:00:08 -0000

Hi Young,

The starting point of the work has been to consider the (Transport) Slice Controller being technology agnostic. Using TE-related or whatever other mechanisms is part of the realization of the slice, so considered as an activity to be carried out later in the DT and or the WG when mapping the slice concept to different IETF related technologies (that could have host in TEAS or any other WG).

The customer/consumer perspective will probably don’t care about if the slice is provisioned through TE mechanisms. The customer is simply not aware of that because will not specify it (only SLOs and other characteristics that can be attributes of the desired slice).

It is true that multiple services could request slices. Note the work in progress in draft-contreras-teas-slice-nbi for this.

Respect to the point of the versatility of TE models to handle non-TE demands, I see it as a point in favor of not limiting the approach taken in the work done till now. I mean, precisely because of that versatility, the work done is valid and more comprehensive than just reducing the scope to TE, since TE is part of it.

Best regards

Luis


De: Teas <teas-bounces@ietf.org> En nombre de Young Lee
Enviado el: sábado, 5 de septiembre de 2020 6:35
Para: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>
CC: BRUNGARD, DEBORAH A <db3546@att.com>om>; Kiran Makhijani <kiranm@futurewei.com>om>; TEAS WG Chairs <teas-chairs@ietf.org>rg>; TEAS WG <teas@ietf.org>rg>; Eric Gray <ewgray2k@gmail.com>om>; Igor Bryskin <i_bryskin=40yahoo.com@dmarc.ietf.org>rg>; EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>om>; adrian@olddog.co.uk; Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com>
Asunto: Re: [Teas] Why term transport slice? WG adoption - draft-nsdt-teas-transport-slice-definition

Hi,

I agree with John. This is a good point. There are a mutiplicity of "customers/consumers" that would like to consume the "services" IETF/TEAS provides, and 3GPP is one of the customers that may be interested in fulfiling its TN subnet requirements for eMBB or uRLLC network slice types.

But there are other customers that TEAS ACTN supports among which are L1VPN for DCI, IP service providers that need a leased line between two end points, etc, let alone L2/3 VPN customers that need TE networks, and enhanced VPN.

TEAS ACTN effort has been to fulfill the common requirements coming from a plethora of diverse customers.

What about non-TE? As Igor nicely put in another email thread, ACTN VN/ TE Yang models can still be used as they provide all necessary basic components (non-TE specific) such as end points, service policies, sharing properties, etc. All components in YANG models can be made optional so all TE components can be skipped if there is a need for that.

Regards,
Young





2020년 9월 5일 (토) 오전 12:15, John E Drake <jdrake=40juniper.net@dmarc.ietf.org<mailto:40juniper.net@dmarc.ietf.org>>님이 작성:
Hi,

‘Network slice’.  As Adrian points out, this is the term that has been used in the IETF for quite some;  it is used in RFCs 8453, 8568, and 8578, as well as the preponderance of I-Ds on this topic.  Even if another term was correct, and I don’t think that, trying to use a term other than ‘network slice’ will continue to cause tremendous confusion.  I.e., changing terms is akin to closing the barn door after the horse has bolted.

As I noted yesterday, and throughout the *Network Slicing* design team meetings, I think it is up to an application that uses IETF network slices as components to indicate where in its design these IETF network slices fit.  I.e., IETF network slices are being designed for use by a multiplicity of applications and trying to make our terminology congruent with this one application is problematic.

Yours Irrespectively,

John



Juniper Business Use Only
From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> On Behalf Of Rokui, Reza (Nokia - CA/Ottawa)
Sent: Friday, September 4, 2020 10:16 AM
To: Kiran Makhijani <kiranm@futurewei.com<mailto:kiranm@futurewei.com>>; adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Eric Gray' <ewgray2k@gmail.com<mailto:ewgray2k@gmail.com>>; 'Igor Bryskin' <i_bryskin=40yahoo.com@dmarc.ietf.org<mailto:40yahoo.com@dmarc.ietf.org>>; 'TEAS WG Chairs' <teas-chairs@ietf.org<mailto:teas-chairs@ietf.org>>; EXT-vishnupavan@gmail.com<mailto:EXT-vishnupavan@gmail.com> <vishnupavan@gmail.com<mailto:vishnupavan@gmail.com>>; 'TEAS WG' <teas@ietf.org<mailto:teas@ietf.org>>; 'BRUNGARD, DEBORAH A' <db3546@att.com<mailto:db3546@att.com>>
Cc: Rokui, Reza (Nokia - CA/Ottawa) <reza.rokui@nokia.com<mailto:reza.rokui@nokia.com>>
Subject: [Teas] Why term transport slice? WG adoption - draft-nsdt-teas-transport-slice-definition

[External Email. Be cautious of content]

All,

Thanks for all feedbacks.

Let’s step back and address these questions: How and why the authors’ of the draft chose the term “Transport Slice”?

Before formation of the TEAS WG NSDT, there were lots of discussions and drafts to address the role of IETF for network slicing. Those discussion and drafts tried to address the network slicing  from different perspectives but in most cases they had one thing in common, they started by discussion the network slicing but at the end they really meant the Transports portion of the network slice. In other words, although the name of the draft and discussion was network slicing, but they just talked about Transport portion.  In other hand, the term network slice and Transport portion of a network slice were used interchangeably.

After creation of the NSDT, we collectively thoughts that the first order of business is to clarify this. So, the “draft definition” started. The following are the reasons:

Reason 1)
The first reason for this draft is to make very clear distinction between a network slice (defined for example by 3GPP) and transport portion of a network slice.
In our opinion it is essential to make a clear distinction between network slice and transport portion of a network slice. They are NOT the same since a network slice contain the transport portion.
The picture below was outcome of that discussion. In summary, a network slice is an end-to-end context and depends on the used case (i.e 5G, DCI, etc), it might contain a few other components (i.e. RAN, Transport, Core etc.)

[cid:image001.png@01D682AC.977C9B80]

Reason 2)
We just established the fact that an end-to-end network slice is different from transport portion of the network slice. The next question is that what the definition of the Transport portion of a network slice is.
This is fully discussed in draft but in summary the transport portion of a network slice describes the CONNECTIVITY between various endpoints. Our definition is aligned with MEF and 3GPP.

  *   MEF uses the same definition for Transport portion of the network slice”. See Section 5.3 of following white paper

     *   https://wiki.mef.net/display/CESG/Slicing+for+Shared+5G+Fronthaul+and+Backhaul+-+White+Paper<https://urldefense.com/v3/__https:/wiki.mef.net/display/CESG/Slicing*for*Shared*5G*Fronthaul*and*Backhaul*-*White*Paper__;KysrKysrKysr!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQ_6Dp7hs$>



  *   This is aligned with 3GPP. See Figure 4.9.3.1 of TR 28.801 and  http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G<https://urldefense.com/v3/__http:/www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G__;!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQECxLoTI$>

According to the picture below,  the reference of transport portion of a network slice  is referred by “Transport network supporting connectivity’

[cidimage001.png@01D6806A.8E70BC90]




Reason 3)
The next question is that which term shall be used for ‘Transport portion of an end-to-end network slice”?


  *   MEF uses the term “Transport Slice”. See Figure 17 of following white paper

     *   https://wiki.mef.net/display/CESG/Slicing+for+Shared+5G+Fronthaul+and+Backhaul+-+White+Paper<https://urldefense.com/v3/__https:/wiki.mef.net/display/CESG/Slicing*for*Shared*5G*Fronthaul*and*Backhaul*-*White*Paper__;KysrKysrKysr!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQ_6Dp7hs$>



  *   3GPP: See Figure 4.9.3.1 of TR 28.801 and  http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G<https://urldefense.com/v3/__http:/www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G__;!!NEt6yMaO-gk!RwBHv_fQ5XdrftEX2118w7OUiQg2mu-eHcRobC4KGZ-EPaqW2EcKPWfQECxLoTI$>

They do not directly address the transport portion of a network slice. They do not have a term for this. They mainly address the 5G RAN and 5G Core. As shown in the picture above, the reference of transport is phrase “Transport network supporting connectivity”.



  *   >From IETF point of view, these are potential choices for Transport portion of a network slice:

  *   Network slice: This for sure is NO. Reason 1) clearly shows that we shall not use term “Network slice” for transport portion. This is not correct.
  *   Use 3GPP phrase: “Transport network supporting connectivity”
  *   Use the phrase “Transport portion of the Network Slice”
  *   Use term “Transport Network Slice”
  *   Use term “Transport Slice”
  *   Adrian, Igor, Deborah and others, is there any other suggestion? If so, please add

From the above choices, the draft authors uses the term “Transport Slice” but not the “Transport Network Slice” to make sure we implicitly stating that Network Slice and Transport part are different.
Having said that, authors are open to suggestion. Please suggest your term.


Reza


_______________________________________________
Teas mailing list
Teas@ietf.org<mailto:Teas@ietf.org>
https://www.ietf.org/mailman/listinfo/teas

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição