Earlier quoted context omitted.
It's not a druthers kind of thing. If you need to trust that it hasn't been tampered with you must sign it. And if you don't care you might as well not add authentication because without signing it's just a fancy CRC - ie, totally replicable by an attacker. As cookies and links are sent over TCP there should be vanishingly few errors in transmission - you're far more likely to introduce false positives with buggy cod…
I'm not sure what your argument is. Yes if you want to trust it you have to sign it and make sure you implement all the crypto correctly. But I don't see a need for that here. Also TCP's checksum sucks.
How many corrupted web pages do you see because of CRC failure in TCP?