The DAA proposal carries on that grand tradition, but I'd like to suggest that we get some clarity in the terms, and propagate it.
Authentication is the process of proving identity.
Authorization is the process of deciding if a request will be honored. The protocol does authentication, in support of authorization, but does not necessarily determine where authorization happens. For example, a server doing authentication for another can redirect, sending it's stamp of approval on the authentication information in the opaque field, and the target server could do the actual authorization, based on the verified authentication.