Re: [Dtls-iot] Current dtls-iot charter text - discuss...
"Keoh, Sye Loong" <sye.loong.keoh@philips.com> Tue, 04 June 2013 17:45 UTC
Return-Path: <sye.loong.keoh@philips.com>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ABCB21F9C86 for <dtls-iot@ietfa.amsl.com>; Tue, 4 Jun 2013 10:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.349
X-Spam-Level:
X-Spam-Status: No, score=-4.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVaALPz2EGoS for <dtls-iot@ietfa.amsl.com>; Tue, 4 Jun 2013 10:45:03 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id DA96421F9E79 for <dtls-iot@ietf.org>; Tue, 4 Jun 2013 09:40:17 -0700 (PDT)
Received: from mail115-ch1-R.bigfish.com (10.43.68.235) by CH1EHSOBE003.bigfish.com (10.43.70.53) with Microsoft SMTP Server id 14.1.225.23; Tue, 4 Jun 2013 16:40:16 +0000
Received: from mail115-ch1 (localhost [127.0.0.1]) by mail115-ch1-R.bigfish.com (Postfix) with ESMTP id BD20A36013E; Tue, 4 Jun 2013 16:40:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -31
X-BigFish: VPS-31(zz98dI15d6O9371I9251J542I1432I217bIdd85kzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz8275ch1033IL17326ah1954cbh8275bh8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1155h)
Received: from mail115-ch1 (localhost.localdomain [127.0.0.1]) by mail115-ch1 (MessageSwitch) id 1370364014858511_13068; Tue, 4 Jun 2013 16:40:14 +0000 (UTC)
Received: from CH1EHSMHS007.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.242]) by mail115-ch1.bigfish.com (Postfix) with ESMTP id CFC59300B72; Tue, 4 Jun 2013 16:40:14 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by CH1EHSMHS007.bigfish.com (10.43.70.7) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 4 Jun 2013 16:40:11 +0000
Received: from 011-DB3MPN1-031.MGDPHG.emi.philips.com ([169.254.1.27]) by 011-DB3MMR1-005.MGDPHG.emi.philips.com ([10.128.28.55]) with mapi id 14.02.0328.011; Tue, 4 Jun 2013 16:39:46 +0000
From: "Keoh, Sye Loong" <sye.loong.keoh@philips.com>
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Thread-Topic: [Dtls-iot] Current dtls-iot charter text - discuss...
Thread-Index: AQHOYKGKhgVVfinMhE+wOtz3Va6RyZkllauAgAAsUwA=
Date: Tue, 04 Jun 2013 16:39:45 +0000
Message-ID: <EAE29B174013F643B5245BA11953A1BE2593CE08@011-DB3MPN1-031.MGDPHG.emi.philips.com>
References: <51AD0949.50806@cs.tcd.ie> <1754A17C-2BA4-44ED-8DAE-C76FC0A32CFE@sensinode.com>
In-Reply-To: <1754A17C-2BA4-44ED-8DAE-C76FC0A32CFE@sensinode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.103]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Cc: Zach Shelby <zach@sensinode.com>
Subject: Re: [Dtls-iot] Current dtls-iot charter text - discuss...
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dtls-iot>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2013 17:45:07 -0000
We are working on an I-D to discuss the challenges/problems implementers experienced when deploying DTLS for IoT applications, especially the fragmentation issues, and what kind of DTLS profiles can be defined for IoT application. Meanwhile, we are in the process of updating our Multicast security draft (http://www.ietf.org/id/draft-keoh-tls-multicast-security-00.txt). Cheers Sye Loong -----Original Message----- From: dtls-iot-bounces@ietf.org [mailto:dtls-iot-bounces@ietf.org] On Behalf Of Zach Shelby Sent: dinsdag 4 juni 2013 15:58 To: dtls-iot@ietf.org Subject: Re: [Dtls-iot] Current dtls-iot charter text - discuss... I know there are several people working on new I-Ds related to this activity, please let us know what you are working on and if any help is needed. On Jun 3, 2013, at 10:23 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > Existing work > > http://www.ietf.org/id/draft-hartke-core-codtls-02.txt > http://www.ietf.org/id/draft-tschofenig-lwig-tls-minimal-02.txt > http://www.ietf.org/id/draft-keoh-lwig-dtls-iot-01.txt > http://www.ietf.org/id/draft-keoh-tls-multicast-security-00.txt > http://www.ietf.org/id/draft-ietf-tls-oob-pubkey-07.txt > http://www.ietf.org/id/draft-jennings-core-transitive-trust-enrollment-01.txt Regards, Zach -- Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com @SensinodeIoT Mobile: +358 40 7796297 Twitter: @zach_shelby LinkedIn: http://fi.linkedin.com/in/zachshelby 6LoWPAN Book: http://6lowpan.net ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
- [Dtls-iot] Current dtls-iot charter text - discus… Stephen Farrell
- Re: [Dtls-iot] Current dtls-iot charter text - di… Zach Shelby
- Re: [Dtls-iot] Current dtls-iot charter text - di… Keoh, Sye Loong
- Re: [Dtls-iot] Current dtls-iot charter text - di… Bert Greevenbosch
- Re: [Dtls-iot] Current dtls-iot charter text - di… Keoh, Sye Loong
- Re: [Dtls-iot] Current dtls-iot charter text - di… Paul Duffy
- Re: [Dtls-iot] Current dtls-iot charter text - di… Don Sturek
- Re: [Dtls-iot] Current dtls-iot charter text - di… Keoh, Sye Loong
- Re: [Dtls-iot] Current dtls-iot charter text - di… Zach Shelby
- Re: [Dtls-iot] Current dtls-iot charter text - di… Don Sturek
- Re: [Dtls-iot] Current dtls-iot charter text - di… Bert Greevenbosch
- Re: [Dtls-iot] Current dtls-iot charter text - di… Kumar, Sandeep
- Re: [Dtls-iot] Current dtls-iot charter text - di… Bert Greevenbosch
- Re: [Dtls-iot] Current dtls-iot charter text - di… Kemp, David P.
- Re: [Dtls-iot] Current dtls-iot charter text - di… Kumar, Sandeep
- Re: [Dtls-iot] Current dtls-iot charter text - di… Keoh, Sye Loong
- Re: [Dtls-iot] Current dtls-iot charter text - di… Zach Shelby
- Re: [Dtls-iot] Current dtls-iot charter text - di… Don Sturek
- Re: [Dtls-iot] Current dtls-iot charter text - di… Kemp, David P.
- Re: [Dtls-iot] Current dtls-iot charter text - di… Rene Struik