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

Qin Wu <> Mon, 30 June 2014 08:04 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 141B91A0079; Mon, 30 Jun 2014 01:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.851
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DG_Dtgd7Ylag; Mon, 30 Jun 2014 01:04:52 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 073491A0053; Mon, 30 Jun 2014 01:04:51 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BGQ02417; Mon, 30 Jun 2014 08:04:48 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Mon, 30 Jun 2014 09:04:34 +0100
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Mon, 30 Jun 2014 16:04:28 +0800
From: Qin Wu <>
To: "" <>, "" <>
Thread-Topic: Issue of OAM information Information gathering Gathering from Service Function
Thread-Index: AQHPkE8W8CxlgcIH60mieSMdYwEo95uIzRhQ
Date: Mon, 30 Jun 2014 08:04:27 +0000
Message-ID: <>
References: <> <787AE7BB302AE849A7480A190F8B9330016F2E@OPEXCLILM23.corporate.adroot.infra.ftgroup> <> <787AE7BB302AE849A7480A190F8B933001D499@OPEXCLILM23.corporate.adroot.infra.ftgroup> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8457B6C5nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Gregory Mirsky <>
Subject: Re: [Time] Issue of OAM information Information gathering Gathering from Service Function
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 30 Jun 2014 08:04:55 -0000

Hi, Greg:
Thanks for comments on SFC related cases in the problem statement draft.
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?

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?