Sam Hartman wrote: > I think we can come up with text that makes it clear what's going on and > that leaves processing to the final AAA server.
That isn't enough. 4282 requires that the NAI be mangled in order to create a normal form. This mangling is done *before* the NAI is used in EAP. No NAI implementation does this. Requiring compliance with 4282 means that implementations of draft-ietf-abfab-gss-eap *cannot* inter-operate with existing EAP implementations. > I do support doing > that. I do not support changing the dependency to a draft instead of an > RFC. I understand why. Alan DeKok. _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
