Re: [Time] Issue of OAM information Information gathering Gathering from Service Function

Gregory Mirsky <gregory.mirsky@ericsson.com> Thu, 03 July 2014 07:59 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 8DCD61A0115; Thu, 3 Jul 2014 00:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level:
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_47=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
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 xGDuRJVtGjIK; Thu, 3 Jul 2014 00:59:48 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7F521A008D; Thu, 3 Jul 2014 00:59:47 -0700 (PDT)
X-AuditID: c618062d-f79206d0000014d2-e4-53b4bb8291e3
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 3B.D1.05330.28BB4B35; Thu, 3 Jul 2014 04:10:11 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0174.001; Thu, 3 Jul 2014 03:59:43 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Qin Wu <bill.wu@huawei.com>, "time@ietf.org" <time@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Issue of OAM information Information gathering Gathering from Service Function
Thread-Index: AQHPkE8W8CxlgcIH60mieSMdYwEo95uIzRhQgAM9N3CAAfsMcIAAAviA
Date: Thu, 3 Jul 2014 07:59:42 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B7E62A9@eusaamb103.ericsson.se>
References: <B8F9A780D330094D99AF023C5877DABA845491A9@nkgeml501-mbs.china.huawei.com> <787AE7BB302AE849A7480A190F8B9330016F2E@OPEXCLILM23.corporate.adroot.infra.ftgroup> <B8F9A780D330094D99AF023C5877DABA84573094@nkgeml501-mbs.china.huawei.com> <787AE7BB302AE849A7480A190F8B933001D499@OPEXCLILM23.corporate.adroot.infra.ftgroup> <B8F9A780D330094D99AF023C5877DABA84575736@nkgeml501-mbs.china.huawei.com> <B8F9A780D330094D99AF023C5877DABA8457B6C5@nkgeml501-mbs.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B7E5543@eusaamb103.ericsson.se> <B8F9A780D330094D99AF023C5877DABA8457CE92@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA8457CE92@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_7347100B5761DC41A166AC17F22DF1121B7E62A9eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyuXRPuG7z7i3BBtdKLR7PXcBqseLkZiaL ebs+MDkwe7QcecvqsWTJT6YApigum5TUnMyy1CJ9uwSujNnPX7AXfDjOWPHs217WBsYzhxi7 GDk4JARMJH7Pku9i5AQyxSQu3FvP1sXIxSEkcJRRYu3nxYwQzjJGiQPbPzCBVLEJGEm82NjD DmKLCKRLPLqxlRHEFhaIldhxt5UVIh4n0b+pA6rGTWLmt2NMIMtYBFQkju4BK+cV8JXobTkO tewri8TVgx9ZQGo4BcIkfv2LAKlhBDro+6k1YGuZBcQlbj2ZzwRxqIDEkj3nmSFsUYmXj/+x QthKEh9/z2eHqM+XWHm5ixVil6DEyZlPWCYwisxCMmoWkrJZSMpmAV3BLKApsX6XPkSJosSU 7ofsELaGROucuezI4gsY2VcxcpQWp5blphsZbGIERtExCTbdHYx7XloeYhTgYFTi4U0U2BIs xJpYVlyZe4hRmoNFSZx3Vu28YCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MYjujLFaX9Aav kMuJ7tu9aikr5xZXuTD3WZ+furydoze/81ZEnMJM23yLxvKJM8585loufnG12yfZ9lMbxT17 108/ZXmwdttE74DiCWv/drxSTecur6gLuDy1+Zam3daoE6GbAjZvNjywb/a6bxkh2xMEfL1f saVaF209b/Vt4o38FweefjvjpMRSnJFoqMVcVJwIADLxITWDAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/time/R2HXf_DyXAbLV4EyEvVuHIAaScQ
Subject: Re: [Time] Issue of OAM information Information gathering Gathering from Service 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: Thu, 03 Jul 2014 07:59:52 -0000
X-List-Received-Date: Thu, 03 Jul 2014 07:59:52 -0000

Hi Qin,
like your proposal. Let’s run with it.

                Regards,
                                Greg

From: Qin Wu [mailto:bill.wu@huawei.com]
Sent: Thursday, July 03, 2014 12:50 AM
To: Gregory Mirsky; time@ietf.org; opsawg@ietf.org
Subject: RE: Issue of OAM information Information gathering Gathering from Service Function

Hi, Greg:
I think the relationship between service node and service function is service node can host service function, service function maintain affinity with service node.
Service node can be virtual or physical.
Therefore to avoid confusion, I propose the following change:
s/service node/service node(virtual or physical) hosting service function.

Regards!
-Qin
发件人: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
发送时间: 2014年7月2日 9:53
收件人: Qin Wu; time@ietf.org<mailto:time@ietf.org>; opsawg@ietf.org<mailto:opsawg@ietf.org>
主题: RE: Issue of OAM information Information gathering Gathering from Service Function

Hi Qin,
please find my notes in-line and tagged by GIM>>.

                Regards,
                                Greg

From: Qin Wu [mailto:bill.wu@huawei.com]
Sent: Monday, June 30, 2014 1:04 AM
To: time@ietf.org<mailto:time@ietf.org>; opsawg@ietf.org<mailto:opsawg@ietf.org>
Cc: Gregory Mirsky
Subject: RE: Issue of OAM information Information gathering Gathering from Service Function

Hi, Greg:
Thanks for comments on SFC related cases in the problem statement draft.

http://tools.ietf.org/html/draft-ww-opsawg-multi-layer-oam-01
See my reply inline below.

Greg>Service may be in form of NF instantiated in a cloud/data center. I think that in such case there would not be physical node to point to.

[Qin]:Yes, service node can be either physical node or virtual node. Do you have any proposed change here?
GIM>> I’d propose to use “Service Function” in place of “service node” as that seems to be accepted term for an element of an Service Function Chain.


Greg> For the purpose of SFC OAM location of SF is irrelevant. Location of SF is OAM information of the lower layer than SFC OAM.
[Qin]:Correct, for SFC OAM, SF location doesn’t matter, what matter is where OAM information is located and where OAM function is performed.
Any proposed change here?

GIM>> Service Functions may be applied at different network layers, not only above Layer 3. (Interesting, if SFC may include SFs at different layers.)  I’d propose to edit the first sentence of the Section 3.6.1 to
The service packets are steered through a set of service functions distributed in the network that may be applied at different layers of the network protocol stack.