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

"Andrew G. Malis" <agmalis@gmail.com> Tue, 28 July 2015 11:50 UTC

Return-Path: <agmalis@gmail.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 6F3FC1A89AB for <mpls@ietfa.amsl.com>; Tue, 28 Jul 2015 04:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 cj9IIRf40kpP for <mpls@ietfa.amsl.com>; Tue, 28 Jul 2015 04:50:00 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E809E1A8863 for <mpls@ietf.org>; Tue, 28 Jul 2015 04:49:59 -0700 (PDT)
Received: by wibxm9 with SMTP id xm9so153368014wib.0 for <mpls@ietf.org>; Tue, 28 Jul 2015 04:49:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8N6Fapba64HjDlEZnGyOBxmNhkmCZSJlAl464M+50xQ=; b=HrBliE3ikoeeK0tknhiSmhahkm3ZX3oUPuVThRWJhttbLjDtuVbmJldbCJwxZgOaRL D04KPlmER7J72hADkIUDsZp1bXUnHPQHGcasl7OgbGvsflzwlRKtENoQbP71CiLM/nAY voplg2PmxpMZSESJ6qAVc8toqOpzVn3/kB1o9CR1dZ6JtsmPPgXok7M3aUHONUOa81+F /kAl727MaZrRnqawDx30+mRmkgKdWRJ5snAxBmQ4wo2to5GsQhkyiSmkiFICTeEvbCC6 E5MnqQaEHAMltnEiq4y1mRkdLfqtp5PKAznIpEJb4zjjp6/12sUVaYDt0s07aYlLS67k bkrQ==
X-Received: by 10.180.182.40 with SMTP id eb8mr32169675wic.47.1438084198696; Tue, 28 Jul 2015 04:49:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.87.18 with HTTP; Tue, 28 Jul 2015 04:49:38 -0700 (PDT)
In-Reply-To: <55B64078.7030601@cisco.com>
References: <DB3PR03MB0780AE3E11BEA6B29B81FF5B9D810@DB3PR03MB0780.eurprd03.prod.outlook.com> <EA360A7AB9D90D4B9E9173B6D27C371EE3F60C0D@MTKMBS61N1.mediatek.inc> <55B64078.7030601@cisco.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 28 Jul 2015 07:49:38 -0400
Message-ID: <CAA=duU35ZvDAvxZ7kGVCVfHyfCUKWd2GFQa6uCb-C7SfE7giAg@mail.gmail.com>
To: Stewart Bryant <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b66f46fd20b9a051bee1197
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/eWCx3o09BACZnFYrAMVb6hZ2-l4>
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 11:50:01 -0000

Stewart has it right:

On Mon, Jul 27, 2015 at 10:30 AM, Stewart Bryant <stbryant@cisco.com> wrote:

> If that is not a requirement in your world, then I suggest
> that you get a new ethertype and call it MPLS2
>

This is enough of a deviation from the millions of devices in the installed
base that you can just get a new Ethertype and optimize to your heart's
content. You're going to need new ASICs anyway, may as well go all the way.
This also removes the need to do any sort of peer capability negotiation
for backwards compatibility, and gives you the freedom to produce devices
that ONLY support MPLS2 if you so desire, to have a less expensive and
optimized data center solution. I would support standardization in this
case.

Cheers,
Andy