Re: [mpls] mpls-in-udp entropy

Curtis Villamizar <curtis@ipv6.occnc.com> Wed, 15 January 2014 20:56 UTC

Return-Path: <curtis@ipv6.occnc.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 B73261AE248 for <mpls@ietfa.amsl.com>; Wed, 15 Jan 2014 12:56:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, 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 XThJPZZdouPX for <mpls@ietfa.amsl.com>; Wed, 15 Jan 2014 12:56:29 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id E7FED1AE0D5 for <mpls@ietf.org>; Wed, 15 Jan 2014 12:56:28 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FKuBNT022977; Wed, 15 Jan 2014 15:56:11 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401152056.s0FKuBNT022977@maildrop2.v6ds.occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Wed, 15 Jan 2014 19:44:53 +0000." <5b0765246d204750a50e1aad52a3b72e@AM3PR03MB532.eurprd03.prod.outlook.com>
Date: Wed, 15 Jan 2014 15:56:11 -0500
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: curtis@ipv6.occnc.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 20:56:30 -0000

In message <5b0765246d204750a50e1aad52a3b72e@AM3PR03MB532.eurprd03.prod.outlook.com>
Alexander Vainshtein writes:
 
> Eric,
> Lots of thanks for a prompt and highly informative response.
>  
> I have been actually thinking about the same thing, namely that the entropy port should be the result of some hash over the label stack.  
>  
> If this is indeed the intention of the authors, it would make sense (at least, from my point of view) of saying so in the draft. There is no need to make such a statement normative, but it would really help the readers (both implementors and operators) to understand what it is about.
>  
> Regards,
>      Sasha 

Avoiding the lower 8K of the port number space might not be a bad idea
to avoid a return port being a WKP including the non-root WKP space
used by X-Windows and other things.

Curtis


> ________________________________________
> From: Eric Rosen <erosen@cisco.com>
> Sent: Wednesday, January 15, 2014 6:35 PM
> To: Alexander Vainshtein
> Cc: mpls@ietf.org
> Subject: Re: mpls-in-udp entropy
>  
> (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?
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls