IETF Logo Mail Archive

Re: [sfc] SFC OAM Framework

<mohamed.boucadair@orange.com> Fri, 21 September 2018 13:23 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15144130E73 for <sfc@ietfa.amsl.com>; Fri, 21 Sep 2018 06:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 l2fRU_OVPKHd for <sfc@ietfa.amsl.com>; Fri, 21 Sep 2018 06:23:47 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BB1D130DDB for <sfc@ietf.org>; Fri, 21 Sep 2018 06:23:47 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 42GvSK2yzJz4yMh; Fri, 21 Sep 2018 15:23:45 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.60]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 42GvSK26WzzDq7R; Fri, 21 Sep 2018 15:23:45 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0415.000; Fri, 21 Sep 2018 15:23:45 +0200
From: mohamed.boucadair@orange.com
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] SFC OAM Framework
Thread-Index: AQHURfLQ97QadvRci0iWm4vKW9vgn6T6z2MA
Date: Fri, 21 Sep 2018 13:23:44 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DFE4D86@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <0dc300ef-ed9e-6ee1-7cd3-320e637c9bb3@joelhalpern.com>
In-Reply-To: <0dc300ef-ed9e-6ee1-7cd3-320e637c9bb3@joelhalpern.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/uac9q8QT8lf-GhGnoZJrHcf4oU8>
Subject: Re: [sfc] SFC OAM Framework
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Sep 2018 13:23:49 -0000

Hi Joel, all,

I'm afraid that including "Service Function Availability" into the scope of this document is a little bit challenging. Assessing that a given SF is responsive (from a connectivity standpoint) and is providing the service it is expected to provide is an interesting problem to address but it is IMHO beyond the chaining matters. 

I would declare those aspects as out if scope. 

Cheers,
Med

> -----Message d'origine-----
> De : sfc [mailto:sfc-bounces@ietf.org] De la part de Joel M. Halpern
> Envoyé : jeudi 6 septembre 2018 17:03
> À : sfc@ietf.org
> Objet : [sfc] SFC OAM Framework
> 
> I noticed that the Framework now has a better description of what
> problem we want to solve.
> It includes a short section on monitoring service functions.  Unless I
> misread that, the description could be enhanced by noting that another
> measurement method would be to monitor traffic on both sides of the SF
> (at the relevant SFF, and perform suitable correlation.
> 
> Yours,
> Joel
> 
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc

v2.23.0 | Report a Bug | By Email