[Standards] Re: Proposed XMPP Extension: End-to-End Encrypted Contacts Metadata

This seems basically the same as bookmarks2. We have previously discussed putting contacts in bookmarks2 and some have complained that they assume everything in bookmarks2 is a MUC and so it's not allowed there. In the interest of reducing duplication we've then discussed putting extensions in the classic roster and then the client merges from both sources as today. Now if we want to move contacts into pubsub anyway it feels like what we really want is boomarks3: bookmarks2 but with wording that makes it clear that not everything in there is a MUC. This solves all the extended metadata questions that have been coming up over recent years while also making both things possible to encrypt with pubsub encryption methods as desired.