documentation: bring vxlan documentation more up-to-date

A few things have changed since the previous version of the vxlan
documentation was written, so update it and correct some grammar and
such while we are at it.

Signed-off-by: Rick Jones <rick.jones2@hp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

Documentation/networking/vxlan.txt

@@ -1,32 +1,36 @@
 Virtual eXtensible Local Area Networking documentation
 ======================================================
 
-The VXLAN protocol is a tunnelling protocol that is designed to
+The VXLAN protocol is a tunnelling protocol designed to solve the
-solve the problem of limited number of available VLAN's (4096).
+problem of limited VLAN IDs (4096) in IEEE 802.1q.  With VXLAN the
-With VXLAN identifier is expanded to 24 bits.
+size of the identifier is expanded to 24 bits (16777216).
 
-It is a draft RFC standard, that is implemented by Cisco Nexus,
+VXLAN is described by IETF RFC 7348, and has been implemented by a
-Vmware and Brocade. The protocol runs over UDP using a single
+number of vendors.  The protocol runs over UDP using a single
-destination port (still not standardized by IANA).
+destination port.  This document describes the Linux kernel tunnel
-This document describes the Linux kernel tunnel device,
+device, there is also a separate implementation of VXLAN for
-there is also an implantation of VXLAN for Openvswitch.
+Openvswitch.
 
-Unlike most tunnels, a VXLAN is a 1 to N network, not just point
+Unlike most tunnels, a VXLAN is a 1 to N network, not just point to
-to point. A VXLAN device can either dynamically learn the IP address
+point. A VXLAN device can learn the IP address of the other endpoint
-of the other end, in a manner similar to a learning bridge, or the
+either dynamically in a manner similar to a learning bridge, or make
-forwarding entries can be configured statically.
+use of statically-configured forwarding entries.
 
-The management of vxlan is done in a similar fashion to it's
+The management of vxlan is done in a manner similar to its two closest
-too closest neighbors GRE and VLAN. Configuring VXLAN requires
+neighbors GRE and VLAN. Configuring VXLAN requires the version of
-the version of iproute2 that matches the kernel release
+iproute2 that matches the kernel release where VXLAN was first merged
-where VXLAN was first merged upstream.
+upstream.
 
 1. Create vxlan device
-  # ip li add vxlan0 type vxlan id 42 group 239.1.1.1 dev eth1
+ # ip link add vxlan0 type vxlan id 42 group 239.1.1.1 dev eth1 dstport 4789
 
-This creates a new device (vxlan0). The device uses the
+This creates a new device named vxlan0.  The device uses the multicast
-the multicast group 239.1.1.1 over eth1 to handle packets where
+group 239.1.1.1 over eth1 to handle traffic for which there is no
-no entry is in the forwarding table.
+entry in the forwarding table.  The destination port number is set to
+the IANA-assigned value of 4789.  The Linux implementation of VXLAN
+pre-dates the IANA's selection of a standard destination port number
+and uses the Linux-selected value by default to maintain backwards
+compatibility.
 
 2. Delete vxlan device
   # ip link delete vxlan0