Add issue marker noting guidance about decoy values is not final.

Author: msporny

index.html

@@ -1418,7 +1418,21 @@ <h3>Decoy Values</h3>
       <p>
 [=Issuer=] use of decoy values in status lists has been explored as a mechanism
 to increase the privacy of [=subjects=]. While algorithms for employing decoy
-values are out of scope for this specification, implementers are advised that
+values are out of scope for this specification, implementers are advised that...
+      </p>
+
+      <p class="issue" data-number="150">
+The Working Group is currently discussing what sort of guidance to provide
+for decoy values. It has been suggested that decoy values are, in general,
+harmful to this specification's privacy characteristics. However, the group
+has not provided a complete analysis and thorough review for that assertion.
+The analysis might result in some use cases where decoy values are helpful, or
+might conclude that decoy values are, in general, harmful. Further
+thought is currently being put into the language around decoy values and
+it is expected that this language will be finalized during the Candidate
+Recommendation phase.
+      </p>
+        <!-- TEXT BELOW NEEDS TO BE FURTHER ANALYZED AND JUSTIFIED
 the use of decoy values does not improve privacy and can harm privacy in
 most cases.
       </p>
@@ -1436,6 +1450,7 @@ <h3>Decoy Values</h3>
 most if not all use cases, as random allocation of status list entry indexes
 provides adequate protection.
       </p>
+      -->
     </section>
 
     <section class="informative">