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

Xuxiaohu <xuxiaohu@huawei.com> Wed, 28 October 2015 04:07 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4C0C1B45D0; Tue, 27 Oct 2015 21:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 dopqt-aZH9P5; Tue, 27 Oct 2015 21:07:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B369D1B45CC; Tue, 27 Oct 2015 21:07:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CDE15256; Wed, 28 Oct 2015 04:07:40 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 28 Oct 2015 04:07:39 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.187]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0235.001; Wed, 28 Oct 2015 12:07:30 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "'sfc@ietf.org'" <sfc@ietf.org>, "sfc-chairs@tools.ietf.org" <sfc-chairs@tools.ietf.org>
Thread-Topic: New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt
Thread-Index: AQHQ6uEhwUT+nrZsQk6IpAAbYfyXTp4z7JRggEylwuA=
Date: Wed, 28 Oct 2015 04:07:30 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3DFAF@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/1SS-DL25PWe_LFc7V9ee-NkLTrE>
Cc: "'mpls@ietf.org'" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>
Subject: Re: [mpls] New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 28 Oct 2015 04:07:46 -0000

Hi SFC co-chairs,

I haven't received any response from you yet. Would you please tell us your thoughts on the new version of this draft. Thanks a lot.

Best regards,
Xiaohu (on behalf of all co-authors)

> -----Original Message-----
> From: Xuxiaohu
> Sent: Wednesday, September 09, 2015 5:45 PM
> To: 'sfc@ietf.org'; sfc-chairs@tools.ietf.org
> Cc: 'mpls@ietf.org'; mpls-chairs@tools.ietf.org
> Subject: FW: New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt
> 
> 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: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > 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:
> > https://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring-04
> > .txt
> > Status:
> > https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
> > Htmlized:       https://tools.ietf.org/html/draft-xu-sfc-using-mpls-spring-04
> > Diff:
> > https://www.ietf.org/rfcdiff?url2=draft-xu-sfc-using-mpls-spring-04
> >
> > 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 tools.ietf.org.
> >
> > The IETF Secretariat