Agenda for CORE at interim-2012-core-1
agenda-interim-2012-core-1-1

2012-05-16 14:30Z..17:30Z

CoRE Virtual Interim 2012-05-16

Below, find a rough agenda for disposing of 39 tickets.
The guesses for the times are probably somewhat optimistic, so we may
not even get to the end of all tickets.
Still:

Per draft, we distinguish:

-- check defined resolution and go ahead (~ 2 min per)
   The ticket has a defined resolution with non-trivial impact.
   We should check that this is what we want to do.

-- discuss (~ 10 min per)
   The ticket is still in need of a defined resolution.

-- tickets with a clear way forward (optional) (~ 1 min per)
   There is some relatively straightforward work to do, but not
   necessarily here -- speak up if you think discussion is needed.

-- tickets that need more work on the mailing list (~ 1 min per)
   Next interim.

In reverse alphabetical order:

* Call to order (10 min) 14:30Z..14:40Z

-- Notetakers etc.
-- Technical issues
-- Agenda bashing

* Observe (49 min) 14:40Z..15:29Z

-- check defined resolution and go ahead (2 min)

#225  Explain why it is not always possible to react to a RST that is in reply
to a NON (editorial minor)

-- discuss (40 min)

#204  Introduce a minimal version of Pledge (protocol enhancement major)
#217  how fast must the observe clock be able to go? (protocol enhancement
major) #220  Should observe support time series data? (protocol enhancement
minor) #227  Make aborting the previous transaction optional (protocol
enhancement minor)

-- tickets with a clear way forward (optional) (7 min)

#219  Clarify that observe is about eventual consistency (editorial minor)
#221  Occasionally sending CON is not just a security consideration (protocol
defect minor) #223  Fix reordering detection condition description (editorial
minor) #234  Editorial updates to -observe examples (editorial minor) #235 
Avoid extending the base standard retransmission rules (other technical minor)
#236  Clarify the semantics of the "obs" link target attribute (other technical
minor) #237  Multicast -> reference groupcomm draft (editorial minor)

-- tickets that need more work on the mailing list

(none)

* CoAP (59 min) 15:29Z..16:28Z

-- check defined resolution and go ahead (22 min)

#202  Remove the 270 byte artificial limit (protocol defect minor)
#213  Path/Query options minimum length (protocol defect minor)
#214  Adopt vendor-defined option into core-coap (protocol enhancement minor)
#218  Mostly obvious section 5.10.8 fixes (other technical minor)
#222  RawPublicKey identifier (protocol enhancement minor)
#228  Proxying of multicast requests (protocol enhancement minor)
#229  Move sections 10-10.2. out of the "Security Considerations" (editorial
minor) #232  Clarify inclusion of Location options in a 2.01 (Created) response
(editorial minor) #233  Response codes with payload inconsistency (editorial  
trivial #239  Always reserve option delta 15 (other technical minor)

-- discuss (30 min)

#201  Clarify use of retransmission window for duplicate detection (editorial
minor) #215  editorial issues around Congestion Control (editorial major) #230 
Multiple Location options need to be processed as a unit (protocol defect minor)

-- tickets with a clear way forward (optional) (5 min)

#207  Add advice on default values for critical options (editorial minor)
#212  Option numbers 14, 28, 42, ... reserved but usable (editorial minor)
#224  Clarify the concept of end-point (editorial major)
#216  IANA: get Multicast addresses (other technical major)
#226  Clarify which language addresses intermediaries in general vs. forward
proxies specifically (other technical major)

-- tickets that need more work on the mailing list (2 min)

#231  Splitting/combining Location options (other technical minor)
#238  Proxy terminology (editorial minor)

* Block (9 min) 16:28Z..16:37Z

-- check defined resolution and go ahead (6)

#203  Restrict the potential combinations of Block1 and Block2 (protocol defect
major) #210  Disentangle Block and Token (protocol defect major) #211  Signal
provisional responses (atomic Block1) in the response code (protocol defect
major)

-- discuss (0)

-- tickets with a clear way forward (optional) (3)

#206  Clarify that atomic Block1 transfers match per token *and* endpoint
(editorial major) #205  Clarify that Size does not modify the request semantics
beyond adding the size information (editorial minor) #209  Add potential
attacks to security considerations (editorial minor)

-- tickets that need more work on the mailing list

* Non-tickets (38 min) 16:37Z..17:15Z

What do we want to do here, *if* we really have that time?

Link-Format?

* Wrap-up, planning (15 min) 17:15Z..17:30Z