IETF Logo Mail Archive

Re: [Txauth] Name suggestion for next round...

Dick Hardt <dick.hardt@gmail.com> Thu, 28 May 2020 23:03 UTC

Return-Path: <dick.hardt@gmail.com>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BBC3A0F79 for <txauth@ietfa.amsl.com>; Thu, 28 May 2020 16:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=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 z9hSyhJOBpDY for <txauth@ietfa.amsl.com>; Thu, 28 May 2020 16:03:45 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 C57663A0F7C for <txauth@ietf.org>; Thu, 28 May 2020 16:03:44 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id e4so248367ljn.4 for <txauth@ietf.org>; Thu, 28 May 2020 16:03:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mitdOtoZGG1KsBJcqB+iw7Nf+iaxrjHb8AteWIYvt4k=; b=RA6+8VNkv2Fckaxm2BTA2UoNLXo6ojJPsZ9heTSkj+FDc9zINaU+XetQx2VVE9wndQ xnFw/XoHyzdYkw9aHQ4Cm/k3qUqo/KQ4kYZLHDlW33bryOK/Rl7pw2Rw0W7kSD6vyXXb 8gNgeDASGpJwerIJp4SlpWUw3ZyBf+ylQQlRdsX268FOYPwbsi20X1td/WoNewigZlJF M0gHQZq5Vy0Un1qco+89IVhyvMhXwvMVY03AVf2QtYFJI/btq+25OimmzL7D8RdGJTBX /hPl+HgTrwpNEcnJUPaeNAIYQA0CBxqyDzoQrza8etVmXGRCLFAF5UZg/bsVCsdCuaQX 2VZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mitdOtoZGG1KsBJcqB+iw7Nf+iaxrjHb8AteWIYvt4k=; b=MzZ5/67Z73hXoT3XlfDX4Sw3PPQ5h39z0Dn/BUqIeVyIo3C2dap+WNVWIUW8ef+WeI cwLXaMLaBCg4jrXTAtfNg9qwCKRiMZp6SR3DWwYLNl7A5BSH26HVBwd3LchzDNjJ3lfJ XC837BKuoTo/ovhupsmwCwy62iAn9v6bS+zlrWSkUK+VepzKuVMVVG/n4es9sMG/bk2V 2zDBiXe6sJYxDtuvWGPK9WeXcLyq4Hy0eJy9kwzVm2jiVx3+vouvhmcDOesqPUWYQWhi R/rhS1f5rGe7zfCYmLQ84NXslCMFkoK7eMPmCXZdSt/30mIF8wXH0SZsZ6O5tteabm6N /0ww==
X-Gm-Message-State: AOAM532iWmal42M/E4N6jX5RTAnRCOJoj7dZQGMsmUEGP/Fy1T7QBcOC m37iWCLGfqj5aX3ACzic2ZNh3yIdGgECk7ppjwo=
X-Google-Smtp-Source: ABdhPJzMYzhgLRjg4Gbfns0HSqelg/TIJ2XpJuCosHY47+G/J3fzt+Kc2Sd0DfwBHJ1SH9dCgRObJozZJaAev1JqbSo=
X-Received: by 2002:a2e:9910:: with SMTP id v16mr2706376lji.213.1590707022609; Thu, 28 May 2020 16:03:42 -0700 (PDT)
MIME-Version: 1.0
References: <CAEADennZGfNKh0VMOMihYgkMvjqXygOp=JhO9m9mpLnfsxjJYw@mail.gmail.com> <BB68C005-6CA7-48B3-801B-2117E3A39593@mit.edu> <CAEADenm2MUbHT10wiut8NSV=XqPyJBtHjQp+Md8958DeiSkmtw@mail.gmail.com>
In-Reply-To: <CAEADenm2MUbHT10wiut8NSV=XqPyJBtHjQp+Md8958DeiSkmtw@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 28 May 2020 16:03:16 -0700
Message-ID: <CAD9ie-s_uTE6FPcCaxLpxCRA4dhuRM-JGQvKqDBuNo9iM5MGnQ@mail.gmail.com>
To: Vijay IETF <vijay.ietf@gmail.com>
Cc: Justin Richer <jricher@mit.edu>, txauth@ietf.org
Content-Type: multipart/alternative; boundary="00000000000006462e05a6bd57e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/iBUsFbOfpre_f--h_X7yz4Sk9wo>
Subject: Re: [Txauth] Name suggestion for next round...
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2020 23:03:47 -0000

Vijay

The IETF does not operate by voting, but by rough consensus. Consensus is a
solution where there are no strong objections. It is not the most popular
solution.

Here is a good read:

On Consensus and Humming in the IETF
https://tools.ietf.org/html/rfc7282




ᐧ

On Thu, May 28, 2020 at 8:43 AM Vijay IETF <vijay.ietf@gmail.com> wrote:

> Hi Justin,
>
> Thanks. My bad. Suggesting a name of a company that exists is a
> terrible idea. I should have done my homework. Sorry about that!
>
> Was flooded by DNSOP WG emails and lost track of the cut-off dates and the
> name selection process thread.
>
> I give up. Naming is hard.
>
> I do find the process to "strongly object" in order to eliminate a popular
> vote a bit odd.
>
> Is there a precedent for this mode of selection in any setting within
> IETF? Genuinely curious since I am new to the working internals of IETF.
>
>
> On Thu, 28 May 2020 at 20:07, Justin Richer <jricher@mit.edu> wrote:
>
>> Hi Vijay,
>>
>> Sorry to say this, but according to the process put forward by the
>> chairs, the cut-off for suggesting new names has already passed. Now the
>> group is looking for feedback on the existing list of candidates, not for
>> additional candidates.
>>
>> In addition, AuthX is an existing company name in this space:
>> https://www.authx.com/
>>
>>  — Justin
>>
>> > On May 28, 2020, at 5:38 AM, Vijay IETF <vijay.ietf@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I'd like to suggest AuthX for inclusion in the next round...
>> >
>> > Why AuthX?
>> >
>> > The group's draft charter includes concepts, not in words but perhaps
>> by induction, from the realms of identity, authorization, and
>> authentication.
>> >
>> > 1. The X in AuthX indicates that.
>> > 2. It's simple.
>> > 3. Avoids the unproductive conversations on the semantics of
>> Transaction.
>> > 4. It indicates that the group is open to exploring all things X
>> (known, unknown) wrt identity, authorization, authentication.
>> >
>> > No matter how narrow we try to scope the charter down, those are
>> inescapable and related concepts.
>> >
>> > Witness the massive confusion thrust upon developers arising from OIDC
>> and OAuth2 specifications coming from two different organizations on
>> concepts that in my mind are inseparable from a systems perspective.
>> >
>> > Specifications that are not self contained are confusing at minimum.
>> And do a disservice to the wider community at worst when they punt on
>> something fundamental and related as being out of scope.
>> >
>> > If we are breaking from the past then it behoves upon us to not repeat
>> the mistakes from the past.
>> >
>> > - Vijay
>> > --
>> > Txauth mailing list
>> > Txauth@ietf.org
>> > https://www.ietf.org/mailman/listinfo/txauth
>>
>> --
> Txauth mailing list
> Txauth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>

v2.23.0 | Report a Bug | By Email