The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2005-May> msg00035



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

RE: Ability to route specific end points based on application

  • From: "M. ELK" <elkou141061@hotmail.com>
  • Date: Sat, 21 May 2005 18:12:48 +0000
  • Resent-Date: Sat, 21 May 2005 14:37:05 -0400
  • X-OriginalArrivalTime: 21 May 2005 18:12:48.0755 (UTC) FILETIME=[B1FD8430:01C55E30]
  • X-Originating-Email: [elkou141061@hotmail.com]
  • X-Originating-IP: [57.250.229.136]
  • X-Scanned-By: MIMEDefang 2.45

Hi Spice

AFAIK

Classification is an Access function :
it could be a deep packet classification (up to layer 7) or simple based on 
Layer3.
Currently their are many external box/appliance which could do such deep 
classification .
One the classification is done it is mapped to one of the service class of 
the network (DSCP values).

On the network :
Say a network do support 4 service class .
between PEx and PEy we could have 4 LSP .Each LSP serve one Service Class .

Traffic classified as say bronze and destination to PEy , will travel over 
the LSP bronze terminated
at PEy ...etc .

So U question could be re-worded about capabilities to provide QOS routing .

For Cisco , it start at 12.0(29s) :
MPLS Traffic Engineering—Class-Based Tunnel Selection
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a00802659b9.html

The problem that deep packet classification is currently provided by sperate 
box and not integrated into the PE (some vendor of PE provide such feature 
but not comparable with the features provided by the appliance) .
My guess that the PE will not scale for several hundred VRF's if it start to 
provide those value added
features (Traffic mang , Deep Packet classification , Acceleration ...etc ). 
May be the answer is to
integrate those functionalities into the CPE router which mean some alliance 
between the provider
of those appliances and the router manufactureres .

N.B: This is nice draft reg conf guideline for definning service class .
       Configuration Guidelines for DiffServ Service Classes
                 draft-baker-diffserv-basic-classes-04

Brgds

>From: Spice Sylvia <falsesylvia@yahoo.co.uk>
>To: mpls-ops@mplsrc.com
>Subject: [MPLS-OPS]: Ability to route specific end points based on 
>application
>Date: Thu, 19 May 2005 12:18:55 +0100 (BST)
>
>Hi,
>
>I would like to know if there is any work being done
>on having the ability to choose specific paths based
>on application.
>
>For example, I have multiple RSVP-TE LSPs terminated
>on my LERs to various different components on the VPN.
>
>Instead of manually configuring ACLs per VRF etc based
>on destination&&application_port pairs, is it possible
>that the desination&&applications are "learnt via a
>specific" LSP themselves.
>
>For example, i would like any LER to use a specific
>LSP to reach all mail servers, and any LER to reach
>all web servers via another specific LSP.
>To futher elaborate the concept, I would also like to
>have the ability to be able to distinguish based on
>"domain prefixes". In other words can one route all
>traffic destined to site1.vpnmember.com via LSP1 etc?
>
>Is there any work being done in this direction?
>Do operators consider this as a viable requirement?
>
>
>
>
>___________________________________________________________
>How much free photo storage do you get? Store your holiday
>snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
>MPLScon 2005 - May 16-19, NYC, NY
>http://www.mplscon.com/

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml