The MPLS-OPS Archive

[Robert Raszuk <raszuk@cisco.com>]

Saqib, 

I don't think that the approach of application specific VPNs even makes
sense. L2 or L3 VPNs provide you mainly with connectivity (routing
information distribution). 

For application level scheduling guarantees you should be using the
right QoS tools available both in each hop as well on ingress. That way
you can classify very important traffic (VoIP for example) to be taking
the dedicated LLQ resources at each hop. I don't know how building VPNs
(routing information disgtribution) may replace basic qos engineering in
your network. 

Also the existance or not of NMPLS-BGP VPNs is orthogonal to the
possibiliy of using more complex QoS tools like diffserv aware TE which
can be a perfect complement to the VPNs itself, but not a reason for it.

R.

> Saqib Jang wrote:
> 
> As I understand it, MPLS/BGP VPNs (per RFC2547) enable site-to-site
> VPNs at for all traffic flowing between sites in the VPN. Can MPLS
> VPNs handle the requirement of creation of VPNs among sites for
> specific types of traffic (say e.g. VoIP traffic)? Would this require
> a VoIP swtich (other type of allication-aware switches) to be an MPLS edge
> router or can a "one size fits all" approach work here (i.e. can standard
> MPLS-aware IP routers create application-specific MPLS VPNs). I'm looking
> for technical rationale (i.e. not company/product positioning) here.
> 
> TIA,
> Saqib
> 
> Saqib Jang
> Margalla Communications, Inc.
> 3301 El Camino Real, Suite 220
> Atherton, CA 94027
> Ph: 650 298 8462
> Fax: 650 851 1613
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

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