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

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

Issues
------
* ietf-tapswg/api-drafts (+8/-0/💬16)
  8 issues created:
  - Section 7 default (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/319 [API] 
  - More editorial author comments on API (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/318 [API] 
  - The recommended default and can we specify rather than recommend? (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/317 [API] [discuss] 
  -  Section 4.2.1 - Transport Properties (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/316 [API] 
  - Default for Control checksum coverage (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/315 [API] 
  - Default for Use 0-RTT session establishment (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/314 [API] 
  - API Draft author editorial comments (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/313 
  - Detailed author review of Arch text for -03 to prepare -04 (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/312 [Architecture] [ready for text] 

  3 issues received 16 new comments:
  - #317 The recommended default and can we specify rather than recommend? (14 by adfalk, philsbln, mwelzl, gorryfair, MaxF12)
    https://github.com/ietf-tapswg/api-drafts/issues/317 [API] [discuss] 
  - #316  Section 4.2.1 - Transport Properties (1 by philsbln)
    https://github.com/ietf-tapswg/api-drafts/issues/316 [API] 
  - #286 Interface draft should describe a way to express transport-level padding for messages (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/286 [API] [discuss] [help wanted] 

Pull requests
-------------
* ietf-tapswg/api-drafts (+2/-0/💬0)
  2 pull requests submitted:
  - Clarify Message References and enable their use for Requests/Response protocols (by philsbln)
    https://github.com/ietf-tapswg/api-drafts/pull/321 
  - Clarify that a TAPS connection has no 1:1 relation to an underlying transport connection (by philsbln)
    https://github.com/ietf-tapswg/api-drafts/pull/320 [API] [Architecture] 

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