>Anyways, the reason that PAP is still in widespread operational,
>day-to-day, present use, is that most authentication servers store
>passwords in one-way encrypted forms (Unix, WinNT, and LDAP) and the CHAP
>(RFC 1994) algorithm requires clear text passwords.
Actually, at this point, most usage of PAP that we see is for use with
token card authentication. Pre-EAP this was the most common way of
implementing this in PPP. So in a new protocol, the appropriate thing
to do is either to support EAP, or to have support for a generic
token card method. There really isn't much need to continue to support
PAP. Including a normative reference to a deprecated protocol isn't
a great idea.