IETF Logo Mail Archive

Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 21 July 2015 08:26 UTC

Return-Path: <Alexander.Vainshtein@ecitele.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 209391B2A3A for <mpls@ietfa.amsl.com>; Tue, 21 Jul 2015 01:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, 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 RWCrhwWle5YO for <mpls@ietfa.amsl.com>; Tue, 21 Jul 2015 01:26:35 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0784.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::784]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E9861B2A3D for <mpls@ietf.org>; Tue, 21 Jul 2015 01:26:34 -0700 (PDT)
Received: from DB3PR03MB0780.eurprd03.prod.outlook.com (10.161.55.12) by DB3PR03MB0778.eurprd03.prod.outlook.com (10.161.54.28) with Microsoft SMTP Server (TLS) id 15.1.219.17; Tue, 21 Jul 2015 08:26:13 +0000
Received: from DB3PR03MB0780.eurprd03.prod.outlook.com ([10.161.55.12]) by DB3PR03MB0780.eurprd03.prod.outlook.com ([10.161.55.12]) with mapi id 15.01.0219.018; Tue, 21 Jul 2015 08:26:13 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "S. Davari" <davarish@yahoo.com>
Thread-Topic: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?
Thread-Index: AQHQwwSARLWhMNTKB0OPv6fwBySQ6Z3ki/OAgAAOioCAAA1IgIAACkOAgAACaoCAANy6AIAABbLQ
Date: Tue, 21 Jul 2015 08:26:13 +0000
Message-ID: <DB3PR03MB0780B923E92B93CDA49C3EBC9D840@DB3PR03MB0780.eurprd03.prod.outlook.com>
References: <55AD19F2.1010206@cisco.com> <4A6CE49E6084B141B15C0713B8993F2831F73A21@SJEXCHMB12.corp.ad.broadcom.com> <55AD2DAD.4060908@juniper.net> <4A6CE49E6084B141B15C0713B8993F2831F73F3A@SJEXCHMB12.corp.ad.broadcom.com> <55AD416D.2020306@juniper.net> <8EF0C870-0688-49BB-A537-B0EF28EE93D3@yahoo.com> <CAA=duU2KYgvV8VMcJKLRpfrDzDynUhzu=8FrFYpKYY7MPqMa_w@mail.gmail.com>
In-Reply-To: <CAA=duU2KYgvV8VMcJKLRpfrDzDynUhzu=8FrFYpKYY7MPqMa_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-originating-ip: [109.67.54.34]
x-microsoft-exchange-diagnostics: 1; DB3PR03MB0778; 5:IBe027Ox0Q79oXmKfRbyTjJ50RGQz9YXVszMRiCzNgz7G8riagClGNqQr0Gg1hBszK0mDUJIqmcRQ+iFfx9Oh+Tydl5kNDTPFDOaozWn0sukMFTmcsC2FhnueiGII/xvBvpg6itwu4N5QH4hrVASlw==; 24:oF5CE8o5I985sALK9hGIAxedPw3NJg2DCL9d0gX1WiSDNarOnfVfVRseUo3Yyqvk9jy/wTgTRYJswR2ProOrjxSDVWBU1KCTN3fMedomXP0=; 20:v9081OtXzfmgTIrGnvXD+OHb54EwOHHNxFS6a64PVe1fangjAJ3k6vM13vk/53HKciwIs4hj4DhMDRRboGKQ7A==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB3PR03MB0778;
db3pr03mb0778: X-MS-Exchange-Organization-RulesExecuted
x-microsoft-antispam-prvs: <DB3PR03MB07784FB824843940626485549D840@DB3PR03MB0778.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:DB3PR03MB0778; BCL:0; PCL:0; RULEID:; SRVR:DB3PR03MB0778;
x-forefront-prvs: 0644578634
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(252514010)(24454002)(479174004)(377454003)(54356999)(74316001)(106116001)(92566002)(76176999)(5002640100001)(2950100001)(2900100001)(230783001)(76576001)(5001770100001)(50986999)(77096005)(122556002)(15975445007)(2521001)(102836002)(40100003)(19609705001)(87936001)(46102003)(19300405004)(2656002)(189998001)(66066001)(62966003)(5001960100002)(19580405001)(19625215002)(77156002)(19617315012)(33656002)(86362001)(5003600100002)(93886004)(19580395003)(16236675004); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR03MB0778; H:DB3PR03MB0780.eurprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB3PR03MB0780B923E92B93CDA49C3EBC9D840DB3PR03MB0780eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jul 2015 08:26:13.4733 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR03MB0778
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/2j6Vfh_IZYCLoWZ4ICzcueBU160>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?
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: <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: Tue, 21 Jul 2015 08:26:37 -0000

Andy, Shahram and all,

I may have missed something, but I do not understand why this draft is needed even as an Informational since, as Eric has noticed, it describes a local optimization trick.


Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Tuesday, July 21, 2015 11:03 AM
To: S. Davari
Cc: mpls@ietf.org
Subject: Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?

As there are no architectural or protocol changes or IANA considerations, this draft should be informational if it goes forward (it currently says "standards track").

Cheers,
Andy


On Mon, Jul 20, 2015 at 8:52 PM, S. Davari <davarish@yahoo.com<mailto:davarish@yahoo.com>> wrote:
Eric

I agree no standard change is required since this is a local optimization issue.

Regards,
Shahram


> On Jul 20, 2015, at 11:43 AM, Eric C Rosen <erosen@juniper.net<mailto:erosen@juniper.net>> wrote:
>
>> On 7/20/2015 2:07 PM, Shahram Davari wrote:
>> The new swapped labels (The outgoing  label that replaces the
>> incoming label) need to be stored in a table. Using this draft
>> reduces the number of swapped labels that needs to be stored,
>> regardless of  implementation. Don't you agree?
>
> No.  If you notice that the incoming label needs to be 'replaced' by an outgoing label of the same value, you could just make the rewrite string shorter, so it won't overwrite the top label on the stack.  This seems to be what the draft suggests, but it could be done as an optimization for the particular case where the incoming and outgoing labels have the same value.  You could do this today, as a local implementation optimization. There doesn't seem to be any interop issue or any change to the data plane semantics.
>
>> It also reduces the configuration and management of the new swapped labels.
>
> We're not discussing whether there are any advantages to the use of domain-wide labels.  We're discussing whether the use of domain-wide labels requires a change in the forwarding plane architecture.  I just don't see that it does.
>
> _______________________________________________
> 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