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

Andrew Qu <andrew.qu@mediatek.com> Fri, 24 July 2015 15:46 UTC

Return-Path: <andrew.qu@mediatek.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 D92961A876E for <mpls@ietfa.amsl.com>; Fri, 24 Jul 2015 08:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.975
X-Spam-Level:
X-Spam-Status: No, score=-0.975 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_42=0.6, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=no
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 jNKUJ0BJB0K5 for <mpls@ietfa.amsl.com>; Fri, 24 Jul 2015 08:46:09 -0700 (PDT)
Received: from mailgw01.mediatek.com (mailgw01.mediatek.com [69.46.227.141]) by ietfa.amsl.com (Postfix) with ESMTP id 39BEB1A874C for <mpls@ietf.org>; Fri, 24 Jul 2015 08:46:09 -0700 (PDT)
X-Listener-Flag: 11101
Received: from mtkcas64.mediatek.inc [(172.29.17.144)] by mailgw01.mediatek.com (envelope-from <andrew.qu@mediatek.com>) (Cellopoint E-mail Firewall v3.9.12 Build 0312 with TLS) with ESMTP id 271999371; Fri, 24 Jul 2015 11:45:56 -0500
Received: from MTKMBS61N1.mediatek.inc ([fe80::2898:86df:e627:42ee]) by MTKCAS64.mediatek.inc ([::1]) with mapi id 14.03.0181.006; Fri, 24 Jul 2015 11:45:56 -0400
From: Andrew Qu <andrew.qu@mediatek.com>
To: Eric C Rosen <erosen@juniper.net>, Loa Andersson <loa@pi.nu>, "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>, Stewart Bryant <stbryant@cisco.com>, "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: AQHQw8aajUti3orAQEqCOvm3DZDbXZ3pFwWwgAB2V4D///4uQIABdXEA///B49A=
Date: Fri, 24 Jul 2015 15:45:55 +0000
Message-ID: <EA360A7AB9D90D4B9E9173B6D27C371EE3F61299@MTKMBS61N1.mediatek.inc>
References: <DB3PR03MB078098C91E8D3C7DCDCCF8C39D840@DB3PR03MB0780.eurprd03.prod.outlook.com> <EA360A7AB9D90D4B9E9173B6D27C371EE3F6038F@MTKMBS61N1.mediatek.inc> <55B11D6D.2040102@pi.nu> <EA360A7AB9D90D4B9E9173B6D27C371EE3F607FB@MTKMBS61N1.mediatek.inc> <55B2552A.80702@juniper.net>
In-Reply-To: <55B2552A.80702@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.17.249]
x-tm-as-product-ver: SMEX-10.2.0.3176-8.000.1202-21698.005
x-tm-as-result: No--41.995700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
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/tGrNkAOomRKLyXIUEnp7H3w5yMI>
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: Fri, 24 Jul 2015 15:46:11 -0000


-----Original Message-----
From: Eric C Rosen [mailto:erosen@juniper.net] 
Sent: Friday, July 24, 2015 5:10 PM
To: Andrew Qu; Loa Andersson; Alexander Vainshtein; Stewart Bryant; Andrew G. Malis; S. Davari
Cc: erosen@juniper.net; mpls@ietf.org
Subject: Re: [mpls] draft-fang-mpls-label-forwarding-no-swap - how much does it really save?

> When standard defines a "no-swap" operation,  ASIC engineer would 
> implement such operation completely differently

Well, this is where we came in.  

[Andrew]  That is right, we are supposed to do some bridging works.  But when RFC is better written, 
	You may be "called" in less and we can spend more time to do greater good.

The RFCs do not dictate how the ASICs should be designed, and your ASIC designers are free to design in whatever way best meets the needs of the systems that are going to use those ASICs.  You can put in any optimizations you think are warranted. 

  If you expect the ASICs to be used in products that will never need to swap label values, never need to push labels, never need to pop labels, then you are free to design the ASICs without any of these features.  If you think that these operations are needed, but that "don't change the label value or the stack size" are the most common operations, you can certainly optimize your design for that case.

But if you think you can get the ASICs designed properly simply by handing the RFCs to the ASIC designers, you may be in for an unpleasant surprise.


[Andrew] I don't know where did you get this idea from,  it is funny that how can you concluded that when I am asking
	better written doc implies that I will simply hand off the work completely.

> Since the label is to be "swap"ed with a new LABEL stack, then the 
> design of SWAPPING need to consider TTL handling such as 1) just 
> decrement of original TTL or 2) using a brand new TTL, such as using 
> local new register stored value to Fill the sawp'ed new label stack.

The TTL handling is exactly the same for both cases.  If you have been telling your ASIC designers something different, you most definitely are in for an unpleasant surprise.

[Andrew] I am using this case to indicate better written doc might help to reduce confusion.  
	This is the human thought process when people read "swap" and "no_swap" and consider how to implement
	Them.  Hence my point of no_swap may be defined to differentiate "swap".  

Thanks,

Andrew



************* 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!