RFC2 - Seperate UI-Related Items from Interaction Portions of Specification

Currently, the CAS Protocol specification details some aspects of the protocol that go beyond interaction between the server, the user, and the client. Examples include the suggested name of the session cookie, and the Warn UI feature. While important, and useful, these details may not belong in the protocol specification.

For example, in CAS4 we'll be supporting multiple protocols, and it may not make sense to call the session cookie TGC (which is CAS specific), or we may have an alternate UI that does not need warn.