CoRE @ IETF94
Draft 0.1.4

Chairs:
Andrew Mcgregor <andrewmcgr@google.com>
Carsten Bormann <cabo@tzi.org>

# Tuesday

TUESDAY, November 3, 2015

0900-1130  Morning Session I
Rm 301  	ART ***	core	Constrained RESTful Environments WG


## Chairs' Intro (10)

  RFC 7641 published
  draft-ietf-core-block status
  recharter progress
  registry:
  -- content-format procedure
  -- option 284 (draft-tcs-coap-no-response-option-12.txt)

## CoAP Maintenance

* CoAP over TCP (15)

    draft-tschofenig-core-coap-tcp-tls-04.txt

    * Closing the length shim discussion
    * What else before we can WGLC?

## WG documents

* HTTP Mapping (5)

    draft-ietf-core-http-mapping-07.txt

    * Fall-out from WGLC

* CoRE Resource Directory (20)

    draft-ietf-core-resource-directory-05.txt

    (also discuss relationship to draft-ietf-core-links-json-03)

* Reusable Interface Definitions for Constrained RESTful Environments (15)

    draft-ietf-core-interfaces-04.txt

    * Trailing slashes in collection URIs?

## Data formats

* SenML (30)

    draft-jennings-core-senml-02.txt

    * Is ASCII charset too strict requirement for data (should allow full UTF-8)?
    * Should we avoid nested arrays in SenML document and just have
      alternating base and measurement objects in array?
    * Should there be "base value" too in the base object?

## Management (45 minutes)

* COMI (20)

    draft-vanderstok-core-comi-08.txt

    * Adding NETCONF RPC

* PATCH (15)

    draft-vanderstok-core-patch-02.txt

    * confirm outcome on error code 4.09
    * PATCH vs. IPATCH -- do we need this?
    * Atomicity

* FETCH, COOL (10)

    draft-bormann-core-coap-fetch-00.txt
    (draft-veillette-core-cool -- missed deadline)

    * Besides PATCH/iPATCH -- is this proliferation of proposed CoAP
      methods healthy?
    * Where does the request payload come from (form relations...)?

## Pub-sub

* Pub-sub (10)

    draft-koster-core-coap-pubsub-03

Σ 150

# Friday

FRIDAY, November 6, 2015

0900-1130  Morning Session I
Rm 302  	ART ***	core	Constrained RESTful Environments WG

## Issues spilling over from T2TRG [1]

* Security implications of delay attacks (20) John Matsson

    draft-mattsson-core-coap-actuators-00.txt

    * an attack and a mitigation when CoAP is used to control
      actuators (Section 2.2 and 3)
    * an attack and a mitigation when CoAP is protected with DTLS
      (Section 2.3)

## Security

* Object Security: OSCOAP, OSCON, DCAF-COSE (30)

    draft-selander-ace-object-security-03
    draft-bergmann-ace-dcaf-cose-00

    * what CoAP features do we want to protect end-to-end?
    * what transformations should proxies be allowed to perform?

## CoAP Maintenance

* CoCoA (15) Carles Gomez, Markku Kojo/Ilpo Järvinen

    draft-bormann-core-cocoa-03.txt

    * Emulation results of CoCoA on NONs
    * Are the new controls for aggregate congestion useful?

    * Quick overview of results from cs.helsinki.fi

## If time permits (10)

	draft-zotti-core-sleepy-nodes-04 2015-09-30


## Flextime (15)

Σ 90

# Documents without slot requests and not on T2TRG agenda either

	draft-savolainen-core-coap-websockets-05 2015-10-01
	draft-silverajan-core-coap-alternative-transports-08 2015-06-20
	draft-silverajan-core-coap-protocol-negotiation-01 2015-09-08