[i2rs] network-type: container vs. identity?

"Zhangxian (Xian)" <zhang.xian@huawei.com> Fri, 08 July 2016 03:47 UTC

Return-Path: <zhang.xian@huawei.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 436A9126FDC for <i2rs@ietfa.amsl.com>; Thu, 7 Jul 2016 20:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pl0Lqk62VmzV for <i2rs@ietfa.amsl.com>; Thu, 7 Jul 2016 20:47:21 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A88E512B04A for <i2rs@ietf.org>; Thu, 7 Jul 2016 20:47:20 -0700 (PDT)
Received: from (EHLO lhreml706-cah.china.huawei.com) ([]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CNI29172; Fri, 08 Jul 2016 03:47:18 +0000 (GMT)
Received: from SZXEMA415-HUB.china.huawei.com ( by lhreml706-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Fri, 8 Jul 2016 04:47:17 +0100
Received: from SZXEMA512-MBS.china.huawei.com ([]) by SZXEMA415-HUB.china.huawei.com ([]) with mapi id 14.03.0235.001; Fri, 8 Jul 2016 11:47:11 +0800
From: "Zhangxian (Xian)" <zhang.xian@huawei.com>
To: "draft-ietf-i2rs-yang-network-topo@tools.ietf.org" <draft-ietf-i2rs-yang-network-topo@tools.ietf.org>
Thread-Topic: network-type: container vs. identity?
Thread-Index: AdHYy2fqE/Tzjev7QKGinU6EIX1VyA==
Date: Fri, 08 Jul 2016 03:47:11 +0000
Message-ID: <C636AF2FA540124E9B9ACB5A6BECCE6B7DEDFCE6@SZXEMA512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_C636AF2FA540124E9B9ACB5A6BECCE6B7DEDFCE6SZXEMA512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0205.577F2246.0093, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c418d0baaee1cdb63c6b7ec79083372a
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/ICM-TLQxd8I8NDlGvNkQZ_FXsXc>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
Subject: [i2rs] network-type: container vs. identity?
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 08 Jul 2016 03:47:23 -0000

Hi, Authors,

   while using this model as a base to augment for technology-specific topologies, I wonder why the leaf network-types is a container, instead of being as a identity?

I remember I asked Alex offline before, but the response I got was that the identity was also under consideration at that time. Given the latest version (June 2016 version) still use container, I wonder if the authors can explain why the alternative is discarded? Thank you.