The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: RFC 3032 : Determining the L3 header at egress.
Doug, No this is just Alex typo. He meant to say L2 Transport over MPLS and not over MPLS/VPNs. You are correct over MPLS-VPNs you can only carry ipv4 unicast at the present shipping code. Extensions to carry ipv6 as well as mulitcast are comming shortly. R. > Doug Stanfield wrote: > > Alexander, > > In your response to another thread, "RFC 3032 : Determining the L3 header at > egress", you said the following: > > 3) L2 transport over MPLS/VPN > > By creating 2 tunnels between ingress and egress and > > exchanging labels via > > LDP/TDP between the non-adjacent head and tail-nodes of the > > tunnel, the > > correspondence between packettype/destination and label is > > given. ( this is > > true for any L2 over MPLS) > > Somehow in my reading I hadn't got that L2 over MPLS/VPN was particularly > easy if at all possible. Your statement implies both. Do you have pointers > to further reading or links to Cisco configs (frame based) or even advice on > how I might proceed to test and implement something? > > Thanks, > > -Doug- > > ------- > 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
|
|