Re: [CCAMP] Fwd: New Version Notification fordraft-izh-ccamp-flexe-fwk-06.txt

<niu.xiaobing@zte.com.cn> Fri, 11 January 2019 08:07 UTC

Return-Path: <niu.xiaobing@zte.com.cn>
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 81930130DEC for <ccamp@ietfa.amsl.com>; Fri, 11 Jan 2019 00:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 2_Npf5bfEuiV for <ccamp@ietfa.amsl.com>; Fri, 11 Jan 2019 00:07:25 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 9FF64130E5B for <ccamp@ietf.org>; Fri, 11 Jan 2019 00:07:24 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.164.215]) by Forcepoint Email with ESMTPS id 5A74BA81350758549929 for <ccamp@ietf.org>; Fri, 11 Jan 2019 16:07:22 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Forcepoint Email with ESMTPS id 39D4CD893E9915C06077; Fri, 11 Jan 2019 16:07:22 +0800 (CST)
Received: (from root@localhost) by mse02.zte.com.cn id x0B87Jlx085707; Fri, 11 Jan 2019 16:07:19 +0800 (GMT-8) (envelope-from niu.xiaobing@zte.com.cn)
Message-Id: <201901110807.x0B87Jlx085707@mse02.zte.com.cn>
Received: from kjyxapp02.zte.com.cn ([10.30.12.201]) by mse02.zte.com.cn with SMTP id x0B6BdY2037080; Fri, 11 Jan 2019 14:11:39 +0800 (GMT-8) (envelope-from niu.xiaobing@zte.com.cn)
Received: from mapi (kjyxapp05[null]) by mapi (Zmail) with MAPI id mid17; Fri, 11 Jan 2019 14:11:41 +0800 (CST)
Date: Fri, 11 Jan 2019 14:11:41 +0800
X-Zmail-TransId: 2b075c38339d356b6fb1
X-Mailer: Zmail v1.0
In-Reply-To: <e100027a-3052-aa08-dd5a-5baa5ed3263e@pi.nu>
References: 201812250811.wBP8BdKY018302@mse01.zte.com.cn, e100027a-3052-aa08-dd5a-5baa5ed3263e@pi.nu
Mime-Version: 1.0
From: niu.xiaobing@zte.com.cn
To: loa@pi.nu
Cc: ccamp@ietf.org, ccamp-chairs@tools.ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse02.zte.com.cn x0B87Jlx085707
X-MSS: AUDITRELEASE@mse02.zte.com.cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/5-Wtb1ukNcZ87W0_8R77O3VzRGY>
Subject: Re: [CCAMP] Fwd: New Version Notification fordraft-izh-ccamp-flexe-fwk-06.txt
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: Fri, 11 Jan 2019 08:07:33 -0000

hi,

Sorry for the late reply.

From my understanding, when an Ethernet frame is to be transmitted over Ethernet PHY (or FlexE group), it will be encapsultated and adapted through RS and xMII into the FlexE client. It looks like a one-to-one relationship between an Ethernet frame and the flexe client.

Refere to clause 5.2 'Relationship to IEEE 802.3 Stack' in FlexE 2.0 IA for more information: 

The FlexE Shim can be envisioned as being in the middle of the PCS in the 100GBASE-R stack as illustrated in [802.3] Figure 80-1 or in the 200GBASE-R or 

400GBASE-R stack as illustrated in [802.3bs] Figure 116-1. Each FlexE Client has its own separate MAC, Reconciliation Sublayer, and xMII above the FlexE Shim which 

operate at the FlexE Client rate. The layers below the PCS (100GBASE-R PMA, optional FEC, PMD) are used intact as specified for Ethernet.






BRs,




牛小兵     Xiaobing NIU


E: niu.xiaobing@zte.com.cn



www.zte.com.cn





原始邮件



发件人:LoaAndersson <loa@pi.nu>
收件人:牛小兵10019881;
抄送人:ccamp@ietf.org <ccamp@ietf.org>;ccamp-chairs@tools.ietf.org <ccamp-chairs@tools.ietf.org>;
日 期 :2018年12月27日 14:28
主 题 :Re:  [CCAMP] Fwd: New Version Notification fordraft-izh-ccamp-flexe-fwk-06.txt


Xiaobing,

Let me see if I understand you correctly.

Let us assume that we have a 100GE PHY with on 100GE FlexE Group
and that FlexE Group have 5 FlexE Clients.

If an Ethernet frame is to be transmitted over the FlexE Group, are you
saying that it is arbitrary which FlexE Client it will be transmitted
over??

/Loa


On 2018-12-25 14:41, niu.xiaobing@zte.com.cn wrote:
> hi Loa,
> 
> Sorry for the late reply.
> 
> In Fig2, 3,  and  4 of FlexE 2.0 IA, 'control' model works in this way,
> 
> The control function manages which calendar slots each FlexE Client is 
> inserted into
> 
> and inserts the FlexE overhead on each FlexE PHY in the transmit direction.
> 
> It does not relate to the mapping from 'the correct 
> Ethernet Frame to the correct FlexE Client' in the FlexE Mux.
> 
> I'm not sure if I understand your question correctly.
> 
> 
> Happy Christmas!
> 
> 
> 牛小兵     Xiaobing NIU
> 
> 标准预研工程师   Standard Engineer
> 
> 算法标准部/有线研究院/有线产品经营部   Algorithm Standard Department/ 
> Wireline Product R&D Institute
> 
> **
> 
> 中兴通讯股份有限公司   ZTE Corporation
> 
> 北京市朝阳区安定路5号院8号外运大厦A座4楼, 邮编: 100029
> 
> 4/F, Sinotrans Tower A, Building 8, No.5 Anding Road, Chaoyang 
> District,Beijing, P.R.China,
> 
> T: +86 755 xxxxxxxx M: +86 13439566425 <javascript:void(0);>
> 
> E: niu.xiaobing@zte.com.cn <mailto:niu.xiaobing@zte.com.cn>
> 
> www.zte.com.cn <http://www.zte.com.cn/>
> 
> 
> *发件人:*LoaAndersson <loa@pi.nu>
> *收件人:*牛小兵10019881;
> *抄送人:*ccamp@ietf.org <ccamp@ietf.org>;ccamp-chairs@tools.ietf.org 
> <ccamp-chairs@tools.ietf.org>;
> *日 期 :*2018年12月19日 14:37
> *主 题 :**Re:  [CCAMP] Fwd: New Version Notification 
> fordraft-izh-ccamp-flexe-fwk-06.txt*
> 
> 
> On 2018-12-18 17:52, niu.xiaobing@zte.com.cn wrote:
>  > hi, Loa
> 
> <snip>
>  >
>  > Once a FlexE group is created, it can be seen as one huge PCS module
>  > created as well. Transport of different FlexE client information streams
>  > over the FlexE group is decided by the data plane "control" module.
> 
> What info does the data plane "control" module use to map the correct
> Ethernet Frame to the correct FlexE Client?
> 
> /Loa
> 
> <nip>
> 
> 
> 
> -- 
> 
> 
> Loa Andersson                        email: loa@pi.nu
> Senior MPLS Expert
> Bronze Dragon Consulting             phone: +46 739 81 21 64
> 
> 

-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64