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

Gregory Mirsky <gregory.mirsky@ericsson.com> Wed, 02 July 2014 01:53 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 2EF301B27B3; Tue, 1 Jul 2014 18:53:06 -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 DjYY-vjZmpKJ; Tue, 1 Jul 2014 18:53:04 -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 EF2071B27AA; Tue, 1 Jul 2014 18:53:03 -0700 (PDT)
X-AuditID: c618062d-f79206d0000014d2-8f-53b3141dabf9
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id E0.9D.05330.D1413B35; Tue, 1 Jul 2014 22:03:41 +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; Tue, 1 Jul 2014 21:52:57 -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: AQHPkE8W8CxlgcIH60mieSMdYwEo95uIzRhQgAM9N3A=
Date: Wed, 2 Jul 2014 01:52:57 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B7E5543@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>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA8457B6C5@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.9]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B7E5543eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPuK6syOZggxuvtCwez13AarHi5GYm i3m7PjA5MHu0HHnL6rFkyU+mAKYoLpuU1JzMstQifbsEroyT084xFbT1Mla8fPOUtYFxSSdj FyMHh4SAicTi5yJdjJxAppjEhXvr2boYuTiEBI4ySsz8/oAZwlnGKHHj42E2kCo2ASOJFxt7 2EFsEYF0iUc3tjKC2MICsRI77rayQsTjJPo3dUDVWEl8+XoCrIZFQEXi6/pbbCCLeQV8JZrX qkDMf8os8ergYxaQGk6BMInPk6Yxg9iMQBd9P7WGCcRmFhCXuPVkPhPEpQISS/acZ4awRSVe Pv7HCmErSuzrn84OUZ8vcX3pJ7B6XgFBiZMzn7BMYBSZhWTULCRls5CUzQI6j1lAU2L9Ln2I EkWJKd0P2SFsDYnWOXPZkcUXMLKvYuQoLU4ty003MtjECIykYxJsujsY97y0PMQowMGoxMP7 YN+mYCHWxLLiytxDjNIcLErivLNq5wULCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYExVWVF0 LjbZ/UDJp0OTmP3erLJyXB+h4W/6/5rPr0JhH16pw7sKr1qK3mae/S+r6vn600xz7tWenb7F xP7UD//NuSV73gTPnFyzfNJR7mW1xybO/rrpa8QhjT71h63uNZ8cnI69/XxplZzBivgGRu/Z N6vYxX/efPNgs/azrq8spYFy7+6KPFqvxFKckWioxVxUnAgArbm/TIUCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/time/yMB76gqNs2wk_0As3IzjxOwukJ4
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: Wed, 02 Jul 2014 01:53:06 -0000

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; 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.