| Re: RFC 3748 Review of EAP SIM | <– Date –> <– Thread –> |
|
From: Jari Arkko (jari.arkko |
|
| Date: Mon, 22 Nov 2004 08:50:31 -0500 (EST) | |
Bernard Aboba wrote:
--Jari
I think there is an issue with the IANA considerations section.
An IANA registry is requested for the Subtype and Attribute Type number, allocated using "specification required". No review mechanism is specified, yet it is indicated that the same protocol numbers should be assigned to EAP AKA and EAP SIM. It is not clear how this requirement is to be enforced, given the allocation policy. The authors may wish to rethink this.
Now I think I understand what your problem was. Would it help if the document(s) stated that ONE registry of parameters is established at IANA?
--Jari
- Re: RFC 3748 Review of EAP SIM, (continued)
-
Re: RFC 3748 Review of EAP SIM Bernard Aboba, November 22 2004
- How to design fast handoffs (Was: Re: [eap] RFC 3748 Review of EAP SIM) Jari Arkko, November 22 2004
- Re: How to design fast handoffs Bernard Aboba, November 22 2004
- RE: RFC 3748 Review of EAP SIM Joseph Salowey, November 22 2004
-
Re: RFC 3748 Review of EAP SIM Bernard Aboba, November 22 2004
- Re: RFC 3748 Review of EAP SIM Bernard Aboba, November 22 2004
- RE: RFC 3748 Review of EAP SIM Bernard Aboba, November 22 2004
Results generated by Tiger Technologies using MHonArc.