"Black, David" <[email protected]> writes: > Lars, > > Mirja explained the path forward in this case in the adoption calls > for both drafts:
Suppose we go down path 3, namely to publish both approaches as different versions of tcpinc. Is it required that both be published simultaneously? If we can just publish each RFC when it is ready, then there might be incentive for people to work on independent implementations. Right now, one problem for anyone considering investing time in tcpcrypt is that even if we get the draft into great shape, get two independent implementations, etc., we might still end up stuck waiting for TCP-use-TLS, which might in turn be stuck waiting for TLS 1.3. So while having two different RFCs does not seem like the end of the world, forcing them both to proceed in lockstep may greatly delay deploying anything. Would it be possible to decouple progress on the two protocols by working group consensus? David _______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
