IETF Logo Mail Archive

Re: [hackathon] One Tax API Hackathon proposal

Bob Hinden <bob.hinden@gmail.com> Sat, 25 September 2021 15:19 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: hackathon@ietfa.amsl.com
Delivered-To: hackathon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 909823A16FF for <hackathon@ietfa.amsl.com>; Sat, 25 Sep 2021 08:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9Mi3Qvas-8PL for <hackathon@ietfa.amsl.com>; Sat, 25 Sep 2021 08:19:20 -0700 (PDT)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A6983A16FB for <hackathon@ietf.org>; Sat, 25 Sep 2021 08:19:20 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id o59-20020a9d2241000000b0054745f28c69so15404725ota.13 for <hackathon@ietf.org>; Sat, 25 Sep 2021 08:19:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=WTTPJ2GL3CYK4YW1gKvjBxRB/6jy0nSrw8qKzEza+K4=; b=c/zBamamlhrgqy1X5UNunA/OW35lmkW0OIRJkDoMQdrkNvK/+8a6z88JNtdxbhbuok lWPcLzJ8TUG+ZaYVYsGFi5NCFm8t1ak0cz4svHsWozs3P9R3A2wgkrT23OJhQQW+8gNF 5sBqcxxjMJmyahPWthUYST/gyolCvM5kmxORxA5LEU/lr2JVGWhEZLmG8uj/S7mO5E0H jGD7SwP37L67kHwyqy//WrG4/uwuPUcdLZmoh6H0Em+y1ZyJGSupNPemF+CepK2qRSEa Dx4cmnXF1RP1YTPXbjCoM/evk/l/G9F68AQcH1naayuO2Ap6OOQZrukY2nAe4eP2gLGl 0pLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=WTTPJ2GL3CYK4YW1gKvjBxRB/6jy0nSrw8qKzEza+K4=; b=aQwLmjBMY7ZRqPGuNI4awQ2fogpIoWGk6IiDRW6JYU3kpWdvEVJKElMrjrHfVu+Cay mMfscuX9lp4RRZI95f5P/smYEiMwVW4J9X6Bkh4nrOgBv5JkuYYxWC2sZiUiX9i6hNVL Ln4+a/zXp4OAVb3nT7mqW/q6k4IaFp+mT63vzHAEP7TUPpgzOsH/BsLNrGucmCdqZDV0 kh6ZHtQr2SDb16o/CTVXWcSZKCKmFbuGqUqtbp78+hkN4RCMtW5f4LR4FpE8WCpUqirb 6HKy7JcUDZsVXGyYerkWFLuhNkCZvtjLhx0q3yNEHXL82gJ626Ai4H35cyje/3GETDD0 fFBg==
X-Gm-Message-State: AOAM531KVBTQRYgyo5+xEqW5mQPywLT+Jk0656x+NitPtPFY4OP2jhc5 r0yGSsQatjCzywpzlUn14NgcnzKp7sg=
X-Google-Smtp-Source: ABdhPJyljFfTgaKS74EVMjUfDppwGsIxnuwLckY4w/9h5ZFDnVy1r7Dxf9OPMDy7lZeXhuYD3aknBg==
X-Received: by 2002:a05:6830:165a:: with SMTP id h26mr9540516otr.301.1632583158290; Sat, 25 Sep 2021 08:19:18 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:659:79cc:8a72:95f:360a? ([2601:647:5a00:659:79cc:8a72:95f:360a]) by smtp.gmail.com with ESMTPSA id d68sm1167589otb.55.2021.09.25.08.19.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Sep 2021 08:19:17 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <4A45A5FF-F2F7-4030-8931-0A16BC44DC67@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_680E4A9C-16A2-4334-927A-88FCAE708622"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Sat, 25 Sep 2021 08:19:16 -0700
In-Reply-To: <fc304942-66a2-6bb0-2f2b-50ec1aa8651d@lear.ch>
Cc: Bob Hinden <bob.hinden@gmail.com>, Benson Muite <benson_muite@emailplus.org>, hackathon@ietf.org
To: Eliot Lear <lear@lear.ch>
References: <dd59e549-7739-0cc2-36c2-12bccbc19703@emailplus.org> <fc304942-66a2-6bb0-2f2b-50ec1aa8651d@lear.ch>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/7bx8xzVwt-CD2hHvAWuGygg5Ja8>
Subject: Re: [hackathon] One Tax API Hackathon proposal
X-BeenThere: hackathon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hackathon>, <mailto:hackathon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon/>
List-Post: <mailto:hackathon@ietf.org>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hackathon>, <mailto:hackathon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Sep 2021 15:19:25 -0000

Eliot,

I had the same reaction to reading this proposal.   It is a problem, but pretty far away from anything IETF does.   We don’t usually develop APIs and I don’t read that this is related to any IETF protocol development.

Bob


> On Sep 25, 2021, at 2:18 AM, Eliot Lear <lear@lear.ch> wrote:
> 
> Signed PGP part
> Hi,
> 
> In general I like a low bar for hackathons, but I am not sure that the IETF should take this one on.  For one, it's not clear to me that this isn't more a matter of data models rather than APIs. We also have no experience with handling of this sort of information: this is WAY up the stack.
> 
> But if you're going to do this, we need to understand what code is going to be hacked.  Are the developers from accounting packages going to participate?  Can you lay out a bit more of a landscape here?
> 
> Eliot
> 
> 
> On 25.09.21 11:04, Benson Muite wrote:
>> Hi,
>> 
>> Have proposed a hackathon topic on One Tax API:
>> https://trac.ietf.org/trac/ietf/meeting/wiki/112hackathon
>> Many countries are proposing taxes on e-commerce and also labor services that are supplied from outside their jurisdictions that have been enabled by improvements in internet connectivity. Complying with these requirements can be time consuming and is a trade barrier for trade in items and services that do not require regulatory approval.  Having a standardized API for reporting and paying these electronically would enable compliance at a low cost, especially since automation could be used.  Privacy and security considerations are also important in creating a standard for such an interface. The aim of this hackathon project is to develop a prototype implementation that could become an RFC and be adopted as a standard.
>> 
>> Suggestions and contributions are welcome.
>> 
>> Regards,
>> Benson
>> 
>> _______________________________________________
>> hackathon mailing list
>> hackathon@ietf.org
>> https://www.ietf.org/mailman/listinfo/hackathon
>> Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe
>> 
> 
> 
>

v2.8.7 | Report a Bug | By Email