IETF Logo Mail Archive

Re: [mpls] Clarification on source label usage

Shahram Davari <davari@broadcom.com> Wed, 19 March 2014 14:17 UTC

Return-Path: <davari@broadcom.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 E4AD31A0779 for <mpls@ietfa.amsl.com>; Wed, 19 Mar 2014 07:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level:
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547] 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 psyJKmuZXKKw for <mpls@ietfa.amsl.com>; Wed, 19 Mar 2014 07:17:09 -0700 (PDT)
Received: from mail-gw2-out.broadcom.com (mail-gw2-out.broadcom.com [216.31.210.63]) by ietfa.amsl.com (Postfix) with ESMTP id 701D91A03FF for <mpls@ietf.org>; Wed, 19 Mar 2014 07:17:09 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.97,686,1389772800"; d="scan'208,217"; a="20193361"
Received: from irvexchcas06.broadcom.com (HELO IRVEXCHCAS06.corp.ad.broadcom.com) ([10.9.208.53]) by mail-gw2-out.broadcom.com with ESMTP; 19 Mar 2014 07:36:07 -0700
Received: from SJEXCHCAS05.corp.ad.broadcom.com (10.16.203.12) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 19 Mar 2014 07:17:00 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ([fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS05.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0174.001; Wed, 19 Mar 2014 07:16:59 -0700
From: Shahram Davari <davari@broadcom.com>
To: Mach Chen <mach.chen@huawei.com>
Thread-Topic: [mpls] Clarification on source label usage
Thread-Index: Ac859wY/HtI+Q5xYT9KoGBS6SQcBeQIu3ZoAADYtZwD//+VjUw==
Date: Wed, 19 Mar 2014 14:16:59 +0000
Message-ID: <C0B15F36-4413-4473-BFDD-51B01D3F4C05@broadcom.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25D98D4C6@SZXEMA510-MBX.china.huawei.com> <CAHcPYOx0zH-2F6Bo-xD11ssq+k=ObST31tK36-PNxj-zRti_8w@mail.gmail.com>, <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25D98ECAE@SZXEMA510-MBX.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25D98ECAE@SZXEMA510-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_C0B15F3644134473BFDD51B01D3F4C05broadcomcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/oRXjUIeS7SBLVBkS1R4Mn1Vj5z8
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Clarification on source label usage
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: Wed, 19 Mar 2014 14:17:15 -0000

Hi

For flow identification. You could use a MEPID inside the OAM message. Why do you need another label?

Regards,
Shahram


On Mar 19, 2014, at 1:52 AM, "Mach Chen" <mach.chen@huawei.com<mailto:mach.chen@huawei.com>> wrote:

Hi Binny,

No,  G-Ach works fine.

The OAM I mentioned mainly refers to the performance measurement(passive) that is listed as the first use case in the draft, the source label is used for flow identification.

Best regards,
Mach

From: Binny Jeshan [mailto:binnyjeshan@gmail.com]
Sent: Tuesday, March 18, 2014 3:01 PM
To: Mach Chen
Cc: mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Clarification on source label usage

Mach,

Do you mean the G-Ach ?

Regards,
Binny.

Aricent

On 18 March 2014 02:51, Mach Chen <mach.chen@huawei.com<mailto:mach.chen@huawei.com>> wrote:
Hi MPLSers,

Yesterday, there are a lots of discussions on source label, thanks for the discussions. I’d like to make a clarification on the usage of source label, I think there may be a  misunderstanding of the usage of source label. The main purpose for MPLS source label is OAM, source label applies to real packets is optional.


Best regards,
Mach



_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls

v2.23.0 | Report a Bug | By Email