| Issue on eap-keying: naming of AMSks | <– Date –> <– Thread –> |
|
From: Florent Bersani (florent.bersani |
|
| Date: Mon, 4 Oct 2004 09:40:39 -0400 (EDT) | |
Description of issue: should AMSK naming be mandatory?
Submitter name: Florent Bersani
Submitter email address: florent.bersani [at] francetelecom.com
Date first submitted: 10/04/2004
Document: Keying Framework
Comment type: 'E'ditorial
Priority: 1 should fix
Section: 2.4
Rationale/Explanation of issue:
section 2.4 reads: "AMSK Name
However, I think it is sound practice to name keys. Since AMSK are new, we shouldn't be bothered with legacy reasons. Hence, why not make this AMSK naming "mandatory"
Requested change
Submitter name: Florent Bersani
Submitter email address: florent.bersani [at] francetelecom.com
Date first submitted: 10/04/2004
Document: Keying Framework
Comment type: 'E'ditorial
Priority: 1 should fix
Section: 2.4
Rationale/Explanation of issue:
section 2.4 reads: "AMSK Name
AMSKs, if any, may be named by the concatenation of the string
"AMSK", key label, application data (see Appendix F), and EMSK
Name."However, I think it is sound practice to name keys. Since AMSK are new, we shouldn't be bothered with legacy reasons. Hence, why not make this AMSK naming "mandatory"
Requested change
Replace the previous text by "AMSK Name
AMSKs, if any, are named by concatenating the string
"AMSK", key label, application data (see Appendix F), and EMSK
Name."-
Issue on eap-keying: naming of AMSks Florent Bersani, October 4 2004
- Re: Issue on eap-keying: naming of AMSks Jari Arkko, October 4 2004
-
RE: Issue on eap-keying: naming of AMSks Joseph Salowey, October 4 2004
-
Re: Issue on eap-keying: naming of AMSks Jari Arkko, October 5 2004
- Re: Issue on eap-keying: naming of AMSks Florent Bersani, October 5 2004
-
Re: Issue on eap-keying: naming of AMSks Jari Arkko, October 5 2004
Results generated by Tiger Technologies using MHonArc.