[saag] Where-to I-Ds: HTTP Auth with SASL, EAP method for SASL
Rick van Rein <rick@openfortress.nl> Tue, 15 August 2017 07:08 UTC
Return-Path: <rick@openfortress.nl>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBAF132511 for <saag@ietfa.amsl.com>; Tue, 15 Aug 2017 00:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 934paoxOQnrM for <saag@ietfa.amsl.com>; Tue, 15 Aug 2017 00:08:19 -0700 (PDT)
Received: from lb1-smtp-cloud7.xs4all.net (lb1-smtp-cloud7.xs4all.net [194.109.24.24]) (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 7976F132513 for <saag@ietf.org>; Tue, 15 Aug 2017 00:08:16 -0700 (PDT)
Received: from airhead.local ([IPv6:2001:980:93a5:1:292e:13c1:776d:d434]) by smtp-cloud7.xs4all.net with ESMTPSA id hVxUdKURYAr7rhVxWd4ffr; Tue, 15 Aug 2017 09:08:14 +0200
Message-ID: <59929DDC.2000407@openfortress.nl>
Date: Tue, 15 Aug 2017 09:08:12 +0200
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: saag@ietf.org
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfEySYfIJhBxHraINv3AmxWgVfKG3EeXiPRvnd9j6m+DjhqwLKyse0qMdjuILoHgVyqJYTxFZK60epRwE42/z6Gw6akJj5KfDw3e0fbZwb2432HZNWX8L vC70H6XtuKX2MQfZ7BVhoy54bcDZAbiNFRygU8gG/hCwIA2UTb0WkgC0ixv3fZyxiMC/Y3ITchW82z8uYnHnueMDTz5ukeEUeVjrL51HyoVLBK5TudJgfIK5 jEuOv6T91xE5CXZxX+UmmHBEcp48ZoqRQEWE36LKpUo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/stEf0BxTPKGEJq-2RDrlKj1rxRc>
Subject: [saag] Where-to I-Ds: HTTP Auth with SASL, EAP method for SASL
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Aug 2017 07:08:23 -0000
Hello SAAG, I have just posted two I-Ds and am looking where to send them, since the HTTP Auth WG and EAP WG have both been concluded. Could you advise me? https://datatracker.ietf.org/doc/draft-vanrein-httpauth-sasl/ This one explains how SASL can be used as an HTTP Auth mechanism. This turns out to be beneficial for SASL as well as HTTP. https://datatracker.ietf.org/doc/draft-vanrein-eap-sasl/ This one allows the various front-ends that use SASL to relay the interaction to a backend over EAP, which in turn might be carried over Diameter or RADIUS. I was advised to ask for directions here, so if you have suggestions than I would love to hear them. FYI, EAP requires a specification and an expert review, so it could be an independent submission. I currently think that would be best. And, HTTP Auth through SASL registers an Authentication Scheme, for which IETF Review is the standard. Thank you, Rick van Rein InternetWide.org / ARPA2.net / OpenFortress.nl
- [saag] Where-to I-Ds: HTTP Auth with SASL, EAP me… Rick van Rein