[j-nsp] MPLS and QoS at penultimate hop ?

[Saku Ytti]

On (2013-02-05 11:30 +0100), Daniel Roesen wrote:
 
> > Classification on EXP may be more accurate: as there are no "payload
> > type" field in MPLS header, this router just can't know that packet's
> > content is IPv4).
> 
> MPCs (Trio) uses a heuristic to determine MPLS payload for
> load-balancing purposes. If the first payload octet is 0x04, IPv4 is
> assumed, for 0x06, IPv6 is assumed. Otherwise, it will be treated as
> ethernet frame, IIRC.

It would be quite easy to solve this issue

0x8847 == mpls, unspecified
0xnew1 == mpls, ip
0xnew2 == mpls, ethernet

-- 
  ++ytti