[CCAMP] Comments and questions on draft-ietf-ccamp-mw-topo-yang-01

Stephen Cheng <Stephen.Cheng@Aviatnet.com> Sun, 07 July 2019 22:22 UTC

Return-Path: <Stephen.Cheng@Aviatnet.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 CE7EC1200B4; Sun, 7 Jul 2019 15:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aviatus.onmicrosoft.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 ojo8UO-JoJIp; Sun, 7 Jul 2019 15:22:28 -0700 (PDT)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690068.outbound.protection.outlook.com [40.107.69.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DF3C12004C; Sun, 7 Jul 2019 15:22:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aviatus.onmicrosoft.com; s=selector2-aviatus-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yuVFrwilwmysAbW6vtIEOTg3DyD5By7UdNMOR9WN/7E=; b=ShOF0U6DVU3+JAM7htkByMLq1RtTNZbXwWZVNiigx0SZfwIX51iadAFZr84meNtoG98wZW057AwsQStQdAQp+Ty7T0AgbDf/JcCcTbQc5+r4obqqoAr1vSMqGO2EE8pWppk1OMQ0yD5wSqK/kELVS34gSGb2/br2dOgKVP4KqTk=
Received: from MWHPR2201MB1215.namprd22.prod.outlook.com (10.172.63.138) by MWHPR2201MB1710.namprd22.prod.outlook.com (10.164.206.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.17; Sun, 7 Jul 2019 22:22:26 +0000
Received: from MWHPR2201MB1215.namprd22.prod.outlook.com ([fe80::d6e:67f7:6a82:d020]) by MWHPR2201MB1215.namprd22.prod.outlook.com ([fe80::d6e:67f7:6a82:d020%8]) with mapi id 15.20.2052.019; Sun, 7 Jul 2019 22:22:26 +0000
From: Stephen Cheng <Stephen.Cheng@Aviatnet.com>
To: "ccamp@ietf.org" <ccamp@ietf.org>, "draft-ietf-ccamp-mw-topo-yang@ietf.org" <draft-ietf-ccamp-mw-topo-yang@ietf.org>
Thread-Topic: Comments and questions on draft-ietf-ccamp-mw-topo-yang-01
Thread-Index: AdU1EZ5CsDfvdLzlQQGTds16iK8mWw==
Date: Sun, 07 Jul 2019 22:22:25 +0000
Message-ID: <MWHPR2201MB12151ACFD94DC5F5AE1E87BB99F70@MWHPR2201MB1215.namprd22.prod.outlook.com>
Accept-Language: en-NZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Stephen.Cheng@Aviatnet.com;
x-originating-ip: [202.27.34.26]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ea4b604d-dc19-4fe4-0503-08d703299748
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MWHPR2201MB1710;
x-ms-traffictypediagnostic: MWHPR2201MB1710:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MWHPR2201MB171074341DC36936151841E099F70@MWHPR2201MB1710.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0091C8F1EB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39850400004)(376002)(346002)(396003)(136003)(366004)(189003)(199004)(25584004)(450100002)(66066001)(9686003)(99286004)(68736007)(25786009)(6436002)(33656002)(55016002)(6306002)(54896002)(53936002)(7736002)(478600001)(74316002)(72206003)(8936002)(8676002)(71200400001)(71190400001)(81156014)(2501003)(81166006)(14444005)(5660300002)(5024004)(256004)(52536014)(554214002)(66476007)(66556008)(64756008)(66446008)(14454004)(76116006)(66946007)(486006)(73956011)(413944005)(476003)(86362001)(7696005)(2906002)(102836004)(790700001)(110136005)(3846002)(6506007)(186003)(316002)(6116002)(26005); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR2201MB1710; H:MWHPR2201MB1215.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: Aviatnet.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 41Cuv8msG0OSwiZCS9XNjXfj3+wd8Hu7kXADEKdLPv65jHTNFfgOIaUjqIHuqm7ZpJJ3ZkcmoF5m/uIsAdY2K7MTZ+xi2esrdQ/cYDw7NZd3vpzwIQllW13n8f0xNcPHZKe/Vh4lIJEFEAuUAdRpnKz6Us5Y2hqbRI7EDjAPWPSxdoFLApnEf+sMObI6RUCJpcGaKYK+xDHH7RD5D5fndU2C2/SQR0lEka4sJuuSJCqfglILokmU/TflM45MvdcIOwGjqiTkTf7vq9FBYQNSm/XUAD7OBwU3Ft84GaJ00QjC/bTLIOi5rbNBRJCxXyzfCqyL1hhGnZbCrIehG7TVV4Jyz7+2seSbv+ggGs+V2tJBWLfgCgMaPdETBY2kJn+FB9mouMyCP6AEFhJQQAIjwlJn7p000PYiRWpR0hj84iw=
Content-Type: multipart/alternative; boundary="_000_MWHPR2201MB12151ACFD94DC5F5AE1E87BB99F70MWHPR2201MB1215_"
MIME-Version: 1.0
X-OriginatorOrg: aviatnet.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ea4b604d-dc19-4fe4-0503-08d703299748
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jul 2019 22:22:25.9964 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8d7d22b9-3890-4eef-95a6-a226e64151be
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: stephen.cheng@aviatnet.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR2201MB1710
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/trZduEKDubvL6UKn9LQ3ANaNSWw>
Subject: [CCAMP] Comments and questions on draft-ietf-ccamp-mw-topo-yang-01
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: Sun, 07 Jul 2019 22:22:32 -0000

Dear draft-ietf-ccamp-mw-topo-yang-01 authors,

I have been reviewing the current draft, and I have a number of questions and comments attached below. I am looking forward to your illumination and feedback. Thank you.

Warm regards,
Stephen Cheng


The current draft of ietf-microwave-topology augments ietf-te-topology. I would like to better understand the basis of this design choice.

  *   Is it to enable the modelling of a fully traffic engineered network from L1 all the way to L2/L3/MPLS and beyond?
  *   It appears that many aspects of ietf-te-topology that would unlikely to be applicable to Microwave topology, such as
     *   TTP
     *   TE-Path
     *   Inter-Layer Lock
     *   Transition Link
     *   Can the authors clarify if they would be applicable to a L1 microwave topology?
  *   Appendix A.1 and A.2 examples do not show how any of the attributes defined in ietf-te-topology are used in the context of modelling microwave L1 topology. They only show the attributes defined in ietf-microwave-topology. It would be useful to show such examples.
  *   It would be helpful if a section is added to the I-D to explain which aspects defined in ietf-te-topology would be typically applicable to a L1 microwave topology, and how they should be used in conjunction with ietf-microwave-topology.

I would like to understand how authors intend to model/use connectivity matrix/LLCL in ietf-microwave-topology. I would argue that connectivity matrix/LLCL is of limited applicability for modelling L1 microwave network:

  *   Most microwave-capable devices have microwave links and links of other L1 technology (such as Ethernet and optical).
     *   At a radio site, a microwave device is typically connected to other microwave devices, switches or routers via an Ethernet or optical link
  *   Traffic between different links (whether microwave/non-microwave) within a node are typically switched at layer 2, or routed at layer 3 or IP/MPLS, and not at L1 level.
  *   As such if it is desired to describe traffic engineering between links (whether microwave/non-microwave), it should be described at the layer which the traffic switching/routing occurs.
     *   For example:
        *   a L2 topology (perhaps augmenting ietf-te-topology) could describe the switching capability at the layer 2, with L1 TE topology as the underlay topology
        *   a ietf-te-topology topology could be used to describe the traffic engineering for IP/MPLS, with L1 TE topology as the underlay topology
     *   Due to the fact that a L1 TE topology being an underlay for L2 TE, L3, MPLS TE topologies, the domain controller or operators can still determine if a L1 microwave link is over-subscribed.
  *   If the above reasoning is correct, ietf-microwave-topology should not need to augment connectivity matrix/LLCL with new microwave specific attributes, unless L1 switching is expected on microwaves.

It is a common requirement for users (of a domain controller) to expect a single layer 1 topology to describe all the physical devices and all the L1 links no matter what the L1 technology is. In most networks where microwave plays a part, there would be other L1 technologies such as Ethernet and optical. As such it would be desirable to structure ietf-microwave-topology so that it could co-exist with the modelling of other L1 technologies.

  *   At the moment this is not possible with the proposed ietf-microwave-topology, even although RFC 8345 section 4.1 says
"a network can even have multiple types simultaneously. The type or types are captured underneath the container "network-types""
     *   It is not possible to determine if a LTP is a microwave termination point or another type of link
     *   It is not possible to determine if a link is a microwave link or another type of link
  *   One possible solution is as follow:
     *   Add a "microwave" presence container under nt:tp to indicate that it is a microwave TP
     *   Add a "microwave" presence container under nt:link to indicate that it is a microwave link
     *   the mw-link-attributes in nt:tp are conditional on the "microwave" presence container under nt:tp
     *   the mw-tp-attributes in nt:link are conditional on the "microwave" presence container under nt:link
  *   If other L1 technology topology models follow a similar protocol (i.e. technology-specific presence container for TP and link), it would be possible to have a single L1 TE topology instance to model a network with a mix of L1 technologies.