IETF Logo Mail Archive

Re: [lemonade] URLAUTH authorization mechanisms

Barry Leiba <barryleiba@computer.org> Thu, 02 May 2013 19:29 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 B513221F8E96 for <lemonade@ietfa.amsl.com>; Thu, 2 May 2013 12:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.892
X-Spam-Level:
X-Spam-Status: No, score=-101.892 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, 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 tH3EeD14ELZt for <lemonade@ietfa.amsl.com>; Thu, 2 May 2013 12:29:13 -0700 (PDT)
Received: from mail-vb0-x230.google.com (mail-vb0-x230.google.com [IPv6:2607:f8b0:400c:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 8831C21F8E93 for <lemonade@ietf.org>; Thu, 2 May 2013 12:29:06 -0700 (PDT)
Received: by mail-vb0-f48.google.com with SMTP id q16so782714vbe.7 for <lemonade@ietf.org>; Thu, 02 May 2013 12:29:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=DdZajqKAMOc8BCfzKpi/2WwWn1kM4lN19JBmJCKwYss=; b=pj2xzNBIy+pQnqCNbECOj+YewW5VVaam/tw1uU1JAuDW4MgKxP+IbP7r1+TCeFJh8z bRriEGYRpUX5B8euUezXFudT7Z8trI5w7umlLhaWAmslUCaGWoqrRPor3Hb0LyL7ZQkQ qhJuT5hdrXgUD4zAKB+TMifrlU/kehirDaY4F5VBPrFSqcA4RpjKIOFXECjofWOFGxCU qi0lYoT1bBaQwFEOtVluA6XhOoc4I8co3URDW/WL37uAvhr7UY849tRjcSqdHUXH3gFP ZgpdlpK05MzOqu13Ziuu4Tu5cyu9qt3J6YxdeHuz++RwJ2Nw5rMXLjH+cYPIRwXzLRJC /A0w==
MIME-Version: 1.0
X-Received: by 10.58.230.130 with SMTP id sy2mr2669491vec.22.1367522946039; Thu, 02 May 2013 12:29:06 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Thu, 2 May 2013 12:29:05 -0700 (PDT)
In-Reply-To: <60D7D6E9-8A9C-4282-B5E5-F6F9B8B0E124@iki.fi>
References: <60D7D6E9-8A9C-4282-B5E5-F6F9B8B0E124@iki.fi>
Date: Thu, 02 May 2013 15:29:05 -0400
X-Google-Sender-Auth: QZKHviXeg7c8fJJzFsgeZF6Iz7Y
Message-ID: <CAC4RtVDYkvD+2o4hsxX8rgvvxD-xeovBrUe6ZD3+pM1M4A-3gQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Timo Sirainen <tss@iki.fi>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Enhancements to Internet email to support diverse service enivronments <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 19:29:13 -0000

> 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?

There's no need to do this with an errata report, and I would only
Reject such a report anyway, because this isn't an erratum.

Nothing at all needs to happen until there's a new mechanism, and then
the specification for that mechanism can say what needs to be said,
and it can "update" 4467.

Barry

v2.26.15 | Report a Bug | By Email | System Status