Re: [CCAMP] my review of draft-izh-ccamp-flexe-fwk

Loa Andersson <> Fri, 18 January 2019 12:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E61DE130F4A; Fri, 18 Jan 2019 04:48:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uUBrwcSoA1eY; Fri, 18 Jan 2019 04:48:25 -0800 (PST)
Received: from ( []) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8011D130F56; Fri, 18 Jan 2019 04:48:25 -0800 (PST)
Received: from [] (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id 39BA11802AAA; Fri, 18 Jan 2019 13:48:20 +0100 (CET)
To: Daniele Ceccarelli <>, "" <>
Cc: "CCAMP (" <>
References: <>
From: Loa Andersson <>
Message-ID: <>
Date: Fri, 18 Jan 2019 20:48:14 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [CCAMP] my review of draft-izh-ccamp-flexe-fwk
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 18 Jan 2019 12:48:29 -0000


On 2019-01-17 22:12, Daniele Ceccarelli wrote:> Authors,
 > I reviewed draft-izh-ccamp-flexe-fwk. Please find below my comments.
 >   * Figure 1: I don't understand the figure. So far the main topic is
 >     the fact that MAC rate and PHY rate do not necessarily map 1:1 but
 >     now I don't understand what this reference model means. Can you
 >     add some text?

Thanks for a careful review, much appreciated. As for your first point
I have a working copy pre-07 and have added the following text to the

    This document is a framework for the network control plane signaling
    and routing extensions required to establish FlexE links (FlexE
    Groups (PHY) and FlexE CLients (MAC)).  FlexE Links may interconnect
    customer edge devices (CE to CE), CE to provider edge devices (PE),
    PE to PE, or devices at the edge to devices in the core (PE to P) or
    devices in the core (P to P).

    Any pair of neighboring L2 and L3 device that support FlexE
    interfaces may be interconnected P2P using a FlexE link (PHY and
    MAC).  Further a device that terminates a FlexE link MUST be able to
    extract either the L2 or L3 payload and switch on the appropriate
    level, i.e.  Ethernet, MPLS or IP.  It should be noted that any type
    of switching is outside is out of scope for the FlexE specification.

    FlexE CE devices may typically be L3 routers or other devices that
    use FlexE at layers 1 and 2 to provide point-to-point connectivity
    between each other.

    Thus this draft considers the cases in which the two peer FlexE
    devices are:

    o  interconnecting two parts of a customer network (CE to CE).

    o  at the edge of the customer network (CE) and the close edge of the
       provider network (PE to CE).

    o  opposite edges of the FlexE capable network (PE tom PE).

    o  at the edge of the FlexE network PE interconnected to a provider
       device (PE to P).

    o  interconnecting two provider devices (P to P).

    This list of deployment cases will help identify the GMPLS control
    plane (i.e.  routing and signaling) extensions that may be required
    to support establishment of FlexE services.

And changed the reference model like this;

4.  FlexE Reference Model

    The figure below gives a simplified FlexE reference model.

                                     |  P  |
                 n x PHY  .    n x     | |    m x       .
                          .  crunched  | |  crunched    .
        +----+      +-----+    PHYs    | |    PHYs      +-----+    +----+
        | CE +------+ PE1 +------------+ +--------------+ PE2 +----+ CE |
        +----+      +-----+                             +-----+    +----+
                          .                             .
        +----+   p x PHY  .                             .          +----+
        | CE +-----------------------------------------------------+ CE |
        +----+            .                             .          +----+
                          .       OTN Network           .
                          .                             .

        +----+   q x PHY                                           +----+
        | CE +-----------------------------------------------------+ CE |
        +----+                                                     +----+

                   Legend: m, n, p and q indicates how many PHYs
                           there are in a FlexE Group

Would this be a step in the right direction??


<snip - rest of the point<, will try to respond to those asap >

> BR
> Daniele
> _______________________________________________
> CCAMP mailing list


Loa Andersson                        email:
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64