Re: [CCAMP] I-D Action: draft-ietf-ccamp-flexigrid-lambda-label-01.txt

Rajan Rao <> Thu, 24 July 2014 00:45 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E56551A0381 for <>; Wed, 23 Jul 2014 17:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vWJsER-8HN0w for <>; Wed, 23 Jul 2014 17:45:51 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 87D3B1A0115 for <>; Wed, 23 Jul 2014 17:45:51 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 23 Jul 2014 17:45:35 -0700
Received: from ([]) by ([]) with mapi id 15.00.0847.030; Wed, 23 Jul 2014 17:45:35 -0700
From: Rajan Rao <>
To: Iftekhar Hussain <>, "" <>
Thread-Topic: [CCAMP] I-D Action: draft-ietf-ccamp-flexigrid-lambda-label-01.txt
Thread-Index: Ac+kGXH6Y94TWY5qRO6+Mbd8d/ZgZwCHVBDQAC3TLQD//9EBQA==
Date: Thu, 24 Jul 2014 00:45:35 +0000
Message-ID: <>
References: <04d701cfa419$b7f9c1d0$27ed4570$> <>, <128601cfa6b3$6438e200$2caaa600$>
In-Reply-To: <128601cfa6b3$6438e200$2caaa600$>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-flexigrid-lambda-label-01.txt
X-Mailman-Version: 2.1.15
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: Thu, 24 Jul 2014 00:45:53 -0000


No issues with 1-3.  For # 4, As long as we don't preclude use of single label for multiple flex grid slots we should be fine.  Para # 2 starts with composite label  but clarification later in the section you have is good.

From: Adrian Farrel <>
Sent: Wednesday, July 23, 2014 1:19:20 PM
To: Rajan Rao; Iftekhar Hussain
Subject: RE: [CCAMP] I-D Action:        draft-ietf-ccamp-flexigrid-lambda-label-01.txt

Hello Rajan,

> The composite label section in the draft (sec 4.3) refers to RFC 7139.

The draft says...
   The creation of a composite of multiple channels to support inverse
   multiplexing is already supported in GMPLS for TDM and OTN [RFC4606],
   [RFC6344], [RFC7139].  The mechanism used for flexigrid is similar.

> In OTN label we did not enforce this.

I don't understand that.
RFC 7139 *is* signaling for OTN. What is it you didn't enforce in OTN label?

> The OTN Label allows use of non-contiguous time slots within a Te-Link.

This is true.

> It is not clear from this draft as to why we shouldn't take the
> same approach?

Because the data plane to support this has not been defined by the ITU-T.
(If you disagree with this, perhaps you could point me at the relevant

> Perhaps we should step back and look at possible uses cases that would fall in
> VCAT/inverse-muxing (IM) categories.  I can think of the following:
> 1. IM across Te-Links within a single fiber
> 2. IM across Te-links in different fibers
> 3. IM across Te-links within a bundle
> 4. IM across frequency slots within a Te-Link
> While none of these are defined by ITU, this label draft seems to be
> #4.  It is not clear why one would enforce VCAT/IM within a Te-Link.   Do you
> a use case in mind?

The draft says...

   Note further that while the mechanism described here naturally means
   that all component channels are corouted, a composite channel can
   also be achieved by constructing individual LSPs from single flexi-
   grid slots and managing those LSPs as a group.  A mechanism for
   achieving this for TDM is described in [RFC6344], but is out of scope
   for discussion in this document because the labels used are normal,
   single slot labels and require no additional definitions.

This seems to cover 1, 2, and 3.
Do you see a way that those models are handled in our OTN signaling without
sending more than one signaling message?
But note that the ITU-T does not currently define how you would achieve such a
composite channel in flexi-grid, and that would mean that anyone writing an I-D
that explained how achieve this would be blocked until the data plane had been

The document also says...

   At the time of writing [G.694.1] only supports only groupings of
   adjacent slots (i.e., without intervening unused slots that could be
   used for other purposes) of identical width (same value of m), and
   the component slots must be in increasing order of frequency (i.e.,
   increasing order of the value n).  The mechanism defined here MUST
   NOT be used for other forms of grouping unless and until those forms
   are defined and documented in Recommendations published by the ITU-T.

This covers 4, and explains how that case is split into two different scenarios.

What is not clear about this text?

> If we take same position as in RFC 7139 then there is no reason to restrict
use of
> single Label with non-contiguous frequency slots.

But we do take the same position!
7139 did not do anything that was not already defined in a data pane
We are taking the same approach.