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

Qin Wu <bill.wu@huawei.com> Thu, 23 January 2020 01:44 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 E6EF8120045; Wed, 22 Jan 2020 17:44:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 qhEtRGZCeyWX; Wed, 22 Jan 2020 17:44:29 -0800 (PST)
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 0F723120018; Wed, 22 Jan 2020 17:44:29 -0800 (PST)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id AC28C364166C72F70F74; Thu, 23 Jan 2020 01:44:27 +0000 (GMT)
Received: from lhreml718-chm.china.huawei.com (10.201.108.69) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 23 Jan 2020 01:44:27 +0000
Received: from lhreml718-chm.china.huawei.com (10.201.108.69) by lhreml718-chm.china.huawei.com (10.201.108.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 23 Jan 2020 01:44:27 +0000
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml718-chm.china.huawei.com (10.201.108.69) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 23 Jan 2020 01:44:26 +0000
Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.143]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0439.000; Thu, 23 Jan 2020 09:44:13 +0800
From: Qin Wu <bill.wu@huawei.com>
To: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.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>, "Cristian Felipe Rosero Carvajal (COMMS-EGM)" <cristian.carvajal@wipro.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
Thread-Topic: Mail regarding draft-ietf-i2rs-yang-l2-network-topology
Thread-Index: AdXRjFcIGdJtSQvQRQam0avtkWVeYA==
Date: Thu, 23 Jan 2020 01:44:12 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA95F5FDE@dggeml531-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.123]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA95F5FDEdggeml531mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/LeKf8CTxVsN_IBdmVj6aKjhqgM0>
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: Thu, 23 Jan 2020 01:44:32 -0000

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; i2rs@ietf.org
抄送: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>om>; Cristian Felipe Rosero Carvajal (COMMS-EGM) <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