Re: Straw-man charter for http-bis

Paul Hoffman <phoffman@imc.org> Wed, 30 May 2007 15:33 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 1HtQB4-00008i-CN; Wed, 30 May 2007 11:33:34 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HtQB2-00008c-Nm for discuss-confirm+ok@megatron.ietf.org; Wed, 30 May 2007 11:33:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtQB2-00008U-EB for discuss@apps.ietf.org; Wed, 30 May 2007 11:33:32 -0400
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtQB1-0001MS-1r for discuss@apps.ietf.org; Wed, 30 May 2007 11:33:32 -0400
Received: from [10.20.30.108] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4UFXTDj099405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 May 2007 08:33:29 -0700 (MST) (envelope-from phoffman@imc.org)
Mime-Version: 1.0
Message-Id: <p06240846c2834902c575@[10.20.30.108]>
In-Reply-To: <465D9142.9050506@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>
Date: Wed, 30 May 2007 08:33:27 -0700
To: Julian Reschke <julian.reschke@gmx.de>
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: 7655788c23eb79e336f5f8ba8bce7906
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 4:59 PM +0200 5/30/07, Julian Reschke wrote:
>I guess the idea was that the more we restrict the scope of what we 
>want to do, the easier it'll be to gather the right group of people 
>to do it.

Fully agree.

>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 proposed charter has:
   * Document the security properties of HTTP and its associated
     mechanisms (e.g., Basic and Digest authentication, cookies, TLS)
     for common applications
So, would obviously-needed changes to the associated mechanisms be in 
scope for the WG, or not?

>Are there any specific extensions you have in mind?

Definitely not. I was asking whether or not we want to clamp down on 
charter creep now or later.