"
IESG Note: EAP-FAST has been implemented by many vendors and it is
used in the Internet. Publication of this is intended to promote
interoperability, even though the use of the EAP-MSCHAPv2 and
EAP-FAST-GTC EAP methods might be difficult in some software
environments. If EA
Bernard Aboba [mailto:bernard_ab...@hotmail.com] writes:
IESG Note: EAP-FAST has been implemented by many vendors and it is
used in the Internet. Publication of this is intended to promote
interoperability, even though the use of the EAP-MSCHAPv2 and
EAP-FAST-GTC EAP meth
Dan Harkins said: > draft-cam-winget-eap-fast-provisioning claims a reference
to RFC 5226> but nowhere in that RFC can I find description of the following
label> for an initial assignment of repository values:>> "allocated for
management by Cisco">> yet the draft instructs IANA to set aside val
>
> Are you saying that the registry of "EAP-FAST PAC Attribute
> Types" also
>
> relates to RFC 4507, which is a standards track document?
>
[Joe] This is not directly related to 4507. RFC 4507 treats tickets as
opaque.
>
> If so, then I may see your point. RFC 5226 does permit
> v
Bernard Aboba [mailto:bernard_ab...@hotmail.com] writes:
Dan Harkins said:
> draft-cam-winget-eap-fast-provisioning claims a reference to RFC 5226
> but nowhere in that RFC can I find description of the following label
> for an initial assignment of repository values:
>
> "allocated for manag
I would like to remind everyone that these documents did go through
IETF Last Call, and have already been approved by IESG.
If folks are opposed to publishing descriptions of deployed EAP method
when they're less than perfect (or even ugly hacks with bad architecture),
and may not offer perfect se
