[core] OMA LWM2M & Dependencies on IETF CoRE - Requesting
"Subramani, Padmakumar (Nokia - IN)" <padmakumar.subramani@nokia.com> Tue, 19 April 2016 12:34 UTC
Return-Path: <padmakumar.subramani@nokia.com>
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 97A8312DA25 for <core@ietfa.amsl.com>; Tue, 19 Apr 2016 05:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 IkN2xhJyvn80 for <core@ietfa.amsl.com>; Tue, 19 Apr 2016 05:34:51 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpatc-esg-01.alcatel-lucent.com [135.245.18.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BD9612D17C for <core@ietf.org>; Tue, 19 Apr 2016 05:34:51 -0700 (PDT)
Received: from us70tumx1.dmz.alcatel-lucent.com (unknown [135.245.18.13]) by Websense Email Security Gateway with ESMTPS id 1E7C6C4B26034 for <core@ietf.org>; Tue, 19 Apr 2016 12:34:47 +0000 (GMT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (us70tusmtp1.zam.alcatel-lucent.com [135.5.2.63]) by us70tumx1.dmz.alcatel-lucent.com (GMO) with ESMTP id u3JCYnWN003717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <core@ietf.org>; Tue, 19 Apr 2016 12:34:49 GMT
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id u3JCYlZ8024765 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <core@ietf.org>; Tue, 19 Apr 2016 12:34:49 GMT
Received: from SG70XWXCHHUB02.zap.alcatel-lucent.com (135.253.2.47) by US70UWXCHHUB01.zam.alcatel-lucent.com (135.5.2.48) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 19 Apr 2016 08:34:48 -0400
Received: from SG70YWXCHMBA08.zap.alcatel-lucent.com ([169.254.8.20]) by SG70XWXCHHUB02.zap.alcatel-lucent.com ([135.253.2.47]) with mapi id 14.03.0195.001; Tue, 19 Apr 2016 20:34:16 +0800
From: "Subramani, Padmakumar (Nokia - IN)" <padmakumar.subramani@nokia.com>
To: "core@ietf.org" <core@ietf.org>
Thread-Topic: OMA LWM2M & Dependencies on IETF CoRE - Requesting
Thread-Index: AQHRmjfIGgogCuquqUueebPfCi+Lpg==
Date: Tue, 19 Apr 2016 12:34:15 +0000
Message-ID: <30BE9EF0-4A9C-48E6-B158-493E19C30D1E@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.151206
x-originating-ip: [135.253.19.16]
Content-Type: multipart/alternative; boundary="_000_30BE9EF04A9C48E6B158493E19C30D1Ealcatellucentcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/x3fPInv3UJ6sv_cmX-kGbRnnE6g>
Subject: [core] OMA LWM2M & Dependencies on IETF CoRE - Requesting
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: Tue, 19 Apr 2016 12:34:53 -0000
Dear CoRE Working Group Chairs, Hi all, I am co-chair of the OMA Device Management working group, who develops the LWM2M specification. We are currently in the process of defining version 1.1 of the LWM2M protocol and would like to re-use as many IETF specifications as possible. For this purpose we are seeking for further information about the status of the following specifications and their anticipated completion dates. * Publish-Subscribe Broker for the Constrained Application Protocol (CoAP): <draft-koster-core-coap-pubsub-04> * A TCP and TLS Transport for the Constrained Application Protocol (CoAP): <draft-ietf-core-coap-tcp-tls-01> * CoRE Resource Directory: <draft-ietf-core-resource-directory-07> * Block-wise transfers in CoAP: <draft-ietf-core-block-19> Our timeline for completion of LWM2M v1.1 is Dec 2016. We are aware of the milestones page of the IETF working groups and the information about the datatracker but it is nevertheless difficult to determine a completion date. Please let us know if there is anything we can do to accelerate the completion of the above-mentioned specifications. Best Regards, Padhu Principal Product Manager, Industry Standards Customer Experience Management, NOKIA 20th century our best minds went to work on how to conquer nature, 21st century our best minds are working to restore it This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited without the prior consent of its author.
- [core] OMA LWM2M & Dependencies on IETF CoRE - Re… Subramani, Padmakumar (Nokia - IN)