[mpls] Clarification on source label

Mach Chen <mach.chen@huawei.com> Tue, 11 March 2014 02:26 UTC

Return-Path: <mach.chen@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 0AFF51A06E9 for <mpls@ietfa.amsl.com>; Mon, 10 Mar 2014 19:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] 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 gTwFzI7aVyat for <mpls@ietfa.amsl.com>; Mon, 10 Mar 2014 19:26:09 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A66D01A06E8 for <mpls@ietf.org>; Mon, 10 Mar 2014 19:26:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBY11931; Tue, 11 Mar 2014 02:26:02 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 02:25:14 +0000
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 11 Mar 2014 02:26:02 +0000
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.94]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Tue, 11 Mar 2014 10:25:56 +0800
From: Mach Chen <mach.chen@huawei.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: Clarification on source label
Thread-Index: Ac880Trpsvr7vpPcSMWcK9MZDdVgUA==
Date: Tue, 11 Mar 2014 02:25:55 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25D988C4D@SZXEMA510-MBX.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/4GNwEBi3dlJ0CW1liPM1YW7WXto
Subject: [mpls] Clarification on source label
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: <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: Tue, 11 Mar 2014 02:26:10 -0000

Hi,

During the second MPLS session last week, there are lot of discussions on the source label, thanks for the discussions!

Regarding to the usage of source label, there may be some misunderstanding. The main purpose of source label is for OAM, although the source label can be applied to real packets, but it's optional, it depends on how you use it.

In addition, regarding to the depth of label stack, IMHO, this is proved that is not an real issue for the new generation hardware (chips and NPs), the depth is only related the need. 


Best regards,
Mach