This is a copy from the slide presentation.


This proposal represents work-in-progress, in collaboration with the MCG.

Contents Copyright © E. Gerck, 1997. All rights reserved.

Allowed copying and public distribution of the complete work only, with author and source citation.

Meta-Certificate Development steps (1996 - 1997):

The MCG (1997):

Main Features

MC Exclusive Concepts

MC X (TTP, PKI, key-escrow)

Authentication Channels



Today's Certification Procedures

Domain-Space and Image-Space:
What are they?

Can we go back to Domain-Space?

- a basic question that must be answered first -

What is being certified?

Basic definitions
- towards clear engineering concepts -
(this list still represents work-in-progress at the MCG)

Meta-Certificate: Definition 1

A Meta-Certificate (or MC) is a unit of data and code, cryptographically signed, that allows objects with entities, attributes and methods to be distributed, redistributed and certified.

A MC is an object, in Object-Oriented (O-O) terminology.

Meta-Certificate: Definition 2

Meta-Certificates are persistent and remote class-object structures. MC-objects are sent to client machines -- and can be further redistributed -- as instances of a class stored in a server machine, which is known as Meta-Certificate Class (MCC). The MCC also has class methods and data. The MCs are used to authenticate the server and to allow assigned tasks to be carried over even in other machines. The MCC can be different in each server machine but all MCCs inherit common features from a uniquely defined Meta-Certificate Abstract Class (MCAC).

Meta-Certificate Implementations
- based on MC-server, using existing infrastructure -