Re: [Time] Fault management in SFC

Qin Wu <bill.wu@huawei.com> Mon, 07 July 2014 12:57 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 C0C921A0400; Mon, 7 Jul 2014 05:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, 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 FtYoDfZc-mtC; Mon, 7 Jul 2014 05:57:37 -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 E29CB1A0008; Mon, 7 Jul 2014 05:57:35 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJS22592; Mon, 07 Jul 2014 12:57:34 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Jul 2014 13:57:15 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.155]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Mon, 7 Jul 2014 20:57:05 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, ramki Krishnan <ramk@Brocade.com>, "time@ietf.org" <time@ietf.org>, "daniel@olddog.co.uk" <daniel@olddog.co.uk>
Thread-Topic: Fault management in SFC
Thread-Index: AQHPl2IwdP+ejxTE2UyNesn6tN0/7ZuPaEiAgABio4CABMd+EA==
Date: Mon, 7 Jul 2014 12:57:05 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8457FDDE@nkgeml501-mbs.china.huawei.com>
References: <20140702191729.12270.32098.idtracker@ietfa.amsl.com> <CA+C0YO0D=SB0VJ+A9_V-sK1KX=Vje0rxzpEWrpiWvkChD=yCtA@mail.gmail.com> <3B0A1BED22CAD649A1B3E97BE5DDD68B5A77ADC8@szxema506-mbs.china.huawei.com> <C7634EB63EFD984A978DFB46EA5174F2C14FDB8457@HQ1-EXCH01.corp.brocade.com> <255EC6AA-C077-4169-9110-8462CF4655E0@cisco.com>
In-Reply-To: <255EC6AA-C077-4169-9110-8462CF4655E0@cisco.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_B8F9A780D330094D99AF023C5877DABA8457FDDEnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/NYzc5KQgHLIN2FORqONTDXb1oZc
Cc: Sam Aldrin <aldrin.ietf@gmail.com>, Jiangyuanlong <jiangyuanlong@huawei.com>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, "sfc@ietf.org" <sfc@ietf.org>, "draft-krishnan-sfc-oam-req-framework@tools.ietf.org" <draft-krishnan-sfc-oam-req-framework@tools.ietf.org>
Subject: Re: [Time] Fault management in SFC
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: Mon, 07 Jul 2014 12:57:40 -0000

The generic requirements aspect of draft-krishnan-sfc-oam-req-framework@tools.ietf.org<mailto:draft-krishnan-sfc-oam-req-framework@tools.ietf.org> maybe more fit into
http://tools.ietf.org/html/draft-king-opsawg-time-multi-layer-oam-use-case-01.
draft-king-opsawg-time-multi-layer-oam-use-case-01 did sort out some high level requirements in the section 4.
But high level requirements in draft-king-opsawg-time-multi-layer-oam-use-case-01 are not specific to SFC OAM.
They also can be applicable to Overlay OAM described in section 3.3 of draft-king-opsawg-time-multi-layer-oam-use-case.

Regarding draft-jxc-sfc-fm-00, is it too rush to go to solution scope to discuss what kind of SFC specific OAM functionalities need to be support and
What SFC specific packet format looks like?

Regards!
-Qin
·¢¼þÈË: sfc [mailto:sfc-bounces@ietf.org] ´ú±í Carlos Pignataro (cpignata)
·¢ËÍʱ¼ä: 2014Äê7ÔÂ5ÈÕ 3:41
ÊÕ¼þÈË: ramki Krishnan
³­ËÍ: Sam Aldrin; Jiangyuanlong; Nobo Akiya (nobo); sfc@ietf.org; draft-krishnan-sfc-oam-req-framework@tools.ietf.org
Ö÷Ìâ: Re: [sfc] Fault management in SFC

Hi, Ramki, Yuanlong,

Thanks for bringing up these two documents! Here's my initial observations:

draft-krishnan-sfc-oam-req-framework:

  *   This document seems to be really thin in actual content.
  *   Removing the introduction, acronyms, and boiler, there's a bit over a page of very generic very high-level requirements.
  *   Although the title says "SFC OAM Requirements and Framework", I do not see text supporting a framework.

draft-jxc-sfc-fm-00:

  *   I am concerned with the creation of a new OAM Protocol in Section 3. SFC architectural documents have a goal of reusing OAM protocols, not re-inventing.
  *   It's not clear of the value of defining a TLV structure when there's no Types. In other words, why draw TLV ASCII diagrams when the requirements and gap analysis are not clear?
  *   The document says things like "BFD can also be used as a tool of proactive CC & CV in SFC.", but then goes on into drawing packets...

I agree this can be a topic for discussions in Toronto.

Thanks,

Carlos.

On Jul 4, 2014, at 9:48 AM, ramki Krishnan <ramk@Brocade.com<mailto:ramk@Brocade.com>> wrote:


Hi Sam, Yuanlong, All,

We uploaded a document on the SFC OAM topic yesterday  ¨C 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.

https://datatracker.ietf.org/doc/draft-krishnan-sfc-oam-req-framework/

Thanks,
Ramki

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jiangyuanlong
Sent: Friday, July 04, 2014 1:17 AM
To: Sam Aldrin; sfc@ietf.org<mailto:sfc@ietf.org>
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:
http://tools.ietf.org/html/draft-jxc-sfc-fm-00

Your opinions are greatly appreciated.

Thanks,
Yuanlong

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

Hi,

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

cheers
-sam
---------- Forwarded message ----------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Wed, Jul 2, 2014 at 12:17 PM
Subject: New Version Notification for draft-aldrin-sfc-oam-framework-00.txt
To: Nobo Akiya <nobo@cisco.com<mailto:nobo@cisco.com>>, "Sam K. Aldrin" <aldrin.ietf@gmail.com<mailto:aldrin.ietf@gmail.com>>, Carlos Pignataro <cpignata@cisco.com<mailto:cpignata@cisco.com>>



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
URL:            http://www.ietf.org/internet-drafts/draft-aldrin-sfc-oam-framework-00.txt
Status:         https://datatracker.ietf.org/doc/draft-aldrin-sfc-oam-framework/
Htmlized:       http://tools.ietf.org/html/draft-aldrin-sfc-oam-framework-00


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




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org/>g/>.

The IETF Secretariat