Re: [sfc] Fault management in SFC
"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Fri, 04 July 2014 19:41 UTC
Return-Path: <cpignata@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4722B1B2F1B for <sfc@ietfa.amsl.com>; Fri, 4 Jul 2014 12:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level:
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 A804-HhrcuZ3 for <sfc@ietfa.amsl.com>; Fri, 4 Jul 2014 12:41:10 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E68971B2F2B for <sfc@ietf.org>; Fri, 4 Jul 2014 12:41:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18390; q=dns/txt; s=iport; t=1404502870; x=1405712470; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=wYv3TE0RUr3ZKljRt10FKFjp+JnE05DJVAN+K6kANwY=; b=gtuJ9UtoEJQiIN/EVxBIYcz09ji2pJ4RZ5wyb7tMlPwE6o1EhCPcyZV/ hP4tI7RKHh4C0Y9Qp+Re1oyp1frFeRlTacVWQME5YCivrNcwHfddMYsZK tgkjFwtWVr5ntDJ0PkLSd7z6B2gwQWRddKAHOKVViFcXnXxrDI1rnOY9A Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AloFAKUCt1OtJA2I/2dsb2JhbABagkdHUlq9FokVAYELFnWEAwEBAQR5EAIBCBEDAQEBKAchERQJCAIEDgUJiCUDEQ3DdA2GUheMeoFFUg0EBgEGA4MkgRYFhWqTDIIAgUiMMIYUg0NsgUQ
X-IronPort-AV: E=Sophos;i="5.01,603,1400025600"; d="scan'208,217";a="334729569"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-9.cisco.com with ESMTP; 04 Jul 2014 19:41:09 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s64Jf9JI030948 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Jul 2014 19:41:09 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.120]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Fri, 4 Jul 2014 14:41:08 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: ramki Krishnan <ramk@Brocade.com>
Thread-Topic: Fault management in SFC
Thread-Index: AQHPl2CHHSuc/a/+tke6YdVWoqakFJuQQjmAgABipYA=
Date: Fri, 04 Jul 2014 19:41:07 +0000
Message-ID: <255EC6AA-C077-4169-9110-8462CF4655E0@cisco.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>
In-Reply-To: <C7634EB63EFD984A978DFB46EA5174F2C14FDB8457@HQ1-EXCH01.corp.brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.231.106]
Content-Type: multipart/alternative; boundary="_000_255EC6AAC077416991108462CF4655E0ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/mxZg3eOGuKMVh7ZOQ7P3Qf4oO4c
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: [sfc] Fault management in SFC
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jul 2014 19:41:12 -0000
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 – 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/>. The IETF Secretariat
- [sfc] Fwd: New Version Notification for draft-ald… Sam Aldrin
- [sfc] Fault management in SFC Jiangyuanlong
- Re: [sfc] Fault management in SFC ramki Krishnan
- Re: [sfc] Fault management in SFC Carlos Pignataro (cpignata)
- Re: [sfc] Fault management in SFC Qin Wu
- Re: [sfc] Fault management in SFC Jiangyuanlong
- Re: [sfc] Fault management in SFC Qin Wu