Re: [71attendees] IPv6 Jabber Identity server anyone?

Michael Graff <michael_graff@isc.org> Tue, 11 March 2008 20:14 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 4FB113A6B1C; Tue, 11 Mar 2008 13:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.087
X-Spam-Level:
X-Spam-Status: No, score=-102.087 tagged_above=-999 required=5 tests=[AWL=-1.694, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, 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 4D7sCAz7IyZy; Tue, 11 Mar 2008 13:14:08 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A8863A6882; Tue, 11 Mar 2008 13:14:07 -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 A8D8C28C4ED for <71attendees@core3.amsl.com>; Tue, 11 Mar 2008 13:14:01 -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 rwuo9pW5n2Bk for <71attendees@core3.amsl.com>; Tue, 11 Mar 2008 13:13:58 -0700 (PDT)
Received: from white.flame.org (white.flame.org [204.152.186.144]) by core3.amsl.com (Postfix) with ESMTP id 22EF93A6E49 for <71attendees@ietf.org>; Tue, 11 Mar 2008 13:13:36 -0700 (PDT)
Received: from white.flame.org (localhost [127.0.0.1]) by white.flame.org (Postfix) with ESMTP id 8DD6D327A75; Tue, 11 Mar 2008 13:11:16 -0700 (PDT)
Received: from dhcp-13bb.ietf71.ietf.org (dhcp-13bb.ietf71.ietf.org [130.129.19.187]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by white.flame.org (Postfix) with ESMTP id C73F3327A5A; Tue, 11 Mar 2008 13:11:14 -0700 (PDT)
From: Michael Graff <michael_graff@isc.org>
To: 71attendees@ietf.org
Date: Tue, 11 Mar 2008 10:11:09 -0500
User-Agent: KMail/1.9.9
References: <2788466ED3E31C418E9ACC5C3166155708508D@mou1wnexmb09.vcorp.ad.vrsn.com>
In-Reply-To: <2788466ED3E31C418E9ACC5C3166155708508D@mou1wnexmb09.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200803111011.09512.michael_graff@isc.org>
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 71attendees-bounces@ietf.org
Errors-To: 71attendees-bounces@ietf.org

On Tuesday 11 March 2008 14:59:49 Hallam-Baker, Phillip wrote:
> 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.

This is one reason I don't think the no-v4 experiment is really of use right 
now.

The fact is that ipv4 is not going to go away on some magical day.  It's going 
to be here until we're all long dead.  The ability for V6 only hosts to 
contact V4 only hosts is where the magic is.  We all know we cannot reach our 
favorite search engines, mail servers, or whatnot over V6.  This does not 
require an hour to learn.

Most of the magic at this point seems to be in clients being able to not only 
understand IPv6 addresses and sockets, but to know how to reach IPv4 hosts 
when there is no local IPv4 address available.  NAT for the win.  And 
teaching applications to deal with the fact that IPv4 is not "the internet" 
anymore is critical before anyone will want to put an IPv6 only network on 
the air in more than an experiement.

--Michael
_______________________________________________
71attendees mailing list
71attendees@ietf.org
https://www.ietf.org/mailman/listinfo/71attendees