Re: [lemonade] URLAUTH authorization mechanisms
Eric Burger <eburger@standardstrack.com> Thu, 02 May 2013 15:51 UTC
Return-Path: <eburger@standardstrack.com>
X-Original-To: lemonade@ietfa.amsl.com
Delivered-To: lemonade@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C3721F9017 for <lemonade@ietfa.amsl.com>; Thu, 2 May 2013 08:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A8qFEuVmN6-l for <lemonade@ietfa.amsl.com>; Thu, 2 May 2013 08:51:23 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.246.244]) by ietfa.amsl.com (Postfix) with ESMTP id A6E8221F8FFA for <lemonade@ietf.org>; Thu, 2 May 2013 08:51:21 -0700 (PDT)
Received: from [141.161.20.235] (port=50338) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1UXvmW-00032X-7D; Thu, 02 May 2013 08:51:19 -0700
Content-Type: multipart/signed; boundary="Apple-Mail=_507BE3EB-4202-473C-9779-51061AD52C61"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <60D7D6E9-8A9C-4282-B5E5-F6F9B8B0E124@iki.fi>
Date: Thu, 02 May 2013 11:50:48 -0400
Message-Id: <000E4CB9-7687-45F6-B50A-920114820841@standardstrack.com>
References: <60D7D6E9-8A9C-4282-B5E5-F6F9B8B0E124@iki.fi>
To: Timo Sirainen <tss@iki.fi>
X-Mailer: Apple Mail (2.1503)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: lemonade@ietf.org
Subject: Re: [lemonade] URLAUTH authorization mechanisms
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 15:51:27 -0000
Before we go too deep, I wold like to solve two problems with one email. The overarching problem: does anyone care about lemonade? I have not heard boo since 2009 about implementations. So, to find out who cares, it would be interesting to find out who does. Can people let me know if their information is correct, updated, or you are new to implementing lemonade. See http://www.standardstrack.com/ietf/lemonade/Lemonade-Plans.html for what I know about now. On May 2, 2013, at 11:42 AM, Timo Sirainen <tss@iki.fi> wrote: > Only INTERNAL mechanism was specified by RFC 4467, but it made it possible to add more in future. But it doesn't look like there's any easy way for a client to find out which mechanisms are supported? Perhaps there should be an errata saying that URLMECH reply MUST be returned by SELECT/EXAMINE if there are any other mechanisms besides INTERNAL? > > _______________________________________________ > lemonade mailing list > lemonade@ietf.org > https://www.ietf.org/mailman/listinfo/lemonade > Supplemental Web Site: > http://www.standardstrack.com/ietf/lemonade
- [lemonade] URLAUTH authorization mechanisms Timo Sirainen
- Re: [lemonade] URLAUTH authorization mechanisms Eric Burger
- [lemonade] Re: URLAUTH authorization mechanisms Jan Kundrát
- Re: [lemonade] URLAUTH authorization mechanisms Alexey Melnikov
- Re: [lemonade] URLAUTH authorization mechanisms Timo Sirainen
- Re: [lemonade] URLAUTH authorization mechanisms Eric Burger
- [lemonade] Re: URLAUTH authorization mechanisms Jan Kundrát
- Re: [lemonade] URLAUTH authorization mechanisms Dave Cridland
- Re: [lemonade] URLAUTH authorization mechanisms Alexey Melnikov
- Re: [lemonade] URLAUTH authorization mechanisms Barry Leiba