I don't see the text as harmful. It may be somewhat
redundant, but I
would like to better understand why its presence is
restrictive. That
would seem to indicate that it is not redundant.
Joe
> -----Original Message-----
> From: Bernard Aboba [mailto:bernard_aboba hotmail.com]
> Sent: Tuesday, May 02, 2006 5:54 AM
> To: eap frascone.com
> Subject: [eap] Re: Issue 360: EMSK Transport
>
> Since EMSK sharing is prohibited elsewhere in the
document,
> the text to be
> deleted is redundant at best. Any objections to
accepting
> the proposed
> change?
>
>
------------------------------------------------------------
---------
> Issue 360: EMSK Transport
> Submitter name: Vidya Narayanan
> Submitter email address: vidyan qualcomm.com
> Date Submitted: May 1, 2006
> Reference: http://lists.frascone.com/pipermail/eap/msg04230.html
> Document: KEYING-12
> Comment type: 'T'echnical
> Priority: '1' Should fix
> Section: 2
> Rationale/Explanation of issue:
>
> The section says "The EMSK MUST NOT be
transported by the AAA layer."
> Given that the EMSK usage is currently undefined, it is
not
> clear if it
> will be the AAA layer that derives further keys from
the
> EMSK. In fact,
> doing so will create disparate behavior at the peer and
server, since
> the peer does not have a AAA layer. Although this topic
is pending
> discussion, it seems restrictive to say MUST NOT here.
It does make
> sense, however, to say that the EMSK MUST NOT be
transported to
> additional parties.
>
> Requested change:
>
> Delete the sentence "The EMSK MUST NOT be
transported by the
> AAA layer".
>
>
>
____________________________________________________________
_____
> To unsubscribe or modify your subscription options,
please visit:
> http:/
/lists.frascone.com/mailman/listinfo/eap
>
> Arhives: http://lists.
frascone.com/pipermail/eap
>
____________________________________________________________
_____
To unsubscribe or modify your subscription options, please
visit:
http:/
/lists.frascone.com/mailman/listinfo/eap
Arhives: http://lists.
frascone.com/pipermail/eap
|