[CCAMP] A Recap of Update to Draft "YANG Data Model for FlexE Interface Management"

Jiangyuanlong <jiangyuanlong@huawei.com> Mon, 15 July 2019 12:28 UTC

Return-Path: <jiangyuanlong@huawei.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 852A3120112; Mon, 15 Jul 2019 05:28:58 -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 GH8SYzr-zgkC; Mon, 15 Jul 2019 05:28:56 -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 E8F761200F4; Mon, 15 Jul 2019 05:28:55 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 33F4642548505E990887; Mon, 15 Jul 2019 13:28:54 +0100 (IST)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 15 Jul 2019 13:28:53 +0100
Received: from DGGEML512-MBX.china.huawei.com ([169.254.2.81]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0439.000; Mon, 15 Jul 2019 20:28:44 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: "CCAMP (ccamp@ietf.org)" <ccamp@ietf.org>
CC: "draft-jiang-ccamp-flexe-yang@ietf.org" <draft-jiang-ccamp-flexe-yang@ietf.org>
Thread-Topic: A Recap of Update to Draft "YANG Data Model for FlexE Interface Management"
Thread-Index: AdU7CA8x03aK9CleQxWYcAJCrPxH8Q==
Date: Mon, 15 Jul 2019 12:28:43 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BD3581694@dggeml512-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.74.202.215]
Content-Type: multipart/alternative; boundary="_000_3B0A1BED22CAD649A1B3E97BE5DDD68BD3581694dggeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/ADLBEFIQLInxxVTIclAmV6-datc>
Subject: [CCAMP] A Recap of Update to Draft "YANG Data Model for FlexE Interface Management"
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: Mon, 15 Jul 2019 12:28:59 -0000

Dear CCAMPers,

After the IETF 104th meeting, some authors of draft-jiang-ccamp-flexe-yang and draft-xiaobn-ccamp-flexe-yang-mod had twice met and discussed the possibility of combining these two drafts. But authors of the two drafts had quite different opinions on the target and methodology of the FlexE YANG model, thus we decided to update the drafts in its own right until our WG makes a decision on how this work shall be proceeded.

Here is a brief summary of draft-jiang-ccamp-flexe-yang ("YANG Data Model for FlexE Interface Management"):
1. the philosophy of the model is treating a whole FlexE Group as an interface, and treating the Flex Clients in a FlexE Group as sub-interfaces, so that the same interface logic applies (i.e., familiar flavor).
2. Since a FlexE client is decoupled from the FlexE PHYs, it is modeled as a new type of interface, so that new FlexE clients can be more appropriately modeled, and more easily be augmented to support some new MAC layer features, such as flow control, and etc.
3. it is modeled as a simple flat tree, and leave out internal data plane implementation dependent artifacts where management and control planes do not care much, such as FlexE Instance, Calendar A and B.
3. it uses the nomenclatures which are more compatible with the YANG style in the IETF.
Please see https://tools.ietf.org/html/draft-jiang-ccamp-flexe-yang-01 for the details. Your comments and involvements will be much appreciated.

Best regards,
Yuanlong