IETF Logo Mail Archive

Re: [http-auth] Authentication-Info

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Sat, 06 December 2014 13:47 UTC

Return-Path: <rifaat.ietf@gmail.com>
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 B45CA1A037C for <http-auth@ietfa.amsl.com>; Sat, 6 Dec 2014 05:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 LNCBjHRh7fqS for <http-auth@ietfa.amsl.com>; Sat, 6 Dec 2014 05:47:00 -0800 (PST)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19ED11A0248 for <http-auth@ietf.org>; Sat, 6 Dec 2014 05:47:00 -0800 (PST)
Received: by mail-lb0-f171.google.com with SMTP id n15so1880105lbi.30 for <http-auth@ietf.org>; Sat, 06 Dec 2014 05:46:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nosIFRIEZJgwBjnsIBMC27Nhis/e3MjNs1Ujrn+eH4Q=; b=PKWSNj+PS6nLYg8ExVsoNHcEqThkkwCYEVeFzywJgzgk3j6yJUVvw8Raxr7Wzgm6wG fAZ4AWYOs5cUHIXIZkwnOGRcxbV6/AUPkuIs5BFZGDkI/VYP+C9PkS8eD4KHRVpgbEnL l3py0MKPsJ4YQh57uOUTEq8taghoNDONm8Dh18tGnBmBAkZ7/NVxpox5lHL9HVtPbNXh IBJG1PeF+HjNWJuR2Wx76BEFaJsWhV9fkoERQkTdAlZIsGI6BtaaaNbewQ98TlE5cQGi py53N+sPWB6UXVq03Uq3/V8B8wLRpFcR64SyBfu83KwZ+/Ip837kotlc7y1zCoGoNWkZ f4vA==
MIME-Version: 1.0
X-Received: by 10.152.120.167 with SMTP id ld7mr7486526lab.77.1417873618606; Sat, 06 Dec 2014 05:46:58 -0800 (PST)
Received: by 10.114.99.36 with HTTP; Sat, 6 Dec 2014 05:46:58 -0800 (PST)
In-Reply-To: <5482B951.7000007@gmx.de>
References: <547DB5D1.5040909@gmx.de> <CAGL6ep+1VRALcR1ZGPtOCpsxgpc+aJF2k0s67=-z9CkUhAsADg@mail.gmail.com> <5482B951.7000007@gmx.de>
Date: Sat, 06 Dec 2014 08:46:58 -0500
Message-ID: <CAGL6epJRzi_iTpNrQXc_bkPphrm7wY5ooqmVv6AnUHSwzHfq3Q@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: multipart/alternative; boundary="089e012290f25fa1e005098c6d91"
Archived-At: http://mailarchive.ietf.org/arch/msg/http-auth/TED12A9ThzIoNvH-KJaGmUsyo0w
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 13:47:01 -0000

This is a simple change, and much easier than option 1.
I will make the change in the next version of the document along with the
WGLC changes.

Regards,
 Rifaat



On Sat, Dec 6, 2014 at 3:07 AM, Julian Reschke <julian.reschke@gmx.de>
wrote:

> 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