IETF Logo Mail Archive

[Time] Control Protocol Functionality or OAM function

Qin Wu <bill.wu@huawei.com> Wed, 25 June 2014 09:07 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 EA11A1B2B23 for <time@ietfa.amsl.com>; Wed, 25 Jun 2014 02:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 Qle0PEP6b-8I for <time@ietfa.amsl.com>; Wed, 25 Jun 2014 02:07:06 -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 AB8F91B2B20 for <time@ietf.org>; Wed, 25 Jun 2014 02:07:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGM02867; Wed, 25 Jun 2014 09:07:04 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 25 Jun 2014 10:07:03 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.155]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Wed, 25 Jun 2014 17:06:56 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "time@ietf.org" <time@ietf.org>
Thread-Topic: Control Protocol Functionality or OAM function
Thread-Index: Ac+QVM/Atz/p97ObQgOe/NnQM2x8Vw==
Date: Wed, 25 Jun 2014 09:06:55 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA845757FE@nkgeml501-mbs.china.huawei.com>
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_B8F9A780D330094D99AF023C5877DABA845757FEnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/fxkmnqxyD7AEHHDxlQjgKVuFh-I
Subject: [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 09:07:08 -0000

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

v2.23.0 | Report a Bug | By Email