Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Sun, 07 Aug 2005 03:18:22 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 477B43200B5 for ; Sun, 7 Aug 2005 03:18:22 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32315-02 for ; Sun, 7 Aug 2005 03:18:18 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 0CEFB3200AB for ; Sun, 7 Aug 2005 03:18:13 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E1Zio-0000IN-FP; Sat, 06 Aug 2005 21:13:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E1Zil-0000Gy-9m for ietf@megatron.ietf.org; Sat, 06 Aug 2005 21:12:59 -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 VAA23478 for ; Sat, 6 Aug 2005 21:12:57 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E1aGA-0004sh-Cg for ietf@ietf.org; Sat, 06 Aug 2005 21:47:30 -0400 Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1E1Zid-0007W9-W8 for ietf@ietf.org; Sat, 06 Aug 2005 18:12:52 -0700 Message-Id: <6.2.1.2.2.20050806122843.03093eb0@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sun, 07 Aug 2005 03:12:43 +0200 To: ietf@ietf.org From: "JFC (Jefsey) Morfin" In-Reply-To: <90A9AE46-BEB2-4A08-BEA0-65964256574B@muada.com> References: <90A9AE46-BEB2-4A08-BEA0-65964256574B@muada.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Subject: Dog Food (was "IETF servers aren't for testing") X-BeenThere: ietf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ietf-bounces@ietf.org Errors-To: ietf-bounces@ietf.org X-Virus-Scanned: by amavisd-new at alvestrand.no On 02:04 07/08/2005, JORDI PALET MARTINEZ said: > Yes and not ... Real large scale deployment trials only started in > 2001-2002, and it was already using production space. Then we had commercial > deployment, at that time mainly in Asia Pacific and Europe. > > I will say that IPv6 experimental stage was over around 2002-2003, specially > looking at vendors support. Of course, this always depend on "your own > hands-on experience" ;-) Dear Jordi, There could be many criteria to say IPv6 is operational. Mine is that at this (st)age of IPv6 deployment a SME (we absolutely need them to push and pay for IPv6 acceptance) should be able to: - subscribe an IPv6/IPv4 ADSL access - put a bootable CD in a new machine with a Wi-Fi router plugged on the ADSL line - answer a few well documented questions - and get its server running under Apache, with a xxxmail working as pop, smtp, mailing list and anti-spam, their named operational and reasonable anti-virus, firewall, network management, log reporting tool, backup/restore, security alarm solutions being in operation and full Perl and PHP support for network scripts being loaded. I have the ADSL line and IPv6/IPv4 address for three months. I am still looking for a trustable "dog food" cann: an ISO to dowload, CD to Fedex, a compact nomad version on a bootable USB key? May be then the IETF could a copy: not to test it, but to show it can be used. I know you made a lot of practical efforts: did you come accross of such a dog foot? I would love to test! jfc On 09:44 05/08/2005, Iljitsch van Beijnum said: >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 mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf