Last Call: <draft-ietf-mpls-sfc-04.txt> (An MPLS-Based Forwarding Plane for Service Function Chaining) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 17 January 2019 19:52 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA0E6130F5B; Thu, 17 Jan 2019 11:52:48 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-mpls-sfc-04.txt> (An MPLS-Based Forwarding Plane for Service Function Chaining) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.3
Auto-Submitted: auto-generated
Precedence: bulk
CC: mpls@ietf.org, db3546@att.com, mpls-chairs@ietf.org, Loa Andersson <loa@pi.nu>, draft-ietf-mpls-sfc@ietf.org, loa@pi.nu
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-ID: <154775476880.10396.17928468056341396716.idtracker@ietfa.amsl.com>
Date: Thu, 17 Jan 2019 11:52:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/w6UMmmTkPVfl89sDfbq7I71Hn64>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2019 19:52:49 -0000

The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document: - 'An MPLS-Based Forwarding Plane
for Service Function Chaining'
  <draft-ietf-mpls-sfc-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2019-01-31. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mpls-sfc/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mpls-sfc/ballot/


No IPR declarations have been submitted directly on this I-D.