Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2m-iwg] M3DA protocol proposed as part of initial contribution of Mihini (Fabien Fleutot) (Fabien Fleutot)

Fabien,

Thanks, also for previous answers blowing pretty much in the same horn.
"shared offline..." sounds a bit strange and would leave devices decoupled from vital metadata like what "speed: 33" actually means.
Based on your input so far, M3DA is more or less meant to fix and address faults of OMA-DM and act explicitely in the "Device Management", Licensing or Provisioning, space, but has no relevance to "Runtime Operation" of any such device, right?

If that's the case, the approach may be sufficient, otherwise I don't seem to be the only one here who feels it should be refined and improved.

Werner

On Fri, Feb 1, 2013 at 6:00 PM, <m2m-iwg-request@xxxxxxxxxxx> wrote:
Send m2m-iwg mailing list submissions to
        m2m-iwg@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://dev.eclipse.org/mailman/listinfo/m2m-iwg
or, via email, send a message with subject or body 'help' to
        m2m-iwg-request@xxxxxxxxxxx

You can reach the person managing the list at
        m2m-iwg-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of m2m-iwg digest..."


Today's Topics:

   1. Re: M3DA protocol proposed as part of initial contribution of
      Mihini (Fabien Fleutot) (Fabien Fleutot)


----------------------------------------------------------------------

Message: 1
Date: Fri, 1 Feb 2013 15:56:14 +0100
From: Fabien Fleutot <fleutot@xxxxxxxxx>
To: m2m Industry Working Group <m2m-iwg@xxxxxxxxxxx>
Subject: Re: [m2m-iwg] M3DA protocol proposed as part of initial
        contribution of Mihini (Fabien Fleutot)
Message-ID:
        <CAAOFXS9tQT3gM8+hedJ9PuQqUqwe0osD3ck8t5FpnK-YA_MtOA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

M3DA is about shaving bytes off, when bandwidth cost is the central issue.
Cases where the bandwidth/resilience compromise--e.g. for aerospace or some
automotive applications--are perfectly legitimate, but they're not what
M3DA tries to address.  We use M3DA with some metadata, which happen to
include measurement units, but those are shared offline, not over M3DA.

The most typical use case is that of a GSM gateway, which exchanges data
with a unique server, where its authentication credentials have been
provisioned offline. If a server migration ever needs to occur, offline
metadata must be moved together with the credentials.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dev.eclipse.org/mailman/private/m2m-iwg/attachments/20130201/6077d1ad/attachment.html>

------------------------------

_______________________________________________
m2m-iwg mailing list
m2m-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/m2m-iwg


End of m2m-iwg Digest, Vol 16, Issue 3
**************************************

Back to the top