`<aside>` as a subparagraph in `<li>`

[cabo]

An aside that continues a list item paragraph might turn up inside the <t> for that.
Not quite clear whether the error message:

li-aside.xml(61): Error: Element li has extra content: t, at /rfc/middle/section/ul/li/t[2]

...actually fits the actual syntax error.

Input:

This message consists of:

* `verification_key_id`: An identifier for the shared secret
  that will be used for this aggregation job.
  This allows a Leader to nominate a verification key
  from a set of prearranged keys.
  This might also allow for verification keys to be updated by Aggregators.

  {:aside}
  > IMPORTANT: this this does not change the security requirements
  > for verification keys.
  > The analysis in {{DPRS23}} depends on an assumption
  > that verification keys are selected prior to a report being generated;
  > a different analysis would be required
  > to enable selecting a verification key after a task has started.

Output has a vspace:

<t><list style="symbols">
  <t><spanx style="verb">verification_key_id</spanx>: An identifier for the shared secret
that will be used for this aggregation job.
This allows a Leader to nominate a verification key
from a set of prearranged keys.
This might also allow for verification keys to be updated by Aggregators.  <vspace blankLines='1'/>
    <aside>
      <t>IMPORTANT: this this does not change the security requirements
for verification keys.
The analysis in <xref target="DPRS23"/> depends on an assumption
that verification keys are selected prior to a report being generated;
a different analysis would be required
to enable selecting a verification key after a task has started.</t>
    </aside>
  </t>
</list></t>

After conversion to v3 (which turns the vspace into a split point for the <t>:

      <ul spacing="normal">
        <li>
          <t><tt>verification_key_id</tt>: An identifier for the shared secret
that will be used for this aggregation job.
This allows a Leader to nominate a verification key
from a set of prearranged keys.
This might also allow for verification keys to be updated by Aggregators.  </t>
          <t><aside>
              <t>IMPORTANT: this this does not change the security requirements
for verification keys.
The analysis in <xref target="DPRS23"/> depends on an assumption
that verification keys are selected prior to a report being generated;
a different analysis would be required
to enable selecting a verification key after a task has started.</t>
            </aside>
          </t>
        </li>
      </ul>

[cabo]

From:
ietf-wg-ppm/draft-ietf-ppm-dap@2c044b1