Re: [FW: Re: [eap] Please review -- IETF Last Call ondraft-barany-eap-gee-04.txt]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yoshihiro,
> If we agree that EAP GEE is part of a 3GPP2 EAP lower layer, wouldn't
> it be more appropriate to standarize EAP GEE within 3GPP2, with
> utilizing this EAP WG review as peer review as we have done for IEEE
> 802.16e and 802.1aa?
>   
I fully agree with Bernard that the work needs to be tied
to the specific lower layer and specific use of EAP in that.
If this was a general mechanism for all EAP uses, it
would require a different IETF process, consideration
of a broad set of requirements from different
usage scenarios, etc. As Bernard points out, merely
turning this on in other link layers would break them.
(We need to work on what the details are for
the sufficient tie-in to the link layer is, however.
The current document is already tied to 3GPP2 link
layer, though based on Bernard's review, in an
inadequate manner.)

However, I believe that submitting specifications
developed outside the IETF as non-standard RFCs
is sometimes useful, as long as the situation
and status is clearly indicated. Typical cases where
such publication can be useful are "Using IETF
technology <X> in environment <Y>" documents
where it is felt that significant IETF review is
warranted (such as in this case), and where
the community might benefit from availability
of an RFC.

Jari


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]