Re: [Taps] Early TAPS Implementation in Go, Feedback Welcome

Thorben Krüger <thorben.krueger@ovgu.de> Thu, 06 January 2022 15:30 UTC

Return-Path: <thorben.krueger@ovgu.de>
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 30EDF3A1146 for <taps@ietfa.amsl.com>; Thu, 6 Jan 2022 07:30:21 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 5VxPbaRXQgsL for <taps@ietfa.amsl.com>; Thu, 6 Jan 2022 07:30:19 -0800 (PST)
Received: from mail.ovgu.de (mail.ovgu.de [141.44.1.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB5243A113C for <taps@ietf.org>; Thu, 6 Jan 2022 07:30:17 -0800 (PST)
Received: from RavenclawTower (port-ip-88-150-57-68.reverse.mdcc-fun.de [88.150.57.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.ovgu.de (Postfix) with ESMTPSA id F2389A01CF; Thu, 6 Jan 2022 16:30:13 +0100 (CET)
References: <87czl7k2rd.fsf@ovgu.de> <12159_1641391400_61D5A527_12159_104_1_8D6F910B-B6E1-4E8F-B1C7-2CF570C34DCA@ericsson.com>
User-agent: mu4e 1.7.0; emacs 27.2
From: Thorben Krüger <thorben.krueger@ovgu.de>
To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>
Cc: taps@ietf.org
Date: Thu, 06 Jan 2022 16:26:11 +0100
In-reply-to: <12159_1641391400_61D5A527_12159_104_1_8D6F910B-B6E1-4E8F-B1C7-2CF570C34DCA@ericsson.com>
Message-ID: <87v8ywj30e.fsf@ovgu.de>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/SsK1quZet6_tTWseO7blCSPMTNY>
Subject: Re: [Taps] Early TAPS Implementation in Go, Feedback Welcome
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: Thu, 06 Jan 2022 15:30:24 -0000

Hi Mirja,

thank you for the quick feedback. I have just created a ticket 
with my most important point of puzzlement: 
https://github.com/ietf-tapswg/api-drafts/issues/1001

Thorben


Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org> 
writes:

> Hi Troben,
>
> thanks for sharing and using the taps API. For the mistakes you 
> found
> I recommend to open issues on github or even create a PR if the
> resolution is straight-forward: https://github.com/ietf-tapswg
>
> Mirja