Re: [mpls] [sfc] Working Group adoption of draft-farrel-mpls-sfc

" 徐小虎(义先) " <xiaohu.xxh@alibaba-inc.com> Fri, 30 March 2018 01:42 UTC

Return-Path: <xiaohu.xxh@alibaba-inc.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15823124B18; Thu, 29 Mar 2018 18:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 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, HTTPS_HTTP_MISMATCH=1.989, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alibaba-inc.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 hGk2gLrMzd0Z; Thu, 29 Mar 2018 18:42:12 -0700 (PDT)
Received: from out0-139.mail.aliyun.com (out0-139.mail.aliyun.com [140.205.0.139]) (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 3B7C9126C25; Thu, 29 Mar 2018 18:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1522374127; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=o1ucUysF0otQnkx8yVwb0FJeS3Ejbns8yw2WPhaYTPA=; b=rWmU+k6eFz/o3L5tqB+wXk4TJb1pVh8fjBNuY6Mb+eJL0bRgnrM+GwLqyrhPy/q/VJS8Auq/s9974bs/Zq3/b9h6mTAuSXR+frwAQtyw3k9kK06eUarZ0pyvg8nVgG44ynx8VZrWNaXBbMCjFyJnoMNN7t1hJhrvCtz8AwDSKbI=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R101e4; CH=green; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03305; MF=xiaohu.xxh@alibaba-inc.com; NM=1; PH=DW; RN=8; SR=0; TI=W4_5221377_v5ForWebDing_0A9323E5_1522372124087_o7001c128k;
Received: from WS-web (xiaohu.xxh@alibaba-inc.com[W4_5221377_v5ForWebDing_0A9323E5_1522372124087_o7001c128k]) by e01l10450.eu6 at Fri, 30 Mar 2018 09:42:02 +0800
Date: Fri, 30 Mar 2018 09:42:02 +0800
From: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, Robert Raszuk <robert@raszuk.net>, "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, draft-farrel-mpls-sfc <draft-farrel-mpls-sfc@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, mpls <mpls-bounces@ietf.org>
Reply-To: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
Message-ID: <49eddceb-dd21-4a77-879c-3b0b86c92de8.xiaohu.xxh@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent revision 948139][W4_5221377][v5ForWebDing][Safari]
MIME-Version: 1.0
References: <2ac6b61d-3a38-1aaf-62ae-d923f1ad7468@pi.nu> <a392880f-6b86-4406-a348-42398e24285a.xiaohu.xxh@alibaba-inc.com> <DB5PR07MB158998C7FAAB4831C243D88D83A30@DB5PR07MB1589.eurprd07.prod.outlook.com> <CA+b+ERnJNad6Awo+-2dU2kz6rwx-HQEniXcWgjoWUd-zm3r2qQ@mail.gmail.com>, <F64C10EAA68C8044B33656FA214632C88828EFEB@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C88828EFEB@MISOUT7MSGUSRDE.ITServices.sbc.com>
x-aliyun-mail-creator: W4_5221377_v5ForWebDing_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTJfNikgQXBwbGVXZWJLaXQvNjA0LjUuNiAoS0hUTUwsIGxpa2UgR2Vja28pIFZlcnNpb24vMTEuMC4zIFNhZmFyaS82MDQuNS42La
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_15658_56f03940_5abd95ea_4cd4f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/2qrGNwhpFCLyqfPUVpwc6tZuF5I>
Subject: Re: [mpls] [sfc] Working Group adoption of draft-farrel-mpls-sfc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2018 01:42:15 -0000

Hi Deborah and Martin,
draft-farrel* currently describes two SFC approaches : one is to encode the NSH info, more specifically, the SPI and SI info into two MPLS labels which is a stateful SFC approach just like NSH, another is to leverage the SR, most specifically MPLS-SR to realize a stateless SFC approach (see section 6). 
I wonder whether the former approach or both approaches should be pursued in the MPLS WG from your points of view as ADs.
BTW, as has been pointed out by many people before, the latter has overlapping with the approach as has been described in https://tools.ietf.org/html/draft-xu-mpls-service-chaining-03 (Note that this draft has been proposed many years before and now it has been merged into https://tools.ietf.org/html/draft-xu-clad-spring-sr-service-chaining-00 which includes both MPLS-SR-based and SRv6-based SFC approaches). Fortunately, some author of draft-farrel* has acknoledged this overlapping issue indirectly in his previous email. Unfortunately, the current modifcation of section 6 DOES NOT solve the overlapping issue at all. 
Best regards,Xiaohu
------------------------------------------------------------------BRUNGARD, DEBORAH A <db3546@att.com>2018年3月30日(星期五) 02:58Robert Raszuk <robert@raszuk.net>; "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>mpls@ietf.org <mpls@ietf.org>; 徐小虎(义先) <xiaohu.xxh@alibaba-inc.com>; sfc@ietf.org <sfc@ietf.org>; draft-farrel-mpls-sfc <draft-farrel-mpls-sfc@ietf.org>; mpls-chairs@ietf.org <mpls-chairs@ietf.org>; mpls <mpls-bounces@ietf.org>RE: [sfc] [mpls] Working Group adoption of draft-farrel-mpls-sfc
Hi, Both myself (AD for MPLS) and Martin (AD for SFC and SPRING) were consulted on this draft and we agreed for it to progress in MPLS. WG adoption allows the document to be a document of the working group vs. the authors. If you have input for the document, provide it on the MPLS list. The document will be coordinated at key transitions with SFC. This is not the first
 time that documents early in their timelines may seem to overlap in the different groups, and need the authors to collaborate to sort out/merge, as these documents are ultimately products of IETF, and not the individual authors. I noted below it is said that this new version does not eliminate the conflict with the other draft’s approach. It is best to say specifically which text is in conflict and do a proposal to align. Thanks,Deborah  From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of
Robert Raszuk
Sent: Thursday, March 29, 2018 8:06 AM
To: Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com>
Cc: mpls@ietf.org; 徐小虎(义先) <xiaohu.xxh@alibaba-inc.com>; sfc@ietf.org; draft-farrel-mpls-sfc <draft-farrel-mpls-sfc@ietf.org>; mpls-chairs@ietf.org;
 mpls <mpls-bounces@ietf.org>
Subject: Re: [sfc] [mpls] Working Group adoption of draft-farrel-mpls-sfc Hey Wim, It is very obvious on what basis this adoption happened ....   If ADs do not take any serious action here it will progress smooth & direct to RFC.  I am only a bit puzzled why the WG last call has not started yet on this :/.  Best,R.  On Wed, Mar 28, 2018 at 10:25 AM, Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com> wrote:Similar comment here on what basis do we adopt this. There were serious issues and although a new draft was posted they have not been addressed. On what basis do you adopt this? I thought IETF works on basis of consensus and in my view
 this was not achieved so far. From iPhoneFrom: mpls <mpls-bounces@ietf.org> on behalf of
徐小虎(义先) <xiaohu.xxh@alibaba-inc.com>
Sent: Wednesday, March 28, 2018 10:17:04 AM
To: mpls; mpls@ietf.org
Cc: draft-farrel-mpls-sfc; 
mpls-chairs@ietf.org; sfc@ietf.org
Subject: Re: [mpls] Working Group adoption of draft-farrel-mpls-sfc Hi Loa, I don't believe the modification in Section 6 of draft-farrel-mpls-sfc (https://tools.ietf.org/rfcdiff?url2=draft-farrel-mpls-sfc-05.txt)
 has eliminated the serious conflict with the SR-MPLS-based SFC approach as described in  https://tools.ietf.org/html/draft-xu-mpls-service-chaining-03 (note
 that this draft has been merged into https://tools.ietf.org/html/draft-xu-clad-spring-sr-service-chaining-00)
 as had been pointed by many people before. Therefore, it seems a little bit unreasonable to hurry the adoption of the current version, IMHO. Xiaohu------------------------------------------------------------------Loa Andersson <loa@pi.nu>2018年3月28日(星期三)
 15:56mpls@ietf.org <mpls@ietf.org>draft-farrel-mpls-sfc <draft-farrel-mpls-sfc@ietf.org>;
sfc@ietf.org <sfc@ietf.org>;
mpls-chairs@ietf.org <mpls-chairs@ietf.org>[mpls] Working Group adoption of draft-farrel-mpls-sfc Working Group,


The MPLS working group have decided to adopt draft-farrel-mpls-sfc-05 as

an MPLS working group document.


Can the authors please post draft-ietf-mpls-sfc-00, without any other

than administrative (filename, version and dates) changes.


/Loa

for the MPLS wg chairs


-- 



Loa Andersson                        email: loa@pi.nu

Senior MPLS Expert

Bronze Dragon Consulting             phone: +46 739 81 21 64


_______________________________________________

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

_______________________________________________

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