[v6ops] use of Teredo addresses in Apple devices

"STARK, BARBARA H" <bs7652@att.com> Fri, 24 July 2015 08:25 UTC

Return-Path: <bs7652@att.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 13C7D1A00BE for <v6ops@ietfa.amsl.com>; Fri, 24 Jul 2015 01:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id W_2a4f4kbroJ for <v6ops@ietfa.amsl.com>; Fri, 24 Jul 2015 01:25:11 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5D401A00D8 for <v6ops@ietf.org>; Fri, 24 Jul 2015 01:25:09 -0700 (PDT)
Received: from unknown [] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id 566f1b55.0.839773.00-2378.2383639.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>); Fri, 24 Jul 2015 08:25:09 +0000 (UTC)
X-MXL-Hash: 55b1f6652cda08c8-54d50f5b8352cc90a60fd58d1aa90426bab00b9c
Received: from enaf.aldc.att.com (localhost []) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t6O8P8Th015938 for <v6ops@ietf.org>; Fri, 24 Jul 2015 04:25:08 -0400
Received: from alpi133.aldc.att.com (alpi133.aldc.att.com []) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t6O8P3LE015927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <v6ops@ietf.org>; Fri, 24 Jul 2015 04:25:03 -0400
Received: from GAALPA1MSGHUBAA.ITServices.sbc.com (GAALPA1MSGHUBAA.itservices.sbc.com []) by alpi133.aldc.att.com (RSA Interceptor) for <v6ops@ietf.org>; Fri, 24 Jul 2015 08:24:59 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([]) by GAALPA1MSGHUBAA.ITServices.sbc.com ([]) with mapi id 14.03.0224.002; Fri, 24 Jul 2015 04:24:58 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: v6ops list <v6ops@ietf.org>
Thread-Topic: use of Teredo addresses in Apple devices
Thread-Index: AdDF6S3NgWeVgLgjSKOp7/BiIjWFpA==
Date: Fri, 24 Jul 2015 08:24:58 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61132A90D2D@GAALPA1MSGUSRBF.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=QrfpKyOd c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=zQP7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=ALLY0qxVpFoA:10 a=zOBTX]
X-AnalysisOut: [jUuO1YA:10 a=7asZlWqdK6GnX_Y_fgcA:9 a=CjuIK1q_8ugA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2015072401)]
X-MAIL-FROM: <bs7652@att.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/CIYv0MWaO2vj0wH_6nJgI0cgL3Q>
Subject: [v6ops] use of Teredo addresses in Apple devices
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jul 2015 08:25:13 -0000

Great presentation on what Apple is doing to drive apps to implement IPv6.
In thinking about use of the Teredo address space to advertise a prefix to tethered devices, I do have a concern. In many of my personal home networked devices, I've purposefully disabled Teredo and ISATAP and even put in some rules to prevent the devices from accepting such addresses.

I think this would be a reasonable use of a ULA. A PI might be even better. I hear PIs are pretty easy to come by. The PI would have the advantage of being known to come from an Apple device for this NAT64 purpose. That could help with trouble shooting.