Re: IPv6 @ IETF-71, especially Jabber
Ralph Droms <rdroms@cisco.com> Fri, 29 February 2008 14:45 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 27B4A3A6F57; Fri, 29 Feb 2008 06:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.148
X-Spam-Level:
X-Spam-Status: No, score=-1.148 tagged_above=-999 required=5 tests=[AWL=-0.711, 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 5oyWgLddbq0V; Fri, 29 Feb 2008 06:45:46 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B998D3A6BD3; Fri, 29 Feb 2008 06:45:46 -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 7A1F93A685D for <ietf@core3.amsl.com>; Fri, 29 Feb 2008 06:45:44 -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 zAnzCGf0Vpai for <ietf@core3.amsl.com>; Fri, 29 Feb 2008 06:45:38 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id CDF093A6A02 for <ietf@ietf.org>; Fri, 29 Feb 2008 06:45:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.25,426,1199682000"; d="scan'208";a="149452500"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 29 Feb 2008 09:45:31 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1TEjVPs025544; Fri, 29 Feb 2008 09:45:31 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1TEjUjE028493; Fri, 29 Feb 2008 14:45:31 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Feb 2008 09:45:30 -0500
Received: from [161.44.65.201] ([161.44.65.201]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Feb 2008 09:45:30 -0500
Message-Id: <61BE6C39-78FD-4C85-A73A-862AE1916A50@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <55067F48-573A-4FC4-996A-260D0F00B82B@muada.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: IPv6 @ IETF-71, especially Jabber
Date: Fri, 29 Feb 2008 09:45:29 -0500
References: <55067F48-573A-4FC4-996A-260D0F00B82B@muada.com>
X-Mailer: Apple Mail (2.919.2)
X-OriginalArrivalTime: 29 Feb 2008 14:45:30.0563 (UTC) FILETIME=[BB1E8930:01C87AE1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2274; t=1204296331; x=1205160331; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20IPv6=20@=20IETF-71,=20especially=20Jabb er |Sender:=20 |To:=20Iljitsch=20van=20Beijnum=20<iljitsch@muada.com>; bh=7uQEuqTLa4df4J8/6x1L3wAXXJo39zORkOCPwbdxShw=; b=mpMaQq3tULvuOi9ljtdDhepw6EtJwO2WrDL1vuWoI5A6WxMJJ1p3ZnWtUh G4QGA+IWiA8B8ilIWRS4yAuLNBCPsKfTw+TUw3RorL/6NJNaFx5p3wpgikNy VaDT/oI3bY;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: IETF discussion list <ietf@ietf.org>
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
Iljitsch raises an interesting point that I'll generalize: can we maximize the learning by identifying specific applications to target for IPv6 compatibility during the IPv4 eclipse? - Ralph On Feb 29, 2008, at Feb 29, 2008,9:34 AM, Iljitsch van Beijnum wrote: > 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 _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- IPv6 @ IETF-71, especially Jabber Iljitsch van Beijnum
- Re: IPv6 @ IETF-71, especially Jabber Ralph Droms
- Re: IPv6 @ IETF-71, especially Jabber Stephane Bortzmeyer
- Re: IPv6 @ IETF-71, especially Jabber Leslie Daigle
- Re: IPv6 @ IETF-71, especially Jabber Lucy Lynch
- Re: IPv6 @ IETF-71, especially Jabber Iljitsch van Beijnum
- wiki for IETF71 IPv6 experience Re: IPv6 @ IETF-7… Leslie Daigle
- Re: wiki for IETF71 IPv6 experience Re: IPv6 @ IE… Iljitsch van Beijnum
- Re: wiki for IETF71 IPv6 experience Re: IPv6 @ IE… Leslie Daigle
- Re: wiki for IETF71 IPv6 experience Re: IPv6 @ IE… Cyrus Daboo
- Re: wiki for IETF71 IPv6 experience Re: IPv6 @ IE… Mark Andrews