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

Gregory Mirsky <> Wed, 18 June 2014 08:50 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E36E21A0099 for <>; Wed, 18 Jun 2014 01:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.463
X-Spam-Status: No, score=-101.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_02=0.437, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vYkM2pDwb61J for <>; Wed, 18 Jun 2014 01:50:09 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8C70E1A00A9 for <>; Wed, 18 Jun 2014 01:50:08 -0700 (PDT)
X-AuditID: c618062d-f79be6d000006b89-f1-53a0fe086a81
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id BF.A1.27529.80EF0A35; Wed, 18 Jun 2014 04:48:40 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Wed, 18 Jun 2014 04:34:55 -0400
From: Gregory Mirsky <>
To: Qin Wu <>, "" <>
Thread-Topic: Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM
Thread-Index: Ac+KyAQrUp5LcO31SUuBFH47dMtMfwAB0YRQ
Date: Wed, 18 Jun 2014 08:34:54 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/related; boundary="_004_7347100B5761DC41A166AC17F22DF1121B7DC378eusaamb103erics_"; type="multipart/alternative"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyuXRPlC7HvwXBBs86tS0ez13AajFv1wcm ByaPliNvWT2WLPnJFMAUxWWTkpqTWZZapG+XwJXRtf4oY8GbZZwVD77tZmpgvNzE2cXIySEh YCLx7dFUNghbTOLCvfVgtpDAUUaJS73yXYxcQPZyRomeE5sYQRJsAkYSLzb2sIPYIgIOEvMv NjN1MXJwCAtkSrw5DxXOkrh0YwEzhG0kMeHMQbCZLAKqElf+zmIFsXkFfCXu/ellgdgVKjF3 3Wcwm1MgTGLV+YlgcxiB7vl+ag0TiM0sIC5x68l8Jog7RSQeXjwNdbOoxMvH/1ghbEWJff3T 2UFuZhboZpToXv2cDWKZoMTJmU9YJjCKzEIyaxayullI6iCK8iXm/v7NBmHrSCzY/QnK1pZY tvA1M4x95sBjJkxxHYnf37qg6hUlbl+dygphAwNy8mw5mJpTfT/gaqZ0P2RfwMi7ipGjtDi1 LDfdyGATIzCmj0mw6e5g3PPS8hCjAAejEg/vA88FwUKsiWXFlbmHGKU5WJTEeWfVzgsWEkhP LEnNTk0tSC2KLyrNSS0+xMjEwSnVwOjJwdP72uTe2kd+6Ze5qn8LHmqvDc/7Miu4feUn5oKu CzWTc4SPxkxjfLnfPmft3y9+C2uNTjh8y2o8IVqgkFu+f1fsxG8b+oUtH3uaPHHQCOeTvnBj 7n3+hmWPtosLiTEWv7KOtNrxwmqOeLto2NRp2nVpUvrlAQIcFu9Nz32qrP9Xo2NtqMRSnJFo qMVcVJwIAKpZyCbKAgAA
Subject: Re: [Time] Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 18 Jun 2014 08:50:11 -0000

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.


From: Time [] On Behalf Of Qin Wu
Sent: Wednesday, June 18, 2014 12:36 AM
Subject: [Time] Use Case1 for Transport Independent OAM in Multi-Layer Environment (TIME): Multi-Level OAM


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.