IETF Logo Mail Archive

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

Yaron Sheffer <yaronf.ietf@gmail.com> Thu, 28 May 2020 14:56 UTC

Return-Path: <yaronf.ietf@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 5CBCE3A0F4A for <txauth@ietfa.amsl.com>; Thu, 28 May 2020 07:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, MIME_QP_LONG_LINE=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 4WLSayKiu_Rt for <txauth@ietfa.amsl.com>; Thu, 28 May 2020 07:56:48 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 8AEB23A0F55 for <txauth@ietf.org>; Thu, 28 May 2020 07:56:48 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id w90so246190qtd.8 for <txauth@ietf.org>; Thu, 28 May 2020 07:56:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=GyYCFjgE9wjDoOElFcX+SH9L+kXNvR8TSSKQeWdgd9w=; b=KapjBr3eGE80GVyvCEbzXc0/x/D5GmnkmDFr/kIAnAHhucSPr+nFI9mjOqC/ZY/Rtx ZB3wTD1GxtHTz0U2J7R42r3U6KF96Exc+amtcLfqFvsk2cMStGKvvFx6HRqK5OR3cWAP aXP1sbXz2CtgKUintZOt4Clmb9EcP6IKkczaZ+6HcCke3/lMyM52N188wzKtqQR1e/37 2bl/byVOx/9nFzoCe+3VnxCDrugHGDRODTgsvdmIAMwTaMmXcEQcJI9E76TaJ+UH30WL FYO/yZzkbU8DR+dh2nFVmpak0UKHlgWoqPLU6SKOuH6xdNz0rsOuhwi+5axh/AWzVVCQ jdXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=GyYCFjgE9wjDoOElFcX+SH9L+kXNvR8TSSKQeWdgd9w=; b=BMat7fdpgFmYEsip+HcGftlgFpkdFlxQQ0CBb+LTgBkVNZ7gtNAZTsADZ+/w5zyTrx VRDpRSJK9z1rs712EvJJ8FuoPpDo+ZG/itPqe+NgNhJLt4P0YHxJfrKni6ZN7dTxBjku eMCnC7JqarqL4XWig+sE3JllbbVNsOWf7T1z8bMArHSusybW2/snrOjCNqWERSQsh4ve Npyk2ecy0VmXkCwtYmLTysYMLkZ2PQv1K+BGMYubVR9e2Lq2Bt7zlEst0AXhIAjCqrY4 PWurZ8z7sgF587B8FE8wei6JGd//VZX8fRTYOXZbNBVkxu6VZwDPC9ndEXHikYfp4FaZ AVzw==
X-Gm-Message-State: AOAM533NBvjUW+TyRiYoFazBGOxkdTuxI+Ohc1eT3GN+Uco7ps6/lbHr QdP6DVXE6kQwoulAHtY7X2k=
X-Google-Smtp-Source: ABdhPJw42g6kTm9nHV5FOJ7e8nKuRovvyzf+9R2wXHBlY2gv1kNkgfA5Eh92p/6ROZsg1E2yijJF+A==
X-Received: by 2002:aed:33e5:: with SMTP id v92mr3530678qtd.348.1590677806801; Thu, 28 May 2020 07:56:46 -0700 (PDT)
Received: from [172.26.49.35] (pub-corp-42-8.intuit.com. [91.102.42.8]) by smtp.gmail.com with ESMTPSA id u41sm5718034qte.28.2020.05.28.07.56.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 May 2020 07:56:45 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.37.20051002
Date: Thu, 28 May 2020 17:56:39 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: Justin Richer <jricher@mit.edu>, Vijay IETF <vijay.ietf@gmail.com>
CC: txauth@ietf.org
Message-ID: <DD472F29-2F8A-48F4-BA6D-CB8EA6B051FA@gmail.com>
Thread-Topic: [Txauth] Name suggestion for next round...
References: <CAEADennZGfNKh0VMOMihYgkMvjqXygOp=JhO9m9mpLnfsxjJYw@mail.gmail.com> <BB68C005-6CA7-48B3-801B-2117E3A39593@mit.edu>
In-Reply-To: <BB68C005-6CA7-48B3-801B-2117E3A39593@mit.edu>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/l23_9i5zya-QcmmuulAeAeJxmoE>
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 14:56:59 -0000

Please see here for the latest on the name selection process: https://mailarchive.ietf.org/arch/msg/txauth/Gr_FZOKAmIeZOjPvVK_2JyaVIZY/

The deadline is June 4, 0800 UTC.

Thanks,
	Yaron

On 5/28/20, 17:37, "Txauth on behalf of Justin Richer" <txauth-bounces@ietf.org on behalf of 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