Re: [Mpls-interop] FW: Question for Clarification on the MPLS-TPOAMRequirement Draft

Jia HE <hejia@huawei.com> Tue, 05 May 2009 02:19 UTC

Return-Path: <hejia@huawei.com>
X-Original-To: mpls-interop@core3.amsl.com
Delivered-To: mpls-interop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 002493A6F73 for <mpls-interop@core3.amsl.com>; Mon, 4 May 2009 19:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.743
X-Spam-Level: **
X-Spam-Status: No, score=2.743 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_24=0.6, MIME_BASE64_TEXT=1.753, RDNS_NONE=0.1]
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 hZCysTPyP6yJ for <mpls-interop@core3.amsl.com>; Mon, 4 May 2009 19:19:43 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 0A2B13A7132 for <mpls-interop@ietf.org>; Mon, 4 May 2009 19:19:43 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ500CQJFUYXM@szxga02-in.huawei.com> for mpls-interop@ietf.org; Tue, 05 May 2009 10:20:58 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ500LHCFUXMG@szxga02-in.huawei.com> for mpls-interop@ietf.org; Tue, 05 May 2009 10:20:58 +0800 (CST)
Received: from h48726 ([10.70.77.156]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ500CJMFUWHP@szxml06-in.huawei.com> for mpls-interop@ietf.org; Tue, 05 May 2009 10:20:57 +0800 (CST)
Date: Tue, 05 May 2009 10:20:56 +0800
From: Jia HE <hejia@huawei.com>
To: ext Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Message-id: <006401c9cd28$1faeb8e0$9c4d460a@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.3138
Content-type: multipart/alternative; boundary="Boundary_(ID_hg2JzpqALdnpZCOl4kfb1w)"
X-Priority: 3
X-MSMail-priority: Normal
References: <077E41CFFD002C4CAB7DFA4386A53264A4243E@DEMUEXC014.nsn-intra.net>
Cc: MEAD team <mpls-interop@ietf.org>
Subject: Re: [Mpls-interop] FW: Question for Clarification on the MPLS-TPOAMRequirement Draft
X-BeenThere: mpls-interop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF MPLS Interoperability Design Team <mpls-interop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-interop>
List-Post: <mailto:mpls-interop@ietf.org>
List-Help: <mailto:mpls-interop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2009 02:19:45 -0000

Hi Martin,

I have the same concerns as Nurit and Italo. Ans still one more question for clarification about Section 2.1.2. 

It indicates the first scenario as IP/MPLS environments, how is this interpreted? Does it mean "MPLS-TP is run with IP routing and forwarding capabilities" as described in Section 2.1.3?

And what about the description in Section 2.1.3  "When MPLS-TP is run with IP routing and forwarding capabilities, it MUST be possible to operate any of the existing IP/MPLS and PW OAM functionalities"? Is it the same as the first requirement in Section 2.1.2?

Can we simply interpret this as "MPLS-TP OAM doesn't rely on IP routing and forwarding capabilities" and "MPLS-TP OAM doesn't impact existing IP/MPLS and PW OAM functionalities when they are used together"?

Thanks for your help!


Best Regards,
Jia



  ----- Original Message ----- 
  From: Sprecher, Nurit (NSN - IL/Hod HaSharon) 
  To: ext Martin Vigoureux 
  Cc: MEAD team 
  Sent: Thursday, April 30, 2009 2:17 PM
  Subject: [Mpls-interop] FW: Question for Clarification on the MPLS-TPOAMRequirement Draft


   

  Hi martin,

  Could you please update the text accordingly to avoid confusions?

  Thanks,

  Nurit


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

  From: ext BUSI ITALO [mailto:Italo.Busi@alcatel-lucent.it] 
  Sent: Wednesday, April 29, 2009 1:43 AM
  To: Sprecher, Nurit (NSN - IL/Hod HaSharon); VIGOUREUX MARTIN
  Cc: MEAD team
  Subject: RE: [Mpls-interop] Question for Clarification on the MPLS-TP OAMRequirement Draft

   

  Nurit,

   

  I have the same interpretation as you have.

   

  I wonder whether not to rephrase the paragraph on the basis of what you wrote below.

   

  Italo

     


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

    From: mpls-interop-bounces@ietf.org [mailto:mpls-interop-bounces@ietf.org] On Behalf Of Sprecher, Nurit (NSN - IL/Hod HaSharon)
    Sent: Tuesday, April 28, 2009 6:59 PM
    To: VIGOUREUX MARTIN
    Cc: MEAD team
    Subject: [Mpls-interop] Question for Clarification on the MPLS-TP OAMRequirement Draft

    Martin,

    I have a question for clarification on section 2.1.2.

    In the first bullet it is written that "In some environments.IP routing and forwarding capabilities are inherently present. In this case, the OAM functionality MUST support the use of IP routing and forwarding capabilities." 

    I guess that MUST means that the protocol MUST support OAM mechanisms based on IP functionality to be able to run it in this environment, but do not require that this will be necessarily the implementation in this environment. Right? We can still may select to use OAM mechanisms in this environment that are not based on IP functionality. Right? It is just that the protocol MUST support it.

    I'll appreciate if you can confirm it or clarify the intention.

    Thanks and best regards,

    Nurit.

     

     

    ----------------------------------------- 
    Best regards, 

    Nurit Sprecher

     

    Nokia Siemens Networks GmbH & Co. KG 
    Industry Environment

    Senior Specialist, Carrier Ethernet Transport

    3 Hanagar St. Neve Ne'eman B

    45241 Hod Hasharon, Israel


    Tel. +972 9 7751229

    Mobile +972 54 2200954 
    Email: nurit.sprecher@nsn.com

     



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


  _______________________________________________
  Mpls-interop mailing list
  Mpls-interop@ietf.org
  https://www.ietf.org/mailman/listinfo/mpls-interop