PAP [was Re: forging a new pppext charter]
James Carlson <[email protected]>
| Newsgroups | gmane.ietf.pppext |
|---|---|
| Message-ID | <[email protected]> |
Carsten Bormann writes: > > And isn't RFC 1334 already in obsoleted status? What are the important > > cases where PAP is useful? > > How about PAP in EAP-TTLS? > (RFC 1334 is carefully not referenced in > draft-ietf-pppext-eap-ttls-03.txt, but it has a whole subsection 10.2.5 > devoted to it.) I don't think that solves the original problem; it just creates a new one. One meager but important advantage that PAP had was ubiquity. Burying it inside EAP will destroy that, as there are few real implementations of EAP deployed and used. In any event, EAP extensions should really be referred to the EAP working group. As I understand it, they're supposed to be working on methods once they're done with the current specification efforts. -- James Carlson, IP Systems Group <[email protected]> Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677