Re: [sfc] [spring] [mpls] The MPLS WG has placed draft-farrel-mpls-sfc in state "Call For Adoption By WG Issued"

Robert Raszuk <robert@raszuk.net> Wed, 14 March 2018 16:38 UTC

Return-Path: <rraszuk@gmail.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 77122129C5D; Wed, 14 Mar 2018 09:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ZiY1iAcWyIis; Wed, 14 Mar 2018 09:38:09 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 5FC5D127337; Wed, 14 Mar 2018 09:38:09 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id u10so5088649wmu.4; Wed, 14 Mar 2018 09:38:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=WPa402JcrvkDacHhuiDKJunDAr7c319L+52Cxwl9U7c=; b=jDLIkj+jXR1TK612T4gJfXGDfIzxGJSevdGRDRQwUY6T997b7ZYALgJAH9l2e/gDkU c8zHVUAW0cL1LWlAQTYIGOZWyJJgE81J7T5qbt57e/vZArTBUFj1MIn1GJbHbT/WzX5G Vnk6vdq2V76xNl1BuQmVHiQ5OcPRIrFSC4TiSStUvDel6jdq7LAiG73K2o/sR+olV+dy rqffcsyv4VH2aZYETTHBpqE7dxOd81hCI6InjbsD/07iZ4bMtHMpiG++7a8nAgRVf1tK H9MiBXmkasn5a/gUwdwR5xX7KAHqnL54Vp0Nllyc95aXU8xM4xT/T87XwSZCLylC2ezh yOzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=WPa402JcrvkDacHhuiDKJunDAr7c319L+52Cxwl9U7c=; b=DbLDk7zKhiYxQf95hsNJA8iFGFHPER1LMT4T1eL2rxMWBZYrWTjuM9s2w1UH8k6tA9 npt59GiVDkDc2MEjXtP9vCtUIXbV50GXYmM9rnlQeD4iOLLngAK7AG9okk/V9W41vjvP i/3ZMKD74zKPPGKPrNTr0ODoyi3uDu+rmCuQ0mZZw6Pru6B0Ckhac5V8c9gpxDSb593Q Wka2So/Lz2zU4ARh2TBG8l1BxB06JjFYgo9sjKQFmquoIK7/o+7XlxyCBDEad1LA+DbI XLy0N1bIfY8SzgLDDSJGAH05JsqC7kZQftsCBPReJVWYffYXY7TgySrPpCiICOYEbhhM Umzg==
X-Gm-Message-State: AElRT7GyhaLMc0tAycNQ/Mcmu4eisXkPP8NHVi21wiD1yeQF/hWLSIFd s8+9WtAoyK9+9p6O3Umstyo0JSYdT60rGr/MnWU=
X-Google-Smtp-Source: AG47ELuSWf4zwRM7CKza/XeieAouFlpu8xv5j71ApWe1xXcBCnE9BsMimG5QdSRkJgetD3TmE3i+yiVY1ZWrAHzGM44=
X-Received: by 10.28.184.8 with SMTP id i8mr2426956wmf.52.1521045487546; Wed, 14 Mar 2018 09:38:07 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.28.66.2 with HTTP; Wed, 14 Mar 2018 09:38:06 -0700 (PDT)
In-Reply-To: <DM5PR0501MB3831684E174360726E74AE61C7D10@DM5PR0501MB3831.namprd05.prod.outlook.com>
References: <152034533897.28338.3516810951049973930.idtracker@ietfa.amsl.com> <783286e2-e7ef-4a1a-8fe3-3adf6142d92e.xiaohu.xxh@alibaba-inc.com> <FE22665C-98ED-457A-AE11-93B8D8718A0A@cisco.com> <223B2356-E9EA-4627-B989-A68382CF3DED@cisco.com> <053801d3b787$71f117d0$55d34770$@olddog.co.uk> <B38EC124-80B8-4CBC-A218-E68A0BC7FF42@cisco.com> <BF1BE6D99B52F84AB9B48B7CF6F17DA3134EBF9C@sjceml521-mbs.china.huawei.com> <DM5PR0501MB3831DDA10DEE8C2E770B6812C7D20@DM5PR0501MB3831.namprd05.prod.outlook.com> <CA+b+ER=8F3Zb-rd1c9Gjs+nD--cpSKSm5b+eCO0U74mQc6nvGw@mail.gmail.com> <DM5PR0501MB3831490AC323865727F57DD6C7D20@DM5PR0501MB3831.namprd05.prod.outlook.com> <CA+b+ERmjhBYbwz4NOdBJdPUcnP4gNc-5P6QMFF5NO+CN1fJHbg@mail.gmail.com> <DM5PR0501MB3831BD3CA5998533D776079CC7D10@DM5PR0501MB3831.namprd05.prod.outlook.com> <1521039244026.37163@bell.ca> <DM5PR0501MB3831B58B241B9D032F339497C7D10@DM5PR0501MB3831.namprd05.prod.outlook.com> <CA+b+ERkva_ss1MGdmRjuAJzRsp23B_JgRnswMz4gaD9_0B+NuQ@mail.gmail.com> <DM5PR0501MB3831684E174360726E74AE61C7D10@DM5PR0501MB3831.namprd05.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 14 Mar 2018 17:38:06 +0100
X-Google-Sender-Auth: QBMaYjGX762CLewQZnnBypmpwcw
Message-ID: <CA+b+ERnp5-t_sHNcjZLY=gC=dTre8RHWn4pLBT9D2qnTQqq46g@mail.gmail.com>
To: John E Drake <jdrake@juniper.net>
Cc: "EXT - daniel.bernier@bell.ca" <daniel.bernier@bell.ca>, mpls <mpls@ietf.org>, SPRING WG List <spring@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, James N Guichard <james.n.guichard@huawei.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Francois Clad (fclad)" <fclad@cisco.com>
Content-Type: multipart/alternative; boundary="001a114b2c56f912fe056761ffb0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/XtW3hQ1xCd0n2jpaF0dLpM1PqqQ>
Subject: Re: [sfc] [spring] [mpls] The MPLS WG has placed draft-farrel-mpls-sfc in state "Call For Adoption By WG Issued"
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 14 Mar 2018 16:38:12 -0000

 *> [JD  They both draw upon the same heritage.*

I respectfully disagree John with that. One should not equate control plane
solution with data plane embedded solution. Those are completely different
spaces and different heritages.

I would further claim that we do have much more heritage in control plane
path steering rather then in data plane embedding of the same.

Cheers,
R.



On Wed, Mar 14, 2018 at 5:30 PM, John E Drake <jdrake@juniper.net> wrote:

> Robert,
>
>
>
> Comments inline
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* rraszuk@gmail.com [mailto:rraszuk@gmail.com] *On Behalf Of *Robert
> Raszuk
> *Sent:* Wednesday, March 14, 2018 12:00 PM
> *To:* John E Drake <jdrake@juniper.net>
> *Cc:* EXT - daniel.bernier@bell.ca <daniel.bernier@bell.ca>; mpls <
> mpls@ietf.org>; SPRING WG List <spring@ietf.org>; sfc@ietf.org; James N
> Guichard <james.n.guichard@huawei.com>; adrian@olddog.co.uk; Francois
> Clad (fclad) <fclad@cisco.com>
> *Subject:* Re: [spring] [mpls] [sfc] The MPLS WG has placed
> draft-farrel-mpls-sfc in state "Call For Adoption By WG Issued"
>
>
>
> Hi John,
>
>
>
> Daniel,
>
>
>
> It has a multiplicity of issues, primarily wrt scalability and ease of
> configuration.
>
>
>
>
>
> ​Am I reading your comment correctly that draft-ietf-bess-service-chaining-04
> is unscalable and hard to configure and draft ​draft-farrel-mpls-sfc is
> superior ?
>
>
>
>
>
> *[JD]  The authors of that draft provided much input and guidance to the
> authors of ​draft-farrel-mpls-sfc. *
>
>
>
>
>
> Please observe that your own Juniper products are based already for a long
> time on the former and as you admited no one has any product based on the
> latter.
>
>
>
>
>
> *[JD]  I am not sure of your point.*
>
>
>
>
>
> Doesn't this makes it a bit of an odd argument ? Also please do notice
> that  draft-ietf-bess-service-chaining-04 vastly reuses 20 years of
> experience of L3VPNs service so your claim may be IMHO a little weak :)
>
>
>
>
>
> *[JD  They both draw upon the same heritage. *
>
>
>
>
>
> Cheers,
> R.
>
>
>
>
>
>  Yours Irrespectively,
>
> John
>
>
>
> *From:* spring [mailto:spring-bounces@ietf.org] *On Behalf Of *Bernier,
> Daniel
> *Sent:* Wednesday, March 14, 2018 10:54 AM
> *To:* John E Drake <jdrake@juniper.net>; Robert Raszuk <robert@raszuk.net>
> *Cc:* mpls <mpls@ietf.org>; SPRING WG List <spring@ietf.org>; sfc@ietf.org;
> James N Guichard <james.n.guichard@huawei.com>; adrian@olddog.co.uk;
> Francois Clad (fclad) <fclad@cisco.com>
>
> *Subject:* Re: [spring] [mpls] [sfc] The MPLS WG has placed
> draft-farrel-mpls-sfc in state "Call For Adoption By WG Issued"
>
>
>
> Hi John,
>
>
>
> Don't we already have draft-fm-bess-service-chaining-01
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dfm-2Dbess-2Dservice-2Dchaining-2D01&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=F3v0beOmsieoZ48B9JYfPjhGusHbW5F5SF9W20KcURU&s=UHNxeZF9m0BVCmAjG-ODELBOjV1v2yu25uDOeZSRw6g&e=>
> to perform service chains with existing MPLS implementations ?
>
>
>
> Thanks,​
>
>
>
>