Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard

Mark Tinka <mark.tinka@seacom.mu> Mon, 13 January 2014 17:10 UTC

Return-Path: <mark.tinka@seacom.mu>
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 4D9B21AE1AB for <mpls@ietfa.amsl.com>; Mon, 13 Jan 2014 09:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level:
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] 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 078SlJVQOMoL for <mpls@ietfa.amsl.com>; Mon, 13 Jan 2014 09:09:59 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id 646311ADFA3 for <mpls@ietf.org>; Mon, 13 Jan 2014 09:09:57 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W2l0h-0004z8-Ej; Mon, 13 Jan 2014 19:09:11 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: stbryant@cisco.com
Date: Mon, 13 Jan 2014 19:09:00 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <201401130713.13126.mark.tinka@seacom.mu> <52D3B345.4050002@cisco.com>
In-Reply-To: <52D3B345.4050002@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1713835.9GnLoDKGqv"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Content-Transfer-Encoding: 7bit
Message-Id: <201401131909.00922.mark.tinka@seacom.mu>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
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: Mon, 13 Jan 2014 17:10:01 -0000

On Monday, January 13, 2014 11:35:01 AM Stewart Bryant 
wrote:

> It can be arbitrary, but the router designers try rather
> hard to make sure that flows follow the same path. This
> is because the transport protocols in the hosts complain
> if the routers introduce misordering.  Remove that
> constraint and the forwarders become a lot simpler and
> we can do all sorts of anti-PM in the network.

I'm not talking about flow load sharing. I'm talking about 
simple, linear flows.

Mark.