Re: [saag] [6lowpan] SOLACE things at SAAG

[Carsten Bormann <[e-mail]>]

On Oct 29, 2012, at 21:45, Stephen Farrell <[e-mail]> wrote:

> If he and Cullen want to arm-wrestle
> that's fine:-)

Well, Cullen's I-D (please have a look at draft-jennings-core-transitive-trust-enrollment-01.txt,.pdf)
is a very good example for the kind of input document that we are looking for.

But it is just one way of doing things.  There are so many others.  To a large extent, the differences are not just based on technological choices, but on what people are actually trying to do with the smart objects, i.e., what purpose in life they have.

After half a decade of kicking around half-baked solutions in this space in various IETF working groups, I think it is a good idea to spend more time understanding the design space.  How, and where, to spend this time in the most productive way is what I would like to discuss with interested people before we do the SAAG slot: -> [e-mail]

Grüße, Carsten


PS. Here is section 3.3 of the CoRE roadmap I-D, which lists a couple more related drafts:


   Several individual drafts analyze the issues around the security of
   constrained devices in constrained networks.

  | draft-garcia-core-security                      |     | 2012-03-26 |
  | draft-sarikaya-core-sbootstrapping              | -05 | 2012-07-10 |
  | draft-jennings-core-transitive-trust-enrollment | -01 | 2012-10-13 |

   [I-D.garcia-core-security] in particular describes the "Thing
   Lifecycle" and discusses resulting architectural considerations.
   [I-D.jennings-core-transitive-trust-enrollment] demonstrates a
   specific approach to securing the Thing Lifecycle based on defined
   roles of security players, including a Manufacturer, an Introducer,
   and a Transfer Agent.

   Further work around Thing Lifecycles is also expected to occur in the
   SOLACE initiative (Smart Object Lifecycle Architecture for
   Constrained Environments), with its early mailing list at
   [e-mail] -- developed after the model of the COMAN initiative
   (Management for Constrained Management Networks and Devices,
   [e-mail], [I-D.ersue-constrained-mgmt]).