Re: Straw-man charter for http-bis

Paul Hoffman <phoffman@imc.org> Wed, 30 May 2007 22:55 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtX4j-000536-AO; Wed, 30 May 2007 18:55:29 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HtX4i-00051f-Ao for discuss-confirm+ok@megatron.ietf.org; Wed, 30 May 2007 18:55:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtX4i-00051T-11 for discuss@apps.ietf.org; Wed, 30 May 2007 18:55:28 -0400
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtX4g-000694-LE for discuss@apps.ietf.org; Wed, 30 May 2007 18:55:28 -0400
Received: from [10.20.30.108] (adsl-66-125-125-65.dsl.pltn13.pacbell.net [66.125.125.65]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4UMtM3f057048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 May 2007 15:55:23 -0700 (MST) (envelope-from phoffman@imc.org)
Mime-Version: 1.0
Message-Id: <p06240866c283b0f79e2e@[10.20.30.108]>
In-Reply-To: <465DEA9C.2060508@gmx.de>
References: <BA772834-227A-4C1B-9534-070C50DF05B3@mnot.net> <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net> <p06240843c2833f4d7f2f@[10.20.30.108]> <465D9142.9050506@gmx.de> <465D987F.5070906@cisco.com> <465DEA9C.2060508@gmx.de>
Date: Wed, 30 May 2007 15:55:19 -0700
To: Julian Reschke <julian.reschke@gmx.de>, Eliot Lear <lear@cisco.com>
From: Paul Hoffman <phoffman@imc.org>
Subject: Re: Straw-man charter for http-bis
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Apps Discuss <discuss@apps.ietf.org>, Mark Nottingham <mnot@mnot.net>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

At 11:20 PM +0200 5/30/07, Julian Reschke wrote:
>Eliot Lear wrote:
>>Julian Reschke wrote:
>>>For instance, RFC2617 needs a revision badly as well (for 
>>>instance, wrt to I18N of usernames and passwords, and, as far as I 
>>>can recall, certain problems with the definition of Digest Auth). 
>>>IMHO; this should occur in a separate working group.
>>
>>The HTTP auth model needs a lot of work.  Creating an update 
>>without addressing it seems to me pointless.
>
>Well, RFC2616 needs updating, so does RFC2617. Why does this need to 
>be the same activity?

If the effort for the two are temporally linked (they have to be done 
at the same time), and there will be a lot of overlap in the groups 
working on the two (that is, HTTP implementers and HTTP weenies are 
needed for both efforts), having two WGs seems like a waste of 
resources.