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

Shahram Davari <davari@broadcom.com> Tue, 28 July 2015 16:40 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 53A9B1ACEE9 for <mpls@ietfa.amsl.com>; Tue, 28 Jul 2015 09:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 vf4LRj0m-ZvW for <mpls@ietfa.amsl.com>; Tue, 28 Jul 2015 09:40:24 -0700 (PDT)
Received: from mail-gw3-out.broadcom.com (mail-gw3-out.broadcom.com [216.31.210.64]) by ietfa.amsl.com (Postfix) with ESMTP id DE0A91ACEE8 for <mpls@ietf.org>; Tue, 28 Jul 2015 09:40:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.15,564,1432623600"; d="scan'208";a="70799073"
Received: from irvexchcas06.broadcom.com (HELO IRVEXCHCAS06.corp.ad.broadcom.com) ([10.9.208.53]) by mail-gw3-out.broadcom.com with ESMTP; 28 Jul 2015 09:58:37 -0700
Received: from SJEXCHCAS03.corp.ad.broadcom.com (10.16.203.8) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 28 Jul 2015 09:40:22 -0700
Received: from SJEXCHMB12.corp.ad.broadcom.com ([fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS03.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0235.001; Tue, 28 Jul 2015 09:40:22 -0700
From: Shahram Davari <davari@broadcom.com>
To: Andrew Qu <andrew.qu@mediatek.com>
Thread-Topic: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?
Thread-Index: AQHQxdE8OwfTAAS3/0O9L44IGnUJ+p3quROAgAUiJgCAAEpHgIABDj8AgABBbwD//6dfbA==
Date: Tue, 28 Jul 2015 16:40:21 +0000
Message-ID: <F9B5D5ED-6380-4D82-9A61-589150DFF6D4@broadcom.com>
References: <DB3PR03MB0780AE3E11BEA6B29B81FF5B9D810@DB3PR03MB0780.eurprd03.prod.outlook.com> <EA360A7AB9D90D4B9E9173B6D27C371EE3F60C0D@MTKMBS61N1.mediatek.inc> <55B64078.7030601@cisco.com> <EA360A7AB9D90D4B9E9173B6D27C371EE3F624BE@MTKMBS61N1.mediatek.inc> <55B7617A.90808@cisco.com>, <EA360A7AB9D90D4B9E9173B6D27C371EE3F64252@MTKMBS61N1.mediatek.inc>
In-Reply-To: <EA360A7AB9D90D4B9E9173B6D27C371EE3F64252@MTKMBS61N1.mediatek.inc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/fzsgHhNzQvXueI6mlzgWYLNU75U>
Cc: "mpls@ietf.org" <mpls@ietf.org>, Robert Raszuk <robert@raszuk.net>
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, 28 Jul 2015 16:40:26 -0000

Andrew

Continue operation in segment routing and in HSDN is not global label. Global label means every router knows how to forward a global label. What is the application for a global label and how does each router know how to forward it?

Regards,
Shahram


> On Jul 28, 2015, at 7:58 AM, Andrew Qu <andrew.qu@mediatek.com> wrote:
> 
> Hi Stewart,
> 
> Agreed that SWAP must be kept because MPLS fundamentals can't be broken.
> And I agreed that _if_ there is NO such global label space idea,  no-swap is
> optimization of swap as well. 
> 
> However I don't agree no-swap become an optimization in terms of network
> Behavior when global label idea become a needed thing.
> 
> 
> When global Label introduced, then no_swap is the conceptually right thing for the transition [even
> Local implementation can use swap to achieve, again, per previous conversation,
> the popular wisdom, which I agreed as well,  is that this is local implementation, we should
> not get involved, so we must define no-swap as the new primitive at RFC level]
> 
> 
> So the question really boils down to that do we need global label?
> 
> I believe that is the key thing here.  May be we can put swap/no-swap aside for the moment.
> 
> Thanks,
> 
> Andrew
> 
> 
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com] 
> Sent: Tuesday, July 28, 2015 4:03 AM
> To: Andrew Qu; Alexander Vainshtein; Robert Raszuk; Shahram Davari
> Cc: mpls@ietf.org
> Subject: Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?
> 
>> Adding "NO_SWAP" for new/future generation DEVICE does NOT break 
>> backward capability.
> Andrew
> 
> Existing devices should be assumed to have non-aligned label spaces.
> (there is much empirical evidence to support this position)
> 
> So if you have a no-swap only device between two existing devices you cannot be sure that you can build an LSP.
> 
> A backwards compatible device would therefore need to support swap.
> 
> Once you support swap then no-swap become an optimization.
> 
> - Stewart
> 
> 
> ************* Email Confidentiality Notice ********************
> The information contained in this e-mail message (including any 
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be 
> conveyed only to the designated recipient(s). Any use, dissemination, 
> distribution, printing, retaining or copying of this e-mail (including its 
> attachments) by unintended recipient(s) is strictly prohibited and may 
> be unlawful. If you are not an intended recipient of this e-mail, or believe 
> that you have received this e-mail in error, please notify the sender 
> immediately (by replying to this e-mail), delete any and all copies of 
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. Thank you!
>