I'm expecting to turn on basic 4.1 support by default on the Linux server before supporting two mandatory 4.1 features, and looking for advice on handling that without too much pain to future clients. I suspect I'm not the only server in this situation; anyone know what others are doing? The features are: - State protection (SSV and MACH_CRED): I'm currently returning SERVERFAULT on EXCHANGE_ID's that request this, but this isn't really what SERVERFAULT is for. I'm inclined to switch to ENC_ALG_UNSUPP; that leaves future clients unable to distinguish between servers lacking SSV entirely from those lacking support for a particular algorithm, but in practice I think they'd handle both in the same way anyway. - GSS on the backchannel: currently CREATE_SESSION or BACKCHANNEL_CTL will succeed but SEQUENCE will start returning with the CB_DOWN flag set. I would rather return an error immediately than make the client guess what's going on in recovery. Could I get away with returning ENC_ALG_UNSUPP here too? It's not entirely logical, but it's also currently illegal for these two operations so its use wouldn't be confused with some other. Of course my preference would be just to support these features, but given resource limitations, the lack of interest, and the lack of any implementation to test against, that doesn't look likely to happen in the near future. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
