Re: [CCAMP] Discussion on Flex-E YANG model structure [was RE:CCAMPDigest, Vol 139, Issue 5]

Jiangyuanlong <jiangyuanlong@huawei.com> Mon, 06 January 2020 02:20 UTC

From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: "niu.xiaobing@zte.com.cn" <niu.xiaobing@zte.com.cn>
CC: "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [CCAMP] Discussion on Flex-E YANG model structure [was RE:CCAMPDigest, Vol 139, Issue 5]
Thread-Index: AQHVwiHCcsWfnB6RVEu/9HGUzjkpeKfc5OAg
Date: Mon, 06 Jan 2020 02:20:17 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BD382DAEF@dggeml532-mbs.china.huawei.com>
References: mailman.206.1577157479.6898.ccamp@ietf.org <202001031836012280585@zte.com.cn>
In-Reply-To: <202001031836012280585@zte.com.cn>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
Content-Type: multipart/alternative; boundary="_000_3B0A1BED22CAD649A1B3E97BE5DDD68BD382DAEFdggeml532mbschi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/uD6Y8c34AE0qwGTJfPMB1HJWbQI>
Subject: Re: [CCAMP] Discussion on Flex-E YANG model structure [was RE:CCAMPDigest, Vol 139, Issue 5]
Precedence: list

Xiaobing,

Please see my comments inline.

Thanks,
Yuanlong

From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of niu.xiaobing@zte.com.cn
Sent: Friday, January 03, 2020 6:36 PM
To: ccamp-request@ietf.org
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] Discussion on Flex-E YANG model structure [was  RE:CCAMPDigest, Vol 139, Issue 5]

hi,  yuanlong

Please refer to comments entitled with [Xiaobing]

On the contrary, the description in Section 5 of OIF FlexE 2.0 is more specific: "The FlexE Shim is the layer that maps or demaps the FlexE Clients carried over a FlexE Group" and "Each FlexE Client has its own separate MAC, Reconciliation Sublayer, and xMII above the FlexE Shim which operate at the FlexE Client rate." The relationship of a FlexE Client, FlexE Shim and its FlexE Group is rather fixed according to this description.

[Xiaobing] In my opinion, those descriptions exactly support the flexibility between FlexE clients and a FlexE group.

[Jiang] Yes, it should be flexible, but not in the way “they (FlexE Clients) can stand alone before configured to a FlexE group”.

In Rob’s YANG module, the modeling of “client-interface” (similar to flexe-client-list in draft-jiang) actually has an attribute “name if:interface-ref”, which can reference to any internal interface (as described in 7.2.1, unclear what parameter is to be managed yet) or any Ethernet PHY (as described in 7.2.2).

Therefore, it provides the flexibility to support any type of FlexE Client bit-stream (i.e., 64B/66B encoded bit-stream).

Otherwise, if FlexE Client is modeled as standalone and could be associated with different FlexE Groups (assuming there is such a support in the data plane), we can hardly configure anything when its FlexE Group is undetermined, since:

[Xiaobing] The configuration of a FlexE client and group can be performed at different time. Just image you first establish a FlexE group without carry any FlexE client, and then configure some FlexE clients over that group.

[Jiang] Totally agreed that we can create a FlexE Group first, and then configure FlexE Clients over that group. My point was “not to create FlexE Clients first, and then associate with a FlexE Group”.

BR

Xiaobing Niu

Re: [CCAMP] Discussion on Flex-E YANG model struc… niu.xiaobing
Re: [CCAMP] Discussion on Flex-E YANG model struc… Jiangyuanlong
Re: [CCAMP] Discussion on Flex-E YANG model struc… Rob Wilton (rwilton)
Re: [CCAMP] Discussion on Flex-E YANG model struc… Jiangyuanlong
Re: [CCAMP] Discussion on Flex-E YANG model struc… Rob Wilton (rwilton)
Re: [CCAMP] Discussion on Flex-E YANG model struc… Jiangyuanlong
Re: [CCAMP] Discussion on Flex-E YANG model struc… niu.xiaobing