[mpls] New version: draft-ietf-mpls-sfc-03.txt

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 13 October 2018 16:09 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 2AAE0130EF5 for <mpls@ietfa.amsl.com>; Sat, 13 Oct 2018 09:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 aCm_tBMtK6wG for <mpls@ietfa.amsl.com>; Sat, 13 Oct 2018 09:09:18 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 3A52D130E43 for <mpls@ietf.org>; Sat, 13 Oct 2018 09:09:18 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id w9DG9GmM027633 for <mpls@ietf.org>; Sat, 13 Oct 2018 17:09:16 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BEED12203A for <mpls@ietf.org>; Sat, 13 Oct 2018 17:09:15 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs3.iomartmail.com (Postfix) with ESMTPS id AA16022032 for <mpls@ietf.org>; Sat, 13 Oct 2018 17:09:15 +0100 (BST)
Received: from 950129200 (4.43.114.87.dyn.plus.net [87.114.43.4]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id w9DG9EH9015115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mpls@ietf.org>; Sat, 13 Oct 2018 17:09:15 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: mpls@ietf.org
Date: Sat, 13 Oct 2018 17:09:13 +0100
Message-ID: <017501d4630f$15fa9530$41efbf90$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdRjDxH5210LGi40Q4KLlbaBC4g67g==
Content-Language: en-gb
X-Originating-IP: 87.114.43.4
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-24154.001
X-TM-AS-Result: No--18.448-10.0-31-10
X-imss-scan-details: No--18.448-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24154.001
X-TMASE-Result: 10--18.448100-10.000000
X-TMASE-MatchedRID: mW99dfI1akag1DExZSWfTfSG/+sPtZVkvtVce6w5+K8bVUVEY6U/r4Rj b6q99slJL0XFppDD7kskAzbREWz9m7BAQLqGlKivsyNb+yeIRAojo8c0NkYYIn1ZAf3L+lJdf/b TCoZRptJNYvDaO9t+nPE/T9QKeKEb/E5CAZnt+vmVUcz8XpiS9HJrB0Cu3DDnRjHvrQ40NxYON+ MFU6qxaKUsYF0AplQ+WkEwb/DqEve5GIsyuQXveukpglpnF5UNU3rOnQwllENZps+y1VXzqWQcK yBERs/hQ8bD4Z5QhI3s+Xii+PV65vOwVAQ1J9gRgQy/ei4MrjFu/Xr6CKXiN5JWUogu623F7kOM rBz6LkmiVGrfmwmNNY4j5YQcDla2j56IjTnLR+nCtSG/SQAC8ToSfZud5+Ggpcn28zKwP8KnavN TfNDmTe5f+SbQ7VhgC5sAwRKoKs7EPT0UZOWRrJ4CIKY/Hg3AtOt1ofVlaoKm8jxRk5/juFNkM6 vOVn5wdB0ntd9Tzp7iRhduhvElsqX8y2tPBLhQrSeW0KONGqG+qXW3UyOCAk4lo3pPg0d3X2H6y VJN9F3b4eRTZfitXA==
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/fKJiFXFCzLXadarGPf-zwVF6hRo>
Subject: [mpls] New version: draft-ietf-mpls-sfc-03.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Oct 2018 16:09:21 -0000

Hi,

The update here is just to fix an email address and a reference.

>From my point of view this work is done with just one open question for the
WG...

Currently we use an extended special purpose label to identify that SFC labels
follow. The question is: is this work sufficiently mainstream to use a regular
special purpose label?

Thoughts?

Thanks,
Adrian
> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 13 October 2018 17:05
> To: i-d-announce@ietf.org
> Cc: mpls@ietf.org
> Subject: I-D Action: draft-ietf-mpls-sfc-03.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Multiprotocol Label Switching WG of the IETF.
> 
>         Title           : An MPLS-Based Forwarding Plane for Service Function
Chaining
>         Authors         : Adrian Farrel
>                           Stewart Bryant
>                           John Drake
> 	Filename        : draft-ietf-mpls-sfc-03.txt
> 	Pages           : 28
> 	Date            : 2018-10-13
> 
> 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 placed in a packet in a label stack to
>    identify the forwarding actions to be taken at each hop through a
>    network.  Actions may include swapping or popping the labels as well,
>    as using the labels to determine the next hop for forwarding the
>    packet.  Labels may also be used to establish the context under which
>    the packet is forwarded.
> 
>    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.  It does not deprecate or replace the NSH, but
>    acknowledges that there may be a need for an interim deployment of
>    SFC functionality in brownfield networks.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mpls-sfc/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mpls-sfc-03
> https://datatracker.ietf.org/doc/html/draft-ietf-mpls-sfc-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-sfc-03
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt