Re: IPv4 Outage Planned for IETF 71 Plenary

Iljitsch van Beijnum <iljitsch@muada.com> Wed, 19 December 2007 18:12 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J53PJ-00018Z-Er; Wed, 19 Dec 2007 13:12:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J53PH-0000vx-9A for ietf@ietf.org; Wed, 19 Dec 2007 13:12:35 -0500
Received: from sequoia.muada.com ([83.149.65.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J53PE-0003vL-Sh for ietf@ietf.org; Wed, 19 Dec 2007 13:12:35 -0500
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.241]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id lBJI9SFo044436 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Dec 2007 19:09:30 +0100 (CET) (envelope-from iljitsch@muada.com)
Message-Id: <E71A2A3F-3AB4-494D-ACC8-51F7803FE6BF@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Eric Rescorla <ekr@networkresonance.com>
In-Reply-To: <20071219161717.0A5B75081A@romeo.rtfm.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Date: Wed, 19 Dec 2007 18:56:37 +0100
References: <E1J3IFS-0002yV-CG@ietf.org> <200712142154.lBELs1ne090300@drugs.dv.isc.org> <200712181644.lBIGisBx090029@romeo.rtfm.com> <476800BC.5030504@dcrocker.net> <38033976C354EAB237181075@[192.168.101.1]> <p06250103c38dc78214d8@[74.134.5.163]> <20071218203932.GB21605@nsn.com> <20071219153031.B76645081A@romeo.rtfm.com> <20071219160710.GA29000@nsn.com> <20071219161717.0A5B75081A@romeo.rtfm.com>
X-Mailer: Apple Mail (2.915)
X-Spam-Status: No, score=-1.7 required=3.5 tests=AWL,BAYES_00, ILJQX_SUBJ_NUMINWORD autolearn=no version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: IPv4 Outage Planned for IETF 71 Plenary
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>
Errors-To: ietf-bounces@ietf.org

On 19 dec 2007, at 17:17, Eric Rescorla wrote:

> Again, what is the value of this experiment?

The value is that it exposes IETF-goers who don't normally run IPv6- 
only to this type of network configuration. At the very least this  
forces people to formulate their objections to this treatment, which  
may give us valuable information in and of its own, and hopefully, it  
will show one or more of the following:

- how easy it is to run IPv6
- where the problem areas are with running IPv6
- what still needs to be done in standards, implementation and operation

There was a suggestion to rate limit IPv4 or NAT it heavily rather  
than turn it off. That completely misses the point. As long as there  
is IPv4, you don't see what's missing from IPv6.

Another suggestion was to charge more for IPv4. I love that idea. Give  
everyone who only needs IPv6 access a discount on the meeting fee.  :-)

But I think what we really need is to get some people together to  
define the parameters of this experiment and to work out what's needed  
to prepare for it.

In the mean time, I'm interested to hear about jabber clients that can  
work in an IPv6-only environment (even though jabber.ietf.org doesn't  
have an IPv6 address).

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf