Re: [Time] Transport Independent OAM Requirements

<karagian@cs.utwente.nl> Wed, 18 June 2014 08:58 UTC

Return-Path: <karagian@cs.utwente.nl>
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 C91D61A008B for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 01:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 Nqs1ywt0Aku2 for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 01:58:16 -0700 (PDT)
Received: from out22-ams.mf.surf.net (out22-ams.mf.surf.net [145.0.1.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE3671A00B6 for <time@ietf.org>; Wed, 18 Jun 2014 01:58:15 -0700 (PDT)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing1-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s5I8qasa003518; Wed, 18 Jun 2014 10:58:07 +0200
Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.3.181.6; Wed, 18 Jun 2014 10:51:46 +0200
Received: from EXMBX23.ad.utwente.nl ([169.254.3.31]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.03.0181.006; Wed, 18 Jun 2014 10:51:40 +0200
From: <karagian@cs.utwente.nl>
To: <bill.wu@huawei.com>, <time@ietf.org>
Thread-Topic: Transport Independent OAM Requirements
Thread-Index: Ac+KxX8n3PLJHW0XTOiWzkMWLbjS6QADJAYO
Date: Wed, 18 Jun 2014 08:51:38 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F48C092@EXMBX23.ad.utwente.nl>
References: <B8F9A780D330094D99AF023C5877DABA8454CECD@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA8454CECD@nkgeml501-mbs.china.huawei.com>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [86.91.134.3]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F48C092EXMBX23adutwent_"
MIME-Version: 1.0
X-Bayes-Prob: 0.005 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN)
X-CanIt-Geo: ip=130.89.5.49; country=NL; region=Provincie Overijssel; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6
X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default)
X-Canit-Stats-ID: 0uMfIW7Rj - 523b7cd6c332 - 20140618 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: http://mailarchive.ietf.org/arch/msg/time/hBhpXU6rQb5KZ8MU5arYQigFOmk
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 08:58:18 -0000

Hi Qin,



Thanks for the provided answers!



It will be great to hear the opinion of others on your answers!



Best regards,

Georgios





________________________________
Van: Time [time-bounces@ietf.org] namens Qin Wu [bill.wu@huawei.com]
Verzonden: woensdag 18 juni 2014 9:18
Aan: time@ietf.org
Onderwerp: [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
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.