The MPLS-OPS Archive

["Torsten Mueller" <Torsten.Mueller@marconi.com>]

Hallo,

i would like to implement a VPN (mutlisite connectivity) using an ethernet
interface between customer and service provider (Gigabit Ethernet or Fast
Ethernet).
The customer equipment is a router.
The VPN is realized using MPLS. At the interface between customer
and service provider, the different VPN locations are discriminated by
the MPLS label.
The service providers equipment provides only MPLS core functionality
(at least the PE dataplane is not IP-aware, static configuration of MPLS
labels should be possible, which means the LSP through the service
providers
MPLS network is assumed to be established by traffic engineering).

------  label          ------
| CE |---|----------| PE |---- MPLS network
------      /            ------
 edge     /         core device
         Ethernet

My questions:
- Which routers support such a scenario?
   The mapping between destination VPN (next-hop IP router) and
   MPLS label must be configurable (static).
- How can the routers in such a scenario learn each other? The transport
   service provider creates a static MPLS path between 2 locations.
   Is it possible for a router to treat an MPLS label as port, so that it
   can learn the adjacent router connected to this port via the routing
protocols?
   (assuming that the same labels are used in both directions)
- Does such a scenario make sense of are there other (better)
alternatives.

I would appreciate any comment.

Thanks,
Torsten


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