Re: New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Xuxiaohu <xuxiaohu <at> huawei.com>
2015-03-04 04:10:13 GMT
The rationales for leveraging the MPLS-SPRING mechanism to realize the service path layer functionality
of the service function chaining are as follows:
1) eliminate the SFC/SFP states on SFFs. This follows the same logic as MPLS-SPRING and BIER.
2) utilize the existing encapsulation (e.g., the MPLS-SPRING) to a maximum extent. This follows the
Transport Derived SFF concept as described in Section 4.3.1 of draft-ietf-sfc-architecture.
Meanwhile, this is aligned with the current SFC charter, e.g., "...The working group will consider using
an existing encapsulation (with extensions as appropriate) if a suitable candidate is found..."
3) seamlessly support the SFC in a multi-tenant environment (e.g., MPLS VPN). For example, the MPLS VPN
packet (containing metadata) could be further imposed with a label stack which indicates an SFC or SFP
associated with that packet. SFFs receiving the above packet would strip the whole label stack and then
send the payload of the MPLS packet (with metadata) to the corresponding SFs which are tenant-aware and
therefore easily could determine the tenant profile according to the tenant info contained in the
metadata (a.k.a., the NSH).
> -----Original Message-----
> From: Xuxiaohu
> Sent: Wednesday, March 04, 2015 11:31 AM
> To: sfc <at> ietf.org; '<spring <at> ietf.org>'; mpls <at> ietf.org
> Subject: FW: New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
> Hi all,
> This document describes how to leverage the MPLS-based source routing (i.e.,
> MPLS-SPRING) mechanism as developed by the SPRING WG to realize the
> service path layer functionality of the service function chaining. In addition, this
> document also describes how to carry metadata in an MPLS packet by using the
> NSH as a metadata container.
> Any comments are suggestions are welcome.
> Best regards,
> > -----Original Message-----
> > From: internet-drafts <at> ietf.org [mailto:internet-drafts <at> ietf.org]
> > Sent: Wednesday, March 04, 2015 11:24 AM
> > 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-02.txt
> > A new version of I-D, draft-xu-sfc-using-mpls-spring-02.txt
> > has been successfully submitted by Xiaohu Xu and posted to the IETF
> > Name: draft-xu-sfc-using-mpls-spring
> > Revision: 02
> > Title: Service Function Chaining Using MPLS-SPRING
> > Document date: 2015-03-03
> > Group: Individual Submission
> > Pages: 8
> > URL:
> > http://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring-02.
> > txt
> > Status:
> > https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
> > Htmlized: http://tools.ietf.org/html/draft-xu-sfc-using-mpls-spring-02
> > Diff:
> > http://www.ietf.org/rfcdiff?url2=draft-xu-sfc-using-mpls-spring-02
> > 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
mpls mailing list
mpls <at> ietf.org