[IPP] Fwd: [saag] Where-to I-Ds: HTTP Auth with SASL, EAP method for SASL

Ira McDonald <blueroofmusic@gmail.com> Tue, 15 August 2017 13:36 UTC

Return-Path: <ipp-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2D061325E0 for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 15 Aug 2017 06:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.587
X-Spam-Level:
X-Spam-Status: No, score=-1.587 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" 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 PLiJ1iplsEow for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 15 Aug 2017 06:36:57 -0700 (PDT)
Received: from www.pwg.org (www.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3B6132193 for <ipp-archive2@ietf.org>; Tue, 15 Aug 2017 06:36:56 -0700 (PDT)
Received: by www.pwg.org (Postfix, from userid 1002) id 1B7A14780; Tue, 15 Aug 2017 13:36:55 +0000 (UTC)
Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 6FC902688; Tue, 15 Aug 2017 13:36:42 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by www.pwg.org (Postfix, from userid 1002) id DE9FC26E4; Tue, 15 Aug 2017 13:36:40 +0000 (UTC)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) by www.pwg.org (Postfix) with ESMTPS id E1D872634 for <ipp@pwg.org>; Tue, 15 Aug 2017 13:36:37 +0000 (UTC)
Received: by mail-qt0-x233.google.com with SMTP id t37so4289291qtg.5 for <ipp@pwg.org>; Tue, 15 Aug 2017 06:36:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=7kIZ5O3i4cl7qIhMX4ncmDAxta/DwobpRUndcNDmWCw=; b=KmJir1LQfBg92aKz73YC0sAl5UAN3nmt4zti4269PKxyrIvBG702m47s+2OuKgDLd0 fp/daFDrl8PjWeBvlO8jmByZKBhc+9mo4Q0dpGyquR06UmYAjFgjhTOAC9w4gFFOt0Nx gGerdDZkTtugJEnzoXGiwdWM4GbHoE9wcgbhUg/6lOBKa/DLG0t5K8GR6YjUC4cLC49Q APB0sTFPT0+Y8wJeACtAqRGuFYLmE1AXfYutGZcqwjs2lDZFcDpsP8BSgwM9XHHTrAVV BCtP1aYu1FFw0R0YkCSz2O9GxmJonk2dYGzavbKR5c4Ue/4DxVnDs4z1e1wH/kVxQzF/ epXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=7kIZ5O3i4cl7qIhMX4ncmDAxta/DwobpRUndcNDmWCw=; b=TvTSGLP2nNrRdzzdAGA1enawblx1N/hEqhYtDaQPOUXtPYf7Yw+WIJetsj+cE44LQz yW8ghTPfcsKlgLz0Gu6O+fuIbS+sJ+D2kkKSBqFin3EPNNCwijOGMkAQG6lq1dUImVxh W8Cm4O3DbAuv6W1AaK5ozdjQWETBQZUHlCzZbqRkkTLexHDDy+lHLdLRGJtrIGWnwM2Z 2rlIeF4QiRW9gu8No3RIWwSODQup+Z5r0ALOU+skzBKNf1vVg7Oz71IdpVWNzzJejoXl uzPBuvzByExmpVKVeWBP0xrv7yRLV0vWTroaL8qKuoX5HRpDjZypRrr4FNLtTeLf4L4h NaYQ==
X-Gm-Message-State: AHYfb5gi051+3UiILFG+07OcNgnnagaV0kFGVzh6RtE0QaUFEoIOCn+O eqXwaT9sAkdqxgvUnQiVxaSqrKFd/Q==
X-Received: by 10.200.49.230 with SMTP id i35mr35543120qte.113.1502804196646; Tue, 15 Aug 2017 06:36:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.23.135 with HTTP; Tue, 15 Aug 2017 06:36:16 -0700 (PDT)
In-Reply-To: <59929DDC.2000407@openfortress.nl>
References: <59929DDC.2000407@openfortress.nl>
From: Ira McDonald <blueroofmusic@gmail.com>
Date: Tue, 15 Aug 2017 09:36:16 -0400
Message-ID: <CAN40gSuxG_jLnNJHUjDtW+t0HA37cy+CvhPANcq=dHhGZLfPEQ@mail.gmail.com>
To: "ipp@pwg.org" <ipp@pwg.org>, Ira McDonald <blueroofmusic@gmail.com>
Subject: [IPP] Fwd: [saag] Where-to I-Ds: HTTP Auth with SASL, EAP method for SASL
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Printing Protocol Workgroup discussion list <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8392520247545277570=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

Hi,

New work on an HTTP Authentication method using SASL.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
Jan-April: 579 Park Place  Saline, MI  48176  734-944-0094
May-Dec: PO Box 221  Grand Marais, MI 49839  906-494-2434


---------- Forwarded message ----------
From: Rick van Rein <rick@openfortress.nl>
Date: Tue, Aug 15, 2017 at 3:08 AM
Subject: [saag] Where-to I-Ds: HTTP Auth with SASL, EAP method for SASL
To: saag@ietf.org


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 mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag
_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp