IETF Logo Mail Archive

Re: [Time] MEP and maintenance domain boundary

Yuji Tochio <tochio@jp.fujitsu.com> Wed, 02 July 2014 04:02 UTC

Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: time@ietfa.amsl.com
Delivered-To: time@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C211A00E5 for <time@ietfa.amsl.com>; Tue, 1 Jul 2014 21:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.691
X-Spam-Level:
X-Spam-Status: No, score=-1.691 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3a67c7H7lboi for <time@ietfa.amsl.com>; Tue, 1 Jul 2014 21:02:57 -0700 (PDT)
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F9671A0407 for <time@ietf.org>; Tue, 1 Jul 2014 21:02:54 -0700 (PDT)
Received: from kw-mxq.gw.nic.fujitsu.com (unknown [10.0.237.131]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 628D03EE0BB; Wed, 2 Jul 2014 13:02:53 +0900 (JST)
Received: from s4.gw.fujitsu.co.jp (s4.gw.nic.fujitsu.com [10.0.50.94]) by kw-mxq.gw.nic.fujitsu.com (Postfix) with ESMTP id 995A4AC083D; Wed, 2 Jul 2014 13:02:52 +0900 (JST)
Received: from flabmail.flab.fujitsu.co.jp (flabmail.flab.fujitsu.co.jp [10.25.192.52]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 4B87F1DB8032; Wed, 2 Jul 2014 13:02:52 +0900 (JST)
Received: from vskawa.flab.fujitsu.co.jp (vskawa.flab.fujitsu.co.jp [10.25.192.39]) by flabmail.flab.fujitsu.co.jp (8.14.4/8.14.4) with ESMTP id s6242lc4017287; Wed, 2 Jul 2014 13:02:52 +0900
X-AuditID: 0a19c027-f79316d00000123b-7d-53b3846cb93c
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vskawa.flab.fujitsu.co.jp (Symantec Messaging Gateway) with SMTP id 61.23.04667.C6483B35; Wed, 2 Jul 2014 13:02:52 +0900 (JST)
X-SecurityPolicyCheck: OK by SHieldMailChecker v2.2.3
X-SHieldMailCheckerPolicyVersion: FJ-ISEC-20140219
Message-ID: <53B38452.4000505@jp.fujitsu.com>
Date: Wed, 02 Jul 2014 13:02:26 +0900
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA8457B6A4@nkgeml501-mbs.china.huawei.com> <53B15EED.2020701@gmail.com> <B8F9A780D330094D99AF023C5877DABA8457BDB8@nkgeml501-mbs.china.huawei.com> <53B27392.4000700@gmail.com> <B8F9A780D330094D99AF023C5877DABA8457BFDF@nkgeml501-mbs.china.huawei.com> <53B3519C.50403@jp.fujitsu.com> <B8F9A780D330094D99AF023C5877DABA8457C46E@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA8457C46E@nkgeml501-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------030408040901070503020502"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBLMWRmVeSWpSXmKPExsXCJXkgUzenZXOwwed3/BaP5y5gtZi36wOT A5NHy5G3rB5LlvxkCmCK4rJJSc3JLEst0rdL4Mpo2v6RreC1YcWHKzENjD2aXYycHBICJhIP N0xgh7DFJC7cW8/WxcjFISTwmFFixqEZrBDOPkaJT+19bBBVphLvZ/ewQthGElfe3Qbq5uDg FdCVuLAgBSTMIqAqsX3aLbByNgFNiWsz7zCC2KICwRLt27+CxXkFBCVOznzCAmKLCMhLNGy+ C1bDLKAs8fLqRSYQW1jAXGJH2xUWiBt6mSX+z50GVsQpECZx5u5SqIYwif2PNrFMYBSchWTu LCQpCFtX4uaJj0wQtrzE9rdzmCFsHYn3zRfZkcUXMLKtYpQsK85OLE/US8tJTNJLK83KLCku 1UvO18sq2MQICX/1HYzPFmkeYhTgYFTi4f3isDlYiDWxrLgy9xCjBAezkghvPA9QiDclsbIq tSg/vqg0J7X4EKM0B4uSOO8l/sYAIYH0xJLU7NTUgtQimCwTB6dUA6OA5Ifzf3jWHD9lsW76 cy/pe706hRbX+78bb2TZWhCQ9fqEtpS8pcO97ByHE4LxspGBAc0KucVXnb05N89YsvTPo/kN N20DU9JMji3ct8z/6HJfSfusuPDfuYL/LjT/K045JSu82dHAOK3BeVOWzaXJr/TF1q4TTSq5 2pfWzr+9Rn76KvEN05RYijMSDbWYi4oTAVbjMyJ7AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/time/2sbxZz45GMjFGdx2rXFU2Eg7Nv8
Cc: "time@ietf.org" <time@ietf.org>
Subject: Re: [Time] MEP and maintenance domain boundary
X-BeenThere: time@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <time.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/time>, <mailto:time-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/time/>
List-Post: <mailto:time@ietf.org>
List-Help: <mailto:time-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/time>, <mailto:time-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jul 2014 04:02:58 -0000

Hi Qin,

(2014/07/02 12:19), Qin Wu wrote:
>
> Hi, Yuji:
>
> Thanks for pointing me to the relevant references. I will read.
>
> I see how MEL is used in slide 36 associated with RFC5317.
>
> It looks MEL is used to identify which part of network the fault happens, e.g.,
>
> MEL x: Carrier1;
>
> MEL y: Carrier1, Region 1;
>
> MEL z: Carrier1, Region 2;
>

To consider the slide, SPME, section 3.2 of RFC 6371, is adapted to MPLS-TP OAM architecure.
So far, MPLS-TP has only one MEL as Huub pointed out.

Regards, Yuji

v2.23.0 | Report a Bug | By Email