CoRE @ IETF97 (Agenda v0.3)

(Original on https://github.com/core-wg/ietf97/wiki)

Chairs:

WEDNESDAY

WEDNESDAY, November 16, 2016 1330–1500 Afternoon Session I

Room: Studio 2

Intro (10)

WG drafts

WGLC processing

Abstract:
CoAP over stream transports just finished WGLC, cap it here.
Objective:
Feedback from WGLC, Status update.

Note: this is tentative, remaining from IETF96. (Possibly kram this in in first meeting, as this is related to tcp/tls.)

Abstract:
When multiple transports exist for exchanging CoAP resource representations, this document introduces a way forward for CoAP endpoints to agree upon alternate transport and protocol configurations as well as URIs.
Objective:
Present alternatives, obtain WG consensus and reviewers.

RD

(Get slot request from authors)

Objective:
Progress work?

Security

Abstract:
This memo defines Object Security of CoAP (OSCOAP), a method for application layer protection of message exchanges with CoAP and CBOR Object Signing (COSE).
Objective:
Discuss Updates. Are we ready for an Implementation Draft?

Interfaces

Abstract:
This document defines conditional observation attributes that work with Link Bindings or with simple CoAP Observe.
Objective:
Update on document status.
Abstract:
This document defines a set of reusable REST resource design patterns suitable for use in constrained environments.
Objective:
Update on document status.

Σ 100 out of 90 min

THURSDAY

We are having an informal side meeting on Thursday. No decisions will be made, but we can inform each others and have a more relaxed discussion. (This also removes some of the impact of the conflict with anima on Friday.) We might want to pick up some result at the Friday meeting’s flextime.

THURSDAY, November 17, 2016 1330–1500 Afternoon Session I

Room: Park Ballroom 3

Active work

Objective:
Are there any remaining interactions with RD and with the T2TRG work on hypermedia controls and formats?
Related document:
draft-hartke-t2trg-data-hub

New work

Objective:
Discuss the use of CoAP and the security options
Abstract:
This document describes a method for application layer protection of messages exchanged with the CoAP in a group communication context, based on Object Security of CoAP (OSCOAP) and the CBOR Object Signing and Encryption (COSE) format.

Objective: present the work, ask for reviewers

Abstract:
One node can register an interest on behalf of someone else.
Objective:
Present an idea
Abstract:
Explains how to do CoAP over WebRTC Data Channels.
Objective:
Present an idea

Flextime (30)

Σ 90 out of 90 min

FRIDAY

FRIDAY, November 18, 2016 0930–1130 Morning Session I

Room: Studio 2

SenML

(Get slot request from authors)

Abstract:
This draft introduces a new base time offset attribute to SenML
Objective:
To get the draft adopted. Also to discuss what should happen to the XML and EXI representations (they currently don’t seem to allow extension).

Management

Abstract:
This document describes a network management interface for constrained devices, called CoMI.
Objective:
Explain merge with CoOL and ask for WG adoption.

Other work

Abstract:
Allow a CoAP server to redirect a client to a new URI. The primary use case is to allow a client using multicast CoAP discovery to learn a COAPS endpoint of the server, without the server revealing privacy-sensitive information. This improves security and privacy in environments with untrusted clients.
Objective:
Ask for WG support. OCF wants to do this COAP extension either way, but having it be an IETF item is preferred so it isn’t OCF-specific.
Abstract:
This document is an exercise on translating the LWM2M/IPSO Object model to YANG.
Objective:
Comments, insights.
Related document:
draft-jimenez-t2trg-coap-functionality-lwm2m
Abstract:
This draft proposes an update to the RFC6690 IANA procedures to allow an organisational pre-fix to be assigned.
Objective:
Discuss, possibly adopt

Flextime (10)

minus 10 min for protocol-negotiation

Σ 120 out of 120 min