Currently if
1. Client sends mechanisms in these order "Kerberos V5 Legacy", "Kerberos V5" + valid kerberos ticket
2. EAP server sends accept_incomplete (Continuation required) and forces usage of "Kerberos V5"
3. Client sends again the ticket
4. Server sends accept_complete

I wonder is there a chance EAP server can omit one network roundtrip?

1. Client sends mechanisms in these order "Kerberos V5 Legacy", "Kerberos V5" + valid kerberos ticket
2. EAP server sends accept_complete based on that "Kerberos V5" is present and valid kerberos ticket is provided

It could bring big performance gain, because one network client-server roundtrip could be saved.