Hi!
I think the 06 spec can be kept equivalent to the 05 spec, only clarifying things that are unclear in the spec, removing ambiguity, and not adding new features or changing behavior that was already uniquely defined.
So far the only change is https://github.com/remotestorage/spec/commit/c6829443fa58ffa898c34a969dd29861640808f5 (I just created https://github.com/remotestorage/spec/pull/105 as an improvement of that), and we were talking about making it clearer how URI_ENCODE works exactly.
What else should we change in the text to clear up ambiguities, or correct statements that contradict certain RFCs?
https://github.com/remotestorage/spec/issues/101 could be resolved. Ignoring the client_id sort of contradicts the OAuth RFC
We clarified and improved a lot of things in the spec! Release candidate for the 06 spec: https://github.com/remotestorage/spec/releases/tag/06-rc1
If we don’t find any errata until then, I’ll publish it on Monday.
https://github.com/remotestorage/spec/releases/tag/06 tagged! 
IETF-level discussion should take place in this thread:
https://mailarchive.ietf.org/arch/msg/storagesync/6delQp0cRl2c6egesHaIK9l5Etg
(for more detailed discussions about the text, github issues / PRs are easier).
