clarify

diff --git a/isa_conflict_resolution/mvendor_march_warl.mdwn b/isa_conflict_resolution/mvendor_march_warl.mdwn
index 2cb1ea348b070feaae5afb2d68173b4aaa226a4a..f19179818f9a753ca497ad07c97884253a1e66ee 100644 (file)
--- a/isa_conflict_resolution/mvendor_march_warl.mdwn
+++ b/isa_conflict_resolution/mvendor_march_warl.mdwn
@@ -68,7 +68,8 @@ to not be permitted to receive RISC-V Certification Compliance.
 
 How such foreign architectures would switch back to RISC-V when the foreign
 architecture does not support the concept of mvendorid-marchid is out of
-scope and left to implementors.
+scope and left to implementors to define and implement equivalent
+functionality.
 
 ## Implementation
 
@@ -153,3 +154,8 @@ The clear separation which mutually-exclusively redirects encodings based
 on which mvendorid-marchid tuple is currently active clearly meets that
 requirement.
 
+# Questions to be resolved
+
+* Can the declaration (meaning) of read-only be expanded to cover
+  any number of (non-conflicting) Custom Extensions?  What are the
+  implications of doing so?