Re: [ovs-dev] [PATCH] ofproto-dpif: Treat zero MPLS post-decrement TTL as invalid.

2013-03-07 Thread Ben Pfaff
On Thu, Mar 07, 2013 at 06:13:06PM +0100, Simon Horman wrote: > On Wed, Mar 06, 2013 at 02:57:59PM -0800, Ben Pfaff wrote: > > RFC 3443 says that an outgoing MPLS TTL of zero is invalid, so we must send > > packets that have such a TTL post-decrement to the controller rather than > > allowing them

Re: [ovs-dev] [PATCH] ofproto-dpif: Treat zero MPLS post-decrement TTL as invalid.

2013-03-07 Thread Simon Horman
On Wed, Mar 06, 2013 at 02:57:59PM -0800, Ben Pfaff wrote: > RFC 3443 says that an outgoing MPLS TTL of zero is invalid, so we must send > packets that have such a TTL post-decrement to the controller rather than > allowing them to continue through the OpenFlow tables. > > Here is the text from RF

[ovs-dev] [PATCH] ofproto-dpif: Treat zero MPLS post-decrement TTL as invalid.

2013-03-06 Thread Ben Pfaff
RFC 3443 says that an outgoing MPLS TTL of zero is invalid, so we must send packets that have such a TTL post-decrement to the controller rather than allowing them to continue through the OpenFlow tables. Here is the text from RFC 3443 that implies this behavior: oTTL: This is the TTL value us