Re: [Time] Transport Independent OAM Requirements

Gregory Mirsky <> Wed, 18 June 2014 09:01 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0E81E1A008E for <>; Wed, 18 Jun 2014 02:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kSPvUmdZKavy for <>; Wed, 18 Jun 2014 02:01:24 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0EF0D1A008B for <>; Wed, 18 Jun 2014 02:01:24 -0700 (PDT)
X-AuditID: c6180641-f79df6d000002de0-28-53a101cc8d0e
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id D4.0E.11744.CC101A35; Wed, 18 Jun 2014 05:04:45 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Wed, 18 Jun 2014 05:01:22 -0400
From: Gregory Mirsky <>
To: Qin Wu <>, "" <>
Thread-Topic: Transport Independent OAM Requirements
Thread-Index: Ac+KxX8n3PLJHW0XTOiWzkMWLbjS6QADVVKw
Date: Wed, 18 Jun 2014 09:01:21 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B7DC3A9eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyuXRPrO5ZxoXBBju2MFk8nruA1WLerg9M DkweLUfesnosWfKTKYApissmJTUnsyy1SN8ugStj6b+HbAUdJRWb/vxhb2CclNbFyMkhIWAi se7LYSYIW0ziwr31bCC2kMBRRokdi2O6GLmA7OWMEnNPLGMFSbAJGEm82NjDDmKLCDhIzL/Y DNYsLGAsMfH5djaIuIlE86rbQHEOINtI4tQ1a5Awi4CqxNZpP1hAbF4BX4lXvZNYIXaFSvQ3 d4LZnAJhEofuX2YGsRmB7vl+ag3YeGYBcYlbT+ZD3SkgsWTPeWYIW1Ti5eN/rBC2osS+/uns EPX5Eode72eH2CUocXLmE5YJjCKzkIyahaRsFpIyiLiOxILdn9ggbG2JZQtfM8PYZw48ZkIW X8DIvoqRo7Q4tSw33chwEyMwdo5JsDnuYFzwyfIQowAHoxIP7wPPBcFCrIllxZW5hxilOViU xHk1q+cFCwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamBk70jg/zyXPZUt6bTsY5tJU98Un75q XX+4Uu98qGzNeSeWWseJ+XlF+39x5jeuW7dPjPPgDbtQx8yUmoJ/7ypWvbsreWfiMXX/yopU JymJDXcnv3e3aE+q/Xh2crzdUrsov+d3/s585JKQfD97zUk/IfeV2ho/08Ke8s7Xy17Nso+7 i9c3Zo8SS3FGoqEWc1FxIgBmax0yfgIAAA==
Subject: Re: [Time] Transport Independent OAM Requirements
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 09:01:27 -0000

Hi Qin,
please consider my comments in-line and tagged GIM>>.


From: Time [] On Behalf Of Qin Wu
Sent: Wednesday, June 18, 2014 12:18 AM
Subject: [Time] Transport Independent OAM Requirements

Thanks for Gerogies to raise this issue to me.
I like to discuss Transport Independent OAM Requirements.
What are the requirements that we need to apply in TIME in order to identify the mechanisms, models and protocol to be worked out within TIME?
o) What is the information that needs to be collected/disseminated?
[Qin]: My Initial thought about this is
Common OAM information
a.Measurement Domain
b.Measurement Level
c.Measurement Endpoint (MEP)
d. Measurement Intermediary point (MIP)
e. Measurement Association
GIM>> I believe these top questions are our primary focus. Without them we would not be able to make any progress in correlating Ethernet Service OAM to IP and/or MPLS layers.
f. On demand OAM vs Continuous OAM (Connectionless OAM and Connection oriented OAM)
GIM>> I think that we cannot equate on-demand OAM with connectionless mode. Ethernet Service OAM is, IMO, connection-oriented though it has on-demand OAM tools, e.g. Loopback, Linktrace, DMM/DMR, and LMM/LMR. At the same time Continious OAM cannot be viewed as analogous to Connection-oriented OAM, as BFD operates in connectionless IP though continuously.

g.Proactive Activation vs On Demand Activation
h.Point to Point OAM and Point to Multi-Point OAM
GIM>> There are few attempts of p2mp OAM, e.f. CFM and BFD for multi-point networks. I'm not aware of p2mp Performance Measurement OAM.

o) How can this information be modelled?
[Qin]: We can use Yang Data model. But it doesn't exlude other model languages.

o) How is the information being collected and disseminated?
[Qin]We can either use SNMP, or NetConf to collect or disseminate these information.
We prefer to use NetConf protocol.

o) How often (is this periodic or event based) needs this information to be requested and distributed?\

[Qin]: First,It is up to what management plane protocol is selected.
Second, OAM test can triggered on demand or can be performed continuously and collect information periodically.

o) What is the security and privacy that needs to be applied?

[Qin]: It is up to what management plane protocol is selected.

o) Which are the entities that are involved in the above communication procedure?

[Qin]: I think I at least two type of entities that need to involved in. One is management plane entity,e.g., OSS/NMS, the other is network element that is managed by OSS/NMS
o) Are the TIME mechanisms/protocols  technology independend and applied along multiple administrative domains? If yes, what are the additional requirements compared to technology dependend (one technology) mechanisms and protocols applied only to one administrative domain?
Yes, we are focusing on technology independent OAM and we are looking for consolidation in both data plane and management plane.
Yes, it could be applied across domain. So we need to decide the measurement domain, measurement level, measurement endpoints, measurement intermediary point,
For service function chains, it will be more complicated to setup measurement domain and decides measurement endpoints.