IETF Logo Mail Archive

Re: Straw-man charter for http-bis

der Mouse <mouse@Rodents.Montreal.QC.CA> Sun, 17 June 2007 15:08 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 1HzwMN-0002JQ-2O; Sun, 17 Jun 2007 11:08:11 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HzwMM-0002JK-Pw for discuss-confirm+ok@megatron.ietf.org; Sun, 17 Jun 2007 11:08:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzwMM-0002J7-GM for discuss@apps.ietf.org; Sun, 17 Jun 2007 11:08:10 -0400
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzwMI-0001JB-FY for discuss@apps.ietf.org; Sun, 17 Jun 2007 11:08:10 -0400
Received: (from mouse@localhost) by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id LAA10876; Sun, 17 Jun 2007 11:08:02 -0400 (EDT)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200706171508.LAA10876@Sparkle.Rodents.Montreal.QC.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
Date: Sun, 17 Jun 2007 11:02:47 -0400 (EDT)
To: discuss@apps.ietf.org
Subject: Re: Straw-man charter for http-bis
In-Reply-To: <1182080252.751.41.camel@henriknordstrom.net>
References: <BA772834-227A-4C1B-9534-070C50DF05B3@mnot.net> <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net> <6AE049B9045C00064222693F@[10.1.110.5]> <1181250794.24162.109.camel@henriknordstrom.net> <46696B98.1090201@cisco.com> <1181342059.4818.63.camel@henriknordstrom.net> <8DD2BD5A-9068-43C3-973E-382FAD2E0EA8@osafoundation.org> <1181532224.3389.47.camel@henriknordstrom.net> <466CC26F.90603@cs.utk.edu> <342C5167F40AD28C4ED69C9B@[10.1.110.5]> <1182080252.751.41.camel@henriknordstrom.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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

> Since when do IETF specify client implementation besides what impacts
> the wire protocols?

"grep API" in the RFC index returns 27 lines of hits: to list just the
RFC numbers I see in that list (without searching out the RFC numbers
for the lines that don't begin a listing), 1509 1961 1964 2025 2292
2367 2478 2614 2628 2744 2771 2783 2853 3338 3542 3867 4401 4462 4584
4752.  (2292 particularly irritates me, though for non-IETF reasons.)

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

v2.8.7 | Report a Bug | By Email