IPv6 @ IETF-71, especially Jabber

Iljitsch van Beijnum <iljitsch@muada.com> Fri, 29 February 2008 14:35 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EDBC28C593; Fri, 29 Feb 2008 06:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.509
X-Spam-Level:
X-Spam-Status: No, score=-0.509 tagged_above=-999 required=5 tests=[AWL=-0.072, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIXnbTtXj5lI; Fri, 29 Feb 2008 06:35:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D66A728C2F2; Fri, 29 Feb 2008 06:34:57 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8B9328C27C for <ietf@core3.amsl.com>; Fri, 29 Feb 2008 06:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxE5pnOIM1Mv for <ietf@core3.amsl.com>; Fri, 29 Feb 2008 06:34:54 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 580103A68A2 for <ietf@ietf.org>; Fri, 29 Feb 2008 06:34:54 -0800 (PST)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb] ([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m1TEYWCn082205 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 29 Feb 2008 15:34:33 +0100 (CET) (envelope-from iljitsch@muada.com)
Message-Id: <55067F48-573A-4FC4-996A-260D0F00B82B@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: IETF discussion list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: IPv6 @ IETF-71, especially Jabber
Date: Fri, 29 Feb 2008 15:34:41 +0100
X-Mailer: Apple Mail (2.919.2)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

What's going on with the preparations to turn off IPv4 at IETF-71?  
It's been really quiet surrounding that topic since the initial  
discussion.

Because I've had an IPv6 mail server for years and a WWW proxy that  
allows IPv6-only hosts to get access to the IPv4 web is fairly trivial  
to set up (tip for XP users: XP can't do DNS lookups over IPv6, use  
Firefox and configure it with the IPv6 address of the proxy), my  
preperation for this has been mostly getting Jabber to work over IPv6.

A while ago I managed to find a public Jabber server that is reachable  
over IPv6 (amessage.de with some other domains pointing to the same  
server). Unfortunately, the client I generally use, Apple's iChat,  
does support Jabber over IPv6 when there is IPv4 connectivity, but  
when the system has no IPv4 address it says that "you're not connected  
to the internet" and doesn't try to connect over IPv6. Recently I  
thought this was fixed but it turned out that the Parallels Desktop  
virtualization enviroment sets up a bunch of virtual interfaces with  
private addresses, which is enough for iChat to work over IPv6.

Anyway, I started looking for Jabber clients that support IPv6. Most  
don't, but there are so many Jabber clients that there is actually a  
choice of ones that do. Unfortunately, none of them could connect to  
the jabber.ietf.org rooms. I first thought this was because of the  
clients, so I didn't keep a list of clients that support IPv6. But it  
turned out that this is a problem with my iljitsch at amessage.nl  
account on the amessage.de server, which doesn't seem IPv6-related.

So... does anyone know a place to obtain a Jabber account that's  
usable over IPv6? I assumed psg.com would be a good candidate, but  
even though psg.com has a AAAA record, jabber.psg.com doesn't.
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf