Re: [mpls] Progress with draft-farrel-mpls-sfc

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 17 March 2018 17:59 UTC

Return-Path: <adrian@olddog.co.uk>
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 7CE2A129C6A; Sat, 17 Mar 2018 10:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 viNBBO7BfYyL; Sat, 17 Mar 2018 10:59:30 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (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 E177E128D2E; Sat, 17 Mar 2018 10:59:29 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id w2HHxKN6002093; Sat, 17 Mar 2018 17:59:21 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6AC032203C; Sat, 17 Mar 2018 17:59:20 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id 54F602203A; Sat, 17 Mar 2018 17:59:20 +0000 (GMT)
Received: from 950129200 ([82.113.183.179]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id w2HHxGmr028928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Mar 2018 17:59:17 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'James N Guichard' <james.n.guichard@huawei.com>
Cc: mpls@ietf.org, sfc@ietf.org, 'SPRING WG List' <spring@ietf.org>
References: <019501d3bd6b$657d7ef0$30787cd0$@olddog.co.uk> <BB36A9A4-284C-4B36-BDE0-6B919273AB02@nokia.com> <BF1BE6D99B52F84AB9B48B7CF6F17DA3134ED142@sjceml521-mbs.china.huawei.com>
In-Reply-To: <BF1BE6D99B52F84AB9B48B7CF6F17DA3134ED142@sjceml521-mbs.china.huawei.com>
Date: Sat, 17 Mar 2018 17:59:13 -0000
Message-ID: <00a701d3be19$ab0a5fc0$011f1f40$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI9EwwhHSaTHIL3dWRwh0LHnm5F4wK3BYKFAshnYTai1g5FQA==
Content-Language: en-gb
X-Originating-IP: 82.113.183.179
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-23726.002
X-TM-AS-Result: No--2.372-10.0-31-10
X-imss-scan-details: No--2.372-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-23726.002
X-TMASE-Result: 10--2.372100-10.000000
X-TMASE-MatchedRID: +f/wAVSGjuhT9IXaGuGhLcikxLAkSHclC/ExpXrHizxaW2Ktn+I8/vC1 la2SSTU0hM+ZLv123slP0qF38UTP1JSKA+4pcG3Mw2taljzThMYR5c83KIxTTuOxOq7LQlGLvCi wwGwIXrXwLx34aly34Z9Hb5b61qe6IepuJ592H8vPmshbRFtLmFvaIvTGfP8S2oLGTNKlb9eSkJ bMheHNAYtD1IcLRmYmfdqece5XEVf0am4IG1vk7KfXIl6Cf6VrrC1/+Rk3DMMWug0bekn/3zKWg qZ95vjV7ywe6zE0c4s4tzqlFlBRUg4J2XjL3N+OQpxiLlDD9FXRahuPwaQ1WrKQvscnSWbjV9mp YD+fp5LnzlXMYw4XMD3Al4zalJpFJ0RPnyOnrZJ6lXTFlzozTJ/+BSVOXx2w+yidri74ZBuvig+ FufOE5FLt6snrOOhtbrcuJXWC9UfLGxmrJ55reB3Mwdy23jga0zH+lNslcgXoer1EJMvG+yy0eZ xd5bV4FVIZbguNbjQVic9Khd8bxySFgdUD+vyT
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/KBL393iWDK1ljFuTlzD9g4SQhE8>
Subject: Re: [mpls] Progress with 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: Sat, 17 Mar 2018 17:59:31 -0000

Hi Jim,

(Wonders why Wim and Jim. Anyone called Tim want to comment?)

>     3. Support for SFs that do not handle MPLS
> 
>     There is, in our opinion no difference between an SF that does not handle the
>     NSH in RFC 8300 and an SF that does not handle MPLS in this document. Both
>     need to use an SFC Proxy as described in this document.
> 
> Jim> from the SF perspective yes as it has no clue what is being used between
> SFFs. However, this is IMHO not a true statement from an SFF perspective;
> consider metadata as an example. Yes I know you can cobble together a nice long
> label stack to try and mimic NSH behavior but seriously I do not see this as a viable
> solution and even if it was it would not be normal MPLS forwarding behavior so
> would not work for brownfield. Same comment for MPLS-SR FWIW.

Thanks for the kind words about cobbling ;-)

Actually, as you'll see in the draft, a "long stack" is not used, but also (as noted in the draft and as previously discussed) our approach sacrifices "per packet" metadata.

The problem with an SFC proxy and metadata, as I see it is that there has to be some *other* mechanism to get metadata to an SF that is not SFC-aware. That may be a set additional parameters on an RPC, or it may be some other control/management plane mechanism. But note well that PNFs legacy typically don't have any way to receive metadata before the work of your working group, and VNFs (again prior to your working group) relied on a special understanding between router and VNF if metadata was to be available.

So, clearly the NSH under the SFC architecture offers the richest functional approach. But to restate what I just said to Wim, this is about bridging towards an NSH capable world without upgrading the whole network. We can achieve the basic function well, the moderate function with some effort, and the very advanced function not at all.

When you see the next version to the document, could you look to see whether we could make that point more clearly (I think we put in txt about compromise and trade-offs after we last discussed this with you, but you are probably more sensitised to the point than we are, so we would welcome your eyes).

Thanks,
Adrian