Re: [leshan-dev] alignment with the specification

["Kraus Achim (INST/ESY1)" <Achim.Kraus@xxxxxxxxxxxx>]

Hi Stavros,

> As such I guess there is no strict mapping between spec release and Leshan release. Is that correct?

Yes, that's correct. Open source projects are somehow triggered by the concerns of the individual
Developer and not by the strict mapping to the spec draft/release candidate. From my experience,
there are more issues related to general misunderstandings of LWM2M/COAP than to version specific details.

Mit freundlichen Grüßen / Best regards

Achim Kraus

Bosch Software Innovations GmbH
Communications (INST/ESY1)
Stuttgarter Straße 130
71332 Waiblingen
GERMANY
www.bosch-si.de
www.blog.bosch-si.com 

Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B
Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn



-----Ursprüngliche Nachricht-----
Von: leshan-dev-bounces@xxxxxxxxxxx [mailto:leshan-dev-bounces@xxxxxxxxxxx] Im Auftrag von Stavros Petris
Gesendet: Dienstag, 24. Mai 2016 08:42
An: leshan developer discussions
Betreff: Re: [leshan-dev] alignment with the specification

Hi Achim,


Thanks a lot for clearing out how Leshan is progressing. So I understand that you try to keep up with the spec changes as much as you can.
As such I guess there is no strict mapping between spec release and Leshan release. Is that correct?

Wish I had the time to help you but for now I am having a look at Leshan which is helping a lot to understand the protocol.

BR,
Stavros

On 23/5/2016 6:54 μμ, Kraus Achim (INST/ESY1) wrote:
> Hi Stavros,
>
> there was a post from julien some months ago (20. Jan. 2016):
>
> http://dev.eclipse.org/mhonarc/lists/leshan-dev/msg00405.html
>
> "We tend to support the last published draft with maximum possible backward compatibility. Then once 1.0 is released we can use the registration version parameter (if we decide to support 1.1 draft)."
>
> So the developers try to support the last draft's, but sometimes there just not enough helpers :-).
>
> Mit freundlichen Grüßen / Best regards
>
> Achim Kraus
>
> Bosch Software Innovations GmbH
> Communications (INST/ESY1)
> Stuttgarter Straße 130
> 71332 Waiblingen
> GERMANY
> www.bosch-si.de
> www.blog.bosch-si.com
>
> Registered office: Berlin, Register court: Amtsgericht Charlottenburg, 
> HRB 148411 B
> Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: leshan-dev-bounces@xxxxxxxxxxx 
> [mailto:leshan-dev-bounces@xxxxxxxxxxx] Im Auftrag von Stavros Petris
> Gesendet: Montag, 23. Mai 2016 15:23
> An: leshan-dev@xxxxxxxxxxx
> Betreff: [leshan-dev] alignment with the specification
>
> Hello,
>
> Checking the docs at:
> http://member.openmobilealliance.org/ftp/Public_documents/DM/Lightweig
> htM2M/Permanent_documents/ I can see that there have been regular 
> updates/fixes to the specification.
>
> Does Leshan keep up with the updates of the spec? If not then how can I tell how much of the specification is implemented by Leshan?
>
> BR,
> Stavros
>
> _______________________________________________
> leshan-dev mailing list
> leshan-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://dev.eclipse.org/mailman/listinfo/leshan-dev
> _______________________________________________
> leshan-dev mailing list
> leshan-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://dev.eclipse.org/mailman/listinfo/leshan-dev

_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/leshan-dev