[core] LWM2M spec now available for public download ... was Re: Using Yang to describe LWM2M

Hannes Tschofenig <hannes.tschofenig@gmx.net> Wed, 22 June 2016 11:46 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BFD12D0C3 for <core@ietfa.amsl.com>; Wed, 22 Jun 2016 04:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.026
X-Spam-Level:
X-Spam-Status: No, score=-4.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Klt2yJ4jNY2 for <core@ietfa.amsl.com>; Wed, 22 Jun 2016 04:46:14 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E37C12D0D9 for <core@ietf.org>; Wed, 22 Jun 2016 04:46:13 -0700 (PDT)
Received: from [192.168.10.132] ([80.92.114.100]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Mdrph-1b1Zbr1FTZ-00PgvV for <core@ietf.org>; Wed, 22 Jun 2016 13:46:10 +0200
To: "core@ietf.org WG" <core@ietf.org>
References: <570A4583.2030100@tzi.org> <5718A09E.7040607@gmx.net> <BLUPR06MB1763F3B6BDE5240402576758FE6E0@BLUPR06MB1763.namprd06.prod.outlook.com> <20160421174806.GA8710@elstar.local> <571D1E63.9090003@tzi.org> <571DEF4A.50506@gmx.net> <20160425103338.GA17158@elstar.local> <571DF986.6000200@gmx.net> <20160427070744.GA21138@elstar.local>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <576A7A83.8060808@gmx.net>
Date: Wed, 22 Jun 2016 13:46:11 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <20160427070744.GA21138@elstar.local>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="EgfPW9xmGe69L4aiheOXa1oEJLxEMeBfr"
X-Provags-ID: V03:K0:pZXydpYG9Od4Ff+VGbgiCQahTFLSHbUMWKRYvvM+BwQncCPK64R LPMxIaj8SfJSXlunSFkQr1G1gp+GkYj4hnGEnwz6CYoWbmIWElh46997M20dIEPOKb/TrbN 2YpDxbta7tOh2T9vLsZlgMExFJFc0+7rmecHysL8fru+BLi2ArcT94ulHy9AGAgcmrRRVuC Cjgs+y5pJM2jLnqBEDOew==
X-UI-Out-Filterresults: notjunk:1;V01:K0:iZQf4RUT3eI=:OclgjDowNs/nfkyxdBWi2K Vyl3pLrzwU8xznvQZU0BTxa1k63euPnMLLZpr6/Lr7LKKH2VLkDUCK2EENwAqFRS1ytZcDZZT ksqjuhhJoVQl3mROj99Y+EXl7HxNdrbuHFgGgHos1OawuCprBg7Z4WKKMPwmmCvr6HZD/zu+U ny5ZCBEOpRgpVDHvf6vh27KYYUjfLC/xdzhlmOP8Cv+4pKyZzIpK0oxOnnnczt2HQPHiOmqd0 9SKRzxo2tLyjNU6QsUOnP1oba1ztt20ajVc9cuHEI80I6BaAIrwb+gzOdym9qEpOK3HP0qLMF aDHe3sewhpLDHfd33l7Wa2pPGXl5qhGfACsakPVwDfDdnfl5oU78upRrldEVtgumFEwA5m79I C8hirPf3LGG1sZmsGM9c9vB7uwaQ5ri9m7hh1hzme3IRhO+/f4XB4ijt7g5ZI9TmJGocGmFlH Kzu/WcJt2s8r1ODkNTsvHaGalpPP0ln4wX/DxLyQjvsW2Nm9R9k38T31rQFbugSs1mwj7YAOd iNuQ18G5yRTuV/oDumSq0fqnPf9nIgS2M534MMdWV2yFxbtZn5ixYIckwwYmp6aqI3s/sSNaK oeeT67RXh81K6NqUucYE30dQbKWj75ERzUX2jVU1Ii998YN2T8efUsptLYExxTg9QMMvoPO1a FhSb8jU6SYLEv11SxrFZ0m7pf88IFLwJ6Wef+Hknu6dnoLj6EmTXpHUkhlPnZhIeXhm8n6DW2 ZE2ifub4VHaS0UZQB5arbwkEUplwsRzbrCqmLEI2IKVRcJXLgoZ9l8aJqd0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/EvgR6FOIQBu8M5WWXQw7TLvKFfM>
Subject: [core] LWM2M spec now available for public download ... was Re: Using Yang to describe LWM2M
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2016 11:46:16 -0000

I just wanted to follow-up on this discussion in April.

A few of us have worked with OMA to change the access to the LWM2M
specification and it can now be downloaded without having to enter any
personal data or to accept some legal terms prior to the download:

Here is the link:
http://technical.openmobilealliance.org/Technical/Release_Program/docs/LightweightM2M/V1_0-20160407-C/OMA-TS-LightweightM2M-V1_0-20160407-C.pdf

I hope that this will make it easier for others to review the work.

Ciao
Hannes

On 04/27/2016 09:07 AM, Juergen Schoenwaelder wrote:
> On Mon, Apr 25, 2016 at 01:03:34PM +0200, Hannes Tschofenig wrote:
>> Hi Juergen,
>>
>> On 04/25/2016 12:33 PM, Juergen Schoenwaelder wrote:
>>> Hannes,
>>>
>>> whether this YANG fragment makes sense or not I simply do not know
>>> without knowing LWM2M and since there are no open specs there is
>>> little help you can expect. I have no clue about the interaction model
>>> of OMA LWM2M nor do I know what LWM2M_Device is etc.
>>
>> The specs are publically available for download at no cost.
>>
>> Here is the link:
>> http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0
>>
>> You want to look at the 'Technical Specification'.
> 
> They are not open, I have to accept certain legal terms to get
> access. In particular:
> 
>   use all or any part of a Document as part of a specification or
>   standard not emanating from the Licensor without the prior written
>   consent of the Licensor
> 
> I might already need a written consent if I post an example here since
> everything posted to an IETF list may be considered a contribution.
>  
>> The registry for the objects are also public and available in a nicely
>> written page (similar to what IANA provides for the IETF):
>> http://technical.openmobilealliance.org/Technical/technical-information/omna/lightweight-m2m-lwm2m-object-registry
>>
> 
> Looking at examples to infer what the semantics of the schema are is
> not what I am going to spend my time on.
> 
>> There is no permission that needs to be obtained IMHO, if I understand
>> the OMA copyright policy correctly.
> 
> See above.
> 
> /js
>