IETF Logo Mail Archive

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

Gregory Mirsky <gregory.mirsky@ericsson.com> Wed, 18 June 2014 09:08 UTC

Return-Path: <gregory.mirsky@ericsson.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 999111A0126 for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 02:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.894
X-Spam-Level:
X-Spam-Status: No, score=-98.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_04=0.556, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 WYt3FvLuhW41 for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 02:08:28 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCF871A00BF for <time@ietf.org>; Wed, 18 Jun 2014 02:08:24 -0700 (PDT)
X-AuditID: c618062d-f79be6d000006b89-3c-53a105d7c395
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id DE.42.27529.7D501A35; Wed, 18 Jun 2014 05:21:59 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0174.001; Wed, 18 Jun 2014 05:08:14 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Qin Wu <bill.wu@huawei.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+KyAQrUp5LcO31SUuBFH47dMtMfwAB0YRQAADCEaAAAHR6AA==
Date: Wed, 18 Jun 2014 09:08:13 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B7DC3C6@eusaamb103.ericsson.se>
References: <B8F9A780D330094D99AF023C5877DABA8454CEFD@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B7DC378@eusaamb103.ericsson.se> <B8F9A780D330094D99AF023C5877DABA8454D0D5@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA8454D0D5@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.9]
Content-Type: multipart/related; boundary="_004_7347100B5761DC41A166AC17F22DF1121B7DC3C6eusaamb103erics_"; type="multipart/alternative"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBIsWRmVeSWpSXmKPExsUyuXSPt+511oXBBn1nzC0ez13AajFv1wcm ByaPliNvWT2WLPnJFMAUxWWTkpqTWZZapG+XwJXR2PaAteDHdc6KP+9PszQwXtrI2cXIySEh YCIxafk9JghbTOLCvfVsXYxcHEICRxkl7u5sY4dwljNKPPnwgQWkik3ASOLFxh52EFtEwEFi /sVmoG4ODmGBTIk356HCWRKXbixghrCdJH5duQtmswioSiy4cYsZpJxXwFfi2RqwiUICTxkl Xp5TB7E5BcIkDix5A1bOCHTP91NrwG5jFhCXuPVkPtSdIhIPL55mg7BFJV4+/scKYStK7Ouf DnYys0A3o8Saq1vAFvAKCEqcnPmEZQKjyCwks2Yhq5uFpA6iKF/i7pM37BC2lsS8ht9MELai xJTuh1BxTYkrkw9B2doSyxa+ZoawdSR+f+tig6m/fXUqK8QyYDhubnwCV9Tz4yc7sqELGHlX MXKUFqeW5aYbGWxiBEb1MQk23R2Me15aHmIU4GBU4uF94LkgWIg1say4MvcQozQHi5I476za ecFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGNftctrDtd7gw23pL7afE36+TlQJmfNrq+4v hv77P5oPftd50MTNLsX5j+uE/1EDlp7WiUqN4geYc74IR4e+9z+hYMBmEd5r0tzQYRzjoOAs px7vsG3NVkd97T28N5xf3LHU4Nxq1Wv4q95Zq6LKMazmW2Ijw84DjYv5AlzP3Sy5l3U6mem+ EktxRqKhFnNRcSIAgmjfwcsCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/time/906fLVt5fZfxqQeYqLYPs1Kf4dM
Subject: Re: [Time] Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM
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:08:29 -0000

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
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@01CF8A99.F63D8510]


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.

v2.23.0 | Report a Bug | By Email