[Time] Transport Independent OAM Requirements

Qin Wu <bill.wu@huawei.com> Wed, 18 June 2014 07:18 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 55D131A0029 for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 00:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.251
X-Spam-Status: No, score=-4.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id i9v_K9Hnm-ZJ for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 00:18:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3D4C1A001A for <time@ietf.org>; Wed, 18 Jun 2014 00:18:34 -0700 (PDT)
Received: from (EHLO lhreml404-hub.china.huawei.com) ([]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BFN94488; Wed, 18 Jun 2014 07:18:33 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com ( by lhreml404-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Wed, 18 Jun 2014 08:18:31 +0100
Received: from NKGEML501-MBS.china.huawei.com ([]) by nkgeml407-hub.china.huawei.com ([]) with mapi id 14.03.0158.001; Wed, 18 Jun 2014 15:18:26 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "time@ietf.org" <time@ietf.org>
Thread-Topic: Transport Independent OAM Requirements
Thread-Index: Ac+KxX8n3PLJHW0XTOiWzkMWLbjS6Q==
Date: Wed, 18 Jun 2014 07:18:26 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8454CECD@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8454CECDnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/venJ35fc4fKt9IuC7sCoWTLrWMk
Subject: [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 07:18:37 -0000

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
f. On demand OAM vs Continuous OAM (Connectionless OAM and Connection oriented OAM)
g.Proactive Activation vs On Demand Activation
h.Point to Point OAM and Point to Multi-Point 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.