Re: [mpls] mpls-in-udp entropy

Eric Rosen <erosen@cisco.com> Wed, 15 January 2014 16:35 UTC

Return-Path: <erosen@cisco.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 5F9251AE136 for <mpls@ietfa.amsl.com>; Wed, 15 Jan 2014 08:35:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level:
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 L0Gcc1sIA-F4 for <mpls@ietfa.amsl.com>; Wed, 15 Jan 2014 08:35:15 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id B24291AE128 for <mpls@ietf.org>; Wed, 15 Jan 2014 08:35:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=940; q=dns/txt; s=iport; t=1389803703; x=1391013303; h=from:to:cc:subject:in-reply-to:reply-to:date:message-id; bh=3jEl9yjMmyjZbqMtWP+Qafe3IKlVVw/vLR42W0FS3ek=; b=CZCjayvIYN4RH82mFcXqcOEBYBvbBYeBm2FSKkf2FL2MJ5eYYvWf+e5W tnjmJnkGo6ed+xLtUmqj2rPgPDKwjWME+NpPQ123k7d63FrYJMSiYceDV uEezq2ae4YHvqeyynK5AlgS9tzxsphfIOOISpnKvW1mnW0yJfGaVrOdJy 8=;
X-IronPort-AV: E=Sophos;i="4.95,663,1384300800"; d="scan'208";a="103019656"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 15 Jan 2014 16:35:02 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.71.43]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0FGZ01X007549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Jan 2014 16:35:02 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.8/8.13.8) with ESMTP id s0FGZ026006734; Wed, 15 Jan 2014 11:35:00 -0500
From: Eric Rosen <erosen@cisco.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
In-reply-to: Your message of Wed, 15 Jan 2014 11:54:17 +0000. <eaca6d98b34045ba9e08c43417507997@AM3PR03MB532.eurprd03.prod.outlook.com>
Date: Wed, 15 Jan 2014 11:35:00 -0500
Message-ID: <6733.1389803700@erosen-linux>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] mpls-in-udp entropy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: erosen@cisco.com
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, 15 Jan 2014 16:35:16 -0000

(Changed subject line and trimmed cc-list.)

Sasha> I would like to understand whether this protocol can really result in
Sasha> reasonable distribution of traffic. "Reasonable" means that (a) there
Sasha> is sufficient entropy and (b) that the order in specific micro-flows
Sasha> is preserved.

I thought the intention was that the encapsulator would set the UDP source
port based upon the entropy of the packet being encapsulated.  This only
requires that the encapsulator know how to properly apply ECMP to the MPLS
packet that is being encapsulated.  That is, compute the hash that would be
used to apply ECMP to the MPLS packet, and then map from that hash to a UDP
source port.

E.g., two MPLS packets with the same entropy label would get the same UDP
source port, two MPLS packets with no entropy label but containing the same
TCP flow would get the same source port, etc.

Do you think there is a problem here?