--- JSON-XS/XS.pm	2013/10/30 22:11:01	1.152
+++ JSON-XS/XS.pm	2014/03/02 20:41:14	1.153
@@ -1624,6 +1624,22 @@
 Again, this has some limitations - the magic string must not be encoded
 with character escapes, and the constructor arguments must be non-empty.
 
+
+=head1 RFC7158
+
+Since this module was written, Google has written a new JSON RFC, RFC
+7158. Unfortunately, this RFC breaks compatibility with both the original
+JSON specification on www.json.org and RFC4627.
+
+As far as I can see, you can get partial compatibility when parsing by
+using C<< ->allow_nonref >>. However, consider thew security implications
+of doing so.
+
+I haven't decided yet whether to break compatibility with RFC4627 by
+default (and potentially leave applications insecure), or change the
+default to follow RFC7158.
+
+
 =head1 THREADS
 
 This module is I<not> guaranteed to be thread safe and there are no