Re: [Time] Control Protocol Functionality or OAM function

Gregory Mirsky <gregory.mirsky@ericsson.com> Wed, 25 June 2014 14:08 UTC

Return-Path: <gregory.mirsky@ericsson.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 60A531B2CB2 for <time@ietfa.amsl.com>; Wed, 25 Jun 2014 07:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 6Not_oXDgh7c for <time@ietfa.amsl.com>; Wed, 25 Jun 2014 07:08:54 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C25991B2CB0 for <time@ietf.org>; Wed, 25 Jun 2014 07:08:53 -0700 (PDT)
X-AuditID: c6180641-f79df6d000002de0-35-53aa83f9dbab
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 9E.04.11744.9F38AA35; Wed, 25 Jun 2014 10:10:33 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0174.001; Wed, 25 Jun 2014 10:08:45 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Qin Wu <bill.wu@huawei.com>, "time@ietf.org" <time@ietf.org>
Thread-Topic: Control Protocol Functionality or OAM function
Thread-Index: Ac+QVM/Atz/p97ObQgOe/NnQM2x8VwAKPbpA
Date: Wed, 25 Jun 2014 14:08:45 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B7E2509@eusaamb103.ericsson.se>
References: <B8F9A780D330094D99AF023C5877DABA845757FE@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA845757FE@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B7E2509eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyuXSPt+7P5lXBBp3nLC0ez13AajFv1wcm ByaPliNvWT2WLPnJFMAUxWWTkpqTWZZapG+XwJWx+tEXloL1rhUTHx5mamB8aNPFyMkhIWAi cfHHTUYIW0ziwr31bF2MXBxCAkcZJfav/cUM4SxnlJi5ZzcLSBWbgJHEi4097CC2iICDxPyL zUwgtrCAtcSCxR+YIOI2Eo+Ww9QYSRx4NB+sl0VAVeLc/xPMIDavgK9Ey+F2sBohgVCJdTfO gPVyCoRJzDr5DSzOCHTR91NrwOLMAuISt57MZ4K4VEBiyZ7zzBC2qMTLx/9YIWwliY+/5wP1 cgDV50usfqsEsUpQ4uTMJywTGEVmIZk0C6FqFpIqiBIdiQW7P7FB2NoSyxa+Zoaxzxx4zIQs voCRfRUjR2lxalluupHhJkZg7ByTYHPcwbjgk+UhRgEORiUeXgWflcFCrIllxZW5hxilOViU xHk1q+cFCwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamCMaj+84RBjzsZtzk/V65dX5n69GOip ET1D65um/c0izRDWzbfc80JjmVhn/FnsGrWdZ+nrTQdN4i4Us/p8NN1lysX1oDFiSeHtinss Om0nVFIeJs90O/7j74/H50+YTlO607xH56eh5t3lKYvVvUuDW9I2efPyzajZ2iWsPy34uthr /mspTE5KLMUZiYZazEXFiQDsSy4KfgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/time/f6E1l20BLsG53nUGkw2EnJihprs
Subject: Re: [Time] Control Protocol Functionality or OAM function
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, 25 Jun 2014 14:08:57 -0000

Hi Qin,
I agree, that we don't have many examples of OAM Control protocols but there are couple examples that come to mind. IPPM WG developed One-Way Active Measurement Protocol (OWAMP) RFC 4656 and Two-Way Active Measurement Protocol (TWAMP) RFC 5357. Each has Control protocol and Test protocol.
Then there are numerous RSVP and LSP ping extensions to configure , control OAM and MPLS-TP OAM in particular.

                Regards,
                                Greg

From: Time [mailto:time-bounces@ietf.org] On Behalf Of Qin Wu
Sent: Wednesday, June 25, 2014 2:07 AM
To: time@ietf.org
Subject: [Time] Control Protocol Functionality or OAM function

Hi,:
Sometimes I am confused when we talk about Control Protocol Functionality in the data plane OAM.
Do we have control plane OAM protocol, Can BFD, LSP Ping, ICMP be viewed as control plane OAM?

It looks to me there is no control plane OAM protocol such thing, although BFD defines control packet,
I think it is still a data plane OAM protocol.

The control protocol functionality in the data plane OAM is, in my opinion,
referred to various OAM functions(e.g.,Ping, Traceroute) implemented by OAM protocols.
OAM tools can use control-plane functions in the control plane, e.g., to initialize OAM sessions and to
exchange various parameters.  But such control plane functions are not strictly OAM related.

But we do need to distinct OAM protocol like BFD from OAM information being put into data packet header or data packet payload?
Can the latter be regarded as OAM protocol as well or data plane OAM protocol? Do we need to define the new term "control plane OAM"
Is there anybody like to clarify this?

Regards!
-Qin