Yuchung Cheng <ych...@google.com> writes:
> For C2, does that requires "every" TCPINC application to specify its
> roles SO or not? i.e., both sides need to setsockopt("I am [AB]")?
If you are using simultaneous open, exactly one side must specify that
it wants the B role, which requires sending a general suboption byte
with bit b=1. If the other side sends a general suboption byte it must
specify b=0, but since that is the default is b=0, that side need not
send a general suboption byte. In the event that sides do not send the
correct bytes, the connection falls back to unenecrypted TCP but still
works.
In the case of non-simultaneous open, nothing need be specified.
David
_______________________________________________
Tcpinc mailing list
Tcpinc@ietf.org
https://www.ietf.org/mailman/listinfo/tcpinc
