From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "mark.tinka@seacom.mu" <mark.tinka@seacom.mu>,
 "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating
 MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDi/NnXFwG1Tc20SQPsVMzJPOgJp+RLFAgAMa0wCAAIA0EA==
Date: Mon, 13 Jan 2014 01:30:04 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B744E67@eusaamb103.ericsson.se>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com>
 <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
 <7347100B5761DC41A166AC17F22DF1121B7447E4@eusaamb103.ericsson.se>
 <201401121444.31194.mark.tinka@seacom.mu>
In-Reply-To: <201401121444.31194.mark.tinka@seacom.mu>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating
 MPLS in UDP) to Proposed Standard
Precedence: list

Hi Mark,
if by "provisioning" you mean "mapped to", "assigned", then what about IP a=
ddresses? Ain't they pre-provisioned as well? Or these are native propertie=
s of NEs?

	Regards,
		Greg

-----Original Message-----
From: Mark Tinka [mailto:mark.tinka@seacom.mu]=20
Sent: Sunday, January 12, 2014 4:45 AM
To: mpls@ietf.org
Cc: Gregory Mirsky; Eggert, Lars; Joel Halpern; IETF
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

On Friday, January 10, 2014 08:24:02 PM Gregory Mirsky
wrote:

> Hi Lars,
> I think that " The whole point of running MPLS is to create networks=20
> in which paths are provisionable, so this is usually not an issue." is=20
> only partially correct. LDP-based MPLS network is not provisionable=20
> and LSPs follow IP best route selection. Explicit signaling of LSP is=20
> achievable in (G)MPLS by using RSVP(-TE) signaling.

Greg, I think we can delineate provisioning from whether it is dynamic or e=
xplicit.

MPLS LSP's are all pre-provisioned, because of the FEC's created. Whether t=
hose FEC's are dynamically or explicitly provisioned is a separate issue.

Mark.