Re: Straw-man charter for http-bis -- call for errata/clarifications to 2617

"Robert Sayre" <sayrer@gmail.com> Thu, 31 May 2007 21:39 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 1HtsMf-0007Vj-9J; Thu, 31 May 2007 17:39:25 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HtdDH-0000qC-7H for discuss-confirm+ok@megatron.ietf.org; Thu, 31 May 2007 01:28:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtdDG-0000pv-H3 for discuss@apps.ietf.org; Thu, 31 May 2007 01:28:42 -0400
Received: from wa-out-1112.google.com ([209.85.146.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtdDE-00034I-Kj for discuss@apps.ietf.org; Thu, 31 May 2007 01:28:41 -0400
Received: by wa-out-1112.google.com with SMTP id k22so72902waf for <discuss@apps.ietf.org>; Wed, 30 May 2007 22:28:39 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RpgzZjOMx1VO5RDpG3NNRyOUeUh4q1Ztg3/SgzLjoksMdOt35enNUpVi7B4pQ4LPuK6VbbvxI9GmQ6yAlHgdzN+yFkq/zpnZwFEJ7D39g15ZnnCYvfh3Gic8ZinLHmi0NR6WrOMtkeRCOeNA6+G0LXTU5wp2dXyd0RHss8hqgII=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IINLBBRoDhXJ5kcYDAqCb/Hh664FF+yvpqxep3I8d8Ts4PRZAtiO9OXou60IdiM1FEHVTXHmN7zxrGXaWlzoH6NW8sNcops6pR2K0x5o8cTqEeWKhvnwD5fiPD8ND6ccGGK+d3ls6GtCPC1/pRHtg5Yy+SifH1V4ZwtLozisDVA=
Received: by 10.115.54.1 with SMTP id g1mr180398wak.1180589319384; Wed, 30 May 2007 22:28:39 -0700 (PDT)
Received: by 10.114.211.7 with HTTP; Wed, 30 May 2007 22:28:39 -0700 (PDT)
Message-ID: <68fba5c50705302228v7f8ab278y50cf38c9f971f0a3@mail.gmail.com>
Date: Thu, 31 May 2007 01:28:39 -0400
From: "Robert Sayre" <sayrer@gmail.com>
To: "Mark Nottingham" <mnot@mnot.net>
Subject: Re: Straw-man charter for http-bis -- call for errata/clarifications to 2617
In-Reply-To: <E21FCD3A-D51A-4C06-B46D-3EA3ED54592B@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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> <C1E6F3CB-49C6-4C0F-955A-3D69D26987C6@mnot.net> <000c01c7a318$7bc243e0$7346cba0$@org> <E21FCD3A-D51A-4C06-B46D-3EA3ED54592B@mnot.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-Mailman-Approved-At: Thu, 31 May 2007 17:39:23 -0400
Cc: Eliot Lear <lear@cisco.com>, Larry Masinter <LMM@acm.org>, Apps Discuss <discuss@apps.ietf.org>, ietf-http-wg@w3.org, Paul Hoffman <phoffman@imc.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

On 5/31/07, Mark Nottingham <mnot@mnot.net> wrote:
>
> Robert's draft is orthogonal to a 2617 update; the idea of that is to
> address the need for MTI security.

My draft is orthogonal to things that are unimplementable, because it
seeks to document what has actually happened, and why it did. It may
be possible to design an MTI scheme for HTTP. So far, the text in my
draft leads me to believe that HTTP authentication is wedged between
graphic design, scalability, and security in such a way that
implementors of a given protocol will never be able to agree on shared
trade-offs. But I have only written what I know. I'm sure the document
can be augmented and corrected.

> It would be interesting to compile issues for 2617 as well, to see
> what the scope of work would be. If we can keep the scope to errata
> and clarifications (i.e., not introducing new schemes), it might be
> doable.

My feeling is that the current schemes can be updated by documenting
the internationalization behavior of popular implementations, but
nothing else is worth doing.

-- 

Robert Sayre

"I would have written a shorter letter, but I did not have the time."