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

SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com> Thu, 23 January 2020 14:27 UTC

Return-Path: <samier.barguilgiraldo.ext@telefonica.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 B3C6E12013B; Thu, 23 Jan 2020 06:27:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 6BL5PzvSbfmx; Thu, 23 Jan 2020 06:27:02 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00138.outbound.protection.outlook.com [40.107.0.138]) (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 1A101120133; Thu, 23 Jan 2020 06:27:01 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FVTY0qRcDINVwcRbCETHNyXzLmHCqvgGv/cEYiewOm5G/flZRd+vOicADqUAxU9LiUYaXesqwMHokzdWxX2SqZm/kjC84ygok4AxRm9k8Mmcqwogy2Afdan9ESia5D88MJ6hRBDK735+TEv0lE62wS/pOE49F0+ik5eWLpfY8HOjrOr7dM0XVFvSMYOt9AiB9vhi7lflbln+DvOElADNBSnc+MZjMiDQWLSa8Pz3LJNB+Ie/m7lDwHmtP4SREv40saNygSEbWol+M9imHFxclnaIX9R0yXxNib7OwkEJjC/4eGE6Sp4FrsUInWksB5RcDSzhXIvh9lXylOqPlOHLxQ==
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=Jitzy5i8zeyC4xxhFAhtB6ZZN5TvHig019/g9dq2hwk=; b=QV9N8aK0zpiLdlcMZyE6IFhZ4m2ESmUrDVKHBOKADKGUvVgqsuu5CJZ1O/xJf5H7qM2gprjyUQOHNVOp0KHd1vwW7wTrtVO2rnZ7vYNiJEYk2yffdWT+biY4IuI+UoETKy9+YgL9/H9GaJ/Ug3rjIBmzn5oc2Ky82IRhGufY0UZQQ6OxLYb1sbsKn/+nSAuKP0nRgs/PUg8UpIaxXnInDlR2dAQK9Eu+zFKPcwooNrLh6veFKe/qKeks5pghM+e8FeZX9bUV+/jQJULqJXNdLiArVYAS370Gm3VHs6OMD9uW6rj+9VuOtH8rZS40KJzIr0KW5JbS1p598g1v4F02Mg==
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=Jitzy5i8zeyC4xxhFAhtB6ZZN5TvHig019/g9dq2hwk=; b=JKUstd1BY85XH4BFe3Uhwnue6RWLsp6bm2S4r92pLDOjEpnaq8koGXuqmnyaxKcggeSLEpeg9puJ3xfuBCFzpjMpL/Z/5NFf9INIJMP9P201llvgdjnbEOPpQVu9nGpfq6EJzvqHBdzojq0WlAiRTOLMBPnzO5XzUSHG9jWBqfI=
Received: from VI1PR06MB5952.eurprd06.prod.outlook.com (20.178.122.223) by VI1PR06MB4525.eurprd06.prod.outlook.com (20.178.10.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.19; Thu, 23 Jan 2020 14:26:59 +0000
Received: from VI1PR06MB5952.eurprd06.prod.outlook.com ([fe80::59e:2bac:26d7:dcd3]) by VI1PR06MB5952.eurprd06.prod.outlook.com ([fe80::59e:2bac:26d7:dcd3%4]) with mapi id 15.20.2665.017; Thu, 23 Jan 2020 14:26:59 +0000
From: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo.ext@telefonica.com>
To: Qin Wu <bill.wu@huawei.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: AdXRjFcIGdJtSQvQRQam0avtkWVeYAAa1HnK
Date: Thu, 23 Jan 2020 14:26:59 +0000
Message-ID: <VI1PR06MB595282995993010C3411FC2AD50F0@VI1PR06MB5952.eurprd06.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAA95F5FDE@dggeml531-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA95F5FDE@dggeml531-mbs.china.huawei.com>
Accept-Language: es-ES, en-US
Content-Language: es-ES
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=samier.barguilgiraldo.ext@telefonica.com;
x-originating-ip: [186.30.83.151]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 00a1bc33-8636-4360-8a10-08d7a0104e7a
x-ms-traffictypediagnostic: VI1PR06MB4525:|VI1PR06MB4525:
x-ld-processed: 9744600e-3e04-492e-baa1-25ec245c6f10,ExtAddr
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <VI1PR06MB4525F7C6D6E6DCB7EBAF4505D50F0@VI1PR06MB4525.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 029174C036
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(366004)(39860400002)(346002)(376002)(396003)(199004)(189003)(66556008)(86362001)(2906002)(19627405001)(71200400001)(91956017)(8676002)(64756008)(5660300002)(8936002)(66446008)(478600001)(66616009)(66946007)(110136005)(81156014)(55016002)(76116006)(9686003)(81166006)(4326008)(54906003)(66476007)(33656002)(186003)(66574012)(7696005)(26005)(316002)(52536014)(6506007)(786003)(9010500006); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR06MB4525; H:VI1PR06MB5952.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: F+PiQ+EF3hxWJYVBpwMBak+l1kkq/p8IXhByS45N7zpi2iq8HpfEnd9x/pwj5BxlhLI1JZjK7ATcbh7wJ77CQwk1GxTZ+9ufykx2c7XgyOvzS+iAKw6gzKMFsVmgdqqd+XCBUhsuT3wJLjKFj2LhYjhX1Ct7YpfZGpXv0BO7AtxxNKU13/g3ceazqV3ONYA1ZsJ8OwjWH0oADawK2Vk5YfKfWtBhTAztpIU+pMEnNZy7CqAtQvwaBa9lsdtcJISbtHfXqmtkpNQdnoOfwoXoIULhPTYsgFLMwfEruEDW+E9n243IdIjiNkGzKHJd3Xq2Qd0ha12mVS5hvC6qZHtTTpVT8RzcVd9LIHkIC50mdc3lRR2fAh+oq7okdjy8MUIfb7ZpuroaviPx4D8r9n7V3gAmf+RYeLcnnA2pyufD4mfTaMFsB7ybW/xB+wKeCMLH6J3JIt3mh7z2z96FHHe9JdIV0ddcz9AznpF/3enIJXx7fBoyK0S1XmkYXx4t6zN6
Content-Type: multipart/related; boundary="_004_VI1PR06MB595282995993010C3411FC2AD50F0VI1PR06MB5952eurp_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 00a1bc33-8636-4360-8a10-08d7a0104e7a
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jan 2020 14:26:59.1669 (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: MCYERkFVwXSSYg6Hd37Iehih1h0hXcenQ99FoIkknliolGEnVHuYzs+2uQbjXla8RkTg95h0YYqtKlB/PETqK6pa0rgf5m+qGy3+WO+ogIwICZtS8Ar8/gSszqFsPsyw1yW5L8tWXoHoo2wpAJDEhA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR06MB4525
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/pL5HZUJnCCaNCMcDjo27_RPrfYc>
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 14:27:06 -0000

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:f7a65f47-0920-41b5-a2d3-db258e8fbb9b]
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

E-mail samier.barguil@wipro.com

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

________________________________

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