[afnog] Problem bringing up MPLS on disimilar interfaces

[John Tully]

At 04:07 PM 10/3/2008, Mark Tinka wrote:
>On Friday 03 October 2008 18:05:23 John Tully wrote:
>
> > Probably the VPLS pseudowire fragmentation and reassembly
> > (<http://tools.ietf.org/html/rfc4623>RFC 4623) can help
> > when the interfaces don't support the frame size.  This
> > is supported in RouterOS.
>
>This is at a much higher level than the issue the OP was
>facing at the time.
>
>VPLS is an MPLS application. However, basic MPLS forwarding
>needs to work before one can add applications on top of it.

Hello Mark,

You are right.  Though if you only have interfaces that support 1500 
byte MTU, then the RFC4623 implementation will allow you to get 
around all these problems -- considering that the MTU for the MPLS is 
set up properly.

Regards,

John


>With each MPLS label requiring 4 additional bytes, and with
>the increase in label depth as applications such as
>l2vpn's, l3vpn's and Traffic Engineering are added, it's
>vital the core MTU be sufficient enough before customer
>applications such as PWE3 can be brought into play.
>
>Cheers,
>
>Mark.
>
>
>_______________________________________________
>afnog mailing list
>http://afnog.org/mailman/listinfo/afnog