Re: [CCAMP] Comments on draft-zhang-ccamp-gmpls-h-lsp-mln-00

Fatai Zhang <zhangfatai@huawei.com> Thu, 29 July 2010 10:32 UTC

Return-Path: <zhangfatai@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9DC628C11C for <ccamp@core3.amsl.com>; Thu, 29 Jul 2010 03:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.039
X-Spam-Level:
X-Spam-Status: No, score=0.039 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFA7Vjzza1LF for <ccamp@core3.amsl.com>; Thu, 29 Jul 2010 03:32:37 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id 70FB128C131 for <ccamp@ietf.org>; Thu, 29 Jul 2010 03:31:38 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L6B00CD9EL6V3@usaga03-in.huawei.com> for ccamp@ietf.org; Thu, 29 Jul 2010 05:31:54 -0500 (CDT)
Received: from zhang (dhcp-749a.meeting.ietf.org [130.129.116.154]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L6B00GBWEL4ZG@usaga03-in.huawei.com> for ccamp@ietf.org; Thu, 29 Jul 2010 05:31:54 -0500 (CDT)
Date: Thu, 29 Jul 2010 18:31:47 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: "Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>, ccamp@ietf.org
Message-id: <002c01cb2f09$4042ec90$9a748182@zhang>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/alternative; boundary="Boundary_(ID_eYP2fjTYNQSvavrHthyaag)"
X-Priority: 3
X-MSMail-priority: Normal
References: <5292FFA96EC22A4386067E9DBCC0CD2BCF33A0DDB1@EX-NAP.tellabs-west.tellabsinc.net>
Subject: Re: [CCAMP] Comments on draft-zhang-ccamp-gmpls-h-lsp-mln-00
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 29 Jul 2010 10:32:38 -0000

Hi Jonathan,


Thanks for your comments.

Please see in-line below.




Thanks

Fatai Zhang



Advanced Technology Department
Wireline Networking Business Unit
Huawei Technologies Co., LTD.
Huawei Base, Bantian, Longgang,
Shenzhen 518129 P.R.China
Tel: +86-755-28973234
Fax: +86-755-28972935

  ----- Original Message ----- 
  From: Sadler, Jonathan B. 
  To: ccamp@ietf.org 
  Sent: Wednesday, July 28, 2010 8:46 PM
  Subject: [CCAMP] Comments on draft-zhang-ccamp-gmpls-h-lsp-mln-00


  Hello Fatai and Dan,

   

  In this I-D, it looks like source node is specifying the specific technology used in the lower layer connection (i.e. the connection from Node B to C).

   

  If Nodes B, E and C (as shown in Figures 2 and 3) are being provided by a separate carrier, this amounts to the customer of the service provider telling the service provider how to deliver their service.  This is problematic as the carrier may have different policy from the customer for how to deliver the service requested in the client layer.  In this case, do you envision the operator of Nodes B, E and C ignoring or refusing the service request?

   

  Also, how do you signal the specific adaptation method that should be used?  If the adaptations used in Node B and Node C don't match, then the lower layer connection will not be useable by the client layer so coordination is important.



  [Fatai] These questions can be more generic to all the MLN control(e.g, [MLN-EXT]draft and other RFCs), not specific to this draft. Usually, multi-layer for one carrier is more typical for MLN control. In this case, the head node(e.g., it gets the policy from operator or centralized PCE for multi-layers) may prefer to use one specific ISC or granularity for the FA-LSP, so the head node should be capable of indicating this information in the signaling.

   

  Finally, do you see this as being able to operate in a topology that has a widely varying topography (i.e. transitions down through multiple lower layers  and doesn't make an assumption the layers are simply nested)?



  [Fatai] In this case, obviously, the recursive procedures can be used.



  Thanks,

   

  Jonathan  Sadler



------------------------------------------------------------------------------


  _______________________________________________
  CCAMP mailing list
  CCAMP@ietf.org
  https://www.ietf.org/mailman/listinfo/ccamp