Re: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology

Qin Wu <bill.wu@huawei.com> Mon, 23 March 2020 12:06 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51C7E3A0866; Mon, 23 Mar 2020 05:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 ftVOX-rNfAyl; Mon, 23 Mar 2020 05:06:21 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 0EC5C3A0862; Mon, 23 Mar 2020 05:06:21 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id BEB0362C522C5DF3D308; Mon, 23 Mar 2020 12:06:15 +0000 (GMT)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 23 Mar 2020 12:06:15 +0000
Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.75]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0487.000; Mon, 23 Mar 2020 20:06:07 +0800
From: Qin Wu <bill.wu@huawei.com>
To: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com>, "Susan Hares" <shares@ndzh.com>, "draft-ietf-i2rs-yang-l2-network-topology@ietf.org" <draft-ietf-i2rs-yang-l2-network-topology@ietf.org>, "i2rs@ietf.org" <i2rs@ietf.org>
CC: =?utf-8?B?T3NjYXIgR29uesOhbGV6IGRlIERpb3M=?= <oscar.gonzalezdedios@telefonica.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>, "Cristian Felipe Rosero Carvajal (COMMS-EGM)" <cristian.carvajal@wipro.com>
Thread-Topic: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology
Thread-Index: AdYBCbU34H0zo9t8QOu3BoGpE5PG8g==
Date: Mon, 23 Mar 2020 12:06:06 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAAD5820A6@dggeml531-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.123]
Content-Type: multipart/related; boundary="_004_B8F9A780D330094D99AF023C5877DABAAD5820A6dggeml531mbschi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/V2VX7lIZPZeEH-l5R04y8nYiB-0>
Subject: Re: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 12:06:43 -0000

Hi, SAMIER:
Thanks for your proposal. A few comments:
It looks all the  parameters are from LLDP Ethernet frame structure, most of them are state information. Do we need to collect all of them, how do you decide which one needs to be configured, which one needs to be collected and reported?
The most important parameters are neighbor mac address, port-id, what is missing is source mac address. For other parameters, I am
Not sure they are important, e.g., do we expect H-SDN-C to configure age and ttl?
In addition, should neighbor mac address and source mac address is defined as node attributes, what about augment from ietf-network model with LLDP specific attributes, therefore all
LLDP parameters are part of inventory defined in RFC8345.

-Qin
发件人: SAMIER BARGUIL GIRALDO [mailto:samier.barguilgiraldo.ext@telefonica.com]
发送时间: 2020年3月17日 16:44
收件人: Qin Wu <bill.wu@huawei.com>om>; Susan Hares <shares@ndzh.com>om>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org; i2rs@ietf.org
抄送: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>om>; Dongjie (Jimmy) <jie.dong@huawei.com>om>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com>
主题: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology

Hello guys,

Reagarding this topic we have defined a small LLDP model based on the L2-Topology. We appreciate your feedback:

LLDP

module: ietf-l2-lldp-topology

  augment /nw:networks/nw:network/nw:network-types:

    +--rw lldp-topology!

  augment /nw:networks/nw:network/nw:node/nt:termination-point/l2t:l2-termination-point-attributes:

    +--rw lldp-termination-point-attributes

       +--rw enable?            boolean

       +--ro neighbor?          yang:mac-address

       +--rw age?               uint64

       +--rw ttl?               uint16

       +--ro lldp-tlvs-state

          +--ro sys-name?           string

          +--ro sys-desc?           string

          +--ro port-id?            string

          +--ro port-description?   string


Regards,


Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte |

Móvil +57 3017026430

Móvil +34 665416074

E-mail samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>

E-mail samier.barguil@wipro.com<mailto:samier.barguil@wipro.com>

________________________________
De: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>
Enviado: miércoles, 11 de marzo de 2020 5:27
Para: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org> <draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>>; i2rs@ietf.org<mailto:i2rs@ietf.org> <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Cc: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>
Asunto: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology


Thanks SAMIER for feedback, we will move draft-ietf-i2rs-yang-l2-network-topology to the next stage soon.



-Qin

发件人: SAMIER BARGUIL GIRALDO [mailto:samier.barguilgiraldo.ext@telefonica.com]
发送时间: 2020年3月11日 17:54
收件人: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
抄送: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>
主题: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology



Qin/Su Thanks a lot for the interaction and the Quick answer.



I have discussed this topic with @Oscar González de Dios<mailto:oscar.gonzalezdedios@telefonica.com> and we are sure that we need a external draft for this specific purpose. The example, Is good as a reference but we can not ask for it in our controllers as a mandatory requeriment. We are requesting "standards" in order to avoid "cutomizations".



I believe we can deliver an initial version of the LLDP model with our minimal requeriments. And after that start the discussion with the other operators.



Regards,



Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte |

Móvil +57 3017026430

Móvil +34 665416074

E-mail samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>

E-mail samier.barguil@wipro.com<mailto:samier.barguil@wipro.com>



________________________________

De: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>
Enviado: miércoles, 11 de marzo de 2020 2:44
Para: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org> <draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>>; i2rs@ietf.org<mailto:i2rs@ietf.org> <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Cc: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>
Asunto: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology



Samier:

Example LLDP topo model could be put as appendix of the standard if you think it meets your needs.

If my understanding is correct, the L2 topo model can only been extended with L2 specific attributes, from the case you are looking into, it probably should be a separate draft to define such multi-purpose model.



-Qin

发件人: SAMIER BARGUIL GIRALDO [mailto:samier.barguilgiraldo.ext@telefonica.com]
发送时间: 2020年3月10日 23:48
收件人: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
抄送: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>
主题: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology



HI Qin / Sue,



I have one conceptual doubt that maybe you can help me to clarify. If we put the LLDP model as an example It is part of the standard? If not we have a gap because we expect to request the standard support to our network providers.



In that case, we can fill this GAP proposing a new standard based on the definitions you have already done for L2 and L3 topologies. We were thinking a generic multi-purpose topology model to support for example:

  *   LLDP
  *   OSPF
  *   ISIS
  *   BGP

What do you think about tis?



Regards,



Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte |

Móvil +57 3017026430

Móvil +34 665416074

E-mail samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>

E-mail samier.barguil@wipro.com<mailto:samier.barguil@wipro.com>



________________________________

De: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>
Enviado: lunes, 9 de marzo de 2020 22:59
Para: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org> <draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>>; i2rs@ietf.org<mailto:i2rs@ietf.org> <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Cc: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>
Asunto: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology



Thanks Sue to advance this work,

Samier, let me know if you want to add LLDP topo model in the appendix, which is augmented from L2 topo model, similar to OSPF topology example is defined in the Appendix B of RFC8346.

If we reach agreement on this (whether not needed or add an example in the appendix), I think we are ready to go.



-Qin

发件人: Susan Hares [mailto:shares@ndzh.com]
发送时间: 2020年3月10日 1:29
收件人: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>; 'SAMIER BARGUIL GIRALDO' <samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
抄送: 'Oscar González de Dios' <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; 'Cristian Felipe Rosero Carvajal (COMMS-EGM)' <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>
主题: RE: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology



Qin and Samier:



I’m excited to see that L2 Data model is being implemented.



If it turns out that the L2 topology model needs to be augmented with additional LLDP topology drafts,  then I suggest you simply write an augmentation for the L2 model.    I will be glad to support you and work with on the LLDP.    With this in mind, I will close the shepherd’s report and send this long overdue RFC to the IESG.    If the I2RS WG closes, then the



On the BGP-LS information,  I suggest sending a note to IDR to determine if anyone has collected LLDP information across domains.   If you wish, I can (as co-chair of IDR) send that information for you.



Susan Hares



From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Qin Wu
Sent: Monday, February 10, 2020 1:12 AM
To: SAMIER BARGUIL GIRALDO; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
Cc: Oscar González de Dios; Dongjie (Jimmy); Cristian Felipe Rosero Carvajal (COMMS-EGM)
Subject: Re: [i2rs] Mail regarding draft-ietf-i2rs-yang-l2-network-topology



SAMIER:

Come back for this comment, I think similar to L3 Topology, L2 network topology model is independent of layer 2 protocol type, e.g., LLDP. But Layer 2 topology model can be augmented with addition definitions for LLDP topology type.

One OSPF topology example is defined in the Appendix B of RFC8346. LLDP topology model can be defined in the same way.



Regarding your question, I think H-SDN-C should have boundary node information from its inventory model collected by each IP controller and it is the job of H-SDN-C to be responsible for topology stitching in different domains,

 there are many protocols that can be used to expose topology from IP controller to H-SDN-C, e.g., BGP-LS routing protocol.  We haven’t seen LLDP can be used to collect cross inter-domain neighbourhood,e.g.,peer IP controller.



-Qin

发件人: SAMIER BARGUIL GIRALDO [mailto:samier.barguilgiraldo.ext@telefonica.com]
发送时间: 2020年1月23日 22:27
收件人: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
抄送: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>
主题: RE: Mail regarding draft-ietf-i2rs-yang-l2-network-topology



Hi Qin,



I hade made a mistake. I was trying to say LLDP neighbour. A



I will try to explain it again to avoid confusions.  As your mentioned the LLDP can be enabled in the network and create the L2 Links (this is our intention). However, We have not seen in the model the way to express this inter-domain neighbourhood, for example:



[cid:image001.png@01D6014D.5E5B0020]

In this network scenario:

  *   Each domain controller will expose a L2 Topology
  *   IP Controller-1 have not in its node DB the Node B
  *   IP Controller-2 have not in its node DB the Node A

How the H-SDNc can join the two L2-topo (each from a controller) to generate the common view? It is possible with this model?



Regards,

--

Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte |

Móvil +57 3017026430

Móvil +34 665416074

E-mail samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>

E-mail samier.barguil@wipro.com<mailto:samier.barguil@wipro.com>



________________________________

De: Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>
Enviado: miércoles, 22 de enero de 2020 20:44
Para: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>>; draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org> <draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>>; i2rs@ietf.org<mailto:i2rs@ietf.org> <i2rs@ietf.org<mailto:i2rs@ietf.org>>
Cc: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>
Asunto: RE: Mail regarding draft-ietf-i2rs-yang-l2-network-topology



Hi, Samier:

L2 topo is used to describe neighbor relationship and can be collected by LLDP or any other Layer 2 protocol, are you sure LDP protocol should be part of L2 topo model? If there is a use case for LDP, L2 topo model could be augmented in the separate model to support such use case.

BTW, L2 topo has completed WGLC. The token is in the document shepherd’s hand.



-Qin

发件人: SAMIER BARGUIL GIRALDO [mailto:samier.barguilgiraldo.ext@telefonica.com]
发送时间: 2020年1月21日 0:36
收件人: draft-ietf-i2rs-yang-l2-network-topology@ietf.org<mailto:draft-ietf-i2rs-yang-l2-network-topology@ietf.org>; i2rs@ietf.org<mailto:i2rs@ietf.org>
抄送: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com<mailto:oscar.gonzalezdedios@telefonica.com>>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <cristian.carvajal@wipro.com<mailto:cristian.carvajal@wipro.com>>
主题: Mail regarding draft-ietf-i2rs-yang-l2-network-topology



Hello authors,



We have been using your model to describe our L2 Topology in a single domain IP scenario. During the last month we have been exporting this topology to a centralized entity in order to build a multi-domain (two IP domain controllers) L2-Topology. However, In order to build this end-to-end L2 view of our networks we were expecting to use the LDP neighbour relationship, however in the draft-ietf-i2rs-yang-l2-network-topology there is not such possibility.



Do you have any plan to include this information in the model? If not how do you expect a centralized entity (Network Orchestator) can build an end-to-end L2 view of the network if the L2 Topo is reported by two domain controllers?



Thanks in advance for your answer.



Regards,

Samier Barguil
Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte |

Móvil +57 3017026430

Móvil +34 665416074

E-mail samier.barguilgiraldo.ext@telefonica.com<mailto:samier.barguilgiraldo.ext@telefonica.com>

E-mail samier.barguil@wipro.com<mailto:samier.barguil@wipro.com>



________________________________

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



________________________________

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



________________________________

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



________________________________

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

________________________________

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