On Tue, May 2, 2017 at 10:24 AM, Salz, Rich <rs...@akamai.com> wrote:
> > it may be a naïve question, but is it still possible to define and > standardize new cipher suites for TLS 1.2 as an RFC, when TLS 1.3 is almost > finished? > > Yes it is. It might be "informational" not "standards-track" but it's > certainly possible/allowed/etc. > Whether it's worth doing or not depends on the objective. If the desire is to get support for a new TLS 1.2 cipher suite into browsers or open source TLS stacks, well... good luck with that. If the desire is to get something working for their own internal use, standardization is not really necessary, though I would certainly advise doing whatever is required to get a code point from IANA. If the desire is somewhere in the middle, such as internal use plus interop with other organizations within an industry or consortium, then publication of an informational RFC might make sense. I'm skeptical, however, that they will get a lot of attention from folks on this list as there seems to be little interest in spending time on a legacy protocol; and pursuing something standards track will probably go nowhere. Kyle
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
