[Taps] Draft should point at existing implementations
"Philipp S. Tiesel" <philipp@tiesel.net> Mon, 22 July 2019 21:16 UTC
Return-Path: <philipp@tiesel.net>
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 51EEB1200A3 for <taps@ietfa.amsl.com>; Mon, 22 Jul 2019 14:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, URIBL_BLOCKED=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 tnr1RfIi_Znm for <taps@ietfa.amsl.com>; Mon, 22 Jul 2019 14:16:13 -0700 (PDT)
Received: from einhorn-mail.in-berlin.de (einhorn-mail.in-berlin.de [217.197.80.20]) (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 1E3011200B8 for <taps@ietf.org>; Mon, 22 Jul 2019 14:16:12 -0700 (PDT)
X-Envelope-From: philipp@tiesel.net
X-Envelope-To: <taps@ietf.org>
Received: from x-berg.in-berlin.de (x-change.in-berlin.de [217.197.86.40]) by einhorn.in-berlin.de with ESMTPS id x6MLGBgk015435 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <taps@ietf.org>; Mon, 22 Jul 2019 23:16:11 +0200
Received: from [2001:67c:1232:144:61e4:ece:6fb0:5d36] by x-berg.in-berlin.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <philipp@tiesel.net>) id 1hpfdH-0008RE-Lf for taps@ietf.org; Mon, 22 Jul 2019 23:14:08 +0200
From: "Philipp S. Tiesel" <philipp@tiesel.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <2768ADD7-DC1A-4CAA-A627-C328257C52D7@tiesel.net>
Date: Mon, 22 Jul 2019 17:16:03 -0400
To: taps WG <taps@ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/9369qO3m3xGMaVi-klwB7Vcq_gc>
Subject: [Taps] Draft should point at existing implementations
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: Mon, 22 Jul 2019 21:16:15 -0000
Hi, as time did not permit to discuss all open issues in the session today, I’ll take them to the list as proposed. This issue is based on Github issue #145: https://github.com/ietf-tapswg/api-drafts/issues/145 The issue ask for the drafts to point at existing TAPS implementations. It might be useful to reference existing implementations (e.g., Apple NWConnections and PyTAPS) and similar systems (e.g., NEAT, PostSockets, SocketIntents) that where used as input to the TAPS design. Resolution Proposals: a) Add section to appendix b) Add notes to acknowledgements c) Do nothing and close the issue AVE! Philipp S. Tiesel -- Philipp S. Tiesel https://philipp.tiesel.net/
- [Taps] Draft should point at existing implementat… Philipp S. Tiesel
- Re: [Taps] Draft should point at existing impleme… Michael Welzl