ovsdb: Document in SPECS how OVS uses JSON.

CC: Jeremy Stribling <strib@nicira.com>

diff --git a/ovsdb/SPECS b/ovsdb/SPECS
index cbd69defc3f62fc1b929815f1357ef9fb90f995f..524e52f3107c5c5fb75647f8b488d61ee1a3e3a9 100644 (file)
--- a/ovsdb/SPECS
+++ b/ovsdb/SPECS
@@ -5,6 +5,19 @@
 Basic Notation
 --------------
 
+OVSDB uses JSON, as defined by RFC 4627, for its schema format and its
+wire protocol format.  The JSON implementation in Open vSwitch has the
+following limitations:
+
+     - Null bytes (\u0000) are not allowed in strings.
+
+     - Only UTF-8 encoding is supported.  (RFC 4627 also mentions
+       UTF-16BE, UTF-16LE, and UTF-32.)
+
+     - RFC 4627 says that names within a JSON object should be unique.
+       The Open vSwitch JSON parser discards all but the last value
+       for a name that is specified more than once.
+
 The descriptions below use the following shorthand notations for JSON
 values.  Additional notation is presented later.