Re: [CCAMP] EXTERNAL: Microwave topology Notes from October 17

Oscar González de Dios <oscar.gonzalezdedios@telefonica.com> Thu, 24 October 2019 10:02 UTC

Return-Path: <oscar.gonzalezdedios@telefonica.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58A6312089C; Thu, 24 Oct 2019 03:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_FONT_LOW_CONTRAST=0.001, 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 k4r8SuomGOMk; Thu, 24 Oct 2019 03:02:07 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80090.outbound.protection.outlook.com [40.107.8.90]) (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 00F081207FC; Thu, 24 Oct 2019 03:02:06 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=O63JJDPL4PlP4dG6BTggeCJMyfiXA61hm3/HLJKYxrep9AztXN/PIsNsBt5j+ySx596ARuVpeDNki4qL/hlF1v6ycKiMOHwJlZqwE8cCPV90fHS2OsBejRl7Ln4J+X1nZtINby3FNo0wt6qYp0mOV0YUOu6zMDsq7zZBKo560/l1Gv5t+65wVEe46cz3G0WJ8Ca0KxEixMPbX1pbQrq0mIfa0NMGZFuhKr4Yir2F4D7KpXuKt8diEWL+0WzkBUcpudss6zM73inFo+ZXo7Hmu/pTq6HyXeVT2wdLp0t1Ahgo3jmjn1DCq+MOXRjfaGc5Rh1azZsOAPYdniIs+slFgg==
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=9DzkicPc0sGKBmkcAXRCBg13a3FSLafckDwIyOgglM0=; b=U+oRZn+7Ot6pn5iZKLx7bqkETZi2h+E4bD/7nYFbXuksKw5eUqVp36aeKov57lSqIztKzZV9rTYwi7BOZHiswmOZH5zsogFL5BuG+J6rAPC28ramQZ0HthjHh4fpPMM6p7zVzJrWJu4GDikH6TcXwBnnnuCy40tHtpOYA1L+LotkTqF+1Qp1dGtbN3q1m8E3Wfrx5eeX9sSwptDTD1h5CtwITQDyRY0uA31k3lBe/xooxvI5N2jvEwzfgmJf18twnkVVTk5Q3vQbO/1PDTbJDWq3/qigY/8FPUE3Sunj0NWkTYzrrlouZzzdYELRL2rb7gQs9AQACK6l3EEprJXJEQ==
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=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9DzkicPc0sGKBmkcAXRCBg13a3FSLafckDwIyOgglM0=; b=JBtf+n9EJhMiBDwJoQP3WXssKgS8k2e4z3igY00jcl9a7veHZH6zYQB4cFrDiEy23pmLDD5HMfeH2gW8Z7tB/Cei1cV0ZK7cmQvgvE3tNWs5/kJQQGsj/9UplVXU6MTBOoLQX2nr6ZR9/+Mmi1+9JWZaQQTdRpxXxBJif+GPbpk=
Received: from DB6PR0601MB2613.eurprd06.prod.outlook.com (10.168.81.10) by DB6PR0601MB2293.eurprd06.prod.outlook.com (10.169.213.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.22; Thu, 24 Oct 2019 10:02:04 +0000
Received: from DB6PR0601MB2613.eurprd06.prod.outlook.com ([fe80::1997:defa:ef0a:4336]) by DB6PR0601MB2613.eurprd06.prod.outlook.com ([fe80::1997:defa:ef0a:4336%2]) with mapi id 15.20.2387.021; Thu, 24 Oct 2019 10:02:03 +0000
From: =?utf-8?B?T3NjYXIgR29uesOhbGV6IGRlIERpb3M=?= <oscar.gonzalezdedios@telefonica.com>
To: Stephen Cheng <Stephen.Cheng@Aviatnet.com>, Jonas Ahlberg <jonas.ahlberg=40ericsson.com@dmarc.ietf.org>, CCAMP Working Group <ccamp-chairs@ietf.org>, ccamp <ccamp@ietf.org>
Thread-Topic: EXTERNAL: [CCAMP] Microwave topology Notes from October 17
Thread-Index: AdWE5C8/mehCVS9cSmy26BHB7DucWAFHB7/wAA9r/OA=
Date: Thu, 24 Oct 2019 10:02:03 +0000
Message-ID: <DB6PR0601MB261382CF862C4696DC5E04F3FD6A0@DB6PR0601MB2613.eurprd06.prod.outlook.com>
References: <HE1PR0701MB2905CA35C4136FAB7736A741896D0@HE1PR0701MB2905.eurprd07.prod.outlook.com> <MWHPR2201MB1215B790C11EA16FA98D694B996A0@MWHPR2201MB1215.namprd22.prod.outlook.com>
In-Reply-To: <MWHPR2201MB1215B790C11EA16FA98D694B996A0@MWHPR2201MB1215.namprd22.prod.outlook.com>
Accept-Language: es-ES, en-US
Content-Language: es-ES
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=oscar.gonzalezdedios@telefonica.com;
x-originating-ip: [195.235.92.33]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 58edad43-d86d-4276-3b5a-08d75869387b
x-ms-traffictypediagnostic: DB6PR0601MB2293:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <DB6PR0601MB229396CF06AC50AF670A781EFD6A0@DB6PR0601MB2293.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0200DDA8BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(136003)(396003)(39860400002)(366004)(376002)(39224004)(51914003)(43234003)(53754006)(199004)(189003)(40134004)(476003)(6246003)(71190400001)(9686003)(25786009)(5660300002)(236005)(16799955002)(33656002)(19627405001)(66066001)(66574012)(53546011)(71200400001)(102836004)(86362001)(54896002)(6306002)(7736002)(478600001)(99286004)(6506007)(76176011)(966005)(74316002)(26005)(52536014)(66946007)(186003)(76116006)(7696005)(66446008)(64756008)(85202003)(66556008)(66476007)(14444005)(5024004)(446003)(2906002)(6436002)(8936002)(19627235002)(11346002)(229853002)(316002)(606006)(85182001)(786003)(81156014)(81166006)(587094005)(790700001)(6116002)(3846002)(110136005)(8676002)(55016002)(486006)(14454004)(256004)(9010500006)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0601MB2293; H:DB6PR0601MB2613.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: KsJKWpElDDZNlCwGT8EAMXHWbSUregmYR6TlwrVnsx5dL6xkOaBwMSlzpOktwaj8/8hz9M/BS0U6/1VTIMAho40FoDzqeVdYRQ3Zy6OYiU+gM1X8JYe3e5w2CvstfvRv4Qg2vvEtHVB7F3Qm700UfN4dFUFWR9X1LpWyuqvOv+X6osjJmotus3XVxMbRTW2J0rzuxN6dAqsj4Sm30Xl9q+N5tf0qUB7Jofm4T4IEi8KyrZKKfsk0wvrXEANxi4llZ4U3uEW6oCZcTOAjcBEaS6PI3xq5aXJxfEfjVHQ7ItgLxtn37j6mV9sHIEW51crCr/M1wouvgUsWKChswFwFOyoAZuN5behV3bpayN3ydbl55foa+jy/0SaL/iwdi8xCkQQgdgkkTTP7lwQWlWDkGQB3U9Uvykvrl/AxI+MA0yp5kQHEZ6opMLJ7ePx4csUiUVRKY3vik9YfCm80KJPQzep4RTCVkO2ob42gRPLFKF8=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DB6PR0601MB261382CF862C4696DC5E04F3FD6A0DB6PR0601MB2613_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 58edad43-d86d-4276-3b5a-08d75869387b
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Oct 2019 10:02:03.7165 (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: Akp+mZKVjcJ931hKvuGNeXmpVezBj7fwdIFBLNzVvLLiLp7TDh1c6yyBfkGh+aZCp37NdfMpZ0aEihX9I7GdKTPxuWXkPW5WNDZMXsgUAcInQplOz2+5jaBg3et5WOmk
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0601MB2293
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/HpIfM3AhIONgMiwrvAFaTKfhqUs>
Subject: Re: [CCAMP] EXTERNAL: Microwave topology Notes from October 17
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2019 10:02:12 -0000

Hi guys,

        Thanks for the clarifying slides. I have some questions/suggestions:


·         The L2 topology shown in slide 5 can be modeled using the L2 topology model (https://tools.ietf.org/html/draft-ietf-i2rs-yang-l2-network-topology-12 ). Note that in the latest version -12 there is also the possibility to model the LAG. Hence, both point-to-point Ethernet links and lags are modeled. Thus, the “hierarchy” of models (slide 2) could also include l2-network topology (which will be supported over the L1-microwave & L1-fiber)

·         Client interfaces? In the slide 3 (the one of the full network) shows the interface that connects to the client in node 1 (typically there would be a base station connected). I am wondering if that interface should appear or not in the L1-topology. In routers typically we distinguish between the interfaces that belong to the “base router” that you use to connect to other routers, and the client interfaces that you use to set up services. Those will be later attached to VRFs. So, in my opinion, it would be a good idea to have a separate L1 view with that contains the client interfaces (supported by the base L1 topology which contains the node).

·         Modeling of L2 switch vs routers. It was very nice to clearly identify in the scenario that there are nodes which are L2 switches and nodes that are routers.   How is this modeled? Besides having L3 nodes being supported by the L2 nodes and that some L2 nodes are not supporting anything. The ietf-L2 topology is focused on the connections between nodes.

Best Regards,

                Oscar

De: Stephen Cheng <Stephen.Cheng@Aviatnet.com>
Enviado el: jueves, 24 de octubre de 2019 2:32
Para: Jonas Ahlberg <jonas.ahlberg=40ericsson.com@dmarc.ietf.org>rg>; CCAMP Working Group <ccamp-chairs@ietf.org>rg>; ccamp <ccamp@ietf.org>
Asunto: RE: EXTERNAL: [CCAMP] Microwave topology Notes from October 17

Hi all,

I have cleaned up the network structure slides as follow:

  1.  Take account of Amy’s comment of having L2 on top of L1, rather than the other way round
  2.  Added a L2 switch to connect 2 (or more) radios. This is a common network setup in a larger radio site
  3.  Added a separate L2 structure slide (slide 5), to make it easier to read
  4.  Added a L3 structure slide (slide 7), so that IP/MPLS service structure slide can be layered on top
  5.  Cleaned up IP/MPLS service structure (slide 8) and bridging service structure (slide 9) slide to align with L1/L2/L3 structure slides

IMO there is a use case for a L1 topology instance that supports multiple technologies. If not we cannot model the L1 Structure (Slide 3 in slide-deck) with a single topology instance. The very fact that we are drawing the L1 topology in the slide deck indicate that it is a valuable use case, even if it is just for communication. My argument is that we don’t draw the L1 Structure as 3 separate diagrams (as per slide 4), so why should we model it as 3 separate topology instances? I have created slides 4 and 6 to illustrate this argument.

I hope this would help in our further discussion of the use cases.

Also I agree to delay the meeting today, due to key participants not able to join.

Warm regards,
Stephen Cheng



From: CCAMP <ccamp-bounces@ietf.org<mailto:ccamp-bounces@ietf.org>> On Behalf Of Jonas Ahlberg
Sent: 2019年10月18日 1:50 AM
To: CCAMP Working Group <ccamp-chairs@ietf.org<mailto:ccamp-chairs@ietf.org>>; ccamp <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: EXTERNAL: [CCAMP] Microwave topology Notes from October 17

Hi all,

Short notes from our discussion today.

The meeting continued the discussion about the relevant use cases and the underlying network structures to consider in the work going forward.

-          It was clarified that the main purpose of the slides created by Jonas and updated by Stephen is to elaborate the use cases and put them into a context of what the underlying network structures/layers could look like.
o   There was a discussion about the need for and how one instance of a topology model could support multiple L1 technologies. To be continued …
o   Another topic discussed was how the information in a microwave topology model on L1, e.g. about availability and current bandwidth, should be made available to a PCE. Should the information be propagated in the hierarchy of layers and become accessible in the resources used directly by the PCE, or should the PCE have knowledge about when to drill down in the hierarchy of layers to get access to the information. To be continued …
o   There is currently only one service creation example in the slide pack and it illustrates the creation of a TE LSP and its relation to underlying resources and the supported service. There is a need to create other examples, e.g. for non-TE bridge type of services.
-          It was decided the we should continue the discussion and the elaboration of the use cases at the meeting next week.
Until then, contributions / discussion via mail are encouraged.

Regards
JonasA




From: CCAMP <ccamp-bounces@ietf.org<mailto:ccamp-bounces@ietf.org>> On Behalf Of Jonas Ahlberg
Sent: den 3 oktober 2019 14:17
To: CCAMP Working Group <ccamp-chairs@ietf.org<mailto:ccamp-chairs@ietf.org>>; ccamp <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: Re: [CCAMP] Microwave topology

Hi all,

Short notes from our discussion today.

Please remember that the meeting time has been changed.

-          The meeting continued the discussion about the applicability of te-topology concepts and the benefits of augmenting te-topology v.s. network-topology. The meeting concluded that most of the discussions require a refinement/clarification of the use cases to be supported by the model. It was decided that it should be the focus for the coming week and be discussed and agreed on the next meeting.
-          The use cases mentioned (and which need to be further refined) are:
o   L1 microwave radio link topology discovery
§  Illustrate how radio link topology can co-exist with other L1 technologies
o   End-to-end L2 service creation over a L1 topologies, including microwave radio link and L1 connectivity for interconnection between the radio links
§  Show cases with and without bandwidth reservation
o   Use case showing how microwave radio link could support higher order layers such IP/MPLS (other than L2).

Attached is a presentation showing earlier discussions about use-cases.

/JonasA

-----Original Appointment-----
From: CCAMP Working Group <ccamp-chairs@ietf.org<mailto:ccamp-chairs@ietf.org>>
Sent: den 3 oktober 2019 12:00
To: CCAMP Working Group; ccamp
Subject: Microwave topology
When: den 3 oktober 2019 06:00-07:00 America/New_York.
Where: https://ietf.webex.com/ietf


When it's time, join the Webex meeting here.

Meeting number (access code): 647 343 270

Meeting password:
D7dhCJpZ


Join<https://ietf.webex.com/ietf/j.php?MTID=ma65a6a5186962890ec535e711ec3d3f9>



Join by phone
1-650-479-3208<tel:%2B1-650-479-3208,,*01*647343270%23%23*01*> Call-in toll number (US/Canada)
1-877-668-4493<tel:1-877-668-4493,,*01*647343270%23%23*01*> Call-in toll free number (US/Canada)
Global call-in numbers<https://ietf.webex.com/ietf/globalcallin.php?MTID=m57c83575d64804b110f94f798d438720>  |  Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>


Need help? Go to http://help.webex.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