Subject: [Taps] Weekly github digest (TAPS GitHub Activity Digest)

From: TAPS WG status robot <[email-masked]>
Date: Fri, 10 May 2019 08:00:07 +0000

Issues
------
* ietf-tapswg/api-drafts (+1/-4/💬24)
  1 issues created:
  - Issues with framers (by MaxF12)
    https://github.com/ietf-tapswg/api-drafts/issues/322 

  9 issues received 24 new comments:
  - #308 Treatment of optional transport properties (8 by philsbln, mwelzl, gorryfair, MaxF12)
    https://github.com/ietf-tapswg/api-drafts/issues/308 [Implementation] 
  - #315 Default for Control checksum coverage (5 by britram, abrunstrom, gorryfair, philsbln)
    https://github.com/ietf-tapswg/api-drafts/issues/315 [API] 
  - #286 Interface draft should describe a way to express transport-level padding for messages (4 by britram, gorryfair, philsbln, csperkins)
    https://github.com/ietf-tapswg/api-drafts/issues/286 [API] [discuss] 
  - #305 Protocol stacks that are not equivalent (2 by gorryfair, MaxF12)
    https://github.com/ietf-tapswg/api-drafts/issues/305 
  - #322 Issues concerning framers (1 by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/issues/322 
  - #269 Clarify multi-streaming can cause that ConnectionReceived events can be fired from pre-connection used for initate() (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/269 [API] [Architecture] [help wanted] [ready for text] 
  - #304 Clarify mapping of Connection to multiple flows (1 by philsbln)
    https://github.com/ietf-tapswg/api-drafts/issues/304 [Architecture] 
  - #314 Default for Use 0-RTT session establishment (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/314 [API] [discuss] 
  - #287 Consider explicitly handling connection coalescing (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/287 

  4 issues closed:
  - Consider explicitly handling connection coalescing https://github.com/ietf-tapswg/api-drafts/issues/287 
  - Interface draft should describe a way to express transport-level padding for messages https://github.com/ietf-tapswg/api-drafts/issues/286 [API] [discuss] 
  - Reusing Preconnections? https://github.com/ietf-tapswg/api-drafts/issues/222 [API] [ready for text] 
  - Treatment of optional transport properties https://github.com/ietf-tapswg/api-drafts/issues/308 [Implementation] 

Pull requests
-------------
* ietf-tapswg/api-drafts (+1/-1/💬7)
  1 pull requests submitted:
  - Add details to the Framer Interface (by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/pull/323 

  3 pull requests received 7 new comments:
  - #320 Clarify that a TAPS connection has no 1:1 relation to an underlying transport connection (3 by philsbln, gorryfair, tfpauly)
    https://github.com/ietf-tapswg/api-drafts/pull/320 [API] [Architecture] 
  - #321 Clarify Message References and enable their use for Requests/Response protocols (2 by philsbln, mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/321 [API] 
  - #323 Add details to the Framer Interface (2 by mirjak, tfpauly)
    https://github.com/ietf-tapswg/api-drafts/pull/323 

  1 pull requests merged:
  - Clarify that a TAPS connection has no 1:1 relation to an underlying transport connection
    https://github.com/ietf-tapswg/api-drafts/pull/320 [API] [Architecture] 

Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts