[mpls] The concept of MPLS source labels
Xuxiaohu <xuxiaohu@huawei.com> Wed, 31 July 2013 08:25 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 153AC21F9C52 for <mpls@ietfa.amsl.com>; Wed, 31 Jul 2013 01:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.692
X-Spam-Level:
X-Spam-Status: No, score=-4.692 tagged_above=-999 required=5 tests=[AWL=1.907, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36h+UaOSc5lZ for <mpls@ietfa.amsl.com>; Wed, 31 Jul 2013 01:25:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F302621F9223 for <mpls@ietf.org>; Wed, 31 Jul 2013 01:24:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATY58882; Wed, 31 Jul 2013 08:24:48 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 31 Jul 2013 09:24:13 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 31 Jul 2013 09:24:23 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.175]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Wed, 31 Jul 2013 16:24:16 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: The concept of MPLS source labels
Thread-Index: AQHOjcdY7V80ARCTM0S4TEL9yXX/yA==
Date: Wed, 31 Jul 2013 08:24:16 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081DAA35@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.47.150.91]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [mpls] The concept of MPLS source labels
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 31 Jul 2013 08:25:42 -0000
Hi all, As I said at the mic, the concept of source labels has been successfully used in the ATM MPLS paradigm ten years before, which is contained in the VCI field so as to address the ATM cell merge issue. Hence it seems safe to say that the concept of source labels is workable. Identifying the source of the received MPLS packet is valuable for the current non-ATM MPLS paragigm as well. Besides the MPLS performance measurement use case as mentioned in the draft, it is useful for the multicast VPN service as well. AFAIK, one of the major reason that LDP-based MP2P LSPs can not be used in the ingress replicaiton mode of multicast VPN service is it's hard for the egress PE to identify the ingress PE of a given received packet for the multicast RPF check purpose. Best regards, Xiaohu
- [mpls] The concept of MPLS source labels Xuxiaohu
- Re: [mpls] The concept of MPLS source labels Jeffrey (Zhaohui) Zhang
- [mpls] 答复: The concept of MPLS source labels Xuxiaohu
- Re: [mpls] The concept of MPLS source labels Jeffrey (Zhaohui) Zhang