Re: [mpls] [PWE3] 1588 over MPLS draft

Jia HE <hejia@huawei.com> Thu, 15 July 2010 08:17 UTC

Return-Path: <hejia@huawei.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB3313A6A8B; Thu, 15 Jul 2010 01:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.416
X-Spam-Level:
X-Spam-Status: No, score=-0.416 tagged_above=-999 required=5 tests=[AWL=1.298, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001]
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 eXDrdn4x99FN; Thu, 15 Jul 2010 01:16:52 -0700 (PDT)
Received: from szxga05-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 1FB063A6A44; Thu, 15 Jul 2010 01:16:50 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5L00D10AXJDP@szxga05-in.huawei.com>; Thu, 15 Jul 2010 16:15:19 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5L00478AXIMD@szxga05-in.huawei.com>; Thu, 15 Jul 2010 16:15:18 +0800 (CST)
Received: from h48726 ([10.70.77.157]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5L00FQ5AXIFR@szxml04-in.huawei.com>; Thu, 15 Jul 2010 16:15:18 +0800 (CST)
Date: Thu, 15 Jul 2010 16:15:17 +0800
From: Jia HE <hejia@huawei.com>
To: "S. Davari" <davarish@yahoo.com>, Shahram Davari <davari@broadcom.com>
Message-id: <06cd01cb23f5$dc51a910$9d4d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_Q4723r3ARmAyP+mq2Atcaw)"
X-Priority: 3
X-MSMail-priority: Normal
References: <2C2F1EBA8050E74EA81502D5740B4BD6940EC28967@SJEXCHCCR02.corp.ad.broadcom.com> <04ae01cb2310$1a6b2730$9d4d460a@china.huawei.com> <89571.47481.qm@web88402.mail.re1.yahoo.com>
Cc: mpls@ietf.org, pwe3@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] [PWE3] 1588 over MPLS draft
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 08:17:04 -0000

Hi Shahram,

Thanks for your response. But still more for clarification:

So the specified PTP Label Range is for the PHY to easily recognize and get to process PTP information that is carried on LSPs or PWs. This is efficient when we define and make known such a Label range globally at the beginning of setting up a network. What if we want to set up such PTP LSPs using a global label range when there are already LSPs in use in the network? It might be difficult to get a global label range in this case considering the possible label collision. Or in this case we depend on signaling but may cause burden for PHY chips. If I'm right, it seems a compromise between the two. Is that true?

Thanks!

B.R.
Jia

  ----- Original Message ----- 
  From: S. Davari 
  To: Jia HE ; Shahram Davari 
  Cc: mpls@ietf.org ; pwe3@ietf.org ; ticctoc@ietf.org ; mpls-tp@ietf.org 
  Sent: Wednesday, July 14, 2010 2:31 PM
  Subject: Re: [mpls] [PWE3] 1588 over MPLS draft


  Hi Jia,


  Label range is a SHOULD requirements and not MUST. The reason for Label Range is mainly for PHY chips that don't have large memory and can't store a lot of Labels. Otherwise the PTP LSP is setup via signaling that specifies the LSP as carrying 1588.


  So the answer is that if a Label range is used it must be a Global range within a network and should not be used by any router for other applications.


  Thanks,
  Shahram



------------------------------------------------------------------------------
  From: Jia HE <hejia@huawei.com>
  To: Shahram Davari <davari@broadcom.com>
  Cc: mpls@ietf.org; pwe3@ietf.org; ticctoc@ietf.org; mpls-tp@ietf.org
  Sent: Tue, July 13, 2010 9:50:37 PM
  Subject: Re: [mpls] [PWE3] 1588 over MPLS draft


  Hi Shahram,

  One question about "PTP Label Range":

  To my knowledge, label in MPLS network is a local matter. For example, we may have per-interface or per-platform label space. Will this specificed "PTP Label Range" conflict with the current in-use labels for common LSPs? 

  B.R.
  Jia

    ----- Original Message ----- 
    From: Shahram Davari 
    To: ticctoc@ietf.org ; mpls@ietf.org ; mpls-tp@ietf.org ; pwe3@ietf.org 
    Sent: Thursday, July 08, 2010 3:12 AM
    Subject: [PWE3] 1588 over MPLS draft


    Hi All,



    Please find attached our first draft of 1588 over MPLS. Since we have some technical issues converting the Word format to Txt we couldn’t  upload the draft before the cut-off date. However we will present the draft in the next IETF meeting and will upload the draft after the meeting.



    Note that the main WG is TicToc but may require consultation with MPLS and PWE3 WGs.



    Thanks,

    Shahram Davari



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


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