[core] FW: CORE Agenda Ver #3 - IETF 80

"Garcia Morchon, Oscar" <oscar.garcia@philips.com> Fri, 18 March 2011 09:11 UTC

Return-Path: <oscar.garcia@philips.com>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBD773A69F9 for <core@core3.amsl.com>; Fri, 18 Mar 2011 02:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level:
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=0.749, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kC65Ve1t7tCr for <core@core3.amsl.com>; Fri, 18 Mar 2011 02:11:43 -0700 (PDT)
Received: from TX2EHSOBE003.bigfish.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by core3.amsl.com (Postfix) with ESMTP id 4BA603A682E for <core@ietf.org>; Fri, 18 Mar 2011 02:11:43 -0700 (PDT)
Received: from mail156-tx2-R.bigfish.com (10.9.14.251) by TX2EHSOBE003.bigfish.com (10.9.40.23) with Microsoft SMTP Server id 14.1.225.8; Fri, 18 Mar 2011 09:13:12 +0000
Received: from mail156-tx2 (localhost.localdomain [127.0.0.1]) by mail156-tx2-R.bigfish.com (Postfix) with ESMTP id 3161E19F05C7; Fri, 18 Mar 2011 09:13:12 +0000 (UTC)
X-SpamScore: -43
X-BigFish: VPS-43(zz15d6O9251J62a3L542N217bLzz1202hzz8275bh8275dh1033ILz2dh2a8h668h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: KIP:(null); UIP:(null); IPVD:NLI; H:smtpx.philips.com; RD:smtpx.philips.com; EFVD:NLI
Received: from mail156-tx2 (localhost.localdomain [127.0.0.1]) by mail156-tx2 (MessageSwitch) id 1300439583200953_12284; Fri, 18 Mar 2011 09:13:03 +0000 (UTC)
Received: from TX2EHSMHS001.bigfish.com (unknown [10.9.14.248]) by mail156-tx2.bigfish.com (Postfix) with ESMTP id 3F3E61A3805E; Fri, 18 Mar 2011 09:11:48 +0000 (UTC)
Received: from smtpx.philips.com (168.87.56.20) by TX2EHSMHS001.bigfish.com (10.9.99.101) with Microsoft SMTP Server (TLS) id 14.1.225.22; Fri, 18 Mar 2011 09:11:47 +0000
Received: from nlamsexh03.connect1.local (172.16.153.24) by connect1.philips.com (172.16.156.150) with Microsoft SMTP Server (TLS) id 8.3.106.1; Fri, 18 Mar 2011 10:11:46 +0100
Received: from NLCLUEXM03.connect1.local ([172.16.153.29]) by nlamsexh03.connect1.local ([172.16.153.24]) with mapi; Fri, 18 Mar 2011 10:11:46 +0100
From: "Garcia Morchon, Oscar" <oscar.garcia@philips.com>
To: Cullen Jennings <fluffy@cisco.com>, Carsten Bormann <cabo@tzi.org>
Date: Fri, 18 Mar 2011 10:11:44 +0100
Thread-Topic: [core] CORE Agenda Ver #3 - IETF 80
Thread-Index: AcvkvpHfzzrTXaO4TfWm7wuj24Nv+gACmBNwAB2ZldAAACiFoAAB7MpQ
Message-ID: <5F6BB0D9318FCA4083FC774C9A9ECEF68AE2C6317C@NLCLUEXM03.connect1.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5F6BB0D9318FCA4083FC774C9A9ECEF68AE2C6317CNLCLUEXM03con_"
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Cc: core <core@ietf.org>
Subject: [core] FW: CORE Agenda Ver #3 - IETF 80
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 18 Mar 2011 09:11:44 -0000

Dear Cullen and Carsten,

during the last IETF meeting, we shortly discussed the security needs after the second CoRE session and the possibility of a new Internet Draft
describing them.  We have submitted the draft http://datatracker.ietf.org/doc/draft-garcia-core-security/  to feed this discussion.

We think that discussing these requirements and issues is essential for many use cases. In particular, we think that some
BAC applications will not be able to be deployed without addressing them.

We would like to shortly discuss our draft  in Prague to point out important aspects that are not fully addressed.

Regards,

        Oscar.
_________________________________________________________________________

Oscar Garcia-Morchon, Research Scientist,

Distributed Sensor Systems, Philips Research Europe
High Tech Campus 34 - 1.067, 5656 AE Eindhoven, the Netherlands
Tel: +31 40 27-41952, Fax: +31 40 27-46276

E-mail: oscar.garcia@philips.com<mailto:oscar.garcia@philips.com>, www.research.philips.com<http://www.research.philips.com>
_________________________________________________________________________


-----Original Message-----
From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Cullen Jennings
Sent: Thursday 17 March 2011 17:18
To: core WG
Subject: [core] CORE Agenda Ver #3 - IETF 80

Ver 3


Session 1
Admin (10 min)

Link
draft-ietf-core-link-format-03 (5 minutes)

Core
draft-ietf-core-coap-05 (25 minutes)

Block
draft-ietf-core-block-02 (15 minutes)

Observe
draft-ietf-core-observe-02 (25 minutes)

CoAP Security (20 min)
How will draft-ietf-core-coap satisfy BCP 61

Discovery (20 min)
draft-brandt-coap-subnet-discovery-00
draft-bormann-core-simple-server-discovery-00




Session 2

Admin (5 minutes)

Group Communication
draft-rahman-core-groupcomm-04 (10 minutes)

Usages (10 min)
draft-vanderstok-core-bc-03


Mapping (25 minutes)
draft-castellani-core-http-coap-mapping-01
draft-hartke-core-coap-http
draft-moritz-core-soap-over-coap


New Drafts ???? (20 minutes)

Should we have any of the following?

draft-castellani-core-coap-overhead-01
draft-vial-core-link-format-wadl-00
draft-garcia-core-security-01 (late )

Others?







_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core



  ________________________________
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.