IETF Logo Mail Archive

Re: [http-auth] Authentication-Info

Julian Reschke <julian.reschke@gmx.de> Sat, 06 December 2014 08:08 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1FA1A86EE for <http-auth@ietfa.amsl.com>; Sat, 6 Dec 2014 00:08:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
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 TEFgcV80aDXd for <http-auth@ietfa.amsl.com>; Sat, 6 Dec 2014 00:08:02 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 283AF1A87DE for <http-auth@ietf.org>; Sat, 6 Dec 2014 00:08:02 -0800 (PST)
Received: from [192.168.2.160] ([84.187.42.179]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MUZKF-1YNKF52rdj-00RIkc; Sat, 06 Dec 2014 09:07:59 +0100
Message-ID: <5482B951.7000007@gmx.de>
Date: Sat, 06 Dec 2014 09:07:45 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
References: <547DB5D1.5040909@gmx.de> <CAGL6ep+1VRALcR1ZGPtOCpsxgpc+aJF2k0s67=-z9CkUhAsADg@mail.gmail.com>
In-Reply-To: <CAGL6ep+1VRALcR1ZGPtOCpsxgpc+aJF2k0s67=-z9CkUhAsADg@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:oGTOYAcVg0b2qzu/bAYPgE0IutX68lK0tSzUnjpKO3iFwX6Fq1z 3cr3tE/rEUZdsobc5vevg3ZrrRDY0pIZtdXzlbcbh/a0BbbHbsBis2pt670OtawyT3gS07b DmvfJVGelEXfmbBxzevIuByCRldpKa2NFGRVcYfeiFA0Zkvj1oTzWsiJ3LfJ1rk4714RApW gBb6nmJU3dkB1meW8aJSw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/http-auth/cLzCfnKLOGdomifWflrIhM0ofK0
Cc: "http-auth@ietf.org" <http-auth@ietf.org>
Subject: Re: [http-auth] Authentication-Info
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-auth/>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Dec 2014 08:08:04 -0000

On 2014-12-06 01:53, Rifaat Shekh-Yusef wrote:
> Hi Julian,
>
> The Digest draft based the definition of the Authentication-Info header
> on the auth-param defined in RFC7235, and it registers the header with
> the Message Header Field Registry.
>
> What else do you think we need to do to make it generic?
>
> Regards,
>   Rifaat

The only remaining thing to do would be to clarify that this header 
field can be used in other auth schemes as well, and to de-couple the 
generic description completely from the Digest-specific aspects...

Best regards, Julian

v2.23.0 | Report a Bug | By Email