IETF Logo Mail Archive

[Time] MEP and maintenance domain boundary

Qin Wu <bill.wu@huawei.com> Mon, 30 June 2014 07:52 UTC

Return-Path: <bill.wu@huawei.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 B8B651A001C for <time@ietfa.amsl.com>; Mon, 30 Jun 2014 00:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 7XDx_J6Gl-Nk for <time@ietfa.amsl.com>; Mon, 30 Jun 2014 00:52:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDDA81A0016 for <time@ietf.org>; Mon, 30 Jun 2014 00:52:31 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJK18643; Mon, 30 Jun 2014 07:52:29 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 30 Jun 2014 08:52:28 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.155]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Mon, 30 Jun 2014 15:52:19 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "time@ietf.org" <time@ietf.org>
Thread-Topic: MEP and maintenance domain boundary
Thread-Index: Ac+UODd3SS/Sv5mCRnigddsxomKhVA==
Date: Mon, 30 Jun 2014 07:52:18 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8457B6A4@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8457B6A4nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/z8wNtSTCVJlvUbmBRMAtd8nPjuE
Cc: Gregory Mirsky <gregory.mirsky@ericsson.com>
Subject: [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: Mon, 30 Jun 2014 07:52:33 -0000

Hi, Greg:
Thanks for your review to problem statement draft.

http://tools.ietf.org/html/draft-ww-opsawg-multi-layer-oam-01
Section 4 gives an architecture overview of management plane OAM,
You comment on the following quoted sentence
"MEP is a maintenance functional entity that is implemented into
   network entity at the maintenance domain boundary
"

as "Not necessarily, e.g. MEP at Level < 7 in Ethernet Service OAM as CFM or Y.1731".

Are you saying MEP can be placed either at the maintenance domain boundary or within maintenance domain?

Would you like to clarify a little bit on this?

Regards!

-Qin

v2.23.0 | Report a Bug | By Email