From nobody Wed Jun 14 19:19:14 2017 Return-Path: X-Original-To: sunset4@ietfa.amsl.com Delivered-To: sunset4@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE5C1293D9 for ; Wed, 14 Jun 2017 19:19:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 Z8-LVLFmdIvK for ; Wed, 14 Jun 2017 19:19:10 -0700 (PDT) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 27A25127010 for ; Wed, 14 Jun 2017 19:19:10 -0700 (PDT) Received: by mail-it0-x232.google.com with SMTP id m47so2934561iti.0 for ; Wed, 14 Jun 2017 19:19:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=uArRCaofMPxMFoT7WZM/gE5CqW+ULxF/+2ePVCeh4xg=; b=H2iaQJWrkOLYMCpjK3GuiBFHC+FXIsgVns1+0RBjV0rmwP/90HZAU2dL4fywuCerrP 075ZLzfQpcQpZ88IMR8EgyAKIsE+Q3KmYPpB/p9LOo1k4C/wJaBxdDwko+BZTK1YTORK 7FbfxJg7JlcyRJi5wcKxMRuB5u3f84TAoD3OxLP8g4HXetAgHjfwx2wO6g0Ug5+jIyUS b/WwAWKYraf91Yn31iZltalzix8oDeriIVW72+MvacE8g7Ab2PhenPZzrcf+pm7bpD9z 9cE3ez71QlxpFL3tCBiUQTxNhNjeLmQPKojrXKUOHmdc3f8NcCUZfpFngFhF41xemYKO 13Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=uArRCaofMPxMFoT7WZM/gE5CqW+ULxF/+2ePVCeh4xg=; b=dB++NPpb3nHZtKX6YGs0/gGVfqrcV5UUo7It4aoskxLlDnwXmCO5/higXRPxuloEzt vSnl4vJDet8cHvWZ+znnnx1M34c4Vjawlel1bk8uheszx+tMrC2QDx2XBi20y2De/gf8 L28dtTdnNXadvEAenxtjfL9l+wZtbWJGzMlOPAgIAANTo7N6tjyKwUAwan+VLae5xWLO 4Zr3llmzALwaR72CvtinRkisKClDpcDNSmtiKIkM4tkeeJYjg7dlcF9q12105oRXajUT zHQ12l9q/4imUO0gk70G9jIj2IxGYdZwsacHH3znYVbIFjSaH8D8wr+VtElKjMlEJi3s ZeDg== X-Gm-Message-State: AKS2vOxdmPi3VTGoEXhSbuZCel/nuzgUa3XgnJSkUi/taIgEIzTiOuBg HxUjxejqPGPFiyk95Hojb/9q/NfXdSmAEFw= X-Received: by 10.36.65.18 with SMTP id x18mr3094931ita.88.1497493149422; Wed, 14 Jun 2017 19:19:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.198.65 with HTTP; Wed, 14 Jun 2017 19:19:09 -0700 (PDT) From: GangChen Date: Thu, 15 Jun 2017 10:19:09 +0800 Message-ID: To: "sunset4@ietf.org" Cc: draft-ietf-sunset4-nat64-port-allocation , "M\"Marc Blanchet\"" , wesgeorge@puck.nether.net Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [sunset4] About the work item: NAT64 port allocation and address sharing methods X-BeenThere: sunset4@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: sunset4 working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jun 2017 02:19:12 -0000 Hello group, Just intend to synchronize the status of this work item. The item is still in the charter. It might be supposed to continue and complete the works within the work group. We have https://tools.ietf.org/html/draft-ietf-sunset4-nat64-port-allocation-02. But I miss several meeting and not sure the wg thoughts about this work. Much appreciate if someone could update me with the new status. Many thanks Bus Gang From nobody Mon Jun 26 10:07:32 2017 Return-Path: X-Original-To: sunset4@ietf.org Delivered-To: sunset4@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FDDD128D40; Mon, 26 Jun 2017 10:07:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sunset4@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.55.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <149849684615.18420.14124996388059665238@ietfa.amsl.com> Date: Mon, 26 Jun 2017 10:07:26 -0700 Archived-At: Subject: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt X-BeenThere: sunset4@ietf.org X-Mailman-Version: 2.1.22 List-Id: sunset4 working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 17:07:26 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Sunsetting IPv4 of the IETF. Title : Gap Analysis for IPv4 Sunset Authors : Will(Shucheng) Liu Weiping Xu Cathy Zhou Tina Tsou Simon Perreault China Mobile Filename : draft-ietf-sunset4-gapanalysis-08.txt Pages : 11 Date : 2017-06-26 Abstract: Sunsetting IPv4 refers to the process of turning off IPv4 definitively. It can be seen as the final phase of the migration to IPv6. This memo enumerates difficulties arising when sunsetting IPv4, and identifies the gaps requiring additional work. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sunset4-gapanalysis/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sunset4-gapanalysis-08 https://datatracker.ietf.org/doc/html/draft-ietf-sunset4-gapanalysis-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sunset4-gapanalysis-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Jun 26 11:06:21 2017 Return-Path: X-Original-To: sunset4@ietfa.amsl.com Delivered-To: sunset4@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9150712EAFB for ; Mon, 26 Jun 2017 11:06:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es 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 oxhqcnPH1g3l for ; Mon, 26 Jun 2017 11:06:17 -0700 (PDT) Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10E75129AD5 for ; Mon, 26 Jun 2017 11:06:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1498500319; x=1499105119; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=ySo1d7C75ijoGNxIUNl5r55FH K3ZvIOKkOfcQm7KV+M=; b=XsNqGvIBnCLVwwMMgMymoZMPwjUpUI8iO2eg5YYm1 B1qy7P0GjR4bkuTW08M0fKMJ1dNsuJ4hbpX0WP4btTa7qlqeAhvGsTKJIPikmF6b ykSz9GxtzYvbfZoJNDsc84aLkhC90+uZac6ih/blG3QnzDsr1bS6X6yeThcq1PIs Oo= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=sbsJcrQxazvqRDzO7CFkhZ0O+FWRo7Xwb2f8EtGgllVVoPIYYpfX99TOEQc2 LQlVtgS7xUR2yiaRgPM4hGflkc2EvZCb7bFbr+1wBXu39lhk9UiueQseN B2I0EiUOBZoWgGPb72z2t+J6dam4hGAD+n0DE8ZfYUVbLizd0ohZUk=; X-MDAV-Processed: mail.consulintel.es, Mon, 26 Jun 2017 20:05:19 +0200 X-Spam-Processed: mail.consulintel.es, Mon, 26 Jun 2017 20:05:19 +0200 Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005459496.msg for ; Mon, 26 Jun 2017 20:05:18 +0200 X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0) X-Authenticated-Sender: jordi.palet@consulintel.es X-HashCash: 1:20:170626:md50005459496::2g2xxplSeNgV9vXG:00002NpA X-Return-Path: prvs=1350804016=jordi.palet@consulintel.es X-Envelope-From: jordi.palet@consulintel.es X-MDaemon-Deliver-To: sunset4@ietf.org User-Agent: Microsoft-MacOutlook/f.21.0.170409 Date: Mon, 26 Jun 2017 20:05:14 +0200 From: JORDI PALET MARTINEZ To: Message-ID: <8567A66E-28E0-4B52-95A8-371B6100622B@consulintel.es> Thread-Topic: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt References: <149849684615.18420.14124996388059665238@ietfa.amsl.com> In-Reply-To: <149849684615.18420.14124996388059665238@ietfa.amsl.com> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Reply-To: jordi.palet@consulintel.es Archived-At: Subject: Re: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt X-BeenThere: sunset4@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: sunset4 working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 18:06:20 -0000 Hi, In general I agree with the document. I=E2=80=99ve just a couple of comment= s. If we are talking about phases, we should not use migration, but transition= . In many languages, when you translate migration, it means =E2=80=9Cdroppi= ng IPv4 and using only-IPv6=E2=80=9D, which is not the case, and is not the= spirit of the transition mechanism (IETF hasn=E2=80=99t defined migration = mechanisms, right?). It seems a minor comment, but it confuses a lot non-en= glish (and also English speakers, in my opinion). So please, replace all th= e occurrences of migration with transition. Regarding the different issues that are indicated because Happy Eyeballs, a= possible solution is to increase the timers, so even if IPv6 is =E2=80=9Cs= lower=E2=80=9D than IPv4, is not just a matter of 50 milliseconds (for exam= ple), but several seconds, so then IPv6 will get preference anyway. I=E2=80= =99ve described this in a recent email related to the HE-update document (s= o you could use some of the text that I mention in that email): https://www.ietf.org/mail-archive/web/v6ops/current/msg26731.html Regards, Jordi =20 -----Mensaje original----- De: sunset4 en nombre de Responder a: Fecha: lunes, 26 de junio de 2017, 19:07 Para: CC: Asunto: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt =20 A New Internet-Draft is available from the on-line Internet-Drafts dire= ctories. This draft is a work item of the Sunsetting IPv4 of the IETF. =20 Title : Gap Analysis for IPv4 Sunset Authors : Will(Shucheng) Liu Weiping Xu Cathy Zhou Tina Tsou Simon Perreault China Mobile Filename : draft-ietf-sunset4-gapanalysis-08.txt Pages : 11 Date : 2017-06-26 =20 Abstract: Sunsetting IPv4 refers to the process of turning off IPv4 definitively. It can be seen as the final phase of the migration to IPv6. This memo enumerates difficulties arising when sunsetting IPv4, and identifies the gaps requiring additional work. =20 =20 The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sunset4-gapanalysis/ =20 There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sunset4-gapanalysis-08 https://datatracker.ietf.org/doc/html/draft-ietf-sunset4-gapanalysis-08 =20 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sunset4-gapanalysis-08 =20 =20 Please note that it may take a couple of minutes from the time of submi= ssion until the htmlized version and diff are available at tools.ietf.org. =20 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ =20 _______________________________________________ sunset4 mailing list sunset4@ietf.org https://www.ietf.org/mailman/listinfo/sunset4 =20 =20 ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or con= fidential. The information is intended to be for the use of the individual(= s) named above. If you are not the intended recipient be aware that any dis= closure, copying, distribution or use of the contents of this information, = including attached files, is prohibited. From nobody Mon Jun 26 15:42:54 2017 Return-Path: X-Original-To: sunset4@ietfa.amsl.com Delivered-To: sunset4@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD31412702E for ; Mon, 26 Jun 2017 15:42:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.035 X-Spam-Level: X-Spam-Status: No, score=-4.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 zWPN9RKa461W for ; Mon, 26 Jun 2017 15:42:50 -0700 (PDT) Received: from smtp.smtpout.orange.fr (smtp04.smtpout.orange.fr [80.12.242.126]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53BB6126E3A for ; Mon, 26 Jun 2017 15:42:50 -0700 (PDT) Received: from [192.168.43.167] ([77.154.204.178]) by mwinf5d51 with ME id dain1v00B3rTkoD03aina5; Tue, 27 Jun 2017 00:42:48 +0200 X-ME-Helo: [192.168.43.167] X-ME-Auth: bGVvLmdhc3BhcmRAd2FuYWRvby5mcg== X-ME-Date: Tue, 27 Jun 2017 00:42:48 +0200 X-ME-IP: 77.154.204.178 To: sunset4@ietf.org References: <149849684615.18420.14124996388059665238@ietfa.amsl.com> <8567A66E-28E0-4B52-95A8-371B6100622B@consulintel.es> From: Leo Gaspard Message-ID: Date: Tue, 27 Jun 2017 00:42:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <8567A66E-28E0-4B52-95A8-371B6100622B@consulintel.es> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0jHVtUg1tQk3SEacE7mLuqaVk0Pm9kLdK" Archived-At: Subject: Re: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt X-BeenThere: sunset4@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: sunset4 working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 22:42:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0jHVtUg1tQk3SEacE7mLuqaVk0Pm9kLdK Content-Type: multipart/mixed; boundary="X8baU8FMed9T2NCxXXT70I77Eni2e0b8i"; protected-headers="v1" From: Leo Gaspard To: sunset4@ietf.org Message-ID: Subject: Re: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt References: <149849684615.18420.14124996388059665238@ietfa.amsl.com> <8567A66E-28E0-4B52-95A8-371B6100622B@consulintel.es> In-Reply-To: <8567A66E-28E0-4B52-95A8-371B6100622B@consulintel.es> --X8baU8FMed9T2NCxXXT70I77Eni2e0b8i Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06/26/2017 08:05 PM, JORDI PALET MARTINEZ wrote: > Regarding the different issues that are indicated because Happy Eyeball= s, a possible solution is to increase the timers, so even if IPv6 is =E2=80= =9Cslower=E2=80=9D than IPv4, is not just a matter of 50 milliseconds (fo= r example), but several seconds, so then IPv6 will get preference anyway.= I=E2=80=99ve described this in a recent email related to the HE-update d= ocument (so you could use some of the text that I mention in that email):= Please be careful about this (for problem 6): I've already seen people advising to "just disable IPv6 to get a speed boost." If the timeout is going to slow down to several seconds, this may make more people switch to using IPv4 only, which would be the complete opposite of the objective= =2E Sure, you also consider making this setting a knob, but people may go the easiest already known way, because "well, who cares about IPv6 anyway= ?" Then, all this depends on the proportion of the internet that is already quickly IPv6-reachable, but if there is a problem to solve, it can only be solved by making IPv4 slower when IPv6 is enabled... which sounds like a bad idea to me so long as IPv4's sunset (or IPv6's rise?) isn't complete yet (at which point this solution is no longer needed anyway). Best regards, Leo --X8baU8FMed9T2NCxXXT70I77Eni2e0b8i-- --0jHVtUg1tQk3SEacE7mLuqaVk0Pm9kLdK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEEplquSIS+CbvsrRWvilWEi2CQ+c8FAllRjeMACgkQilWEi2CQ +c83IAv/Y3ZOTR9RYBXaQI+h0reEg65F1K5L0sB0XtM9M9mi87M8Owb2paXA5OnY oj6T44LHRQ5hKzhlgxgqLd9pkIwE/rKnSaZsyXkQc/ohbLhQxNddxl+S6AAkuW3H W+gFl/PG7uP20wndZe5s/qngatCERV4UzUjrNNSH8GXZdTazJl6nQfo3N8ffG1vL bt8jPV7HF6FhFcUe8LO2VYS3cmH0QhirRfBIAPG8VLCs+iBnMukLlF1OfvAEtu8r HT6GLoY+/4yw5iPFCeh5MobVwEXD3Zxxzm0gNq15HBw08gu8kRftkKUtXNG7Vy0j iuVCDWKUgG+gMz5OAeGuw28FHY/932GPbHVKB5JVG/Q+nRNR8QN5dLEgy7ReAsHR MY79MeijvjNgRoceI3FCUGqnSWSlDBDjg0HEfAhpgvHf6kMhWC58QYjLLb6Bqd4p sbINwjflC2/qZjEtTdOCqjiqASOoFYTI4NMMQnmpJGHZSJTcJoZmPC+WcBiOb899 0DE+Ftmg =s36J -----END PGP SIGNATURE----- --0jHVtUg1tQk3SEacE7mLuqaVk0Pm9kLdK-- From nobody Tue Jun 27 00:18:55 2017 Return-Path: X-Original-To: sunset4@ietfa.amsl.com Delivered-To: sunset4@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F581128C83 for ; Tue, 27 Jun 2017 00:18:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es 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 td1alA2lMTfC for ; Tue, 27 Jun 2017 00:18:50 -0700 (PDT) Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84BD412EBF3 for ; Tue, 27 Jun 2017 00:18:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1498547870; x=1499152670; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=GqTy6rHWm2qq/kgwMELHk9WrJ 5tepItUmZS372Xs3N0=; b=rCSXuOMunqzaO5RwBv+t2wM4rQmn0OoTcSny2jT89 GCuMc9d57ygpSPPKHbRAj1gXYyiQ1K2XqU0BoKgj3RD3bAEAZ3z+YbUD4kUTZ16Y NlSniUP2UzfWZEnKsxGLaflwNQXh9jfikWdr1KBDUQXRCDDjpoYlMgY1qyL2arGs +8= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=o3ZDDF9LA4q+Lw6o+GMcq6SNBIZtl16oyEGXNHfirchTtuk4n2FHPsrCYvDJ zjh5QMLNZ6Htub0gtKN4MnDiZT/pHaJLjJQkj8o+dWQPcCN6tst7sdys5 gICZ1CPOHOLlk0bsJN3XEwzqORSEK4MjVNjoX460+kddn7S7MXtcDc=; X-MDAV-Processed: mail.consulintel.es, Tue, 27 Jun 2017 09:17:50 +0200 X-Spam-Processed: mail.consulintel.es, Tue, 27 Jun 2017 09:17:49 +0200 Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005459729.msg for ; Tue, 27 Jun 2017 09:17:48 +0200 X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0) X-Authenticated-Sender: jordi.palet@consulintel.es X-HashCash: 1:20:170627:md50005459729::sQPi0d/j4QJ8R9Q4:0000292z X-Return-Path: prvs=1351220515=jordi.palet@consulintel.es X-Envelope-From: jordi.palet@consulintel.es X-MDaemon-Deliver-To: sunset4@ietf.org User-Agent: Microsoft-MacOutlook/f.21.0.170409 Date: Tue, 27 Jun 2017 09:17:45 +0200 From: JORDI PALET MARTINEZ To: Message-ID: <29C17838-52F8-4ECF-A03D-B5137220FF08@consulintel.es> Thread-Topic: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt References: <149849684615.18420.14124996388059665238@ietfa.amsl.com> <8567A66E-28E0-4B52-95A8-371B6100622B@consulintel.es> In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Reply-To: jordi.palet@consulintel.es Archived-At: Subject: Re: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt X-BeenThere: sunset4@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: sunset4 working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2017 07:18:53 -0000 I=E2=80=99m suggesting the other way around, making sure that IPv6 always g= et the preference by making HE to allow IPv6 even if is much slower than IP= v4 =E2=80=A6 because IPv4 is going to be turned down. Regards, Jordi =20 -----Mensaje original----- De: sunset4 en nombre de Leo Gaspard Responder a: Fecha: martes, 27 de junio de 2017, 0:42 Para: Asunto: Re: [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-08.txt On 06/26/2017 08:05 PM, JORDI PALET MARTINEZ wrote: > Regarding the different issues that are indicated because Happy Eyeba= lls, a possible solution is to increase the timers, so even if IPv6 is =E2= =80=9Cslower=E2=80=9D than IPv4, is not just a matter of 50 milliseconds (f= or example), but several seconds, so then IPv6 will get preference anyway. = I=E2=80=99ve described this in a recent email related to the HE-update docu= ment (so you could use some of the text that I mention in that email): =20 Please be careful about this (for problem 6): I've already seen people advising to "just disable IPv6 to get a speed boost." If the timeout is going to slow down to several seconds, this may make more people switch to using IPv4 only, which would be the complete opposite of the objecti= ve. =20 Sure, you also consider making this setting a knob, but people may go the easiest already known way, because "well, who cares about IPv6 anyw= ay?" =20 Then, all this depends on the proportion of the internet that is alread= y quickly IPv6-reachable, but if there is a problem to solve, it can only be solved by making IPv4 slower when IPv6 is enabled... which sounds like a bad idea to me so long as IPv4's sunset (or IPv6's rise?) isn't complete yet (at which point this solution is no longer needed anyway). =20 Best regards, Leo =20 _______________________________________________ sunset4 mailing list sunset4@ietf.org https://www.ietf.org/mailman/listinfo/sunset4 =20 ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or con= fidential. The information is intended to be for the use of the individual(= s) named above. If you are not the intended recipient be aware that any dis= closure, copying, distribution or use of the contents of this information, = including attached files, is prohibited.