"IETF servers aren't for testing"
Iljitsch van Beijnum <iljitsch@muada.com> Fri, 05 August 2005 07:45 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0wt8-0006W7-0r; Fri, 05 Aug 2005 03:45:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0wt5-0006VS-VZ for ietf@megatron.ietf.org; Fri, 05 Aug 2005 03:45:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22823 for <ietf@ietf.org>; Fri, 5 Aug 2005 03:45:01 -0400 (EDT)
Received: from srv0010.pine.nl ([213.156.9.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0xQ6-0006F5-VB for ietf@ietf.org; Fri, 05 Aug 2005 04:19:13 -0400
Received: from localhost (localhost [127.0.0.1]) by srv0010.pine.nl (Pine Digital Security Mailer [srv0010.pine.nl]) with ESMTP id D6FFF4358F1 for <ietf@ietf.org>; Fri, 5 Aug 2005 09:44:51 +0200 (CEST)
Received: from srv0010.pine.nl ([127.0.0.1]) by localhost (srv0010.pine.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 87048-01-14 for <ietf@ietf.org>; Fri, 5 Aug 2005 09:44:29 +0200 (CEST)
Received: from [86.255.14.88] (wep-14-88.ietf63.ietf.org [86.255.14.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by srv0010.pine.nl (Pine Digital Security Mailer [srv0010.pine.nl]) with ESMTP id 7168D4358AA for <ietf@ietf.org>; Fri, 5 Aug 2005 09:44:29 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v733)
Content-Transfer-Encoding: 7bit
Message-Id: <90A9AE46-BEB2-4A08-BEA0-65964256574B@muada.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: IETF General Discussion Mailing List <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 05 Aug 2005 09:44:27 +0200
X-Mailer: Apple Mail (2.733)
X-Virus-Scanned: by amavisd-new at pine.nl
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Subject: "IETF servers aren't for testing"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Hi, Yesterday in the plenary in response to a request for making the IETF servers IPv6-capable, I believe Leslie said we shouldn't use IETF servers for testing. In and of itself I fully agree with that statement. However, the assumption that IPv6 is an experimental protocol and enabling it on the various IETF servers should be considered "testing" isn't exactly a glowing endorsement of 10 years of IETF work. It sounds distasteful, but we should really be eating your own dog food. Limiting myself to the www.ietf.org webservers (yes, this address points to two different hosts) it appears this site runs on: Server: Apache/2.0.46 (Red Hat) Server: Apache/2.0.40 (Red Hat Linux) DAV/2 mod_ssl/2.0.40 OpenSSL/ 0.9.7a Even though these Apache versions are 2 - 3 years old (with many vulnerabilities found and fixed in the mean time), they're fully capable of supporting IPv6, as are Red Hat Linux versions of around the same age. It would be a nice way to mark 7 years of RFC 2460 (or 10 years of RFC 1883, both were published in december) and the closing of the IPv6 wg with addition of IPv6 to at least the IETF WWW servers. (BTW a big "yuck" for being behind two-faced DNS here at the IETF meeting venue.) _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- "IETF servers aren't for testing" Iljitsch van Beijnum
- Re: "IETF servers aren't for testing" shogunx
- Re: "IETF servers aren't for testing" Joel Jaeggli
- Re: "IETF servers aren't for testing" Jeroen Massar
- Re: "IETF servers aren't for testing" Bill Sommerfeld
- Re: "IETF servers aren't for testing" Jari Arkko
- Re: "IETF servers aren't for testing" Eric A. Hall
- Re: "IETF servers aren't for testing" Richard Irving
- Re: "IETF servers aren't for testing" Kevin Loch
- Re: "IETF servers aren't for testing" shogunx
- Re: "IETF servers aren't for testing" JORDI PALET MARTINEZ
- Re: "IETF servers aren't for testing" Ole Jacobsen
- Re: "IETF servers aren't for testing" Harald Tveit Alvestrand
- Re: "IETF servers aren't for testing" shogunx
- Re: "IETF servers aren't for testing" Harald Tveit Alvestrand
- Re: "IETF servers aren't for testing" JORDI PALET MARTINEZ
- Re: "IETF servers aren't for testing" shogunx
- Re: "IETF servers aren't for testing" JORDI PALET MARTINEZ
- Re: "IETF servers aren't for testing" shogunx
- Re: "IETF servers aren't for testing" Harald Tveit Alvestrand
- Re: "IETF servers aren't for testing" shogunx
- Re: "IETF servers aren't for testing" JORDI PALET MARTINEZ
- Re: "IETF servers aren't for testing" JORDI PALET MARTINEZ
- Dog Food (was "IETF servers aren't for testing") JFC (Jefsey) Morfin
- Re: "IETF servers aren't for testing" shogunx
- Re: Dog Food (was "IETF servers aren't for testin… shogunx
- Re: "IETF servers aren't for testing" Harald Tveit Alvestrand
- One and a half points (was: Re: "IETF servers are… Spencer Dawkins
- Re: "IETF servers aren't for testing" Brian E Carpenter