Re: [Txauth] Call for WG name preferences

Mike Jones <Michael.Jones@microsoft.com> Tue, 19 May 2020 21:18 UTC

Return-Path: <Michael.Jones@microsoft.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 7DA4D3A0BFB for <txauth@ietfa.amsl.com>; Tue, 19 May 2020 14:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 5nIzOUCmF7kT for <txauth@ietfa.amsl.com>; Tue, 19 May 2020 14:18:20 -0700 (PDT)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650123.outbound.protection.outlook.com [40.107.65.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DBAF3A0AD4 for <txauth@ietf.org>; Tue, 19 May 2020 14:18:20 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aQ6VIhUmiDUu0CKxRgo2nUUYZ3jGw2BrSL9jyFwZO9WBQFUhlEOTmF/KWGjiL0FZ9KEyqnuvpH3VPVysiBHTksXMKt7PD5qRYf0nAD1/sicjzeGdErr2QlIyLz4OFHvbBoyC/1DrKbNW7Q9cf3BtJ9OTRf5ChX6hbt1Rq6FYUrUDnwTMucc0upgJpRb+aSPXEgF8tLMRgV3GvL9FkTzz0P4BPkgqMMDVHhljXWLA5cxFpBZciemDJIuxmO7Y6a3GSZYZotIhvvNERFWQ1dX/tg5IsuHy+f6bL7fEeHE8qwaORVBNvF1OpMPCrRB6uxFXqftgSDr9IVscNiOusx7Zig==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PzCptIcnEaz4Q+8XlHne43RftcJ92lp5/w73mXjOm3g=; b=EpUtNtOG0C4A4N3T5OMZoxpBvXkBcGSKFbIeLWSqZWCmK+KeXNcyTJX5J/BqIhF6SORuiBVGlKD/jbv5i1eu/hmhCZESDs3gq2Q87iQFjel+9ZgLkggqOIr30RGdyazpIASObjqcWRUjUoXYQIKZfpG6li3wdlMHsVGWj2jmQkt1uO/JwWpjKVbeFE/3fmzOsGO3YK0vGSy75lt5BzX2ChwOmKDt0EhOO1cY3kkfUjGs4dv3caDUfprRK3Mttxq8N0yEqhhfkgdOEBL1mb8/evMwX3jsfEZ5py5+PaNZnbDp5SPI1mwu1fRi0yEMYlGD4sTA4iyhwohGI6ZFqsySKA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PzCptIcnEaz4Q+8XlHne43RftcJ92lp5/w73mXjOm3g=; b=H2xZZ+MFCUoqNbsV+ORuCOFr9reKE/4KSMZ7TTxndeEVn4JufY+ucTjrdK6xKqinYIlgTkWgKUSeurhp72YvnLV+hTCp80vk93FuiNwIOK/DP87ySOoFp7n6mu1iP+HxuebhKoSRXZIe9TkaHZzt060z+c8jITCerPftYoscXcw=
Received: from MN2PR00MB0688.namprd00.prod.outlook.com (2603:10b6:208:199::23) by BL0PR00MB0322.namprd00.prod.outlook.com (2603:10b6:207:1f::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3061.0; Tue, 19 May 2020 21:18:18 +0000
Received: from MN2PR00MB0688.namprd00.prod.outlook.com ([fe80::987e:8a03:43ba:8ad2]) by MN2PR00MB0688.namprd00.prod.outlook.com ([fe80::987e:8a03:43ba:8ad2%6]) with mapi id 15.20.3060.000; Tue, 19 May 2020 21:18:18 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, "txauth@ietf.org" <txauth@ietf.org>
Thread-Topic: Call for WG name preferences
Thread-Index: AQHWLhz1JMnyE3kgbUehUCuB6Mwuwaiv5FeQgAADuQCAAAFUMA==
Date: Tue, 19 May 2020 21:18:18 +0000
Message-ID: <MN2PR00MB0688343C56D4ED7344BED10AF5B90@MN2PR00MB0688.namprd00.prod.outlook.com>
References: <9FD428B4-F3C1-426B-9677-611F5FEC85C8@gmail.com> <MN2PR00MB0688714BB536E943329AAD08F5B90@MN2PR00MB0688.namprd00.prod.outlook.com> <88627C3A-E006-481F-B512-11B0DE218F5C@gmail.com>
In-Reply-To: <88627C3A-E006-481F-B512-11B0DE218F5C@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=7b942006-bd45-4d36-96cc-0000b4db7198; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-05-19T21:16:50Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [50.47.87.252]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 0223fdec-6092-4375-6388-08d7fc3a26a8
x-ms-traffictypediagnostic: BL0PR00MB0322:
x-microsoft-antispam-prvs: <BL0PR00MB0322D956B98B02335F9199C6F5B90@BL0PR00MB0322.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 040866B734
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: HF6fLRYyiT+AMyNH+O2pNGt7dEDTSKZ4uL0OSSQ9JqWtmTayaqWmLRRrPVU4ni7iWOFiXeXRzpCcxBfm5PAHvQ6BgrFgN3w8vPo4PkGEMdgGOzIcvfkOzq+dbTc5pzxoGErC3K2C/JH0LRNlt9zSyZ6UcsEih255y7HoH9YWL5a0Jy9cqaJTYcMuEh4xLSYP3OOGm6oilBlDI/2T27H7xrxH17j2YXA5bonwbdvoqHL3OtVMG55ZBU/rmEJaqmFaw8uzIkc4uwsRCAoBPNn6ItI2GRngZDXX6zd6V3TadvXuTudGvhRPvrctrh46IR+OI8x5KXZ9IZA7NFSIejDqvQza1ACGfwC+5bCzz3PrqnLyAXr/cnV9D8YGvddvPSulw5oWlmBZXqGjqY6TLqSjtw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR00MB0688.namprd00.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(396003)(346002)(366004)(376002)(136003)(39860400002)(10290500003)(82950400001)(82960400001)(64756008)(86362001)(8676002)(5660300002)(8936002)(966005)(8990500004)(71200400001)(55016002)(66446008)(9686003)(53546011)(33656002)(6506007)(478600001)(52536014)(66946007)(76116006)(2906002)(66556008)(316002)(26005)(110136005)(186003)(66476007)(7696005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: bo04PJyhemEAwZNL1ns8Y146oW9+rlwRBYURc3EqFJITdIPfUKSWjq9Of22poJs2FMN/kndkcKtUgVYmGBvMyYoAMGixT7/Lc7/Zfepxq+ZXYQ1lWvGASyvmzXxRj4v48/7x21ENL9Mi+xww6syNZhSi+naOxPCottZGEQ7lvtYkT+JFc/iW3lC16RIrNXJSMZj6FG3TViEsBPRinz4yFZb7zGBRGI17pItcxd2vhtRwEhgc6Bt9pOJ6ryp+AJWC/XV+4KjbqJ+QGIHMKsFJInoQM0ZK263LmsLgUoL3jwTPdav6ZvYOXfOIxxEUaeg2fLRI8aRFnVLLCEg/ZxAtiJMy0bXYb+eZBdIDOarVxN7ACuGgCpOAMOq5i3cEF8aPjnU+ZwREmllk7liqHCAoZB4Nz2LmE933JZqlUMESSfc3/vdkq16ZYs2imebNMdqJGGQdMjV7oBvDgECTJvqEm/iRvVxg5cXD95UdIbiOUaM=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR00MB0688.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0223fdec-6092-4375-6388-08d7fc3a26a8
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 May 2020 21:18:18.1255 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: RSXMeUDEKpfyNkmklWFFt1UN2QuBiTpJkF3b9PVHxhJSnGJ9QwMeTDMcqTE8vjbrUN9P12OZ2UU0JVDJHxN6rA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR00MB0322
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/f6zCI1HTMQlRu0NL42ufF0QQtgM>
Subject: Re: [Txauth] Call for WG name preferences
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: Tue, 19 May 2020 21:18:26 -0000

For convenience of reviewers, resending with the complete list:

    * AAuthZ    Alternative Authorization Protocol (AAuthZ)
    * AZARP    AuthoriZed Access to Resources Protocol
    * AZARAP    AuthoriZation And Resource Access Protocol
    * BeBAuthZ    Back-end Based Authorization Protocol
    * BYOAuthZ    Build-Your-Own Authorization Protocol
    * CPAAP    Comprehensive Privileged Authentication Authorization Protocol
    * DAZARAP    Delegated AuthoriZation And Resource Access Protocol
    * DIYAuthZ    Do-It-Yourself Authorization Protocol
    * GNAP    Grant Negotiation and Authorization Protocol
    * GranPro    GRAnt Negotiation Protocol
    * IDPAuthZ    Intent Driven Protocol for Authorization
    * NIRAD    Negotiation of Intent Registration and Authority Delegation
    * PAuthZ    Protocol for Authorization
    * RefAuthZ    Refactored Authorization Protocol
    * ReAuthZ    Reimagined Authorization Protocol
    * TIAAP    Tokenized Identity and Access Protocol
    * TIDEAuth    Trust via Intent Driven Extension Auth
    * TIDYAuth    Trust via Intent Driven Yield Auth
    * TIEAuth    Trust via Intent Extension Auth
    * TINOA   This Is Not OAuth
    * TXAuth    Testable eXtensible Authorization
    * TxAuth      Transmission of Authority
    * TXAuth      Truly eXtensible Authorization
    * WRAC (Web Resource Authorization Collaboration) - Pronounced like RACK
    * XAuthZ    eXtensible authoriZation protocol

-----Original Message-----
From: Yaron Sheffer <yaronf.ietf@gmail.com> 
Sent: Tuesday, May 19, 2020 2:12 PM
To: Mike Jones <Michael.Jones@microsoft.com>; txauth@ietf.org
Subject: [EXTERNAL] Re: Call for WG name preferences

Hi Mike,

It wasn't added to the previous poll because it came in after the deadline. Everyone is free to propose new names during this poll, so your proposal is also on the table now. However, can you please provide a *single* preferred expansion of the acronym.

Thanks,
	Yaron

On 5/20/20, 00:00, "Mike Jones" <Michael.Jones@microsoft.com> wrote:

    Yaron, it frustrates me that Brian's suggestion has been omitted from the list again:

    	WRAC, pronounced "rack", that expands to Web Resource Authorization Concord (or Compact or Convention) or Collaboration

    It came in before Dick's poll and I asked for it to be added, or at least added to the second round.  Can you please add this to the list and resend, Yaron?

    				Thanks,
    				-- Mike

    -----Original Message-----
    From: Txauth <txauth-bounces@ietf.org> On Behalf Of Yaron Sheffer
    Sent: Tuesday, May 19, 2020 1:35 PM
    To: txauth@ietf.org
    Subject: [EXTERNAL] [Txauth] Call for WG name preferences

    Hi!

    After reviewing the community feedback and discussions with the AD, we’d like to again launch a process to elicit feedback on naming.  Our proposal is below.  We’d appreciate any clarifying questions, proposed improvements or objections by 0800 UTC, Thursday, May 21st .

    Thanks,
    	Yaron and Dick  

    PS, I’m sharing the load with Dick and taking point on this consensus call -- Yaron

    ----

    Before we submit the draft charter [1] to the IESG, we wanted to explore the name of the group. During the chartering discussions, some people objected to the BoF name being the WG name.  We’d like to get consensus on what the WG name should be.  Our first attempt to elicit input [2] wasn’t successful, and this is a second attempt to get consensus from the community.

    To get to consensus, we want to gather preferences on the currently known WG name candidates. Our goal is not to select the most popular name -- it is to select a name everyone can live with and ensure that we understand and weigh any objections there might be with that choice.  To that end, we’d like to elicit your name preferences in the following way:

     (1) In previous discussions, the following candidate names have been voiced (we have listed only these names that received at least one vote previously):

    * AAuthZ    Alternative Authorization Protocol (AAuthZ)
    * AZARP    AuthoriZed Access to Resources Protocol
    * AZARAP    AuthoriZation And Resource Access Protocol
    * BeBAuthZ    Back-end Based Authorization Protocol
    * BYOAuthZ    Build-Your-Own Authorization Protocol
    * CPAAP    Comprehensive Privileged Authentication Authorization Protocol
    * DAZARAP    Delegated AuthoriZation And Resource Access Protocol
    * DIYAuthZ    Do-It-Yourself Authorization Protocol
    * GNAP    Grant Negotiation and Authorization Protocol
    * GranPro    GRAnt Negotiation Protocol
    * IDPAuthZ    Intent Driven Protocol for Authorization
    * NIRAD    Negotiation of Intent Registration and Authority Delegation
    * PAuthZ    Protocol for Authorization
    * RefAuthZ    Refactored Authorization Protocol
    * ReAuthZ    Reimagined Authorization Protocol
    * TIAAP    Tokenized Identity and Access Protocol
    * TIDEAuth    Trust via Intent Driven Extension Auth
    * TIDYAuth    Trust via Intent Driven Yield Auth
    * TIEAuth    Trust via Intent Extension Auth
    * TINOA   This Is Not OAuth
    * TXAuth    Testable eXtensible Authorization
    * TxAuth      Transmission of Authority
    * TXAuth      Truly eXtensible Authorization
    * XAuthZ    eXtensible authoriZation protocol

    We would ask that you consider these names, and respond to the list with your selection of the following two categories:

    * “Wouldn’t Object” -- this is not necessarily your preferred name, but you would be comfortable with it being the name of the WG (choose as many names as you want)
    * “Object” -- you would be uncomfortable with the WG being named in this way (choose as many names as you want; please provide an explanation)

    (2) If your preferred name isn’t in the list per (1), you can send a note to the mailing list stating that you’d like the WG to consider a new name.  Please ensure the name adheres to the previously discussed naming criteria at [3]. We still request that you provide your other preferences and objections.

    (3) If you previously sent in your preferences, but a new name suggestion or someone’s objection changed your mind, then send another message to the mailing list with your revised preferences.  For the purposes of consensus, we’ll assume that everyone who hasn’t commented on a new name introduced per (2) “objects” to it (i.e., we want to hear positive confirmation of preference on new names).

    (4) Please provide your input by 0800 UTC June 4, 2020.

    With that input, our plan is to assess rough consensus in the following way:

    (a) See if there is consensus for a name identified given the “wouldn’t object to being the WG name” preference and the level of “would object” feedback

    (b) If there isn’t clear consensus with (a), but a significantly reduced set of candidates around which there is enthusiasm, the chairs will share the results and request feedback

    (c) If rough consensus appears to be reached through steps (a) – (b), revisit the objections to this candidate name, elicit additional objections and see if they change the consensus.

    Regards,
    	Yaron and Dick

    [1] https://datatracker.ietf.org/doc/charter-ietf-txauth/
    [2] https://mailarchive.ietf.org/arch/msg/txauth/GnTUvD191MGMF63Oe3VTqkYi0Wg/
    [3] https://mailarchive.ietf.org/arch/msg/txauth/lAe06IW4nihUzyTkWVDcq8rnUa8/


    -- 
    Txauth mailing list
    Txauth@ietf.org
    https://www.ietf.org/mailman/listinfo/txauth