[71attendees] IPv6 Jabber Identity server anyone?

"Hallam-Baker, Phillip" <pbaker@verisign.com> Tue, 11 March 2008 20:05 UTC

Return-Path: <71attendees-bounces@ietf.org>
X-Original-To: ietfarch-71attendees-archive@core3.amsl.com
Delivered-To: ietfarch-71attendees-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DAEE28C558; Tue, 11 Mar 2008 13:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.749
X-Spam-Level:
X-Spam-Status: No, score=-99.749 tagged_above=-999 required=5 tests=[AWL=0.688, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 Qw0PV1GQBeAx; Tue, 11 Mar 2008 13:05:50 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7054328C51C; Tue, 11 Mar 2008 13:05:20 -0700 (PDT)
X-Original-To: 71attendees@core3.amsl.com
Delivered-To: 71attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 931ED3A6DA0 for <71attendees@core3.amsl.com>; Tue, 11 Mar 2008 13:05:16 -0700 (PDT)
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 B+wjbhpveJYS for <71attendees@core3.amsl.com>; Tue, 11 Mar 2008 13:05:11 -0700 (PDT)
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by core3.amsl.com (Postfix) with ESMTP id 6681E28C4F8 for <71attendees@ietf.org>; Tue, 11 Mar 2008 13:02:09 -0700 (PDT)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35]) by robin.verisign.com (8.12.11/8.13.4) with ESMTP id m2BJoXEh022616 for <71attendees@ietf.org>; Tue, 11 Mar 2008 12:50:33 -0700
Received: from MOU1WNEXMB09.vcorp.ad.vrsn.com ([10.25.15.197]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Mar 2008 12:59:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 11 Mar 2008 12:59:49 -0700
Message-ID: <2788466ED3E31C418E9ACC5C3166155708508D@mou1wnexmb09.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IPv6 Jabber Identity server anyone?
Thread-Index: AciDsnXkT14m4QNARDWrSakINTdgNw==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: <71attendees@ietf.org>
X-OriginalArrivalTime: 11 Mar 2008 19:59:49.0885 (UTC) FILETIME=[76B1F2D0:01C883B2]
Subject: [71attendees] IPv6 Jabber Identity server anyone?
X-BeenThere: 71attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for IETF Meeting 71 attendees <71attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/71attendees>, <mailto:71attendees-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:71attendees@ietf.org>
List-Help: <mailto:71attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/71attendees>, <mailto:71attendees-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1426100474=="
Sender: 71attendees-bounces@ietf.org
Errors-To: 71attendees-bounces@ietf.org

In an attempt to ensure the all important objective of connecting to the requisite chat room during the plenary I tried out ietf-v6ONLY today.

Issues discovered (OS/X Lepoard on a MacBook Air):

1) Firefox does not allow an IPv6 URL to be entered into the address bar, fe80::... was turned into http://www.fe80.com/...

2) iChat and Adium were both unable to connect to my gmail identity server so I was unable to connect to any chat room whatsoever.


Conclusion: Not only does it not work, the level of user intervention required is such that I am going to have to retreat to a small desert island (no Internet) during the transition phase or spend 110% of my time fixing the transition problems of all my relatives. Might as well be using IPv8...

This has to be completely transparent to the end user. The current scheme requires double ended adoption before IPv6 gives me the same level of usability as IPv4. 
_______________________________________________
71attendees mailing list
71attendees@ietf.org
https://www.ietf.org/mailman/listinfo/71attendees