[Taps] Weekly github digest (TAPS GitHub Activity Digest)
TAPS WG status robot <tapsbot@magpie.corvid.ch> Fri, 28 February 2020 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 849E73A12BA for <taps@ietfa.amsl.com>; Fri, 28 Feb 2020 00:02:20 -0800 (PST)
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 cN5isWV-t_G3 for <taps@ietfa.amsl.com>; Fri, 28 Feb 2020 00:02:18 -0800 (PST)
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 015A63A0F31 for <taps@ietf.org>; Fri, 28 Feb 2020 00:02:17 -0800 (PST)
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 1j7aZ3-0000CA-9m for taps@ietf.org; Fri, 28 Feb 2020 08:00:05 +0000
Content-Type: multipart/alternative; boundary="===============4133162338131889258=="
MIME-Version: 1.0
From: TAPS WG status robot <tapsbot@magpie.corvid.ch>
To: taps@ietf.org
Message-Id: <E1j7aZ3-0000CA-9m@magpie.corvid.ch>
Date: Fri, 28 Feb 2020 08:00:05 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/W1Gz75QhPUoRaTwfH9XSteVhRt8>
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, 28 Feb 2020 08:02:21 -0000
Issues ------ * ietf-tapswg/api-drafts (+2/-12/💬21) 2 issues created: - Discuss interaction between Listen() and ListenClone() (by tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/508 [API] - More text on clone (by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/507 [Implementation] 14 issues received 21 new comments: - #437 Configuring MP active/passive (3 by gorryfair, tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/437 [API] - #449 Right semantics for batch sending? (2 by tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/449 [API] [ready for text] - #429 selection algorithm (text in API doc) (2 by tfpauly, theri) https://github.com/ietf-tapswg/api-drafts/issues/429 [API] - #472 Arch: 4.2.3 could be misinterpreted as connection migration (2 by gorryfair, theri) https://github.com/ietf-tapswg/api-drafts/issues/472 [Architecture] [ready for text] - #441 Questions on Connection Groups (2 by mwelzl, tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/441 [API] - #447 Is "Singular Transmission" the right term (2 by gorryfair, tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/447 [API] - #418 Use of normative language in Arch (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/418 [Architecture] [discuss] - #440 Why do we use functions to set security parameters... (1 by tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/440 [API] - #486 Appendix A.1. / Adding preference properties (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/486 [API] - #427 API, sec 5: SHOULD add Framers (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/427 [API] [ready for text] - #398 Per-protocol behavior needs to be normative (1 by tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/398 [Implementation] - #438 Retransmit notify (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/438 [API] [ready for text] - #476 Arch: service class influences protocol selection? (1 by theri) https://github.com/ietf-tapswg/api-drafts/issues/476 [Architecture] [ready for text] - #446 Do we need msg-reliable and lifetime? (1 by tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/446 [API] 12 issues closed: - Arch: service class influences protocol selection? https://github.com/ietf-tapswg/api-drafts/issues/476 [Architecture] [ready for text] - Arch: 4.2.3 could be misinterpreted as connection migration https://github.com/ietf-tapswg/api-drafts/issues/472 [Architecture] [ready for text] - selection algorithm (text in API doc) https://github.com/ietf-tapswg/api-drafts/issues/429 [API] - Do we need msg-reliable and lifetime? https://github.com/ietf-tapswg/api-drafts/issues/446 [API] - own subsection for read-only properties? https://github.com/ietf-tapswg/api-drafts/issues/467 [API] [editorial] [ready for text] - Timeout for Aborting Connection https://github.com/ietf-tapswg/api-drafts/issues/462 [API] [ready for text] - ECN property? https://github.com/ietf-tapswg/api-drafts/issues/451 [API] [ready for text] - Message size https://github.com/ietf-tapswg/api-drafts/issues/443 [API] [ready for text] - type of properties https://github.com/ietf-tapswg/api-drafts/issues/434 [API] - Syntax Preconnection https://github.com/ietf-tapswg/api-drafts/issues/426 [API] [ready for text] - Minor issues with Message Contexts https://github.com/ietf-tapswg/api-drafts/issues/408 [API] [ready for text] - Event handlers: MUST they always be registered? (or else..?) https://github.com/ietf-tapswg/api-drafts/issues/404 [API] [ready for text] Pull requests ------------- * ietf-tapswg/api-drafts (+5/-7/💬6) 5 pull requests submitted: - Add security parameters to arch (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/506 [Architecture] - Address #416, add message property example (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/505 [Architecture] - Address #476 (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/504 - Address #472 (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/503 [Architecture] - Clean up unnecessary normative language in arch (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/502 [Architecture] 3 pull requests received 6 new comments: - #497 Refactor Local Address Preference, fixes #436 (3 by tfpauly, theri) https://github.com/ietf-tapswg/api-drafts/pull/497 [API] - #501 First attempt to write some privacy considerations (2 by britram) https://github.com/ietf-tapswg/api-drafts/pull/501 - #487 Make the singular transmission text clearer (1 by adventureloop) https://github.com/ietf-tapswg/api-drafts/pull/487 [Implementation] 7 pull requests merged: - Address #416, add message property example https://github.com/ietf-tapswg/api-drafts/pull/505 [Architecture] - Add justification and normative language, fixes #429 https://github.com/ietf-tapswg/api-drafts/pull/496 [API] - Address #476 https://github.com/ietf-tapswg/api-drafts/pull/504 - Add security parameters to arch https://github.com/ietf-tapswg/api-drafts/pull/506 [Architecture] - Address #472 https://github.com/ietf-tapswg/api-drafts/pull/503 [Architecture] - Minor fixes with messageContexts, fixes #408 https://github.com/ietf-tapswg/api-drafts/pull/495 [API] - Various API fixes https://github.com/ietf-tapswg/api-drafts/pull/500 Repositories tracked by this digest: ----------------------------------- * https://github.com/ietf-tapswg/api-drafts
- [Taps] Weekly github digest (TAPS GitHub Activity… TAPS WG status robot