The aim of this group it do design an object security architecture able to provide a better security but also more flexible security services than strict end-to-end encryption. An architecture content owner should be able to express what security levels different objects should be associated with.

There are several ways to design an architecture that fulfills these requirements. All the alternatives have to be explored and discussed in order to understand the pro and cons. An important question to analyze is whether an object security architecture should be designed at the application layer (as a complementary solution to TLS) or further down the stack as a better alternative to TLS.

To post a message to all the list members, send email to
mcic@ietf.org.

You can subscribe to the list, or change your existing
subscription, in the sections below.

Subscribing to Mcic

Subscribe to Mcic by filling out the following
form.
You will be sent email requesting confirmation, to
prevent others from gratuitously subscribing you. This is a private list, which means that the
list of members is not available to non-members.

Your email address:

Your name (optional):

You may enter a
privacy password below. This provides only mild security,
but should prevent others from messing with your
subscription. Do not use a valuable password as
it will occasionally be emailed back to you in cleartext.

If you choose not to enter a password, one will be
automatically generated for you, and it will be sent to
you once you've confirmed your subscription. You can
always request a mail-back of your password when you edit
your personal options.
Once a month, your password will be emailed to you as a reminder.