Re: [CCAMP] draft-ali-ccamp-lsp-inquiry-00

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 31 July 2013 09:11 UTC

Return-Path: <adrian@olddog.co.uk>
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 8F3A621F9D4F for <ccamp@ietfa.amsl.com>; Wed, 31 Jul 2013 02:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.468
X-Spam-Level:
X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkbzx4o1R4nY for <ccamp@ietfa.amsl.com>; Wed, 31 Jul 2013 02:11:26 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id D77F621F9EC6 for <ccamp@ietf.org>; Wed, 31 Jul 2013 02:04:42 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6V94bLW014542; Wed, 31 Jul 2013 10:04:37 +0100
Received: from 950129200 (dhcp-13f0.meeting.ietf.org [130.129.19.240]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r6V94a8r014499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 31 Jul 2013 10:04:37 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Khuzema Pithewan'" <kpithewan@infinera.com>, "'CCAMP'" <ccamp@ietf.org>
References: <D8D01B39D6B38C45AA37C06ECC1D65D53FDD05A8@SV-EXDB-PROD1.infinera.com>
In-Reply-To: <D8D01B39D6B38C45AA37C06ECC1D65D53FDD05A8@SV-EXDB-PROD1.infinera.com>
Date: Wed, 31 Jul 2013 10:04:35 +0100
Message-ID: <03f301ce8dcc$faeca2a0$f0c5e7e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03F4_01CE8DD5.5CB35490"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGu+7aOT387C3jmH4N3pUr4Jl2uR5m9oYZA
Content-Language: en-gb
Subject: Re: [CCAMP] draft-ali-ccamp-lsp-inquiry-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
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, 31 Jul 2013 09:11:33 -0000

Right, Khuzema, you caught the right piece of text.
 
The point here is that the LSP is *not* set up in the data plane if it has a
different label. All that is happening is that the LSP-ID and state is being set
up in the control plane.
 
I may have said it before <snarkle> but it is massively helpful for people to
pay close attention to whether they mean "control plane LSP" or "data plane LSP"
when they say "LSP".
 
A
 
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of
Khuzema Pithewan
Sent: 30 July 2013 15:25
To: CCAMP (ccamp@ietf.org)
Subject: [CCAMP] draft-ali-ccamp-lsp-inquiry-00
 
Authors,
 
The draft relies on ability to setup GMPLS lsp without committing resources in
dataplane.
 
Only reference I found to setup pre-planned GMPLS is in RFC 6001.
 
The green highlighted part says it is not possible to support 0 bandwidth lsp
for TDM/LSC network. While red part alludes that it can be done.
 
Also I couldn' locate the text in any RFC that describes the NULL label behavior
in GMPLS context.
 
 
RFC6001 5.2.2 says
 
......snip.......
 
However, mechanisms for provisioning (pre-planned or not) a TDM or
   LSC LSP with 0 bandwidth is currently not possible because the
   exchanged label value is tightly coupled with resource allocation
   during LSP signaling (e.g., see [RFC4606] for a SONET/SDH LSP).  For
   TDM and LSC LSP, a NULL Label value is used to prevent resource
   allocation at the data plane level.  In these cases, upon LSP
   resource commitment, actual label value exchange is performed to
   commit allocation of timeslots/ wavelengths.
 
.........snip........
 
 
Khuzema