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

Mark Tinka <mark.tinka@seacom.mu> Tue, 14 January 2014 12:32 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 7ABFA1AE0A8 for <mpls@ietfa.amsl.com>; Tue, 14 Jan 2014 04:32: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 Pmjx9Vr0Igoa for <mpls@ietfa.amsl.com>; Tue, 14 Jan 2014 04:32:21 -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 09A151AE0BC for <mpls@ietf.org>; Tue, 14 Jan 2014 04:32:17 -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 1W3396-0008Te-Fq; Tue, 14 Jan 2014 14:31:04 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: curtis@ipv6.occnc.com
Date: Tue, 14 Jan 2014 14:31:00 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <201401132004.s0DK4DFO080786@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401132004.s0DK4DFO080786@maildrop2.v6ds.occnc.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart66180887.yt9NZmRRKX"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Content-Transfer-Encoding: 7bit
Message-Id: <201401141431.03808.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: Tue, 14 Jan 2014 12:32:23 -0000

On Monday, January 13, 2014 10:04:13 PM Curtis Villamizar 
wrote:

> Perhaps someone needs to explain to you what a FEC is and
> how MPLS traffic is routed in most LDP networks.

Thanks for the 101, Curtis, but I think I'm doing alright 
:-).

Again, my input is rooted in operational situations that 
I've experienced, present and past (I'm neither a vendor nor 
a software developer):

J's implementation of LDP treats LDP much like a routing 
protocol (unlike C's implementation).

In such cases, LDP-derived routing has a discrete routing 
table different from the global routing table. Under certain 
conditions (design or code), there could be a mis-alignment 
between what LDP thinks is the best path vs. what the IGP 
thinks is the best path.

A knob exists within J's LDP implementation to synchronize 
LDP and the IGP (i.e., the LDP and IGP metric is always the 
same). Such a knob does not exist (AFAIK) with C because C 
don't treat LDP like a routing protocol. Without this LDP 
knob enabled in J's implementation (which is the default 
case), LDP routes always retain a metric of 1, regardless of 
the route and regardless of what the IGP metric is.

I concede that this case may not be the norm when taking all 
vendor implementations into account, but then again, my 
experience is restricted to C and J.

Mark.