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, 27 January 2014 19:30 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 619821A007C; Mon, 27 Jan 2014 11:30:23 -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 yZ3l3WXINhEd; Mon, 27 Jan 2014 11:30:21 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-mba.ke.seacomnet.com [41.87.100.230]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC111A001E; Mon, 27 Jan 2014 11:30:20 -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 1W7rsc-0008LP-8h; Mon, 27 Jan 2014 21:29:58 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: mpls@ietf.org, curtis@ipv6.occnc.com
Date: Mon, 27 Jan 2014 21:29:54 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <201401252047.s0PKlmgS048899@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401252047.s0PKlmgS048899@maildrop2.v6ds.occnc.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1477944.eXu6q19VvR"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Content-Transfer-Encoding: 7bit
Message-Id: <201401272129.55230.mark.tinka@seacom.mu>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, Greg Daley <gdaley@au.logicalis.com>, IETF discussion list <ietf@ietf.org>, Joe Touch <touch@isi.edu>
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, 27 Jan 2014 19:30:23 -0000

On Saturday, January 25, 2014 10:47:48 PM Curtis Villamizar 
wrote:

> Reality check time.
> 
> To get the PW over MPLS drafts past the TSV AD there is a
> SHOULD regarding congestion control.
> 
> AFAIK: No service providers ask for it.  No one
> implements it.  If they did implement it no one would
> deploy it.
> 
> PW over MPLS is generally carrying relatively low volumes
> of high priority traffic.  The TC bits (MPLS flavor of
> Diffserv DSCP) are used to enforce the higher priority. 
> If congestion occurs other traffic on that
> infrastructure (typically plain old Internet) sees loss.
>  That is intended.  This is the reality of how PW over
> MPLS is deployed.
> 
> Anyone who knows of implementation or deployment of
> congestion control for PW over MPLS can correct me.

And this is what I mentioned several weeks ago. As 
operators, we police traffic on ingress and egress (some 
operators shape on egress, but the result is the same), and 
this is how we control admission to the network.

I have never used intrinsic congestion mechanisms in 
protocols (outside of lab fun-time when I'm really bored), 
and don't know anyone that has either. Of course, the risk 
is that router/switch vendors have all sorts of 
implementation as regards policing/shaping; but I can say 
that in the past 7x years or so (and especially in the past 
year for switches), this is reasonably mature, and no vendor 
worth their salt is shipping product that can't police or 
shape properly.

Just one point to make, not all traffic being carried over 
MPLS is "high priority". Some of it really isn't, and is 
treated on a best-effort basis. But, this is all specific to 
operators and their customers. General traffic admission 
rules still apply all the same.

Personally, if there was congestion mechanisms proposed as 
part of the MPLS-in-UDP spec., I would never run them as an 
operator. I'd rely on policing at the edge, as usual.

Cheers,

Mark.