[Taps] Weekly github digest (TAPS GitHub Activity Digest)
TAPS WG status robot <tapsbot@magpie.corvid.ch> Fri, 05 July 2019 08:02 UTC
Return-Path: <tapsbot@magpie.corvid.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C10012008D for <taps@ietfa.amsl.com>; Fri, 5 Jul 2019 01:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3oABBh81HvM for <taps@ietfa.amsl.com>; Fri, 5 Jul 2019 01:02:18 -0700 (PDT)
Received: from magpie.corvid.ch (magpie.corvid.ch [46.101.110.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3068A120044 for <taps@ietf.org>; Fri, 5 Jul 2019 01:02:17 -0700 (PDT)
Received: from [127.0.0.1] (helo=magpie.corvid.ch) by magpie.corvid.ch with esmtp (Exim 4.92) (envelope-from <tapsbot@magpie.corvid.ch>) id 1hjJ8Y-0000va-PX for taps@ietf.org; Fri, 05 Jul 2019 08:00:06 +0000
Content-Type: multipart/alternative; boundary="===============1511430570921264507=="
MIME-Version: 1.0
From: TAPS WG status robot <tapsbot@magpie.corvid.ch>
To: taps@ietf.org
Message-Id: <E1hjJ8Y-0000va-PX@magpie.corvid.ch>
Date: Fri, 05 Jul 2019 08:00:06 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/pCZOVUkleJFe1dO1IcVQrKahZPA>
Subject: [Taps] Weekly github digest (TAPS GitHub Activity Digest)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jul 2019 08:02:21 -0000
Issues
------
* ietf-tapswg/api-drafts (+2/-7/💬11)
2 issues created:
- Should "send" return a MessageContex? (by philsbln)
https://github.com/ietf-tapswg/api-drafts/issues/336 [API] [discuss]
- Consider message send API that takes padding policy as input (by chris-wood)
https://github.com/ietf-tapswg/api-drafts/issues/334
8 issues received 11 new comments:
- #334 Consider message send API that takes padding policy as input (3 by philsbln, gorryfair, chris-wood)
https://github.com/ietf-tapswg/api-drafts/issues/334
- #315 Default for Control checksum coverage (2 by britram, mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/315 [API] [ready for text]
- #257 Not all Events are shown in the diagram (1 by mirjak)
https://github.com/ietf-tapswg/api-drafts/issues/257 [Architecture]
- #266 Do we want to add Connection Pools to the Architecture / API (1 by philsbln)
https://github.com/ietf-tapswg/api-drafts/issues/266 [API] [Architecture] [discuss]
- #331 9.1 defaults (1 by britram)
https://github.com/ietf-tapswg/api-drafts/issues/331 [API]
- #304 Clarify mapping of Connection to multiple flows (1 by philsbln)
https://github.com/ietf-tapswg/api-drafts/issues/304 [Architecture]
- #305 Protocol stacks that are not equivalent (1 by philsbln)
https://github.com/ietf-tapswg/api-drafts/issues/305 [Architecture]
- #316 Section 4.2.1 - Transport Properties (1 by britram)
https://github.com/ietf-tapswg/api-drafts/issues/316 [API]
7 issues closed:
- 9.1 defaults https://github.com/ietf-tapswg/api-drafts/issues/331 [API]
- Section 4.2.1 - Transport Properties https://github.com/ietf-tapswg/api-drafts/issues/316 [API]
- Default for Control checksum coverage https://github.com/ietf-tapswg/api-drafts/issues/315 [API] [ready for text]
- Default for Use 0-RTT session establishment https://github.com/ietf-tapswg/api-drafts/issues/314 [API] [discuss]
- msgref is never specified https://github.com/ietf-tapswg/api-drafts/issues/310 [API]
- Clarify mapping of Connection to multiple flows https://github.com/ietf-tapswg/api-drafts/issues/304 [Architecture]
- More editorial author comments on API https://github.com/ietf-tapswg/api-drafts/issues/318 [API]
Pull requests
-------------
* ietf-tapswg/api-drafts (+1/-3/💬6)
1 pull requests submitted:
- Various minor issues - closes #314, #315 #316 and #331 (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/335
4 pull requests received 6 new comments:
- #327 Adding a way of forcing the use of specific protocols (2 by philsbln, britram)
https://github.com/ietf-tapswg/api-drafts/pull/327 [API] [discuss]
- #321 Merge Message References and Message Contexts and enable their use for Requests/Response protocols (2 by mwelzl, tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/321 [API]
- #323 Add details to the Framer Interface (1 by tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/323
- #328 Add Transport Property Profiles (1 by philsbln)
https://github.com/ietf-tapswg/api-drafts/pull/328 [API] [discuss]
3 pull requests merged:
- Various minor issues - closes #314, #315 #316 and #331
https://github.com/ietf-tapswg/api-drafts/pull/335
- Merge Message References and Message Contexts and enable their use for Requests/Response protocols
https://github.com/ietf-tapswg/api-drafts/pull/321 [API]
- Add details to the Framer Interface
https://github.com/ietf-tapswg/api-drafts/pull/323
Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
- [Taps] Weekly github digest (TAPS GitHub Activity… TAPS WG status robot