attachment
<div dir="ltr"><div><div><div>Hi,<br><br></div>New work on an HTTP Authentication method using SASL.<br><br></div>Cheers,<br></div>- Ira<br><br clear="all"><div><div><div><div><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br>May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div></div></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Rick van Rein</b> <span dir="ltr"><<a href="mailto:rick@openfortress.nl">rick@openfortress.nl</a>></span><br>Date: Tue, Aug 15, 2017 at 3:08 AM<br>Subject: [saag] Where-to I-Ds: HTTP Auth with SASL, EAP method for SASL<br>To: <a href="mailto:saag@ietf.org">saag@ietf.org</a><br><br><br>Hello SAAG,<br>
<br>
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?<br>
<br>
<a href="https://datatracker.ietf.org/doc/draft-vanrein-httpauth-sasl/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/<wbr>doc/draft-vanrein-httpauth-<wbr>sasl/</a><br>
<br>
This one explains how SASL can be used as an HTTP Auth mechanism.<br>
This turns out to be beneficial for SASL as well as HTTP.<br>
<br>
<a href="https://datatracker.ietf.org/doc/draft-vanrein-eap-sasl/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/<wbr>doc/draft-vanrein-eap-sasl/</a><br>
<br>
<br>
This one allows the various front-ends that use SASL to relay the<br>
interaction to a backend over EAP, which in turn might be carried<br>
over Diameter or RADIUS.<br>
<br>
<br>
I was advised to ask for directions here, so if you have suggestions<br>
than I would love to hear them.<br>
<br>
FYI, EAP requires a specification and an expert review, so it could<br>
be an independent submission. I currently think that would be best.<br>
<br>
And, HTTP Auth through SASL registers an Authentication Scheme, for<br>
which IETF Review is the standard.<br>
<br>
<br>
Thank you,<br>
<br>
Rick van Rein<br>
InternetWide.org / ARPA2.net / OpenFortress.nl<br>
<br>
______________________________<wbr>_________________<br>
saag mailing list<br>
<a href="mailto:saag@ietf.org">saag@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/saag" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/saag</a><br>
</div><br></div></div></div></div></div>