eap Mailing List: FW: [eap] WG Action: RECHARTER: Extensible Authentication Protocol (eap)

[Alper Yegin (alper.yegin]

Hello,

I have some clarification questions.

> While the EAP WG is not currently chartered to standardize EAP
> methods, with the publication of RFC 3748, the EAP WG will
> assume responsibility for review of EAP methods requesting
> a Type code allocation, as specified in the IANA considerations
> section of RFC 3748.

Would these reviews ultimately lead to Type code allocations under the
current charter or not? 

Allocation calls for Specification Required, which mandates "an RFC or
other permanent and readily available reference". If these are not
standards track document, would they become have to become informational
RFCs? I wonder if that's the plan, or am I missing something? 

> 
> When the current work items are completed, the WG may be
> rechartered, or a new WG may be formed to standardize methods.

Thanks.

Alper