Update README.md for AEAD 2022 ciphers

[strangemk2]

Since AEAD 2022 will become next generation default ciphers, it's better to include important guides like "How to generate password for AEAD 2022" in the main readme.
Other information in "Getting Started" session also need to be updated.

[zonyitoo]

Since AEAD 2022 will become next generation default ciphers

I don't think so. It is currently an experimental feature.

[database64128]

shadowsocks-rust seems to be the only implementation that still claims Shadowsocks 2022 is experimental. I just want to point out a few facts:

1. The spec was declared stable last May.
2. The actual behavior of standard-compliant implementations has never changed since the spec freeze.

The Shadowsocks organization is dysfunctional and has proven itself incapable of contributing constructively to the design and standardization of new proxy protocols. Unless major structural changes happen to the organization, there are no plans on my side to work with the organization to have the spec "approved", or whatever it takes for shadowsocks-rust to recognize the protocol as stable.

[zonyitoo]

What's the official process to make a new protocol "stable" in our organization? @madeye @riobard @Mygod

[madeye]

I think those ciphers are stable now, so we can document them on the project site first: https://github.com/shadowsocks/shadowsocks-org/edit/main/docs/guide/aead.md

[database64128]

@madeye Thank you for doing the work of adding the spec in shadowsocks/shadowsocks-org@9291b38. 👍

In addition to the base spec, there's Extensible Identity Headers for native multi-user support. Even though it's optional, all current implementations, even proprietary ones like ShadowRocket, support this extension. Should this be added as well? Should we allocate an extra SIP number for it, or reuse the existing one like what we did with SIP003u?

[madeye]

Please feel free to open PRs for those SIPs.

I think it's always fine to add pages for stable SIPs, even though they may not reach consensus across the whole community.

[madeye]

Should we allocate an extra SIP number for it, or reuse the existing one like what we did with SIP003u?

IMO, a new SIP number should be better.

Eventually, we can make shadowsocks work as a decentralized community: 1) Everyone can add new SIPs; 2) When a SIP become stable and get implemented by many developers, we can publish its spec on our website.