[Standards] Re: Scoping discussion: updating XMPP RFCs / XMPP 2.0

As to "bring in new people", I think that's a bit of a red herring. There is no such thing as "XSF people" or "IETF people" - there are just people. If some people come to the IETF asking to do some work (especially if they are are *coming back* in good faith to update a technology of long standing at the IETF), there is no requirement to get new people interested. In my various roles at the IETF I have seen this repeatedly with work on technologies like FTP. As to "align this work with the need for a common messaging standard", that could be a rat hole of epic proportions, so we'd need to understand what kind of scope people are thinking about. Although I have no doubt that there are ecosystem gaps XMPP can fill (and arguably should have filled long ago), quite possibly those gaps have come about because of product and (roughly speaking) political decisions made by the major players, which can't necessarily be solved by a standardization effort, especially one to update XMPP Core rather than define new extensions or applications of XMPP. If some of the requirements align that's great, but I'd be careful about saddling the update effort with a whole bunch of new requirements just to satisfy the longing for a common messaging standard, which has existed for 30 years and might never be satisfied.