Re: [mpls] mpls-in-udp entropy
Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 16 January 2014 05:35 UTC
Return-Path: <Alexander.Vainshtein@ecitele.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 778C61AE4C7 for <mpls@ietfa.amsl.com>; Wed, 15 Jan 2014 21:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 e4omjf3WsoF6 for <mpls@ietfa.amsl.com>; Wed, 15 Jan 2014 21:35:53 -0800 (PST)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0080.outbound.protection.outlook.com [213.199.154.80]) by ietfa.amsl.com (Postfix) with ESMTP id D3CF21AE4BE for <mpls@ietf.org>; Wed, 15 Jan 2014 21:35:52 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB531.eurprd03.prod.outlook.com (10.242.109.155) with Microsoft SMTP Server (TLS) id 15.0.851.11; Thu, 16 Jan 2014 05:35:39 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0851.011; Thu, 16 Jan 2014 05:35:39 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Thread-Topic: [mpls] mpls-in-udp entropy
Thread-Index: AQHPEjRCieRBwKl/XESIAXm8KkwTF5qG07e6
Date: Thu, 16 Jan 2014 05:35:38 +0000
Message-ID: <75996b50f08c46b5b3809ee628dadcba@AM3PR03MB532.eurprd03.prod.outlook.com>
References: Your message of "Wed, 15 Jan 2014 19:44:53 +0000." <5b0765246d204750a50e1aad52a3b72e@AM3PR03MB532.eurprd03.prod.outlook.com>, <201401152056.s0FKuBNT022977@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401152056.s0FKuBNT022977@maildrop2.v6ds.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [109.66.126.123]
x-forefront-prvs: 0093C80C01
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(779001)(689001)(679001)(51704005)(189002)(199002)(377454003)(50986001)(46102001)(54356001)(53806001)(79102001)(49866001)(56776001)(76786001)(54316002)(76796001)(63696002)(47976001)(83322001)(19580395003)(80976001)(19580405001)(47736001)(33646001)(93136001)(81816001)(59766001)(92566001)(77982001)(76482001)(76576001)(87936001)(31966008)(74876001)(81686001)(4396001)(80022001)(47446002)(90146001)(74706001)(56816005)(15975445006)(81342001)(51856001)(2656002)(65816001)(74662001)(66066001)(85306002)(69226001)(87266001)(81542001)(83072002)(74502001)(74366001)(85852003)(74316001)(93516002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB531; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:109.66.126.123; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
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
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: Thu, 16 Jan 2014 05:35:56 -0000
Curtis, IMHO and FWIW it is preferable to allocate the entropy port from the Dynamic/Private space. 14K values should suffice for any reasonable ECMP scenarios. My 2c, Sasha ________________________________________ From: Curtis Villamizar <curtis@ipv6.occnc.com> Sent: Wednesday, January 15, 2014 10:56 PM To: Alexander Vainshtein Cc: erosen@cisco.com; mpls@ietf.org Subject: Re: [mpls] mpls-in-udp entropy 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
- [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp … l.wood
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Randy Bush
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… l.wood
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Adrian Farrel
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Stewart Bryant
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Mark Tinka
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Stewart Bryant
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Mark Tinka
- [mpls] misdelivered mpls packets - Was: Re: draft… Loa Andersson
- Re: [mpls] misdelivered mpls packets - Was: Re: d… Gregory Mirsky
- Re: [mpls] misdelivered mpls packets - Was: Re: d… Huub van Helvoort
- Re: [mpls] misdelivered mpls packets - Was: Re: d… Mark Tinka
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Andrew G. Malis
- Re: [mpls] misdelivered mpls packets - Was: Re: d… David Allan I
- Re: [mpls] misdelivered mpls packets - Was: Re: d… Curtis Villamizar
- Re: [mpls] misdelivered mpls packets - Was: Re: d… l.wood
- [mpls] OT was Re: draft-ietf-mpls-in-udp was RE: … Curtis Villamizar
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… l.wood
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Mark Tinka
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Curtis Villamizar
- Re: [mpls] OT was Re: draft-ietf-mpls-in-udp was … Mark Tinka
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… l.wood
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… l.wood
- Re: [mpls] [lisp] draft-ietf-mpls-in-udp was RE: … l.wood
- Re: [mpls] OT (was Re: draft-ietf-mpls-in-udp was… l.wood
- Re: [mpls] [lisp] draft-ietf-mpls-in-udp was RE: … Curtis Villamizar
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Wesley Eddy
- Re: [mpls] [lisp] draft-ietf-mpls-in-udp was RE: … Dino Farinacci
- Re: [mpls] [lisp] draft-ietf-mpls-in-udp was RE: … gorry
- Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-… Stewart Bryant
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Curtis Villamizar
- Re: [mpls] OT was Re: draft-ietf-mpls-in-udp was … Curtis Villamizar
- Re: [mpls] OT was Re: draft-ietf-mpls-in-udp was … Mark Tinka
- [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE:… Curtis Villamizar
- Re: [mpls] OT (was Re: draft-ietf-mpls-in-udp was… Stewart Bryant
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Stewart Bryant
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… l.wood
- Re: [mpls] OT (was Re: draft-ietf-mpls-in-udp was… Curtis Villamizar
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… l.wood
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Stewart Bryant
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Randy Bush
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Stewart Bryant
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Alexander Vainshtein
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… l.wood
- Re: [mpls] mpls-in-udp entropy Eric Rosen
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Curtis Villamizar
- Re: [mpls] mpls-in-udp entropy Alexander Vainshtein
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Curtis Villamizar
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Curtis Villamizar
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… gorry
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Curtis Villamizar
- Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in… Curtis Villamizar
- Re: [mpls] mpls-in-udp entropy Curtis Villamizar
- Re: [mpls] mpls-in-udp entropy Alexander Vainshtein
- Re: [mpls] [tsvwg] [lisp] draft-ietf-mpls-in-udp … Curtis Villamizar
- Re: [mpls] mpls-in-udp entropy Curtis Villamizar
- Re: [mpls] [tsvwg] [lisp] draft-ietf-mpls-in-udp … Saku Ytti
- Re: [mpls] mpls-in-udp entropy Alexander Vainshtein
- Re: [mpls] mpls-in-udp entropy Curtis Villamizar
- Re: [mpls] [tsvwg] [lisp] draft-ietf-mpls-in-udp … Saku Ytti
- Re: [mpls] mpls-in-udp entropy Alexander Vainshtein