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

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 25 June 2014 17:48 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBB8F1B2D90 for <ccamp@ietfa.amsl.com>; Wed, 25 Jun 2014 10:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 cl3UhBjDH3kc for <ccamp@ietfa.amsl.com>; Wed, 25 Jun 2014 10:48:14 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FDCE1B2D8A for <ccamp@ietf.org>; Wed, 25 Jun 2014 10:48:14 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5PHmBAx012591; Wed, 25 Jun 2014 18:48:12 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5PHmAKp012532 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 25 Jun 2014 18:48:11 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Iftekhar Hussain' <IHussain@infinera.com>
Date: Wed, 25 Jun 2014 18:48:08 +0100
Message-ID: <065601cf909d$a08e4fa0$e1aaeee0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+QnUWyyMOhUqRVTrGiod0Cvt+RXQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20780.001
X-TM-AS-Result: No--11.013-10.0-31-10
X-imss-scan-details: No--11.013-10.0-31-10
X-TMASE-MatchedRID: UuaOI1zLN1g4HKI/yaqRmycP0e8lTEHzecvjbu/xDjr4JyR+b5tvoMY3 yfovp2x0FdpdmcYmI97IaWFKlmf8cq0ZS7JYIH8qcFEiuPxHjsUY0xNaH5MD2+OxOq7LQlGLM6O RLJS7Bsjew1ZrsjfasaG+yVTNWkkscFR5Op/4/wQIVoCLGbl5T0yQ5fRSh265MMn1rcqKQairl7 44dJIMXKfOccI8nXPJYqgDm0T2AwZh44VlLBLudJznQc/i5PeoIZm2INWXDp4kqhTM/UZ9trwVa urKgC6s19iuiJe0ZleatHmZKT3FaRKi81U7h8qnF9jfTqcDduhE6yEc27b9BmalQ37035l+mV8g igkjMnkjLw/1qNMCfVVRQnd3o4vRSSOWVJeuO1A5f9Xw/xqKXdivpTdmVCR2xEHRux+uk8h+ICq uNi0WJJ+vS6LtvWm7FXu2wbsYDEr7djEqgfvnxkooxWeo7UT/ftwZ3X11IV0=
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/mgiqQccnXtWpAZAe2taYACgyYMs
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-flexigrid-lambda-label-01.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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: <http://www.ietf.org/mail-archive/web/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, 25 Jun 2014 17:48:17 -0000

Hi Iftekhar,

> Clarification for the composite label portion:
> So does this mean that:
> a) we are moving ahead with control plane solution ahead of ITU data plane
> definitions ?
> b) or that the ITU data plane has already defined all the data plane aspects
for the
> composite label use case?
> 
> If it is case (b) - no issue.  However, if it is case (a) shouldn't we wait
for ITU
> before proposing solutions?

I thought the text was clear, but I would be happy to add more clarification.

We currently have:

Section 1
   This document relies on [G.694.1] for the definition of the optical
   data plane and does not make any updates to the work of the ITU-T in
   that regard.

Section 2.1
   The slots in the set could potentially be contiguous or non-
   contiguous (as allowed by the definitions of the data plane) and
   could be signaled as a single LSP or constructed from a group of
   LSPs.
--- Maybe the parentheses are not clear and should say "(only as
   allowed...."

Section 4.3
   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.

So...
Case b)

>  I  disagree with the assertion "more formal discussion of media channels and
> network media channels and their arrangement for inverse multiplexing belongs
> in the framework" .  I believe this document should  elaborate on the use case
for
> which the solution is being proposed.

I would be happy to be guided by the WG and see proposed text. Personally I have
nothing to add here, but if you have then please show it to us. 

Maybe it would also help to say why you think this explanation should go in this
document (which is not the first in the series) rather than in the more general
discussion document that is the framework. I note that the framework already
goes into some considerable detail about what media channels and network media
channels are in the context of flexigrid.

Ciao,
Adrian