Re: [mpls] FW: New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt

"Joel M. Halpern" <> Wed, 09 September 2015 14:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C05A51A8725; Wed, 9 Sep 2015 07:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8VcEwBD72_WV; Wed, 9 Sep 2015 07:21:31 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 48CE01B2C3D; Wed, 9 Sep 2015 07:21:31 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2B98F241025; Wed, 9 Sep 2015 07:21:31 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at
Received: from Joels-MacBook-Pro.local ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id B8691240A39; Wed, 9 Sep 2015 07:21:30 -0700 (PDT)
To: Xuxiaohu <>, "''" <>
References: <>
From: "Joel M. Halpern" <>
Message-ID: <>
Date: Wed, 09 Sep 2015 10:21:29 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Cc: "''" <>
Subject: Re: [mpls] FW: New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Sep 2015 14:21:33 -0000

This draft seems to be written as if MPLS were a transport-independent 
forwarding mechanism for SFC.  While I expect MPLS (and MPLS-SPRING) to 
be used as a transport for MPLS, and sometimes as a transport across 
multiple service functions, I would NOT claim that it is itself 
transport independent.

As such, I am unclear on how the SFC working group could adopt this 

Considered as a transport description, it does not appear to standardize 
anything, so it would seem at most to be an informational document.

Joel M. Halpern

On 9/9/15 5:45 AM, Xuxiaohu wrote:
> Hi all,
> Service chaining is an important function for all type of networks including those using the source routing paradigm as specified by the SPRING working group. This draft is especially focused on the SPRING/MPLS network scenario.
> When we posted the early versions (-00 to -02), the feedback from the SFC working group chairs was that the solution required changes to the MPLS architecture. We discussed this among the authors and posted a new version (-03) that does not require any change to the MPLS Architecture anymore. Version -04 merely corrects some typos.
> Now we would like to ask the SFC chairs and WGs if the draft can now be considered for adoption by the SFC working group.
> Best regards,
> Xiaohu
>> -----Original Message-----
>> From: []
>> Sent: Wednesday, September 09, 2015 5:23 PM
>> To: Lizhenbin; Luis M. Contreras; Xuxiaohu; Himanshu C. Shah; Xuxiaohu;
>> Himanshu Shah; Luis M. Contreras; Lizhenbin
>> Subject: New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt
>> A new version of I-D, draft-xu-sfc-using-mpls-spring-04.txt
>> has been successfully submitted by Xiaohu Xu and posted to the IETF repository.
>> Name:		draft-xu-sfc-using-mpls-spring
>> Revision:	04
>> Title:		Service Function Chaining Using MPLS-SPRING
>> Document date:	2015-09-09
>> Group:		Individual Submission
>> Pages:		7
>> URL:
>> Status:
>> Htmlized:
>> Diff:
>> Abstract:
>>     Source Packet Routing in Networking (SPRING) WG specifies a special
>>     source routing mechanism.  Such source routing mechanism can be
>>     leveraged to realize the service path layer functionality of the
>>     service function chaining (i.e, steering traffic through a particular
>>     service function path) by encoding the service function path or the
>>     service function chain information as the explicit path information.
>>     This document describes how to leverage the MPLS-based source routing
>>     mechanism as developed by the SPRING WG to realize the service path
>>     layer functionality of the service function chaining.
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at
>> The IETF Secretariat
> _______________________________________________
> mpls mailing list