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

wei.yuehua@zte.com.cn Tue, 01 June 2021 02:40 UTC

Return-Path: <wei.yuehua@zte.com.cn>
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 990623A1487 for <sfc@ietfa.amsl.com>; Mon, 31 May 2021 19:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.194
X-Spam-Level:
X-Spam-Status: No, score=-4.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=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
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 dA3rxQM-M4TH for <sfc@ietfa.amsl.com>; Mon, 31 May 2021 19:40:54 -0700 (PDT)
Received: from mxde.zte.com.cn (mxde.zte.com.cn [209.9.37.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E60523A1489 for <sfc@ietf.org>; Mon, 31 May 2021 19:40:53 -0700 (PDT)
Received: from mse-eu.zte.com.cn (unknown [10.35.13.51]) by Forcepoint Email with ESMTPS id 31F2FFC1BE407CE93681; Tue, 1 Jun 2021 10:40:51 +0800 (CST)
Received: from dgapp02.zte.com.cn ([10.35.13.17]) by mse-eu.zte.com.cn with SMTP id 1512ecv5005117; Tue, 1 Jun 2021 10:40:38 +0800 (GMT-8) (envelope-from wei.yuehua@zte.com.cn)
Received: from mapi (dgapp02[null]) by mapi (Zmail) with MAPI id mid1; Tue, 1 Jun 2021 10:40:39 +0800 (CST)
Date: Tue, 01 Jun 2021 10:40:39 +0800
X-Zmail-TransId: 2afa60b59e27f07dcd3b
X-Mailer: Zmail v1.0
Message-ID: <202106011040389753147@zte.com.cn>
In-Reply-To: <2de22857-4947-7360-af5b-47f27ba2f215@joelhalpern.com>
References: 202105290756323443789@zte.com.cn, 2de22857-4947-7360-af5b-47f27ba2f215@joelhalpern.com
Mime-Version: 1.0
From: wei.yuehua@zte.com.cn
To: jmh@joelhalpern.com
Cc: gregory.mirsky@ztetx.com, sfc@ietf.org, mohamed.boucadair@orange.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-eu.zte.com.cn 1512ecv5005117
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/TvhfUbKQpijxIeKjHj54me-8HGo>
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 02:40:59 -0000

It sounds a good idea to merge the substantive part of the two indivisual drafts to draft-ietf-sfc-multi-layer-oam. So that a more complete solution will be in one draft.


and it will save further more review workload for the WG.








Best Regards,


Yuehua Wei


M: +86 13851460269 E: wei.yuehua@zte.com.cn









原始邮件



发件人:JoelM.Halpern
收件人:Gregory10211915;sfc@ietf.org;
抄送人:mohamed.boucadair@orange.com;
日 期 :2021年05月29日 08:34
主 题 :Re: [sfc] 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-specified/>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/>
> 

_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc