CORE WG Agenda for IETF 82
Version 2.3


* Thursday, Nov 17, 1520-1720  Afternoon Session II

15:20 Chair Intro
	Blue sheets
	Note Takers
	Jabber Scribes
        Brief WG and Document status (chairs)

15:30 CoAP core protocol (Zach Shelby)
	draft-ietf-core-coap-08.txt

Objectives:
-- Confirm/reach consensus about on-air URI representation
-- Confirm updates to security model -- are we done yet?
-- Discuss disposition of identity/ACL material
-- ...

17:00 Observe and Block (Carsten Bormann)
        draft-ietf-core-observe-03.txt
        draft-ietf-core-block-04.txt
	draft-li-core-coap-size-option-02.txt

Objectives:
-- Close Observe/Block interaction
-- Now what about the size option?
-- Close any other remaining issues

17:20   end


* Friday, Nov 18, 1120-1330  Afternoon Session I/II

11:20 Chair Intro
	Blue sheets
	Note Takers
	Jabber Scribes

11:25 Artificial limitations (Carsten Bormann)
        draft-bormann-coap-misc-09.txt

Objective:
-- determine if we want to pursue any of the proposals in section 2
   (re the 15 options/270 bytes limitations) for inclusion in
   draft-core-coap

11:35 Group Communication (Akbar Rahman)
	draft-rahman-core-groupcomm-07.txt

Objective:
-- adopt IP Multicast as the underlying protocol for CoAP group comm?

11:43 Naming & Data Formats
	draft-arkko-core-dev-urn-01.txt
        draft-jennings-senml-07.txt

Objectives:
-- Introduce new work on a data format and device
   identification that can be used with CoRE
-- Discuss where to continue work

11:57 Discovery
	draft-cao-core-pd-00.txt (Zhen Cao)
	draft-he-core-energy-aware-pd-00.txt (Zhen Cao)
	draft-ma-core-dhcp-pd-00.txt (Zhen Cao)

Objectives:
-- ...

	draft-nieminen-core-service-discovery-01.txt (Markus Isomaki)

Objectives:
-- Is more standards work needed to help *consumers* to configure
   gadgets
   -- without proper UI to succesfully connect to a service provider,
   -- not just the layer 3 IP network?
   This means
   -- setup of parameters such as service provider domain or hostname,
   -- user's credentials.
   Often similar "non-UI" devices are configured via their internal
   web server, but this may be impractical for constrained devices.
-- Is CoAP a proper tool for this (as it is presumably already
   implemented in the device), and how should it be used?

	draft-shelby-core-resource-directory-02.txt

Objectives:
-- Confirm changes since -01
-- Report on interop feedback
-- How to continue working on this?  Which part should go into CoRE?

12:27 Using CoAP (Kerry Lynn)
	draft-vanderstok-core-bc-05.txt

Objectives:
-- (meta) what are the parts of this that could become normative?
-- what are we trying to discover, and how to do it?
-- discuss overlap between service and resource discovery
-- discuss discovery in mixed REST environments (HTTP/CoAP)

12:35 Mapping (Akbar Rahman)
	draft-castellani-core-http-mapping-02.txt

Objectives:
-- Collect technical feedback
-- are all the issues covered?

12:40 Security
	draft-garcia-core-security-03.txt (Sye Loong Keoh)

Objectives:
-- discuss security issues and requirements,
-- identify/prioritize the security issues that we should be solving
   in the WG.

	draft-yegin-coap-security-options-00.txt (Alper Yegin)

Objectives:
-- collect technical input
-- seek acceptance as a WG item [may be a bit early for that]

	draft-sarikaya-core-sbootstrapping-03.txt

13:10 Core-over-X (Kepeng Li)
	draft-li-core-coap-over-sms-00.txt
	draft-becker-core-coap-sms-gprs-00.txt

Objective:
-- identify interest in CoAP over SMS (and GPRS) for M2M

13:20	Next steps

Objective: plan the work up to the fulfillment of our milestones.

13:30   end