[IPsec] Issue #187, was: Re: Another round of IKEv2-bis issues

It's kind of weird to introduce EAP while avoiding any mention of EAP
methods. So I propose:

The Extensible Authentication Protocol Payload, denoted EAP in this
document, allows IKE SAs to be authenticated using the protocol
defined in RFC 3748 [EAP] and subsequent extensions to that protocol.
When using EAP, an appropriate EAP method needs to be selected. Many of these methods have been defined, specifying the protocol's use with various authentication mechanisms. They are listed in [EAP-IANA].
A short summary of the EAP format is included here for clarity.

Thanks,
	Yaron
> 
> 
> Issue #187 - EAP introduction wording
> =====================================
> The first paragraph of 3.16 now says: 
> 
> The Extensible Authentication Protocol Payload, denoted EAP in this document, allows IKE SAs to be authenticated using the protocol defined in RFC 3748 <xref target='EAP'/> and subsequent extensions to that protocol. The full set of acceptable values for the payload is defined elsewhere, but a short summary of RFC 3748 is included here to make this document stand alone in the common cases. 
> 
> Where is "defined elsewhere"? We should be specific. 
> 
> Also, we agreed to remove the short list of EAP methods, but we didn't fix the last phrase above. Suggested wording would be appreciated.  
> 
> 
> Even Tero didn't reply to this, so here's my suggested wording (I just removed the offending sentence:
>    The Extensible Authentication Protocol Payload, denoted EAP in this
>    document, allows IKE SAs to be authenticated using the protocol
>    defined in RFC 3748 [EAP] and subsequent extensions to that protocol.
>    A short summary of the EAP format is included here for clarity.
> 
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec