eap Mailing List: Re: Another two minor and finicky IANA considerations questions for RFC3748

[Henrik Levkowetz (henrik]

Hi,

Thursday 10 June 2004, Jari Arkko wrote in reply to Florent:
> > 1) It is apparently not specified how expanded (method) types for 
> > vendor-ID 0 (IETF) can be allocated (e.g. Designated Expert, with 
> > Specification Required or standards action, FCFS, ...).
> > In section 6.2 we indeed only read:
> > "Method Type values 256-4294967295 may be allocated after Type values 
> > 1-191 have been allocated."
> > I know we've probably got time before this happens but I just feel 
> > reluctant to leave an incomplete spec behind us ;-)
> 
> I think it would make sense to add ", through the advice of a
> Designated Expert, with Specification Required" to the end of the sentence
> that you quoted. Henrik tells me that he still can send a change
> to the RFC editor.

Ok, so the proposed change is as follows:

Section 6.2., para. 3:
OLD:
 
    Method Type 254 is allocated for the Expanded Type.  Where the
    Vendor-Id field is non-zero, the Expanded Type is used for functions
    specific only to one vendor's implementation of EAP, where no
    interoperability is deemed useful.  When used with a Vendor-Id of
    zero, method Type 254 can also be used to provide for an expanded
    IETF method Type space.  Method Type values 256-4294967295 may be
    allocated after Type values 1-191 have been allocated.
 
NEW:
 
    Method Type 254 is allocated for the Expanded Type.  Where the
    Vendor-Id field is non-zero, the Expanded Type is used for functions
    specific only to one vendor's implementation of EAP, where no
    interoperability is deemed useful.  When used with a Vendor-Id of
    zero, method Type 254 can also be used to provide for an expanded
    IETF method Type space.  Method Type values 256-4294967295 may be
    allocated after Type values 1-191 have been allocated, on the advice
    of a Designated Expert, with Specification Required.
 

I'll send it in.

        Henrik