[Taps] Weekly github digest (TAPS GitHub Activity Digest)
TAPS WG status robot <tapsbot@magpie.corvid.ch> Fri, 03 May 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 3B4461200E5 for <taps@ietfa.amsl.com>; Fri, 3 May 2019 01:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 67KcNFdOuGcH for <taps@ietfa.amsl.com>; Fri, 3 May 2019 01:02:17 -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 0A9301200A0 for <taps@ietf.org>; Fri, 3 May 2019 01:02:16 -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 1hMT6z-0007G4-26 for taps@ietf.org; Fri, 03 May 2019 08:00:05 +0000
Content-Type: multipart/alternative; boundary="===============5189834239452166198=="
MIME-Version: 1.0
From: TAPS WG status robot <tapsbot@magpie.corvid.ch>
To: taps@ietf.org
Message-Id: <E1hMT6z-0007G4-26@magpie.corvid.ch>
Date: Fri, 03 May 2019 08:00:05 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/2TvZauf59CkitgDacUBOSVBRq1k>
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, 03 May 2019 08:02:19 -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
- [Taps] Weekly github digest (TAPS GitHub Activity… TAPS WG status robot