[i2rs] Questions on Network types in draft-ietf-i2rs-yang-network-topo

Qin Wu <bill.wu@huawei.com> Mon, 14 October 2019 06:41 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 4E54A1200CD for <i2rs@ietfa.amsl.com>; Sun, 13 Oct 2019 23:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 zGEifxWFAAFy for <i2rs@ietfa.amsl.com>; Sun, 13 Oct 2019 23:40:58 -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 C56C412006E for <i2rs@ietf.org>; Sun, 13 Oct 2019 23:40:57 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id DD35925D6A1835968B17 for <i2rs@ietf.org>; Mon, 14 Oct 2019 07:40:54 +0100 (IST)
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 14 Oct 2019 07:40:54 +0100
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 14 Oct 2019 07:40:54 +0100
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Mon, 14 Oct 2019 07:40:53 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.72]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0439.000; Mon, 14 Oct 2019 14:40:50 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "ludwig@clemm.org" <ludwig@clemm.org>, "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: Questions on Network types in draft-ietf-i2rs-yang-network-topo
Thread-Index: AdWCVabBIvwzN7pqSX6bVR3gRA+8kg==
Date: Mon, 14 Oct 2019 06:40:49 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA936A55F@dggeml511-mbx.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.134.31.203]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA936A55Fdggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/ZfhRiIHhMWKVOxb2YlncCnArL-0>
Subject: [i2rs] Questions on Network types in draft-ietf-i2rs-yang-network-topo
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, 14 Oct 2019 06:41:01 -0000

Hi, Alex and RFC8345 authors:
As we know, node, link, termination points are three basic elements in the network topology model, network-types defined in ietf-network model indicate certain type of the network, no definition of node-type and link-type in network topology model, see
quoted text in section 4.1 of RFC8345
"
A network has a certain type, such as L2, L3, OSPF, or IS-IS.  A
network can even have multiple types simultaneously.  The type or
types are captured underneath the container "network-types".  In this
model, it serves merely as an augmentation target; network-specific
modules will later introduce new data nodes to represent new network
types below this target, i.e., will insert them below "network-types"
via YANG augmentation.
"
However in some cases, there might be multiple tunnels between the two nodes or endpoints, it seems network-types is not sufficient to indicate
various type of tunnel technology between two nodes, especially when a network can have multiple network type simultaneously.
So I believe link type or tunnel type should be added as link attributes of extension of ietf-network-topology model.
Let me know if my understanding is correct.

-Qin