[mpls] 转发: New Version Notification for draft-xu-mpls-service-chaining-01.txt

Xuxiaohu <xuxiaohu@huawei.com> Mon, 22 May 2017 07:03 UTC

Return-Path: <xuxiaohu@huawei.com>
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 56529129B6C for <mpls@ietfa.amsl.com>; Mon, 22 May 2017 00:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 9JKu2rvefPjN for <mpls@ietfa.amsl.com>; Mon, 22 May 2017 00:03:00 -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 08163129B6D for <mpls@ietf.org>; Mon, 22 May 2017 00:02:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNN06009; Mon, 22 May 2017 07:02:58 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 22 May 2017 08:02:57 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Mon, 22 May 2017 15:02:47 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: New Version Notification for draft-xu-mpls-service-chaining-01.txt
Thread-Index: AQHSyWGscDurMPAbREWzexnvBaUXtKH4Q6Bg
Date: Mon, 22 May 2017 07:02:47 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BBA902E@NKGEML515-MBX.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.184.181]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.59228D22.009C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 7310a0121f9a465931709deb6c8b49fc
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/HFsUrPVvFVjc0dzmyUVQcU9GUZk>
Subject: [mpls] =?utf-8?b?6L2s5Y+ROiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9y?= =?utf-8?q?_draft-xu-mpls-service-chaining-01=2Etxt?=
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 22 May 2017 07:03:04 -0000

Hi all,

As illustrated in (https://tools.ietf.org/html/draft-xu-mpls-unified-source-routing-instruction), the MPLS source routing mechanism developed by the SPRING WG can be leveraged to realize a unified source routing instruction which works across both IPv4 underlay and IPv6 underlay, in addition to the MPLS underlay. In other words, although the MPLS was originally developed as a transport technology, it doesn't prevent us from using it as an overlay instruction. In fact, the VPN label and PW label are concrete examples of overlay instructions.

The unified source routing instruction concept could be leveraged further to realize a transport-independent service function chaining by encoding the service function path information or service function chain information as a unified source routing instruction (a.k.a., an MPLS label stack). Since the unified source routing instruction could work across different underlay networks including IPv4, IPv6 and MPLS underlay, the service function encapsulation header implemented in the form of a unified source routing instruction (a.k.a., an MPLS label stack) is transport-independent accordingly.

Any comments and suggestions are more than welcome.

Best regards,
Xiaohu

> -----邮件原件-----
> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> 发送时间: 2017年5月10日 15:47
> 收件人: Hamid Assarpour; Luis M. Contreras; Xuxiaohu; Stewart Bryant;
> daniel.bernier@bell.ca; Luis Contreras; Daniel Bernier; Himanshu Shah
> 主题: New Version Notification for draft-xu-mpls-service-chaining-01.txt
> 
> 
> A new version of I-D, draft-xu-mpls-service-chaining-01.txt
> has been successfully submitted by Xiaohu Xu and posted to the IETF repository.
> 
> Name:		draft-xu-mpls-service-chaining
> Revision:	01
> Title:		Service Chaining using an Unified Source Routing Instruction
> Document date:	2017-05-10
> Group:		Individual Submission
> Pages:		11
> URL:
> https://www.ietf.org/internet-drafts/draft-xu-mpls-service-chaining-01.txt
> Status:
> https://datatracker.ietf.org/doc/draft-xu-mpls-service-chaining/
> Htmlized:       https://tools.ietf.org/html/draft-xu-mpls-service-chaining-01
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-xu-mpls-service-chaining-01
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-xu-mpls-service-chaining-01
> 
> Abstract:
>    Source Packet Routing in Networking (SPRING) WG is developing an MPLS
>    source routing mechanism.  The MPLS source routing mechanism can be
>    leveraged to realize a unified source routing instruction which works
>    across both IPv4 and IPv6 underlays in addition to the MPLS underlay.
>    This document describes how to leverage the unified source routing
>    instruction to realize a transport-independent service function
>    chaining by encoding the service function path information or service
>    function chain information as an MPLS label stack.
> 
> 
> 
> 
> 
> 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