The text of Issue 383 is enclosed below. The proposed
resolution is as
follows:
Add the following text to Appendix A:
"EAP-PSK
EAP-PSK is defined in [RFCPSK]. The EAP-PSK Session-Id is
the
concatenation of the EAP Type Code (0x2F) with the peer
(RAND_P)
and server (RAND_S) nonces. The Peer-Id is the contents of
the ID_P
field and the Server-Id is the contents of the ID_S field.
EAP-SAKE
EAP-SAKE is defined in [RFC4763]. The EAP-SAKE Session-Id is
the
concatenation of the EAP Type Code (0x30) with the contents
of
the RAND_S field from the AT_RAND_S attribute, followed by
the
contents of the RAND_P field in the AT_RAND_P attribute.
Note that the EAP-SAKE Session-Id is not the same as
the "Session ID" parameter chosen by the Server,
which is
sent in the first message, and replicated in subsequent
messages.
The Peer-Id is contained within the value field of the
AT_PEERID attibute and the Server-Id, if available, is
contained in the
value field of the AT_SERVERID attribute."
--------------------
Issue 383: Definition of Session-Id, Peer-Id, Server-Id for
Additional EAP
Methods
Submitter name: Bernard Aboba
Submitter email address: aboba [at] internaut.com
Date Submitted: November 19, 2006
Reference: http://lists.frascone.com/pipermail/eap/msg04537.html
Document: KEYING-15
Comment type: Technical
Priority: S
Section: Appendix A
Rationale/Explanation of issue:
Appendix A defines the Peer-Id, Server-Id and Session-Id for
existing EAP
methods, including EAP TLS, EAP SIM, EAP AKA. However, it
appears that there
are some EAP methods currently in the RFC Editor Queue that
do not define
these parameters. So either the specs need to be updated in
AUTH48, or
Appendix A needs to be updated to provide the required
information.
____________________________________________________________
_____
To unsubscribe or modify your subscription options, please
visit:
http:/
/lists.frascone.com/mailman/listinfo/eap
Arhives: http://lists.
frascone.com/pipermail/eap
|