Re: [mpls] [sfc] An MPLS Forwarding plane for SFC

"Van De Velde, Gunter (Nokia - BE/Antwerp)" <> Mon, 04 September 2017 07:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C8F981321AA; Mon, 4 Sep 2017 00:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id J-zgI-WjxsTJ; Mon, 4 Sep 2017 00:29:27 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A5621132199; Mon, 4 Sep 2017 00:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=lZA1SQPkirGEKo9A5469Egt8OzddN39Od6t0Zyc4SNU=; b=e+GuGd5F52GB87SxOmmgKvyopv3Gi0H5zP0DvOVRrdyOnFkuHk16QU6/XwbXVCgKAEGbwpSled+dR4bkiPCUJAILqR2KHdl8LIhmrpckkG0hQyNwbS5yMShe8XiA7KlfWOQMLyJfKYHbQnhl9GJ6TH5bn941GgDAAiuR/k7GJ2Q=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id; Mon, 4 Sep 2017 07:29:23 +0000
Received: from ([fe80::dfc:8ef3:9884:fe07]) by ([fe80::dfc:8ef3:9884:fe07%14]) with mapi id 15.20.0035.009; Mon, 4 Sep 2017 07:29:23 +0000
From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" <>
To: "Joel M. Halpern" <>, "" <>, "" <>
CC: 'Service Function Chaining IETF list' <>
Thread-Topic: [sfc] An MPLS Forwarding plane for SFC
Thread-Index: AdMjXxXVPkarGltYRZ25UDV5w+jgOgAAWBSAAH/07YA=
Date: Mon, 04 Sep 2017 07:29:23 +0000
Message-ID: <>
References: <034601d3235f$1f4ef590$5dece0b0$> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-GB
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM4PR07MB1297; 6:zoOWD6oeS9LX4bbm1hiSoq+Jy9sEjj/7hbt1R09s3f6b03swew8/yzXX6Pbhxq1TR8jkZFONIWim8f6q+1ogNJNV5FFnGJts3JQHdDttDgv2UrPcy3NeqsybCOLEz8MLqKKi4qfFKMU3tO/xk/wzuo49py2anSUFmK56quYrXUyi6Uxk+C4AjJqL/PUV+hT38QULfEYhGUx+ij5ZtIj7+yEkL2c+LMTUZluRIBsThB94mB2Hj2Jzi0DbhJONeHKsytJeoHRzCiDIhkbBskyt0EnUzQiOBIkOL2jIuRK7dPXcYYsO9LedidszH8yx8tr1kudUltov8LcTVUTkHh9Mug==; 5:XPvq7376WyR8GqccBPuNo0cQjMZBHj4/KWr13Odc+7p1t981BE2QiwRkQ7JbcTjsx7BChRugDXlgR8iq1ZMVa2im53fdQetxnbYAuhLzKbD+W8i0vJXSfa7/e21++zFLY14ODnqv84XNfFAmGs1AUg==; 24:VBezXNN4OBR9E06gTUlickv+o2XZU74tPac8TGnxXGeSdeSIcgMDKfte1BY1CjjijxLljcnJ17eUVIsqWoixhfI04P+L4/qSgz0mREedMrE=; 7:knBztaZu23IpprhwJvoS24qfJ6DZmK4wwuaFw6SJ5Iyzur/oBa+Hkla2dE5xwhld9zYL4GYt150K6UN9S2nw6fnjl6BNeK2MpXcWsg3CjfvLKz73qOHqok3z6zGE/GDwq6hBvKjOM+0EdTygXWpOKUcHto9XCe54pEirSRO+UCmkPKLN9CH+skcHWPLClaJuEiNeDVt+th2xdUO74nmYLjFHyt/tOYK9tggkYIQIgMM=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: b071ad8d-10a0-44d6-9161-08d4f366aa24
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(48565401081)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:AM4PR07MB1297;
x-ms-traffictypediagnostic: AM4PR07MB1297:
x-exchange-antispam-report-test: UriScan:(278428928389397)(120809045254105);
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(3002001)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123560025)(20161123555025)(20161123558100)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM4PR07MB1297; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM4PR07MB1297;
x-forefront-prvs: 0420213CCD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(24454002)(189002)(377424004)(377454003)(13464003)(199003)(81166006)(8676002)(6486002)(53936002)(966005)(53546010)(2950100002)(106356001)(105586002)(2906002)(6306002)(6512007)(3280700002)(3660700001)(99286003)(14454004)(54356999)(50986999)(5250100002)(76176999)(2501003)(101416001)(6436002)(81156014)(7736002)(6506006)(229853002)(305945005)(8936002)(66066001)(68736007)(33656002)(6116002)(4326008)(189998001)(102836003)(2900100001)(82746002)(36756003)(2201001)(97736004)(83716003)(5660300001)(478600001)(25786009)(86362001)(3846002)(6246003); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB1297;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is );
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2017 07:29:23.1725 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB1297
Archived-At: <>
Subject: Re: [mpls] [sfc] An MPLS Forwarding plane for SFC
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Sep 2017 07:29:30 -0000

I believe that the approach as Adrian outlines is very pragmatic.

Joel, not sure I agree about being bound by transport mechanism when using MPLS, as the 
MPLS sequenced labels can be transported over any type of transport just like NSH could be transported.
For sure there is as Adrian mentions a trade-off regarding flexibility, so each will find its application realm. 
For many the flexibility in the sequenced MPLS label approach will be sufficient for business purpose.


On 01/09/2017, 22:25, "sfc on behalf of Joel M. Halpern" < on behalf of> wrote:

    Reading this draft, what you have proposed is a specific transport 
    mechanism, using MPLS.  By removing the NSH header, you remove the 
    transport agnostic properties that the Working Group was specifically 
    chartered to achieve.
    By recasting the metadata into a label sequence, you make any metaata 
    processing significantly harder, and make applications dependent upon 
    the MPLS transport, rather than being able to rely on the NSH format. 
    If this pattern were followed for other transports, we would require SFF 
    and SF which understood how to parse and process all of the different 
    transport encodings of the path, and SF would have to understand all the 
    different transport encodings of the metadata.
    Why is this beneficial?
    If what you want to do is carry NSH, with an MPLS label stack that 
    represents the whole sequence of places to visit, we would still have to 
    assume that SF preserved the MPLS stack, but their processing, assuming 
    they could find the carried NSH header under the MPLS stack, would at 
    least be independent of the transport.
    On 9/1/17 4:15 PM, Adrian Farrel wrote:
    > Hi,
    > We've been working up some ideas for using an MPLS forwarding plane (switching
    > or SR) for SFC.
    > We have constrained ourselves to the architecture developed by the SFC working
    > group, and have used the NSH as a functional model.
    > MPLS is somewhat limited compared to the NSH encapsulation, so there is a
    > trade-off between using a new encapsulation with full function and a good set of
    > function using an existing forwarding plane.
    > At the moment this is an early version of our work, but we thought you'd like to
    > see our thought processes.
    > (FWIW draft-ietf-bess-nsh-bgp-control-plane is applicable to NSH or MPLS
    > encapsulations and includes mechanisms to select between the two.)
    > Cheers,
    > Adrian
    >> -----Original Message-----
    >> From: I-D-Announce [] On Behalf Of
    >> Sent: 01 September 2017 21:00
    >> To:
    >> Subject: I-D Action: draft-farrel-mpls-sfc-00.txt
    >> A New Internet-Draft is available from the on-line Internet-Drafts
    > directories.
    >>          Title           : An MPLS-Based Forwarding Plane for Service Function
    > Chaining
    >>          Authors         : Adrian Farrel
    >>                            Stewart Bryant
    >>                            John Drake
    >> 	Filename        : draft-farrel-mpls-sfc-00.txt
    >> 	Pages           : 23
    >> 	Date            : 2017-09-01
    >> Abstract:
    >>     Service Function Chaining (SFC) is the process of directing packets
    >>     through a network so that they can be acted on by an ordered set of
    >>     abstract service functions before being delivered to the intended
    >>     destination.  An architecture for SFC is defined in RFC7665.
    >>     The Network Service Header (NSH) can be inserted into packets to
    >>     steer them along a specific path to realize a Service Function Chain.
    >>     Multiprotocol Label Switching (MPLS) is a widely deployed forwarding
    >>     technology that uses labels to identify the forwarding actions to be
    >>     taken at each hop through a network.  Segment Routing is a mechanism
    >>     that provides a source routing paradigm for steering packets in an
    >>     MPLS network.
    >>     This document describes how Service Function Chaining can be achieved
    >>     in an MPLS network by means of a logical representation of the NSH in
    >>     an MPLS label stack.
    >> The IETF datatracker status page for this draft is:
    >> There are also htmlized versions available at:
    >> Please note that it may take a couple of minutes from the time of submission
    >> until the htmlized version and diff are available at
    >> Internet-Drafts are also available by anonymous FTP at:
    >> _______________________________________________
    >> I-D-Announce mailing list
    >> Internet-Draft directories:
    >> or
    > _______________________________________________
    > sfc mailing list
    sfc mailing list