Add a "v2.md" file so we can close v2 issues/PRs

Signed-off-by: Doug Davis <duglin@gmail.com>

Author: duglin

README.md

@@ -120,6 +120,7 @@ native ecosystem by making our systems interoperable with CloudEvents.
   docs](https://drive.google.com/drive/folders/1eKH-tVNV25jwkuBEoi3ESqvVjNRlJqYX?usp=sharing)
 - [Demos & open source](docs/README.md) -- if you have something to share
   about your use of CloudEvents, please submit a PR!
+- [Potential CloudEvents v2 work items](v2.md)
 - [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)
 
 ### Security Concerns

cloudevents/v2.md

@@ -0,0 +1,14 @@
+# CloudEvents Version 2 Consideration List
+
+The list below contains the set of changes that the group had identified as
+potential candidates for a v2 of the CloudEvents specification. There no
+guarantee as to when, or if, a v2 might happen, or that any of these will be
+adopted. Rather this list is just a reminder to consider them so that we can
+reduce the number of open issues and PRs on our backlog.
+
+- [Do we want a new optional "mustunderstand" core attribute](https://github.com/cloudevents/spec/issues/1321)
+- [Why does the HTTP binding for batch require the same spec version for all events in the batch?](https://github.com/cloudevents/spec/issues/807)
+- [handling of datacontenttype is inconsistent](https://github.com/cloudevents/spec/issues/558)
+- [fix(protobuf)!: Expose CloudEvent structure with explicit fields](https://github.com/cloudevents/spec/pull/1354)
+
+