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

Loa Andersson <loa@pi.nu> Wed, 19 December 2018 06:37 UTC

Return-Path: <loa@pi.nu>
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 B8D92124408 for <ccamp@ietfa.amsl.com>; Tue, 18 Dec 2018 22:37:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 HKlNiGDFalJa for <ccamp@ietfa.amsl.com>; Tue, 18 Dec 2018 22:37:40 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E99D12F1A5 for <ccamp@ietf.org>; Tue, 18 Dec 2018 22:37:40 -0800 (PST)
Received: from [192.168.1.20] (unknown [119.94.172.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 490291802AA9; Wed, 19 Dec 2018 07:37:32 +0100 (CET)
To: niu.xiaobing@zte.com.cn
Cc: ccamp@ietf.org, ccamp-chairs@tools.ietf.org
References: <201812181252.wBICqnPt076417@mse01.zte.com.cn>
From: Loa Andersson <loa@pi.nu>
Message-ID: <ecccd353-8089-b76d-2629-b2ba89bcc208@pi.nu>
Date: Wed, 19 Dec 2018 14:37:24 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <201812181252.wBICqnPt076417@mse01.zte.com.cn>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/f_KVwXkEl7sVnHZ4HZB_ypqRIso>
Subject: Re: [CCAMP] =?utf-8?q?Fwd=3A_New_Version_Notification_fordraft-izh-c?= =?utf-8?q?camp-flexe-fwk-06=2Etxt?=
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: Wed, 19 Dec 2018 06:37:43 -0000


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