IETF Logo Mail Archive

Re: [v6ops] Apple and IPv6 - new NAT64 address synthesis API

Ca By <cb.list6@gmail.com> Fri, 30 October 2015 19:22 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A376F1B3AD5 for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 12:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 BHqXQJVvjCNW for <v6ops@ietfa.amsl.com>; Fri, 30 Oct 2015 12:22:42 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D90061B3ACF for <v6ops@ietf.org>; Fri, 30 Oct 2015 12:22:41 -0700 (PDT)
Received: by wijp11 with SMTP id p11so17544152wij.0 for <v6ops@ietf.org>; Fri, 30 Oct 2015 12:22:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=R2g0q/U8yZbQHcGgqFL7kGQRK8ZtoF0Z2c5TPMeqBZ0=; b=I7wfPmQ72nMi2En0SitaNJ4bZCReA7IJkRPsQiyw+DsjMXkppr8HWrdjOsgp3/wxHh SWBm8zi6iDh5k+f/B7GdSbQ6wkNTIuuKGgc4HpusitlvASKfOJ27WxCBgBqTonr8MZiY UreBrTkubfAOPfUw09JJ6jaqzjqnHVYemg0DzIcNs7Mrqpzo7pJcTC8Y3ZHjtzKkeNbA 9NIUNwysaPoS3nSNlfLQcritso3KANVWIbhHonwKTdMxLGJp/22UkHZAffkwEH51pFbr kk5FDoluuEfdNcTJSZjevDwRsdG7kuwz89R9vNS6MRHKFwUAgyVkMRh2sG5IDZG+CdIC 7kFQ==
MIME-Version: 1.0
X-Received: by 10.194.109.99 with SMTP id hr3mr11504763wjb.25.1446232960430; Fri, 30 Oct 2015 12:22:40 -0700 (PDT)
Received: by 10.194.192.40 with HTTP; Fri, 30 Oct 2015 12:22:40 -0700 (PDT)
In-Reply-To: <ED8066C1-76D8-4BCD-BA8F-5D5F9F4FEA21@apple.com>
References: <ED8066C1-76D8-4BCD-BA8F-5D5F9F4FEA21@apple.com>
Date: Fri, 30 Oct 2015 12:22:40 -0700
Message-ID: <CAD6AjGSfp6wupedbnPnSeMd-+W7-D3uPuC=Zb02Pb1156YY34Q@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: David Schinazi <dschinazi@apple.com>
Content-Type: multipart/alternative; boundary="089e010d8a6ede78ea05235759d8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/_pn8Y5d-B3w-LgsyKBTgh4W8Chc>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Apple and IPv6 - new NAT64 address synthesis API
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, 30 Oct 2015 19:22:43 -0000

On Thu, Oct 29, 2015 at 9:51 PM, David Schinazi <dschinazi@apple.com> wrote:

> Hi everyone,
>
> This week Apple released the first betas of iOS 9.2 and OS X 10.11.2.
> With it, we’ve introduced a new API to allow developers to synthesize
> NAT64 IPv6 addresses from IPv4 literals.
> We’re hoping that this will help more applications support NAT64 networks
> correctly while they work on getting server support for IPv6.
> As usual, we’d love feedback from the IETF community.
>
> The API is very simple: we ask developers to always ``resolve'’ their IPv4
> literals using getaddrinfo() by treating their IPv4 literal as a hostname
> string (e.g. ``192.0.2.1''), and we will take care of returning an IPv4
> sockaddr on IPv4 networks and an appropriately synthesized NAT64 IPv6
> sockaddr when the network supports IPv6, NAT64 and DNS64 but not IPv4. This
> is accomplished using RFC 6052 and RFC 7050.
>
> Our target audience is application developers that need to communicate to
> an IPv4-only host for which they do not have a hostname. An example is a
> P2P service transmitting IPv4 literals over the wire. We do agree that the
> correct long-term solution is IPv6 support for all hosts and protocols but
> this is an effort to ease the transition. We believe this will help fix any
> remaining apps that do not support IPv6 before we start rejecting them from
> the App Store in early 2016.
>
> More details and a code sample can be found on the Apple documentation
> website:
>
>
> https://developer.apple.com/library/prerelease/tvos/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-DontLinkElementID_4
>
> Thanks,
> David Schinazi
> Apple CoreOS Networking Engineer
>

Thanks David, this is clearly a helpful step.




>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>

v2.23.0 | Report a Bug | By Email