Re: [sfc] Way forward for draft-ao-sfc-oam-return-path-specified

mohamed.boucadair@orange.com Tue, 01 June 2021 05:46 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 853B13A1AE2 for <sfc@ietfa.amsl.com>; Mon, 31 May 2021 22:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 AQ9g_0-szgOa for <sfc@ietfa.amsl.com>; Mon, 31 May 2021 22:46:00 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19D663A1ADF for <sfc@ietf.org>; Mon, 31 May 2021 22:45:59 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 4FvLjx5TdQz8vwB; Tue, 1 Jun 2021 07:45:57 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622526357; bh=2BbisGD4sC3jXG3CM6bAGBI5TMVQh3MD0cSIKARopG0=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=aBs9dYQLaffqNMpuaqVnHpcTMIzbOdzABR7sRoFZCmXSCfmh+y9SES4j9viKZNO/1 2UGbsoT1Hr40MZW0Z8F3wYyUIfjx+AekqzIhd68nmtAMsnQSBTwddLq4Yxz9AIogU7 7da7rUIXis5D8s/Dtou2ju6PUGS5CpGvw98su4vzBLzG4FJFQsuao2PiYacWTAX4oJ rDptmkJDf7WwmQx98RnJHVrs1XLCHUyqtp6OSAzIZzq/Y+Z7nbagAC05gMHkJMoM9N SiZsNIDQ8cdsQy0Gm+zhx0pQim2+G+PpDiLujgKxv/1CvZV/EkuGDSxK1hH0VxBy+J AVo+juDf8pI+w==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.48]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 4FvLjx4Yrjz5vN0; Tue, 1 Jun 2021 07:45:57 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "gregory.mirsky@ztetx.com" <gregory.mirsky@ztetx.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Way forward for draft-ao-sfc-oam-return-path-specified
Thread-Index: AQHXVB0YVhtyb1EZu0iyAV5O9ItUX6r5etSAgAUuviA=
Date: Tue, 01 Jun 2021 05:45:57 +0000
Message-ID: <4103_1622526357_60B5C995_4103_404_1_787AE7BB302AE849A7480A190F8B9330353954CE@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <202105290756323443789@zte.com.cn> <2de22857-4947-7360-af5b-47f27ba2f215@joelhalpern.com>
In-Reply-To: <2de22857-4947-7360-af5b-47f27ba2f215@joelhalpern.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/kg3LEamfVA7uIAQEIK7w8SGOYkI>
Subject: Re: [sfc] Way forward for draft-ao-sfc-oam-return-path-specified
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: Tue, 01 Jun 2021 05:46:07 -0000

Hi Joel, all, 

I support moving these two TLVs to the main OAM document. Thanks. 

Cheers,
Med

> -----Message d'origine-----
> De : Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Envoyé : samedi 29 mai 2021 02:34
> À : gregory.mirsky@ztetx.com; sfc@ietf.org
> Cc : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>
> Objet : Re: Way forward for draft-ao-sfc-oam-return-path-specified
> 
> While that sounds reasonable, I (and I presume Jim) would like to hear from
> members of the working group.  The base document is adopted by the WG,
> so the WG owns change control.
> Do people think adding the substantive comment from the otehr two
> referenced drafts would be helpful?
> 
> Thank you,
> Joel
> 
> On 5/28/2021 7:56 PM, gregory.mirsky@ztetx.com wrote:
> > Dear Jim, Joel, et al.,
> >
> > in the course of discussing draft-ietf-sfc-multi-layer-oam
> > <https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/>,
> > Med has pointed out that it seems useful to merge the substantive part
> > of
> >
> > draft-ao-sfc-oam-return-path-specified
> > <https://datatracker.ietf.org/doc/draft-ao-sfc-oam-return-path-specifi
> > ed/>to
> > the draft-ietf-sfc-multi-layer-oam:
> >
> > GIM>> I propose adding informational reference
> > to draft-ao-sfc-oam-return-path-specified as follows:
> >
> > /[Med] I would prefer to have the content of
> > ao-sfc-oam-return-path-specified included in
> > draft-ietf-sfc-multi-layer-oam unless you are confident to progress
> > that I-D separately. It is up to you./
> >
> >
> > Thinking of Med's suggestion, I've realized that the same step can be
> > considered for draft-ao-sfc-oam-path-consistency
> > <https://datatracker.ietf.org/doc/draft-ao-sfc-oam-path-consistency/>.
> > Both individual drafts extend SFC NSH Echo Request/Reply defined in
> > draft-ietf-sfc-multi-layer-oam and might be progressed independently.
> > On the other hand, mechanisms described in these individual drafts are
> > useful in an SFC NSH.
> >
> > Much appreciate your suggestions, guidance.
> >
> >
> > Regards,
> >
> > Greg Mirsky
> >
> >
> > Sr. Standardization Expert
> > 预研标准部/有线研究院/有线产品经营部 Standard Preresearch
> Dept./Wireline Product R&D
> > Institute/Wireline Product Operation Division
> >
> >
> >
> > E: gregory.mirsky@ztetx.com <mailto:gregory.mirsky@ztetx.com>
> > www.zte.com.cn <http://www.zte.com.cn/>
> >

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.