Re: Android and IPv6 was [Last Call: RFC 6346 successful: moving to Proposed Standard]
"John Levine" <johnl@taugh.com> Mon, 15 December 2014 05:20 UTC
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 744671A19F2 for <ietf@ietfa.amsl.com>; Sun, 14 Dec 2014 21:20:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.037
X-Spam-Level:
X-Spam-Status: No, score=-1.037 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g_qa2Hm5TOsP for <ietf@ietfa.amsl.com>; Sun, 14 Dec 2014 21:19:59 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B1FF1A19E9 for <ietf@ietf.org>; Sun, 14 Dec 2014 21:19:58 -0800 (PST)
Received: (qmail 8274 invoked from network); 15 Dec 2014 05:19:53 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 15 Dec 2014 05:19:53 -0000
Date: Mon, 15 Dec 2014 05:19:35 -0000
Message-ID: <20141215051935.2077.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Android and IPv6 was [Last Call: RFC 6346 successful: moving to Proposed Standard]
In-Reply-To: <12511.1418595480@sandelman.ca>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hGWQeVhvn5LFdoX3mCi2rLGea5A
Cc: mcr+ietf@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
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>
X-List-Received-Date: Mon, 15 Dec 2014 05:20:00 -0000
In article <12511.1418595480@sandelman.ca> you write: > > Won't get an IPv6 address when placed on a proper IPv6-capable wifi > > segment that does SLAAC, or won't do IPv6 over mobile, or you simply > > haven't seen anything that proves it's doing those things? Note that in >Android 4.0 certainly does work DualStack. I believe you, but not on this phone. On my home LAN, which is dual stack, Chrome and my ssh client both connect over IPv6 when they're running on my Nexus 7 tablet, over IPv4 on the cheap phone. R's, John
- Re: Android and IPv6 was [Last Call: RFC 6346 suc… George, Wes
- Re: Android and IPv6 was [Last Call: RFC 6346 suc… Michael Richardson
- Re: Android and IPv6 was [Last Call: RFC 6346 suc… John Levine