[kitten] Stating support for HTTP-SASL on the HTTP WG list

Rick van Rein <rick@openfortress.nl> Fri, 27 January 2023 16:01 UTC

Return-Path: <vanrein@vanrein.org>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5DCC14CE2E for <kitten@ietfa.amsl.com>; Fri, 27 Jan 2023 08:01:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.664
X-Spam-Level:
X-Spam-Status: No, score=-0.664 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, PDS_RDNS_DYNAMIC_FP=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZjrjfcULKr1 for <kitten@ietfa.amsl.com>; Fri, 27 Jan 2023 08:01:03 -0800 (PST)
Received: from fame.vanrein.org (2a02-58-157-9b00--7.ip6.tweak.nl [IPv6:2a02:58:157:9b00::7]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB40DC151525 for <kitten@ietf.org>; Fri, 27 Jan 2023 08:01:03 -0800 (PST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id 0B3CC2B022; Fri, 27 Jan 2023 16:01:01 +0000 (UTC)
Date: Fri, 27 Jan 2023 16:01:01 +0000
From: Rick van Rein <rick@openfortress.nl>
To: kitten@ietf.org
Message-ID: <20230127160101.GB635@openfortress.nl>
Mail-Followup-To: kitten@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/fVAD9uiTZn79-yVat5HytVwOWkI>
Subject: [kitten] Stating support for HTTP-SASL on the HTTP WG list
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jan 2023 16:01:08 -0000

Hi,

The HTTP WG is considering our embedding of SASL in HTTP.  I need
IETF consensus to be permitted to say "Authorization: SASL", so
to claim the "SASL" name.

They want to see some list traffic, to get an idea of interest in
this mechanism.  If you have any such feelings, please tell them,
because silence in the busy HTTP WG may cause it to be dropped.

While we implemented for Apache, Nginx and FireFox, I think this
opens excellent opportunities for RESTful and other HTTP protocols.
Would be useful to see those popup on that list.


Thanks!
 -Rick


Spec:  https://datatracker.ietf.org/doc/html/draft-vanrein-httpauth-sasl
WG:    https://datatracker.ietf.org/wg/httpbis/about/