eap Mailing List: Fix references to group key management protocol in EAP Key management framework I-D

[Lakshminath Dondeti (ldondeti]

Description of issue: EAP Key management framework I-D currently says 
in Page 14

"
IKEv2, defined in [RFC4306], handles the derivation of unicast
     security associations (phase 2a), while the derivation of multicast
     security associations (phase 2b) is handled in a separate group key
     management protocol, as described in [RFC4046]. "

The problem is 4046 describes MSEC's group key management framework 
and not a particular key management protocol.  MSEC has specified 
three key management protocols for group key establishment and they 
are GDOI, GSAKMP and MIKEY and is working on a third GKDP (this one 
is *similar* to IKEv2).

I'd also suggest using the phrase "establishment of multicast SAs" 
instead of "derivation ..."

Submitter name: Lakshminath Dondeti
Submitter email address: ldondeti [at] qualcomm.com
Date first submitted: April 3, 2006
Reference: <>
Document: Document Requiring change [Keying Framework]
Comment type: ['E']
Priority: ['S' Must fix]
Section: 2.1
Rationale/Explanation of issue:  See above.
Length description of problem

Requested change:

"while the establishment of multicast security associations (phase 
2b) may be handled by a group key management protocol such as GDOI 
[RFC3547], GSAKMP [RFC-to-be-GSAKMP], MIKEY [RFC3830], or GKDP 
[GKDP-work-in-progress]."


+++++++++

regards,
Lakshminath