[MMUSIC] ICE candidate pairing and NAT64

Jonathan Lennox <jonathan@vidyo.com> Tue, 23 June 2015 19:28 UTC

Return-Path: <jonathan@vidyo.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id E3BDE1A1B98 for <mmusic@ietfa.amsl.com>; Tue, 23 Jun 2015 12:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mqxj405EFj_v for <mmusic@ietfa.amsl.com>; Tue, 23 Jun 2015 12:28:43 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34F4D1A1B96 for <mmusic@ietf.org>; Tue, 23 Jun 2015 12:28:42 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net []) by mx0b-00198e01.pphosted.com (8.14.7/8.14.7) with SMTP id t5NJPXe1007686 for <mmusic@ietf.org>; Tue, 23 Jun 2015 15:28:42 -0400
Received: from mail.vidyo.com ([]) by mx0b-00198e01.pphosted.com with ESMTP id 1v0grtdpar-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 23 Jun 2015 15:28:41 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Tue, 23 Jun 2015 14:28:41 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: mmusic <mmusic@ietf.org>
Thread-Topic: ICE candidate pairing and NAT64
Thread-Index: AQHQrerPXTc4tOO/Kka1XSQmTmBoPg==
Date: Tue, 23 Jun 2015 19:28:40 +0000
Message-ID: <CA8D917B-8C7C-42B9-BF65-F7209DFCA15C@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <764BCB3C34D13C45B57DB16411315672@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-06-23_07:2015-06-23,2015-06-23,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1506230308
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/b1qoTRmeB6Cy1f1NctWejMGBnuU>
Subject: [MMUSIC] ICE candidate pairing and NAT64
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2015 19:28:44 -0000

Apple’s recent announcement that all iOS apps are soon going to be required to support running behind NAT64 has led me to contemplate what this means for ICE.

Should ICE endpoints be required and/or recommended to support using RFC 7050 NAT64 prefix discovery to pair local IPv6 candidates which have a NAT64 gateway with remote IPv4 candidates?

What does this do to connectivity check pacing, or to the total number of connectivity checks?

And how many operating systems can support a userspace app doing an RFC 7050 DNS lookup on a per-interface basis?  (Even if you roll your own DNS resolver, you still need to be able to obtain per-interface DNS server configuration information to find the interface’s appropriate DNS64 server.)