Re: [Time] Transport Independent OAM Requirements

Qin Wu <bill.wu@huawei.com> Wed, 18 June 2014 09:31 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 CCD971A0104 for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 02:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.801
X-Spam-Level:
X-Spam-Status: No, score=-1.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, 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 jHSCXTO773Rx for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 02:31:07 -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 08BDC1A0147 for <time@ietf.org>; Wed, 18 Jun 2014 02:31:06 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BFO09669; Wed, 18 Jun 2014 09:31:05 +0000 (GMT)
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 18 Jun 2014 10:31:04 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Wed, 18 Jun 2014 17:30:59 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "time@ietf.org" <time@ietf.org>
Thread-Topic: Transport Independent OAM Requirements
Thread-Index: Ac+KxX8n3PLJHW0XTOiWzkMWLbjS6QADVVKwAADThXA=
Date: Wed, 18 Jun 2014 09:30:57 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8454D13F@nkgeml501-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA8454CECD@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B7DC3A9@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B7DC3A9@eusaamb103.ericsson.se>
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_B8F9A780D330094D99AF023C5877DABA8454D13Fnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/3qpfhOoOvCtgydXfoePdkSxm0Ug
Subject: Re: [Time] Transport Independent OAM Requirements
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:31:10 -0000

发件人: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
发送时间: 2014年6月18日 17:01
收件人: Qin Wu; time@ietf.org
主题: RE: Transport Independent OAM Requirements

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

                Regards,
                                Greg

From: Time [mailto:time-bounces@ietf.org] On Behalf Of Qin Wu
Sent: Wednesday, June 18, 2014 12:18 AM
To: time@ietf.org<mailto:time@ietf.org>
Subject: [Time] Transport Independent OAM Requirements

Hi,all:
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.

[Qin]: Agree.

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.

[Qin]:Thanks for correction. We need to make distinction about these definitions.

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.
[Qin]: me either, P2MP poses great challenge for performance measurement since P2MP service consists of not a single pair of endpoints.

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.