[Time] 答复: Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

Qin Wu <bill.wu@huawei.com> Wed, 18 June 2014 09:16 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 627D21A00BF for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 02:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.655
X-Spam-Level: *
X-Spam-Status: No, score=1.655 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_IMAGE_RATIO_04=0.556, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, 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 Thyr--fhY1Wk for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 02:16:30 -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 4B1391A008E for <time@ietf.org>; Wed, 18 Jun 2014 02:16:29 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIO14948; Wed, 18 Jun 2014 09:16:27 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 18 Jun 2014 10:16:26 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Wed, 18 Jun 2014 17:16:21 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "time@ietf.org" <time@ietf.org>
Thread-Topic: Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM
Thread-Index: Ac+KyAQrUp5LcO31SUuBFH47dMtMfwAB0YRQAADCEaAAAHR6AAAAS73A
Date: Wed, 18 Jun 2014 09:16:20 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8454D10E@nkgeml501-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA8454CEFD@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B7DC378@eusaamb103.ericsson.se> <B8F9A780D330094D99AF023C5877DABA8454D0D5@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B7DC3C6@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B7DC3C6@eusaamb103.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: multipart/related; boundary="_004_B8F9A780D330094D99AF023C5877DABA8454D10Enkgeml501mbschi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/xH7IjjGjaBkorTav2c5zjRTVxvI
Subject: [Time] =?gb2312?b?tPC4tDogVXNlIENhc2UxIGZvciBUcmFuc3BvcnQgSW5k?= =?gb2312?b?ZXBlbmRlbnQgT0FNIGluIE11bHRpLUxheWVyIEVudmlyb25tZW50IChUSU1F?= =?gb2312?b?KTogTXVsdGktTGV2ZWwgT0FN?=
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, 18 Jun 2014 09:16:32 -0000

Good point, I see the reason.
I think it may be a good idea to apply these definitions to technology independent OAM whether is connection oriented or connectionless.
Yes, for technology independent OAM protocol, we still need to distinguish which OAM functions are for connection oriented and which OAM functions are connectionless.
Does this make sense?

Regards!
-Qin
·¢¼þÈË: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
·¢ËÍʱ¼ä: 2014Äê6ÔÂ18ÈÕ 17:08
ÊÕ¼þÈË: Qin Wu; time@ietf.org
Ö÷Ìâ: RE: Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

Hi Qin,
my understanding is that OAM domain, Maintenance Points are applicable only to connection oriented network domains. Hence these been defined to subset of MPLS ¨C MPLS Traffic Profile, not the IP/MPLS which presents connectionless environments. That may explain why there¡¯s no such model for IP yet.

                Regards,
                                Greg

From: Qin Wu [mailto:bill.wu@huawei.com]
Sent: Wednesday, June 18, 2014 1:59 AM
To: Gregory Mirsky; time@ietf.org<mailto:time@ietf.org>
Subject: RE: Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

Greg:
Very good comment, this is something important we need to sort out first.
My initial thought to this, we adopt IEEE 802.1ag CFM model and apply these common definitions to both IP/MPLS and Ethernet, MPLS-TP.
Yes, segment OAM and end to end OAM is another common thing we need to sort out.

Regards!
-Qin
·¢¼þÈË: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
·¢ËÍʱ¼ä: 2014Äê6ÔÂ18ÈÕ 16:35
ÊÕ¼þÈË: Qin Wu; time@ietf.org<mailto:time@ietf.org>
Ö÷Ìâ: RE: Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

Hi Qin,
I¡¯d note that IP and IP/MPLS do not have definitions of MEP and MIP. These, Up and Down MEP and MIP, been only defined in Ethernet and MPLS-TP so far. Thus I believe that we should start with defining these, their location relative to traffic, ports, switching elements, and etc. Further, we should look whether IP and IP/MPLS support only e2e service OAM or Segment and/or Link, e.g. through OAM Levels as in Ethernet Service OAM model of IEEE/ITU-T. MPLS-TP, for example, does support Segment OAM though through SPME LSP.

                Regards,
                                Greg

From: Time [mailto:time-bounces@ietf.org] On Behalf Of Qin Wu
Sent: Wednesday, June 18, 2014 12:36 AM
To: time@ietf.org<mailto:time@ietf.org>
Subject: [Time] Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM

[cid:image001.png@01CF8B18.D15135B0]


Different level has different layer OAM. In the abstract level(i.e., Level3), we can use transport independent OAM. All these OAM at different level forms end to end OAM.