Re: [Dtls-iot] Current dtls-iot charter text - discuss...

Paul Duffy <paduffy@cisco.com> Mon, 10 June 2013 16:34 UTC

Return-Path: <paduffy@cisco.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 1FF6B21F9473 for <dtls-iot@ietfa.amsl.com>; Mon, 10 Jun 2013 09:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 GQv0jXbYPcgp for <dtls-iot@ietfa.amsl.com>; Mon, 10 Jun 2013 09:34:08 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id E024E21F8616 for <dtls-iot@ietf.org>; Mon, 10 Jun 2013 09:34:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3343; q=dns/txt; s=iport; t=1370882048; x=1372091648; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=a4gls62/LwEW5RGu+3yHDISuPqfgmYN+uVTV4xmvga0=; b=duDMYR42Ybc31rlXmbcInQ3T5iu0ftQPANewvuSByzpAdPI8u+TkCi6L N0zKcOwo6J5ZCjegDTBvb2OHvKdGpPGCM9YaFd/hclII1Npg+bFQ6KpfH Pqx32mXMefs0GocKL5C/Ner3g/KkUC6aM6ldyk0+OwFAv6HlBqNxDbB1s 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsAFAKr+tVGQ/khN/2dsb2JhbABagwkwAYM8s12HcoEFFnSCIwEBAQQBAQEeATMZCg0ECxEEAQEBAQMFBhAIAgMCCQMCAQIBFR8JCBMGAgEBBYgEDIxxmzgBkTyBI4xjgQwtBoJDgRcDl0CBKYR2iyODETqBNQ
X-IronPort-AV: E=Sophos;i="4.87,838,1363132800"; d="scan'208";a="14594569"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-4.cisco.com with ESMTP; 10 Jun 2013 16:34:04 +0000
Received: from [10.61.203.51] ([10.61.203.51]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5AGY39Q019875 for <dtls-iot@ietf.org>; Mon, 10 Jun 2013 16:34:03 GMT
Message-ID: <51B5FFF9.9010908@cisco.com>
Date: Mon, 10 Jun 2013 18:34:01 +0200
From: Paul Duffy <paduffy@cisco.com>
Organization: Cisco Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dtls-iot@ietf.org
References: <51AD0949.50806@cs.tcd.ie> <1754A17C-2BA4-44ED-8DAE-C76FC0A32CFE@sensinode.com> <46A1DF3F04371240B504290A071B4DB63D779328@szxeml558-mbx.china.huawei.com> <EAE29B174013F643B5245BA11953A1BE2593E878@011-DB3MPN1-031.MGDPHG.emi.philips.com>
In-Reply-To: <EAE29B174013F643B5245BA11953A1BE2593E878@011-DB3MPN1-031.MGDPHG.emi.philips.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: Re: [Dtls-iot] Current dtls-iot charter text - discuss...
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: paduffy@cisco.com
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: Mon, 10 Jun 2013 16:34:12 -0000

Zigbee IP does not mandate use of CRLs or OCSP for device certificates
(in IEEE 802.1AR-speak ... the UDevID). Supporting these mechanisms for
device certificates on constrained devices and networks, at mass scale,
is highly problematic.

Definitely an area for investigation.


On 6/10/2013 4:48 PM, Keoh, Sye Loong wrote:
> Hi Bert,
>
> Do you know whether the current IoT Deployments, such as Zigbee-IP checks the revocation list? Do you foresee Revocation a potentially serious problem in the future when devices are being replaced, compromised, and when reselling them?
>
> Cheers
> Sye Loong
>
> -----Original Message-----
> From: dtls-iot-bounces@ietf.org [mailto:dtls-iot-bounces@ietf.org] On Behalf Of Bert Greevenbosch
> Sent: vrijdag 7 juni 2013 3:56
> To: Zach Shelby; dtls-iot@ietf.org
> Subject: Re: [Dtls-iot] Current dtls-iot charter text - discuss...
>
> Hi all,
>
> I think the following draft fits in the discussion of DTLS-IOT:
> http://datatracker.ietf.org/doc/draft-greevenbosch-tls-ocsp-lite/
>
> This is quite an early approach to tackling the revocation/authentication issue in a scalable way. Section 4 discusses some requirements.
>
> The draft certainly is to be seen as work in progress, but it addresses an issue that requires due attention.
>
> Best regards,
> Bert
>
>
> -----Original Message-----
> From: dtls-iot-bounces@ietf.org [mailto:dtls-iot-bounces@ietf.org] On Behalf Of Zach Shelby
> Sent: 2013年6月4日 21: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
>
>
>
>
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>
> ________________________________
> 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 mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
> .
>