FAQ.md: Correct claims about MPLS.

An examination of the source code and the tests shows that the FAQ claimed
more for version 2.3 than was really in there.

Reported-by: null pointer <null.pointer.boom@gmail.com>
Signed-off-by: Ben Pfaff <blp@nicira.com>
Acked-by: Pravin B Shelar <pshelar@nicira.com>

diff --git a/FAQ.md b/FAQ.md
index be2c6ab..458e07a 100644 (file)
--- a/FAQ.md
+++ b/FAQ.md
@@ -1257,14 +1257,16 @@ A: Before version 1.11, Open vSwitch did not support MPLS.  That is,
    packet.  Kernel datapath support is unchanged from earlier
    versions.
 
-   Open vSwitch version 2.3 can match, push, or pop up to 3 MPLS
-   labels.  Looking past MPLS labels into the encapsulated packet will
-   still be unsupported.  Both userspace and kernel datapaths will be
-   supported, but MPLS processing always happens in userspace either
-   way, so kernel datapath performance will be disappointing.
-
-   Open vSwitch version 2.4 will have kernel support for MPLS,
-   yielding improved performance.
+   Open vSwitch version 2.3 can match, push, or pop a single MPLS
+   label and look past the MPLS label into the encapsulated packet.
+   Both userspace and kernel datapaths will be supported, but MPLS
+   processing always happens in userspace either way, so kernel
+   datapath performance will be disappointing.
+
+   Open vSwitch version 2.4 can match, push, or pop up to 3 MPLS
+   labels and look past the MPLS label into the encapsulated packet.
+   It will have kernel support for MPLS, yielding improved
+   performance.
 
 ### Q: I'm getting "error type 45250 code 0".  What's that?