IEEE P1619.3
Architecture Subcommittee
Conference Call
November 15, 2007
IEEE P1619.3 Architecture Subcommittee
1
Agenda
•
Review Previous Actions
•
“Draft” KM Conceptual Models
•
“Draft” Key Lifecycle Models
•
Items in Progress
•
Next Steps
IEEE P1619.3 Architecture Subcommittee
2
Previous Action Item Review
•
Mike W. to refine KM conceptual models; integrate
into Model Proposal with definitions
•
•
In progress, models “complete”, working definitions
Bob L., Jon H., and Larry H. to collaborate on
single key lifecycle model
•
Common model agreed to in concept. Still working some
of the finer points. We will discuss a little bit today.
IEEE P1619.3 Architecture Subcommittee
3
Proposed KM Conceptual Models
IEEE P1619.3 Architecture Subcommittee
4
Conceptual Key Management Model
Control Plane
Option #1
Data Plane
KM Client
Cryptographic
Unit
KM Server
Encryption Application
Cryptographic
Unit
KM Server
Encryption Application
Encryption Application
Encryption User
Control Plane
Option #2
OR
KM Message &
Transport Protocol
KM SW Lib
(optional)
KM API
KM Client
Cryptographic
Unit
Storage Medium
IEEE P1619.3 Architecture Subcommittee
5
Conceptual Key Management Model
Key
Backup/Archive
Key
Backup/Archive
KM File
Import/Export
File transfer
KM User
KM Server
KM Server
KMSS Ops
KMCS Ops
Encryption Application
Encryption Application
KMCS Ops
KM Client
Cryptographic Unit
KM SW Lib (Opt)
KM API
KM Client
Cryptographic Unit
Legend
Out of Scope
Storage Medium
Data Transfer
(outside of KMS)
IEEE P1619.3 Architecture Subcommittee
Storage Medium
6
Proposed
Key Lifecycle Model
IEEE P1619.3 Architecture Subcommittee
7
“Draft” Key Lifecycle Models
IEEE P1619.3 Architecture Subcommittee
8
Items in Progress
IEEE P1619.3 Architecture Subcommittee
9
Items in Progress

What do we do with the key exchange data structures
currently defined?


What do we do about Policy definitions and do we
need another model?


Action: Move to OO and MSG sections
Action: Yes?
Do we need interaction models for the API and the
Message/Transport protocol interface?

Action: Yes…
IEEE P1619.3 Architecture Subcommittee
10
Current D1 Policy Model
IEEE P1619.3 Architecture Subcommittee
11
Next Steps

Publish initial draft of model proposal


Need to tackle other models




Integrate conceptual models and key lifecycle
model
Application Template/Policy/Key Interaction Model
API/MSG-Xport Interaction Model
Others?
Next call will be Thursday, Nov. 29th

@ 10 AM PST (1 PM EST)
IEEE P1619.3 Architecture Subcommittee
12