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

Mach Chen <mach@huawei.com> Wed, 14 July 2010 08:53 UTC

Return-Path: <mach@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 4F22E3A698D; Wed, 14 Jul 2010 01:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.169
X-Spam-Level:
X-Spam-Status: No, score=-0.169 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=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 pS9mn3euIKn7; Wed, 14 Jul 2010 01:53:57 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 0CF893A68A4; Wed, 14 Jul 2010 01:53:57 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L5J004EEI0OA7@szxga03-in.huawei.com>; Wed, 14 Jul 2010 16:53:13 +0800 (CST)
Received: from m55527c ([10.110.98.169]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L5J00GX7I0OE8@szxga03-in.huawei.com>; Wed, 14 Jul 2010 16:53:12 +0800 (CST)
Date: Wed, 14 Jul 2010 16:53:11 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <89571.47481.qm@web88402.mail.re1.yahoo.com>
To: "S. Davari" <davarish@yahoo.com>, Jia HE <hejia@huawei.com>, Shahram Davari <davari@broadcom.com>
Message-id: <F8A42E669722437AB6CD24CFD4586300@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-transfer-encoding: 8bit
Importance: Normal
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, ticctoc@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: Wed, 14 Jul 2010 08:53:58 -0000

Hi Shahram,

>From the view of implementation, there is no more difference between SHOULD 
and MUST :-)
For me, the Label Range is more like a mechanim to notify related nodes that 
some LSPs are dedicated for PTP messages other than the chips memory 
limitation, because the memory restriction is always there whatever you use 
Label Range or not.
IMHO, since the objective is to tell related MPLS nodes which LSPs are PTP 
LSPs, an indication in the signaling(RSVP-TE/GMPLS/LDP) is enough and seems 
more common. And it will avoid the strict requirement of "the network and 
all nodes required to support the Label range".
In addition, there should be some mechanims(e.g., ISIS/OSPF extensions) for 
nodes to advertise their PTP capability hence to help PTP LSPs computation.

Best regards,
Mach


--------------------------------------------------
From: "S. Davari" <davarish@yahoo.com>
Sent: Wednesday, July 14, 2010 2:31 PM
To: "Jia HE" <hejia@huawei.com>; "Shahram Davari" <davari@broadcom.com>
Cc: <mpls@ietf.org>; <pwe3@ietf.org>; <ticctoc@ietf.org>; <mpls-tp@ietf.org>
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
>>
>
>



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