Re: IPv4 Outage Planned for IETF 71 Plenary

Jari Arkko <jari.arkko@piuha.net> Wed, 19 December 2007 20:11 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 1J55Fs-000748-Dn; Wed, 19 Dec 2007 15:11:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J55Fq-00073K-5X; Wed, 19 Dec 2007 15:10:58 -0500
Received: from p130.piuha.net ([2001:14b8:400::130] helo=smtp.piuha.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J55Fp-0006FT-Gg; Wed, 19 Dec 2007 15:10:58 -0500
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id DAF4B1986CC; Wed, 19 Dec 2007 22:10:56 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 7C52719867A; Wed, 19 Dec 2007 22:10:56 +0200 (EET)
Message-ID: <47697AD0.3060601@piuha.net>
Date: Wed, 19 Dec 2007 22:10:56 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.14pre (X11/20071022)
MIME-Version: 1.0
To: David Kessens <david.kessens@nsn.com>
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> <20071219163953.GD29000@nsn.com>
In-Reply-To: <20071219163953.GD29000@nsn.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ietf@ietf.org, iesg@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

> And on another topic, I would hope that (members of) the IAB will
> spend the same amount of time and energy as used on this discussion 

Amen, but lets make that apply to the rest of us too.

> on
> more important topics like to get ICANN to have ipv6 and DNSSEC root
> service available before the next IETF meeting.
>   

Actually, I have some trust on the fine people in the ICANN board and I
would expect them to get their stuff in order soon. In any case, we
don't make those decisions on this list.

Focusing a little bit on what we can have an effect on: what would it
take for IETF work -related communications to be possible via IPv6? And
what can we do to increase the number of participants that can deal with
IPv6?

Here are some items, send mail if you have something to add or change:

- IETF web sites to fully IPv6 capable (not all are; I have a list
somewhere)
- Same for the related websites (iab.org, iesg.org, iana.org,
rfc-editor.org,
maybe some tools if not all of them are there yet)
- Datatracker (no AAAA enabled at this time, but should be doable)
- Jabber to work on IPv6 (I have no idea what it takes to do this)
- Training for the IPv6 newbies
- What each of us can do in our own organizations for our VPN, mail etc

Jari


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