RE: Straw-man charter for http-bis

"Larry Masinter" <LMM@acm.org> Thu, 31 May 2007 00:14 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 1HtYIu-0002kg-0X; Wed, 30 May 2007 20:14:12 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HtYIs-0002kb-Vy for discuss-confirm+ok@megatron.ietf.org; Wed, 30 May 2007 20:14:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtYIs-0002kT-Lx for discuss@apps.ietf.org; Wed, 30 May 2007 20:14:10 -0400
Received: from chip2og53.obsmtp.com ([64.18.13.43]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HtYIq-0002K2-S9 for discuss@apps.ietf.org; Wed, 30 May 2007 20:14:10 -0400
Received: from source ([192.150.11.134]) by chip2ob53.postini.com ([64.18.5.12]) with SMTP; Wed, 30 May 2007 17:13:36 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3.adobe.com [192.150.20.198] (may be forged)) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id l4V0CXbg012261; Wed, 30 May 2007 17:12:38 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70]) by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id l4V0DI0g016369; Wed, 30 May 2007 17:13:25 -0700 (PDT)
Received: from namail1.corp.adobe.com ([10.8.192.62]) by fe1.corp.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 May 2007 17:13:20 -0700
Received: from masinterlap06 ([153.32.47.39]) by namail1.corp.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 May 2007 17:13:17 -0700
From: "Larry Masinter" <LMM@acm.org>
To: "'Mark Nottingham'" <mnot@mnot.net>, "'Eliot Lear'" <lear@cisco.com>
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>
In-Reply-To: <C1E6F3CB-49C6-4C0F-955A-3D69D26987C6@mnot.net>
Subject: RE: Straw-man charter for http-bis
Date: Wed, 30 May 2007 17:13:15 -0700
Message-ID: <000c01c7a318$7bc243e0$7346cba0$@org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcejDh3oBPtTP2QjTwCt5VjVvGiV4QACKMAA
Content-Language: en-us
X-OriginalArrivalTime: 31 May 2007 00:13:17.0764 (UTC) FILETIME=[7D27A040:01C7A318]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: 'Paul Hoffman' <phoffman@imc.org>, ietf-http-wg@w3.org, 'Apps Discuss' <discuss@apps.ietf.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

I'm sympathetic to the desire to keep the charter narrow, but I wonder
if it is feasible to update 2616 without updating 2617. I thought
that it was more of a convenience and that the split between
the two was (to some degree) artificial.

If you really want to limit scope, what do you think about
issuing an informational RFC on 'what changes are needed to 2617'
(starting with the Sayre draft, I'd think)? Then 2616bis
could be published and the group rechartered to do the
2617 update (and, if needed, yet another turn of the crank
on 2616bisbis.)

Larry