Merge pull request #168 from vdzhuvinov/iss-35-metadata-policy-json-i…

…nterop

Using non-interoperable JSON may result in unpredictable metadata and metadata policies (iss #35)

openid-federation-1_0.xml

@@ -2041,6 +2041,13 @@
                 An operator MUST NOT output a metadata parameter with the
                 <spanx style="verb">null</spanx> value.
               </t>
+              <t>
+                Metadata parameters and policies that conform to the JSON 
+                grammar but do not represent interoperable uses of JSON,
+                as per Sections 4 and 8 of <xref target="RFC8259"/>, 
+                may cause unpredictable
+                behavior.
+              </t>
 
             </list>
           </t>
@@ -8626,6 +8633,7 @@ HTTP/1.1 302 Found
       <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7591.xml"/>
       <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7638.xml"/>
       <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
+      <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/>
       <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8414.xml"/>
       <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8705.xml"/>
       <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9101.xml"/>
@@ -10043,6 +10051,11 @@ Host: op.umu.se
 	    in the Explicit Registration response to be the Immediate Superior
 	    of the RP in the Trust Chain selected for it by the OP.
 	  </t>
+	  <t>
+	    Fixed #35: Clarified that using non-interoperable JSON, as per sections
+        4 and 8 of RFC 8259, may result in unpredictable metadata and metadata
+        policy behavior.
+	  </t>
 	  <t>
 	    Fixed #162: Trust Mark claim <spanx style="verb">id</spanx> 
 	    renamed to <spanx style="verb">trust_mark_id</spanx>.