Re: [hackathon] One Tax API Hackathon proposal

Eric Rescorla <ekr@rtfm.com> Sat, 25 September 2021 16:23 UTC

Return-Path: <ekr@rtfm.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 D82C23A08B3 for <hackathon@ietfa.amsl.com>; Sat, 25 Sep 2021 09:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20210112.gappssmtp.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 R3OSy2_s_pXY for <hackathon@ietfa.amsl.com>; Sat, 25 Sep 2021 09:23:42 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 2E7F43A08B0 for <hackathon@ietf.org>; Sat, 25 Sep 2021 09:23:42 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id r75so16813781iod.7 for <hackathon@ietf.org>; Sat, 25 Sep 2021 09:23:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0Y8ZsDJ2/8P8YlfWQZvaaavsfdnlULy6am1Kid3N1HQ=; b=gvpVi77YEVHJcTryRPubsTPdKNaROURPAsJuC6JxD5f5MHdXcTN7QXTVmooqVoXdMy 713wT0elgclMGkzwW+Ec4t3nLgTSwoVdp14jpGbY/320MZU0kxxckk/PMWVbKjpQTFHf 9xbYFi1FZWC2Ophrbu0hYTGCVTK+ADvmtypmzkyp0VKPSCw98hT9JXLRXfKOLpeC2AsS uMEu6mXVsyhX/ounujsRGGmfW9pD8T7F4KfVASmkg2gXLJs91KijsX2pQLlnBI20FiU0 hVhMMlA3YU4ZqyddDV3P9hnQUzjYO0lT4lz9DULPMCAC7bJ5V5MDOWY8Py5nIB1WwO7f iPfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0Y8ZsDJ2/8P8YlfWQZvaaavsfdnlULy6am1Kid3N1HQ=; b=J4Kah0KtBUgdH3kjSj0WrPLGX3lQm8ArERNwznA6GIXObcbsE1+fPTBOmn+HT68Mll BqFxVOv0QkrXJ99ayF5IvU1I0uO48XzPAQJl9OKAezCQJOGPlB0v+g4RHjfD8LL60sz0 j74sWbMx2p2XodYqqzoRmvI3j0nAOlfXrV6ld0/sU2FoM+9skfKd9/dA2TRXMfQtf4op jlfj7AcGEfJ6u/V7ubyjbXaNJNb1aBeAnfFpo7OknWyLrOv2chR4jH7T4TammngG4xnK 3pvUYCpFX48BmWPX1Ytx8ae4hcsLu5TxNecMUtgulMHe4d9DGOpzyr56z8GjCfD+Un87 HlfQ==
X-Gm-Message-State: AOAM531iWudJhWLxyWIf1lEih3WKW8zLA+8R0oqOqVVaz8sbUqCXTD3q SWWlv11X1AK3fjW9N5Ejn8kG35vjRUzvXwOu+c0oam6LWyd9Ow==
X-Google-Smtp-Source: ABdhPJxKk6KAXMDmYHriAlXmIT1EeVsE5/dmniMORSUsXW9yuQF7zbkOS164WVIeNDBLiPj3nAMxSEaUKTci73zKGv4=
X-Received: by 2002:a05:6602:1a:: with SMTP id b26mr13611644ioa.0.1632587021402; Sat, 25 Sep 2021 09:23:41 -0700 (PDT)
MIME-Version: 1.0
References: <dd59e549-7739-0cc2-36c2-12bccbc19703@emailplus.org> <fc304942-66a2-6bb0-2f2b-50ec1aa8651d@lear.ch>
In-Reply-To: <fc304942-66a2-6bb0-2f2b-50ec1aa8651d@lear.ch>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 25 Sep 2021 09:23:05 -0700
Message-ID: <CABcZeBP3MVOObN9xkqaZxVQcVmpLbPVNcNHHDPQU2u-rA1dPTQ@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: Benson Muite <benson_muite@emailplus.org>, hackathon <hackathon@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000079e31705ccd449e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/MCD0a6yXmW81UvZWkqBjcw8PgtQ>
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 16:23:48 -0000

On Sat, Sep 25, 2021 at 2:19 AM Eliot Lear <lear@lear.ch> wrote:

> 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.
>

Without taking a position on this proposal, since when do we monitor what
people work on at the hackathon? It's a lot more like a free-for-all than a
BOF and having people work on something at a hackathon certainly isn't any
kind of commitment to take the work on at the IETF.



> 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?
>

These seem like reasonable questions, but I don't agree with the framing
that we "need" to understand them. If you don't want to participate without
an answer, don't do so, but that shouldn't stop others from doing it.

-Ekr


> 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
> >
>
> _______________________________________________
> hackathon mailing list
> hackathon@ietf.org
> https://www.ietf.org/mailman/listinfo/hackathon
> Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe
>