Re: [Time] Fault management in SFC

Qin Wu <> Sat, 05 July 2014 01:17 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id CFF551A00E6; Fri, 4 Jul 2014 18:17:39 -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 Xl4X39qFQGKH; Fri, 4 Jul 2014 18:17:36 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 464841A0011; Fri, 4 Jul 2014 18:17:35 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BJQ44941; Sat, 05 Jul 2014 01:17:33 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Sat, 5 Jul 2014 02:17:32 +0100
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Sat, 5 Jul 2014 09:17:20 +0800
From: Qin Wu <>
To: ramki Krishnan <>, Jiangyuanlong <>, Sam Aldrin <>, "" <>, "" <>
Thread-Topic: Fault management in SFC
Thread-Index: AQHPl2IwdP+ejxTE2UyNesn6tN0/7ZuPaEiAgAFGH6A=
Date: Sat, 5 Jul 2014 01:17:19 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8457F430nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Carlos Pignataro \(cpignata\)" <>, "Nobo Akiya \(nobo\)" <>, "" <>
Subject: Re: [Time] Fault management in SFC
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: Sat, 05 Jul 2014 01:17:40 -0000

We see a lot of energy to do this kind of survey, would it be good to discuss this in TIME mailing list as well?

发件人: sfc [] 代表 ramki Krishnan
发送时间: 2014年7月4日 21:48
收件人: Jiangyuanlong; Sam Aldrin;
抄送: Carlos Pignataro (cpignata); Nobo Akiya (nobo);
主题: Re: [sfc] Fault management in SFC

Hi Sam, Yuanlong, All,

We uploaded a document on the SFC OAM topic yesterday  – this includes requirements besides framework. Given the importance of this topic, guess many of us were working on this in parallel. We should probably get together in Toronto to take the appropriate next steps.


From: sfc [] On Behalf Of Jiangyuanlong
Sent: Friday, July 04, 2014 1:17 AM
To: Sam Aldrin;<>
Cc: Carlos Pignataro (cpignata); Nobo Akiya (nobo)
Subject: [sfc] Fault management in SFC

Hi Sam and all,

I’m glad to see your draft on SFC OAM framework, it is a very basic and important piece of work in my view.

We have also uploaded an I-D discussing fault management in SFC, does anyone of you have an interest in this kind of work?

The link to this I-D is:

Your opinions are greatly appreciated.


From: sfc [] On Behalf Of Sam Aldrin
Sent: Thursday, July 03, 2014 3:21 AM
Cc: Carlos Pignataro (cpignata); Nobo Akiya (nobo)
Subject: [sfc] Fwd: New Version Notification for draft-aldrin-sfc-oam-framework-00.txt


We have submitted a new draft for SFC OAM framework.
Kindly review the ID and provide your comments.

---------- Forwarded message ----------
From: <<>>
Date: Wed, Jul 2, 2014 at 12:17 PM
Subject: New Version Notification for draft-aldrin-sfc-oam-framework-00.txt
To: Nobo Akiya <<>>, "Sam K. Aldrin" <<>>, Carlos Pignataro <<>>

A new version of I-D, draft-aldrin-sfc-oam-framework-00.txt
has been successfully submitted by Sam K. Aldrin and posted to the
IETF repository.

Name:           draft-aldrin-sfc-oam-framework
Revision:       00
Title:          Service Function Chaining Operations, Administration and Maintenance Framework
Document date:  2014-07-02
Group:          Individual Submission
Pages:          11

   This document provides reference framework for Operations,
   Administration and Maintenance (OAM) of Service Function Chaining

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at<>.

The IETF Secretariat