Problem Statements of FlexE Interface Management
draft-jiang-ccamp-flexe-ifmps-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                 Y. Jiang
Internet Draft                                         F. Yang
Intended status: Informational                         I. Busi
                                                        Huawei
                                                       J. Wang
                                                     Fiberhome
Expires: May 2020                         November 4, 2019

            Problem Statements of FlexE Interface Management
                   draft-jiang-ccamp-flexe-ifmps-00

Abstract

   This document outlines the problem statements for FlexE interface
   management; it also gives an analysis of configuration requirements
   for Flex Ethernet (FlexE) interface management. Requirements on FlexE
   interface management are summarized in the end.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF). Note that other groups may also distribute working
   documents as Internet-Drafts. The list of current Internet-Drafts is
   at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 4, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Jiang, et al                Expires May 4, 2020          [Page 1]
Internet-Draft               FlexE Management PS      November 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.    Introduction ........................................ 2
      1.1.  Conventions used in this document ................ 3
      1.2.  Terminology ...................................... 4
   2.    Problem statements .................................. 4
      2.1.  Overview of FlexE management ..................... 4
      2.2.  Considerations on parameters in FlexE Overhead ... 5
      2.2.1. Static or configurable .......................... 6
      2.2.2. Negotiation enable or not ....................... 7
      2.2.3. Management of FlexE clients ..................... 7
      2.3.  Considerations on bidirectional transport ........ 8
   3.    Requirements ........................................ 9
   4.    Security Considerations ............................ 10
   5.    IANA Considerations ................................ 10
   6.    References ......................................... 10
      6.1.  Normative References ............................ 10
      6.2.  Informative References .......................... 10
   7.    Acknowledgments .................................... 10

1. Introduction

   The Flex Ethernet (FlexE) 2.0 Implementation Agreement
   [FLEXE] defined by the OIF provides the support of a
   variety of Ethernet MAC rates that may or may not
   correspond to any existing Ethernet PHY rate. This
   includes MAC rates that are both greater than (through
   bonding) and less than (through sub-rate and
   channelization) the Ethernet PHY rates used to carry
   FlexE.

   Besides 100GBASE-R PHYs as supported in FlexE 1.0, FlexE
   2.0 supports the bonding of 200GBASE-R PHYs or 400GBASE-R
   PHYs respectively. FlexE 2.1 further supports the bonding
   of 50GBASE-R PHYs.

   According to [FLEXE], FlexE supports the following
   features:

   - Bonding of multiple ETH PHYs (1~254)

Jiang, et al                Expires May 4, 2020          [Page 2]
Internet-Draft               FlexE Management PS      November 2019

   - Sub-rates of ETH PHY (minimum of 5G to maximum capacity
   of bandwidth in a PHY)

   - Channelization within a PHY or a group of bonded PHYs
   (5G ~ k*5G, combination of multiple slots, where each
   slot can be allocated from any PHY)

   In the FlexE, multiple Ethernet PHYs (each PHY can
   further consist of one or more FlexE Instances) are
   bonded into a FlexE Group, and the total capacity of the
   FlexE Group is represented as a collection of slots (e.g.,
   each slot has a granularity of 5Gbps or 25Gbps).  Based
Show full document text