Re: [OSPF] Re: [Fwd: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt]

Curtis Villamizar <curtis@occnc.com> Fri, 01 December 2006 01:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpxKq-0005rv-1E; Thu, 30 Nov 2006 20:37:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpxKo-0005qE-HL; Thu, 30 Nov 2006 20:37:02 -0500
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpxKn-0005O6-5w; Thu, 30 Nov 2006 20:37:02 -0500
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1]) by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id kB11m8o2061362; Thu, 30 Nov 2006 20:48:08 -0500 (EST) (envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200612010148.kB11m8o2061362@workhorse.brookfield.occnc.com>
To: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [OSPF] Re: [Fwd: [mpls] WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt]
In-reply-to: Your message of "Thu, 30 Nov 2006 14:29:49 EST." <4354A088-B93C-457F-93FD-55B8EB4A861A@cisco.com>
Date: Thu, 30 Nov 2006 20:48:08 -0500
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: George Swallow <swallow@cisco.com>, rtg-dir@ietf.org, isis-wg@ietf.org, ospf@ietf.org, David Ward <dward@cisco.com>, Loa Andersson <loa@pi.se>
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

In message <4354A088-B93C-457F-93FD-55B8EB4A861A@cisco.com>
JP Vasseur writes:
>  
> Other attributes such as affinity should be used to not allows 0-bw  
> TE LSP to traverse a specific link. This TLV is only used to report  
> the number of such TE LSPs traversing the link.
>  
> Thanks.
>  
> JP.


The provider already has the necessary tools that can be used to
accomplish this.  If a general purpose tool (attributes and
affinities) is available which accomplishes something a special
purpose tool to accomplish the same thing is not needed.

Such a tool would only be useful if the administration of the MPLS
midpoint (where the attribute is set) had no control over the
administration of the MPLS ingress or a border that is doing route
computation (where the affinity is set).  I don't see any anticipated
real world deployment that would benefit from this.  If you do, then
please explain the deployment scenario.

Curtis

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf