eap Mailing List: Re: Re: I-D ACTION: draft-vanderveen-eap-make-00.txt

[Jari Arkko (jari.arkko]

Bernard Aboba wrote:

> > => So I guess there are two options for progressing forward:
> > a. Change the name of the method, or 
> > b. Go for the block allocation, which needs IETF concensus.
> >
> > I don't know if the existing allocation (type 27) is being used by anyone
> > but we're happy with either option, whatever works quicker is fine with
> > us. Does it matter which path we take? It seems that either way we 
> > will need WG concensus to make progress, right?
> >    
>
> The Block Allocation option is only available if 
> draft-vanderveen-eap-make-00 is in fact a specification for the EAP MAKE 
> protocol that was allocated EAP Type 27 by  IANA. 
>
> Otherwise, you will need to change the name. 
>  
And the third possibility is that if Type 27 == draft-vanderveen
then it may be that you are describing the deployed version,
in which case you already have allocation and the usual Individual
RFC submission rules apply, i.e., no EAP WG Expert Review.
Though of course we'd be happy to run one for you.

--Jari