Add "at risk" marker noting bitstring format might change in CR.

index.html

@@ -662,6 +662,19 @@ <h2>Algorithms</h2>
 and validate status lists as described by this document.
     </p>
 
+    <p class="issue atrisk"
+       title="Attempting alignment with IETF Token Status List specification">
+The Working Group is seeking feedback related to implementer desire to align
+with the IETF OAuth Working Group
+<a href="https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/">
+Token Status List</a> specification. If there is interest,
+and to the extent possible, this specification might align
+more closely with the Token Status List bitstring format, as it could be
+beneficial to have the same code base able to process bitstring values from
+both lists. If there is implementer support for these changes, these changes
+might be made during the Candidate Recommendation phase.
+    </p>
+
     <section class="normative">
       <h3>Generate Algorithm</h3>