
From nobody Sun Sep  2 10:08:57 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AEB812F1A6 for <v6ops@ietfa.amsl.com>; Sun,  2 Sep 2018 10:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 ac4RjQR0tWr6 for <v6ops@ietfa.amsl.com>; Sun,  2 Sep 2018 10:08:54 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253F0128BAC for <v6ops@ietf.org>; Sun,  2 Sep 2018 10:08:54 -0700 (PDT)
Received: from [192.168.10.10] (hvaler-7-168-20-185.bb.monsternett.net [185.20.168.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 57B7AFECBC58; Sun,  2 Sep 2018 17:08:52 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com>
Date: Sun, 2 Sep 2018 19:08:49 +0200
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4645850B-9496-49F0-A284-09E01C0ED820@employees.org>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/nYUprsxJX-Fo9WtDrIa66xzKbWI>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 02 Sep 2018 17:08:56 -0000

George is making an important point here.=20
If nothing else, the IPv6 only flag can be used to trigger IPv6 only testing=
 and compliance.=20

Cheers=20
Ole

> On 30 Aug 2018, at 00:41, George Michaelson <ggm@algebras.org> wrote:
>=20
> despite having stood up at a microphone and accused Brian of
> propagating 'the evil bit' again, I actually think an advisory 'this
> is a v6 only managed network' is a good idea. It would allow people to
> write code which does:
>=20
> test if v6only, in getting your v6 bindings:
>=20
> On Thu, Aug 30, 2018 at 8:24 AM Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>>=20
>>> On 2018-08-30 08:52, David Farmer wrote:
>>> On Wed, Aug 29, 2018 at 3:37 PM, Mudric, Dusan (Dusan) <dmudric@avaya.co=
m>
>>> wrote:
>>>=20
>>>>> They control the defaults for how Routers construct Router
>>>> Advertisements.
>>>>=20
>>>> And default 'O' flag set to TRUE should enabled stateless DHCPv6 to obt=
ain
>>>> configuration for hosts.
>>>=20
>>>=20
>>> Only if there is, in fact, a DHCPv6 server and it is configured with
>>> appropriate information.  Maybe you wish to recommend net operators depl=
oy
>>> DHCPv6, but change the default for the O flag in RAs is more that.
>>>=20
>>> While I could be sympathetic to recommendations to provide DHCPv6 server=
s
>>> on networks. However, changing the defaults for the M or O flags is not
>>> something I can support.  If I provide a DHCPv6 server then it is my job=
 to
>>> set the flags appropriately in the RA. If I don't provide a DHCPv6 I sho=
uld
>>> not have to do anything. This is how the defaults for the M and O flag a=
re
>>> currently set.
>>=20
>> Exactly. Working out of the box on an unmanaged network has always been
>> a goal for IPv6, even back when it was called IPng. The defaults are
>> set appropriately for that goal.
>>=20
>>    Brian
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Sun Sep  2 12:43:33 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8974130DC2 for <v6ops@ietfa.amsl.com>; Sun,  2 Sep 2018 12:43:31 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 i-s8XawD2ysm for <v6ops@ietfa.amsl.com>; Sun,  2 Sep 2018 12:43:30 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 B76F512F295 for <v6ops@ietf.org>; Sun,  2 Sep 2018 12:43:29 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id a4-v6so7621364plm.13 for <v6ops@ietf.org>; Sun, 02 Sep 2018 12:43:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=OLl5AP4HwP2tktRlC6AoNW8+xoMh4ZjWGmP+Drzi5d0=; b=CQxAQhRA7w1oBY1/ZocFxSb/2pOFbGK+1yUPUHmmcgEBDFKQ3FQgPMOAO3UtEw6foT W/+GlBRfVOpe/PHm/cEvNwjdTW+ygSZzT+6LZXVWGw50cy1/TvCywmreiVL8O1hiFGg9 lVJjivAvG2M5QpuQomzKoXbTs7LM+9uu5LVblti89EdAhGEVRC/9nurTkZT4atlh5H5q /VsyZ/SwLK4H0R3tskG1+Upr4fLaNLMTbFwK+DRlIIgxocwohjxE/zvgGpMckX7x2Ten 9oorhmwtK/bC9rhmq7CMAr2yh5aiTWNIPYPuFfVboipUtP8cRnZbCPQrJVZtsMr1jFTj 8uuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=OLl5AP4HwP2tktRlC6AoNW8+xoMh4ZjWGmP+Drzi5d0=; b=mfwmdcdTzclkpuCqs9TpNYhID8wfDp6l5eeUP66NCi/5+SynEGItekagGeZhHb2ugB CqqU0vmyDdHLmjsoh71UuL0aMh0c93io9OqccBJPjhcneB/6XWWkxNBM4IgjL81hcEbn HsPe1dPF6EYwshbOF0ldqdW/5Y4T1zr+u2sWg69C/8BjTgVA4P7DC3FHDoOukc/bZXp3 k7mR4CQKWCEdqV4fiiAyrpOoYzzB2GguEXnfOdgoXcxfAAH1+auSS2yvcOKmKlSh1dmL Kek+o1VGYXkK1KhHg73ZsLz06Owd2YucIx/nkZ5C70u10GA0FQoH/iZNonhghTByUlAr yiZg==
X-Gm-Message-State: APzg51BK+2vk73nE73yGtl1ZwvenSsBtDrbJlp6zx9myOT7i5duxbDW1 ZvTVGYz+zLoiMkaWAhMvGYM=
X-Google-Smtp-Source: ANB0VdY8T4mlrLRjqo7vZUXt1pqySQBKSEakpktEw5SNAOQFrwgBGp0Lj4pqG7/P/kGLzPVJqnoj2Q==
X-Received: by 2002:a17:902:da4:: with SMTP id 33-v6mr24901695plv.193.1535917409286;  Sun, 02 Sep 2018 12:43:29 -0700 (PDT)
Received: from [10.100.96.213] (125-236-219-163.adsl.xtra.co.nz. [125.236.219.163]) by smtp.gmail.com with ESMTPSA id p19-v6sm19806238pgh.60.2018.09.02.12.43.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Sep 2018 12:43:27 -0700 (PDT)
To: Ole Troan <otroan@employees.org>, George Michaelson <ggm@algebras.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com> <4645850B-9496-49F0-A284-09E01C0ED820@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <dc95892c-ae6f-0158-0373-e1a57ebd2e4b@gmail.com>
Date: Mon, 3 Sep 2018 07:43:22 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <4645850B-9496-49F0-A284-09E01C0ED820@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/VJeEnkbJej1D5MbJwuGybAbwQbY>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 02 Sep 2018 19:43:32 -0000

Sure. We can add that to the draft.

Regards
   Brian

On 2018-09-03 05:08, Ole Troan wrote:
> George is making an important point here. 
> If nothing else, the IPv6 only flag can be used to trigger IPv6 only testing and compliance. 
> 
> Cheers 
> Ole
> 
>> On 30 Aug 2018, at 00:41, George Michaelson <ggm@algebras.org> wrote:
>>
>> despite having stood up at a microphone and accused Brian of
>> propagating 'the evil bit' again, I actually think an advisory 'this
>> is a v6 only managed network' is a good idea. It would allow people to
>> write code which does:
>>
>> test if v6only, in getting your v6 bindings:
>>
>> On Thu, Aug 30, 2018 at 8:24 AM Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>>
>>>> On 2018-08-30 08:52, David Farmer wrote:
>>>> On Wed, Aug 29, 2018 at 3:37 PM, Mudric, Dusan (Dusan) <dmudric@avaya.com>
>>>> wrote:
>>>>
>>>>>> They control the defaults for how Routers construct Router
>>>>> Advertisements.
>>>>>
>>>>> And default 'O' flag set to TRUE should enabled stateless DHCPv6 to obtain
>>>>> configuration for hosts.
>>>>
>>>>
>>>> Only if there is, in fact, a DHCPv6 server and it is configured with
>>>> appropriate information.  Maybe you wish to recommend net operators deploy
>>>> DHCPv6, but change the default for the O flag in RAs is more that.
>>>>
>>>> While I could be sympathetic to recommendations to provide DHCPv6 servers
>>>> on networks. However, changing the defaults for the M or O flags is not
>>>> something I can support.  If I provide a DHCPv6 server then it is my job to
>>>> set the flags appropriately in the RA. If I don't provide a DHCPv6 I should
>>>> not have to do anything. This is how the defaults for the M and O flag are
>>>> currently set.
>>>
>>> Exactly. Working out of the box on an unmanaged network has always been
>>> a goal for IPv6, even back when it was called IPng. The defaults are
>>> set appropriately for that goal.
>>>
>>>    Brian
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> 


From nobody Mon Sep  3 12:05:52 2018
Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8630E130DDE for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 12:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 4i8iNhHfm0oo for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 12:05:48 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92E4130DEB for <v6ops@ietf.org>; Mon,  3 Sep 2018 12:05:46 -0700 (PDT)
Received: from [192.168.1.14] (unknown [79.106.126.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id A71FD862D9; Mon,  3 Sep 2018 21:05:32 +0200 (CEST)
To: Ole Troan <otroan@employees.org>, George Michaelson <ggm@algebras.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com> <4645850B-9496-49F0-A284-09E01C0ED820@employees.org>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Autocrypt: addr=fgont@si6networks.com; prefer-encrypt=mutual; keydata= xsFNBE5so2gBEACzBQBLUy8nzgAzSZn6ViXT6TmZBFNYNqTpPRvTVtUqF6+tkI+IEd9N2E8p pXUXCd0W4dkxz6o7pagnK63m4QSueggvp881RVVHOF8oTSHOdnGxLfLeLNJFKE1FOutU3vod GK/wG/Fwzkv9MebdXpMlLV8nnJuAt66XGl/lU1JrNfrKO4SoYQi4TsB/waUQcygh7OR/PEO0 EttiU8kZUbZNv58WH+PAj/rdZCrgUSiGXiWUQQKShqKnJxLuAcTcg5YRwL8se/V6ciW0QR9i /sr52gSmLLbW5N3hAoO+nv1V/9SjJAUvzXu43k8sua/XlCXkqU7uLj41CRR72JeUZ4DQsYfP LfNPC98ZGTVxbWbFtLXxpzzDDT8i3uo7w1LJ2Ij/d5ezcARqw01HGljWWxnidUrjbTpxkJ9X EllcsH94mer728j/HKzC9OcTuz6WUBP3Crgl6Q47gY5ZIiF0lsmd9/wxbaq5NiJ+lGuBRZrD v0dQx9KmyI0/pH2AF8cW897/6ypvcyD/1/11CJcN+uAGIrklwJlVpRSbKbFtGC6In592lhu7 wnK8cgyP5cTU+vva9+g6P1wehi4bylXdlKc6mMphbtSA+T3WBNP557+mh3L62l4pGaEGidcZ DLYT2Ud18eAJmxU3HnM8P3iZZgeoK7oqgb53/eg96vkONXNIOwARAQABzSVGZXJuYW5kbyBH b250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20+wsGBBBMBAgArAhsjBQkSzAMABgsJCAcDAgYV CAIJCgsEFgIDAQIeAQIXgAUCTmylpQIZAQAKCRCuJQ1VHU50kv7wD/9fuNtTfxSLk3B3Hs3p ixTy8YXVjdkVwWlnJjFd7BOWmg7sI+LDhpjGfT6+ddOiwkumnvUZpObodj4ysH0i8c7P4C5t F9yu7WjklSlrB5Rth2CGChg5bKt541z2WHkFFxys9qBLmCSYDeKQkzLqhCjIUJizY2kOJ2GI MnSFDzJjhSFEh//oW830Y8fel1xnf/NVF+lBVtRMtMOfoWUqDjvP3sJ1G4zgkDCnF0CfncLx +hq2Mv26Uq9OTzvLH9aSQQ/f067BOkKAJKsfHdborX4E96ISTz57/4xECRSMr5dVsKVm4Y// uVIsb+L5z+a32FaiBZIAKDgnJO7Z8j6CV5e5yfuBTtX52Yi9HjYYqnYJGSDxYd6igD4bWu+7 xmJPHjkdqZgGV6dQIgiUfqkU+s5Cv350vK48CMaT/ZLo2BdsMhWsmaHmb+waePUMyq6E4E9x 9Js+EJb9ZiCfxS9exgieZQpet1L36IvhiwByvkQM009ywfa30JeMOltUtfLi5V06WQWsTzPL 5C+4cpkguSuAJVDTctjCA0moIeVDOpJ8WH9voQ4IeWapQnX35OIoj1jGJqqYdx65gc1ygbyx b8vw+pJ9E5GLse5TQnYifOWpXzX9053dtbwp/2OVhU4KLlzfCPCEsoTyfu9nIZxdI2PMwiL5 M85BfjX4NmwBLmPGoM7BTQRObKNoARAAqqXCkr250BchRDmi+05F5UQFgylUh10XTAJxBeaQ UNtdxZiZRm6jgomSrqeYtricM9t9K0qb4X2ZXmAMW8o8AYW3RrQHTjcBwMnAKzUIEXXWaLfG cid/ygmvWzIHgMDQKP+MUq1AGQrnvt/MRLvZLyczAV1RTXS58qNaxtaSpc3K/yrDozh/a4pu WcUsVvIkzyx43sqcwamDSBb6U8JFoZizuLXiARLLASgyHrrCedNIZdWSx0z0iHEpZIelA2ih AGLiSMtmtikVEyrJICgO81DkKNCbBbPg+7fi23V6M24+3syHk3IdQibTtBMxinIPyLFF0byJ aGm0fmjefhnmVJyCIl/FDkCHprVhTme57G2/WdoGnUvnT7mcwDRb8XY5nNRkOJsqqLPemKjz kx8mXdQbunXtX9bKyVgd1gIl+LLsxbdzRCch773UBVoortPdK3kMyLtZ4uMeDX3comjx+6VL bztUdJ1Zc9/njwVG8fgmQ+0Kj5+bzQfUY+MmX0HTXIx3B4R1I1a8QoOwi1N+iZNdewV5Zfq+ 29NlQLnVPjCRCKbaz9k6RJ2oIti55YUI6zSsL3lmlOXsRbXN5bRswFczkNSCJxJMlDiyAUIC WOay7ymzvgzPa+BY/mYn94vRaurDQ4/ljOfj6oqgfjts+dJev4Jj89vp8MQI3KJpZPEAEQEA AcLBZQQYAQIADwUCTmyjaAIbDAUJEswDAAAKCRCuJQ1VHU50km4xEACho45PZrUjY4Zl2opR DFNo5a6roTOPpgwO9PcBb3I5F8yX2Dnew+9OhgWXbBhAFq4DCx+9Gjs43Bn60qbZTDbLGJ/m 8N4PwEiq0e5MKceYcbetEdEUWhm5L6psU9ZZ82GR3UGxPXYe+oifEoJjOXQ39avf9S8p3yKP Diil0E79rn7LbJjMcgMLyjFg9SDoJ6pHLtniJoDhEAaSSgeV7Y745+gyMIdtQmrFHfqrFdjq D6G0HE+Z68ywc5KN67YxhvhBmSycs1ZSKAXv1zLDlXdmjHDHkU3xMcB+RkuiTba8yRFYwb/n j62CC4NhFTuIKOc4ta3dJsyXTGh/hO9UjWUnmAGfd0fnzTBZF8Qlnw/8ftx5lt4/O+eqY1EN RITScnPzXE/wMOlTtdkddQ+QN6xt6jyR2XtAIi7aAFHypIqA3lLI9hF9x+lj4UQ2yA9LqpoX 6URpPOd13JhAyDe47cwsP1u9Y+OBvQTVLSvw7Liu2b4KjqL4lx++VdBi7dXsjJ6kjIRjI6Lb WVpxe8LumMCuVDepTafBZ49gr7Fgc4F9ZSCo6ChgQNLn6WDzIkqFX+42KuHz90AHWhuW+KZR 1aJylERWeTcMCGUSBptd48KniWmD6kPKpzwoMkJtEXTuO2lVuborxzwuqOTNuYg9lWDl7zKt wPI9brGzquUHy4qRrA==
Message-ID: <68a76cb2-911f-186d-dc78-7d6116dcb790@si6networks.com>
Date: Mon, 3 Sep 2018 21:00:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <4645850B-9496-49F0-A284-09E01C0ED820@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/V8o1nPgRbrvoZbcAVuNibIcn8WU>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 03 Sep 2018 19:05:51 -0000

On 09/02/2018 07:08 PM, Ole Troan wrote:
> George is making an important point here. 
> If nothing else, the IPv6 only flag can be used to trigger IPv6 only testing and compliance. 

In order for that to be possible, shouldn't reaction to the flag need to
be compulsory, rather than simply advisory?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Sep  3 12:06:03 2018
Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75D87130E58 for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 12:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ha7MbJgXFTEE for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 12:05:54 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2A66130E44 for <v6ops@ietf.org>; Mon,  3 Sep 2018 12:05:53 -0700 (PDT)
Received: from [192.168.1.14] (unknown [79.106.126.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 29F79862E1; Mon,  3 Sep 2018 21:05:45 +0200 (CEST)
To: Lee Howard <lee@asgard.org>, v6ops@ietf.org
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <8661280d-fc91-eb1b-2531-29bd6dbb23d8@asgard.org>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Autocrypt: addr=fgont@si6networks.com; prefer-encrypt=mutual; keydata= xsFNBE5so2gBEACzBQBLUy8nzgAzSZn6ViXT6TmZBFNYNqTpPRvTVtUqF6+tkI+IEd9N2E8p pXUXCd0W4dkxz6o7pagnK63m4QSueggvp881RVVHOF8oTSHOdnGxLfLeLNJFKE1FOutU3vod GK/wG/Fwzkv9MebdXpMlLV8nnJuAt66XGl/lU1JrNfrKO4SoYQi4TsB/waUQcygh7OR/PEO0 EttiU8kZUbZNv58WH+PAj/rdZCrgUSiGXiWUQQKShqKnJxLuAcTcg5YRwL8se/V6ciW0QR9i /sr52gSmLLbW5N3hAoO+nv1V/9SjJAUvzXu43k8sua/XlCXkqU7uLj41CRR72JeUZ4DQsYfP LfNPC98ZGTVxbWbFtLXxpzzDDT8i3uo7w1LJ2Ij/d5ezcARqw01HGljWWxnidUrjbTpxkJ9X EllcsH94mer728j/HKzC9OcTuz6WUBP3Crgl6Q47gY5ZIiF0lsmd9/wxbaq5NiJ+lGuBRZrD v0dQx9KmyI0/pH2AF8cW897/6ypvcyD/1/11CJcN+uAGIrklwJlVpRSbKbFtGC6In592lhu7 wnK8cgyP5cTU+vva9+g6P1wehi4bylXdlKc6mMphbtSA+T3WBNP557+mh3L62l4pGaEGidcZ DLYT2Ud18eAJmxU3HnM8P3iZZgeoK7oqgb53/eg96vkONXNIOwARAQABzSVGZXJuYW5kbyBH b250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20+wsGBBBMBAgArAhsjBQkSzAMABgsJCAcDAgYV CAIJCgsEFgIDAQIeAQIXgAUCTmylpQIZAQAKCRCuJQ1VHU50kv7wD/9fuNtTfxSLk3B3Hs3p ixTy8YXVjdkVwWlnJjFd7BOWmg7sI+LDhpjGfT6+ddOiwkumnvUZpObodj4ysH0i8c7P4C5t F9yu7WjklSlrB5Rth2CGChg5bKt541z2WHkFFxys9qBLmCSYDeKQkzLqhCjIUJizY2kOJ2GI MnSFDzJjhSFEh//oW830Y8fel1xnf/NVF+lBVtRMtMOfoWUqDjvP3sJ1G4zgkDCnF0CfncLx +hq2Mv26Uq9OTzvLH9aSQQ/f067BOkKAJKsfHdborX4E96ISTz57/4xECRSMr5dVsKVm4Y// uVIsb+L5z+a32FaiBZIAKDgnJO7Z8j6CV5e5yfuBTtX52Yi9HjYYqnYJGSDxYd6igD4bWu+7 xmJPHjkdqZgGV6dQIgiUfqkU+s5Cv350vK48CMaT/ZLo2BdsMhWsmaHmb+waePUMyq6E4E9x 9Js+EJb9ZiCfxS9exgieZQpet1L36IvhiwByvkQM009ywfa30JeMOltUtfLi5V06WQWsTzPL 5C+4cpkguSuAJVDTctjCA0moIeVDOpJ8WH9voQ4IeWapQnX35OIoj1jGJqqYdx65gc1ygbyx b8vw+pJ9E5GLse5TQnYifOWpXzX9053dtbwp/2OVhU4KLlzfCPCEsoTyfu9nIZxdI2PMwiL5 M85BfjX4NmwBLmPGoM7BTQRObKNoARAAqqXCkr250BchRDmi+05F5UQFgylUh10XTAJxBeaQ UNtdxZiZRm6jgomSrqeYtricM9t9K0qb4X2ZXmAMW8o8AYW3RrQHTjcBwMnAKzUIEXXWaLfG cid/ygmvWzIHgMDQKP+MUq1AGQrnvt/MRLvZLyczAV1RTXS58qNaxtaSpc3K/yrDozh/a4pu WcUsVvIkzyx43sqcwamDSBb6U8JFoZizuLXiARLLASgyHrrCedNIZdWSx0z0iHEpZIelA2ih AGLiSMtmtikVEyrJICgO81DkKNCbBbPg+7fi23V6M24+3syHk3IdQibTtBMxinIPyLFF0byJ aGm0fmjefhnmVJyCIl/FDkCHprVhTme57G2/WdoGnUvnT7mcwDRb8XY5nNRkOJsqqLPemKjz kx8mXdQbunXtX9bKyVgd1gIl+LLsxbdzRCch773UBVoortPdK3kMyLtZ4uMeDX3comjx+6VL bztUdJ1Zc9/njwVG8fgmQ+0Kj5+bzQfUY+MmX0HTXIx3B4R1I1a8QoOwi1N+iZNdewV5Zfq+ 29NlQLnVPjCRCKbaz9k6RJ2oIti55YUI6zSsL3lmlOXsRbXN5bRswFczkNSCJxJMlDiyAUIC WOay7ymzvgzPa+BY/mYn94vRaurDQ4/ljOfj6oqgfjts+dJev4Jj89vp8MQI3KJpZPEAEQEA AcLBZQQYAQIADwUCTmyjaAIbDAUJEswDAAAKCRCuJQ1VHU50km4xEACho45PZrUjY4Zl2opR DFNo5a6roTOPpgwO9PcBb3I5F8yX2Dnew+9OhgWXbBhAFq4DCx+9Gjs43Bn60qbZTDbLGJ/m 8N4PwEiq0e5MKceYcbetEdEUWhm5L6psU9ZZ82GR3UGxPXYe+oifEoJjOXQ39avf9S8p3yKP Diil0E79rn7LbJjMcgMLyjFg9SDoJ6pHLtniJoDhEAaSSgeV7Y745+gyMIdtQmrFHfqrFdjq D6G0HE+Z68ywc5KN67YxhvhBmSycs1ZSKAXv1zLDlXdmjHDHkU3xMcB+RkuiTba8yRFYwb/n j62CC4NhFTuIKOc4ta3dJsyXTGh/hO9UjWUnmAGfd0fnzTBZF8Qlnw/8ftx5lt4/O+eqY1EN RITScnPzXE/wMOlTtdkddQ+QN6xt6jyR2XtAIi7aAFHypIqA3lLI9hF9x+lj4UQ2yA9LqpoX 6URpPOd13JhAyDe47cwsP1u9Y+OBvQTVLSvw7Liu2b4KjqL4lx++VdBi7dXsjJ6kjIRjI6Lb WVpxe8LumMCuVDepTafBZ49gr7Fgc4F9ZSCo6ChgQNLn6WDzIkqFX+42KuHz90AHWhuW+KZR 1aJylERWeTcMCGUSBptd48KniWmD6kPKpzwoMkJtEXTuO2lVuborxzwuqOTNuYg9lWDl7zKt wPI9brGzquUHy4qRrA==
Message-ID: <19f2d65d-8cc6-03c3-4b28-9c7324b1f9e5@si6networks.com>
Date: Mon, 3 Sep 2018 21:05:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <8661280d-fc91-eb1b-2531-29bd6dbb23d8@asgard.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/xUuMucSYk1Xvntlyja_gJoD8UUY>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 03 Sep 2018 19:06:00 -0000

On 08/31/2018 03:47 PM, Lee Howard wrote:
> 
> 
> On 08/30/2018 03:26 PM, Mudric, Dusan (Dusan) wrote:
>>> Exactly. Working out of the box on an unmanaged network has always been
>>> a goal for IPv6,
>> I expected plug-and-play, or unmanaged network, means devices deployed
>> to those networks should work based on the network defaults. If DHCPv6
>> is added to the network, 'O' flag needs to be set. That means managing
>> the network.
> 
> An "unmanaged network" that is "based on the network defaults" sounds
> like it's in conflict with a server being "added to the network."

Agreed.



> The M bit means there are addresses available via DHCPv6. It doesn't
> mean you have to use them.

Well, the bits seems to indicate that that is how you get addresses.
Not using them is kind of the same as not using any information in the RAs.



> The O bit means there is other configuration information available via
> DHCPv6. It is redundant if the M bit is set.
> Neither requires a device to pay attention to them.

This seems more of a flaw thatn a feature to me.



>>>> If I don't provide a DHCPv6 I should
>>>> not have to do anything.
>> Right. If nothing is added to the network, there is no need to change
>> the network configuration. But that is not the point. Plug-and-play is
>> used when something is added to the network. There should not be a
>> need to change 'O' bit when DHCPv6 server and DHCPv6 capable hosts are
>> added to the network. And, if there are no DHCPv6 servers and DHCPv6
>> capable hosts in that network, sending 'O'=TRUE will not impact  the
>> network.
> 
> How does a router (a thing sending RAs) know a DHCPv6 server has been
> added to the network?

Same way as it knows there's no router providing IPv4 service when
setting the "IPv6 only" flag?



> Even if a router is configured as a DHCPv6 relay, how does it know
> whether the M and/or O bits apply? That is, how does it know whether the
> DHCPv6 server is supplying addresses (M bit), or no addresses but
> DNS/NTP/other configuration (O bit)? (If the M bit is set, O is implied,
> per rfc4861).
> 
> You could require DHCPv6 snooping, but it's several layers of logic to
> compare what the client requests vs. what the response is. And to revise
> RAs based on changing DHCPv6 configurations. If the router *is* the
> DHCPv6 server, the logic is much simpler.
> 
> I'm content to say that if you add a server to provide network layer
> information, you are managing the network, and are therefore overriding
> defaults and are expected to manage the network. Essentially, the M bit.

+1

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Sep  3 12:43:42 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E88A130DEB for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 12:43:40 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 HwKyAoOkO9Cj for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 12:43:37 -0700 (PDT)
Received: from mail-pf1-x442.google.com (mail-pf1-x442.google.com [IPv6:2607:f8b0:4864:20::442]) (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 842BB128BAC for <v6ops@ietf.org>; Mon,  3 Sep 2018 12:43:37 -0700 (PDT)
Received: by mail-pf1-x442.google.com with SMTP id j26-v6so545064pfi.10 for <v6ops@ietf.org>; Mon, 03 Sep 2018 12:43:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=5CBlbklRa8z4XWNLXe+HUz9La+3FigorhDOYjiD8AMw=; b=Oec76BnGvD+guoGIe+3ZGPd6RcXHyRA5Xs93NLuAxd5gC8kR6cvhyCus5EIIUrvBW2 RTdZBvs6Uv5tvbspGieYDhSjZSz+5b+XzRP3znDXfCUTm6F5H2LSLrN8/m4k9ZHPlrNA mPEsNd+4PO36fykGh60mNJ4RjZTb53t0xR4Mw0tu27IR2ZF2NY5NmJY1lwLDheGMg8f7 imc0IvFwuZTIb3fGOV/KszLdXJxuOSIZSMtgJCSaOieeBnDuXU6lx9Dok9p71BAizVaF +s0MP8KL/jxgiF9qhkyYF+gPKVDEdLD23+WB352Ew4Bc4bZFDJCNSIYIYyo3NLLWkK5E 9ZzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=5CBlbklRa8z4XWNLXe+HUz9La+3FigorhDOYjiD8AMw=; b=Be4XEsZt4rKjXG4Hx4ISiiOH4cKAGxOhCW5UI4yIBKiOOOPj+EimslTZCRLfpE7VGq DPxZBMqaE+bYHjjLyGLzrvuM0+h9kZw/42QAEK4aqkGPhAAupyjjWnTnm8duWzNiAfsk Cr8tZouPRE7v45i7C1t9eeYaVuNjxsrId8GMyLmIDOtv0MuJ/jYmFvj56Xx1xUuMI1ia o32Ufh9At+dEKPuDMAx12yVMaSOIrL4UXcmJU2SUoWu/X9Erxzc2e2Hl4SYJL10tEgxE SN5M1oH3ngFqra/jhBOwbACjpSr5dyCP79cPY3Qq2u2GK0XiyyoN3WWJse93AWjwG+Zv 3Img==
X-Gm-Message-State: APzg51DbLJYpR3orIDkO838j8CNENbZqu34hgqoOjyR4OAkrZ9/SRhhp TmrUJkfkt7mTD+K2hwkKwWSAPglx
X-Google-Smtp-Source: ANB0VdZEuwoiyt52V0TrtC3hS54GSbtWKu4K8dlDVsvRTVcIK4w1xWIJA7CHvvpZU/yjK/urViawUQ==
X-Received: by 2002:a63:9a02:: with SMTP id o2-v6mr9357954pge.440.1536003816700;  Mon, 03 Sep 2018 12:43:36 -0700 (PDT)
Received: from [10.100.96.213] (125-236-219-163.adsl.xtra.co.nz. [125.236.219.163]) by smtp.gmail.com with ESMTPSA id p64-v6sm31858877pfa.47.2018.09.03.12.43.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Sep 2018 12:43:35 -0700 (PDT)
To: Fernando Gont <fgont@si6networks.com>, Ole Troan <otroan@employees.org>, George Michaelson <ggm@algebras.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com> <4645850B-9496-49F0-A284-09E01C0ED820@employees.org> <68a76cb2-911f-186d-dc78-7d6116dcb790@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a0736784-77f7-5d09-f961-a5b4428e684e@gmail.com>
Date: Tue, 4 Sep 2018 07:43:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <68a76cb2-911f-186d-dc78-7d6116dcb790@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3Prj46Sck1wgzevD4yB97trlCkE>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 03 Sep 2018 19:43:41 -0000

On 2018-09-04 07:00, Fernando Gont wrote:
> On 09/02/2018 07:08 PM, Ole Troan wrote:
>> George is making an important point here. 
>> If nothing else, the IPv6 only flag can be used to trigger IPv6 only testing and compliance. 
> 
> In order for that to be possible, shouldn't reaction to the flag need to
> be compulsory, rather than simply advisory?

There's no such thing as compulsory in the Internet ;-).

It's a SHOULD in the draft**. Any node that emits IPv4 traffic when the bit
is set is either a legacy host or a dual stack host that's not entered
a v6-only mode. So that means it's a host worth checking as part of
the v6-only test.

**"Dual stack hosts that have a good reason to use IPv4, for example for
   a specific IPv4 link-local service, can continue to do so.  This is
   consistent with the SHOULD language in this document."

      Brian


From nobody Mon Sep  3 18:49:01 2018
Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D6B1286E3 for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 18:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.308
X-Spam-Level: 
X-Spam-Status: No, score=-0.308 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Rv8hQdxSYc6a for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 18:48:57 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADAEB12785F for <v6ops@ietf.org>; Mon,  3 Sep 2018 18:48:56 -0700 (PDT)
Received: from [192.168.1.14] (unknown [79.106.126.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 8E39383984; Tue,  4 Sep 2018 03:48:45 +0200 (CEST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ole Troan <otroan@employees.org>, George Michaelson <ggm@algebras.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com> <4645850B-9496-49F0-A284-09E01C0ED820@employees.org> <68a76cb2-911f-186d-dc78-7d6116dcb790@si6networks.com> <a0736784-77f7-5d09-f961-a5b4428e684e@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Autocrypt: addr=fgont@si6networks.com; prefer-encrypt=mutual; keydata= xsFNBE5so2gBEACzBQBLUy8nzgAzSZn6ViXT6TmZBFNYNqTpPRvTVtUqF6+tkI+IEd9N2E8p pXUXCd0W4dkxz6o7pagnK63m4QSueggvp881RVVHOF8oTSHOdnGxLfLeLNJFKE1FOutU3vod GK/wG/Fwzkv9MebdXpMlLV8nnJuAt66XGl/lU1JrNfrKO4SoYQi4TsB/waUQcygh7OR/PEO0 EttiU8kZUbZNv58WH+PAj/rdZCrgUSiGXiWUQQKShqKnJxLuAcTcg5YRwL8se/V6ciW0QR9i /sr52gSmLLbW5N3hAoO+nv1V/9SjJAUvzXu43k8sua/XlCXkqU7uLj41CRR72JeUZ4DQsYfP LfNPC98ZGTVxbWbFtLXxpzzDDT8i3uo7w1LJ2Ij/d5ezcARqw01HGljWWxnidUrjbTpxkJ9X EllcsH94mer728j/HKzC9OcTuz6WUBP3Crgl6Q47gY5ZIiF0lsmd9/wxbaq5NiJ+lGuBRZrD v0dQx9KmyI0/pH2AF8cW897/6ypvcyD/1/11CJcN+uAGIrklwJlVpRSbKbFtGC6In592lhu7 wnK8cgyP5cTU+vva9+g6P1wehi4bylXdlKc6mMphbtSA+T3WBNP557+mh3L62l4pGaEGidcZ DLYT2Ud18eAJmxU3HnM8P3iZZgeoK7oqgb53/eg96vkONXNIOwARAQABzSVGZXJuYW5kbyBH b250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20+wsGBBBMBAgArAhsjBQkSzAMABgsJCAcDAgYV CAIJCgsEFgIDAQIeAQIXgAUCTmylpQIZAQAKCRCuJQ1VHU50kv7wD/9fuNtTfxSLk3B3Hs3p ixTy8YXVjdkVwWlnJjFd7BOWmg7sI+LDhpjGfT6+ddOiwkumnvUZpObodj4ysH0i8c7P4C5t F9yu7WjklSlrB5Rth2CGChg5bKt541z2WHkFFxys9qBLmCSYDeKQkzLqhCjIUJizY2kOJ2GI MnSFDzJjhSFEh//oW830Y8fel1xnf/NVF+lBVtRMtMOfoWUqDjvP3sJ1G4zgkDCnF0CfncLx +hq2Mv26Uq9OTzvLH9aSQQ/f067BOkKAJKsfHdborX4E96ISTz57/4xECRSMr5dVsKVm4Y// uVIsb+L5z+a32FaiBZIAKDgnJO7Z8j6CV5e5yfuBTtX52Yi9HjYYqnYJGSDxYd6igD4bWu+7 xmJPHjkdqZgGV6dQIgiUfqkU+s5Cv350vK48CMaT/ZLo2BdsMhWsmaHmb+waePUMyq6E4E9x 9Js+EJb9ZiCfxS9exgieZQpet1L36IvhiwByvkQM009ywfa30JeMOltUtfLi5V06WQWsTzPL 5C+4cpkguSuAJVDTctjCA0moIeVDOpJ8WH9voQ4IeWapQnX35OIoj1jGJqqYdx65gc1ygbyx b8vw+pJ9E5GLse5TQnYifOWpXzX9053dtbwp/2OVhU4KLlzfCPCEsoTyfu9nIZxdI2PMwiL5 M85BfjX4NmwBLmPGoM7BTQRObKNoARAAqqXCkr250BchRDmi+05F5UQFgylUh10XTAJxBeaQ UNtdxZiZRm6jgomSrqeYtricM9t9K0qb4X2ZXmAMW8o8AYW3RrQHTjcBwMnAKzUIEXXWaLfG cid/ygmvWzIHgMDQKP+MUq1AGQrnvt/MRLvZLyczAV1RTXS58qNaxtaSpc3K/yrDozh/a4pu WcUsVvIkzyx43sqcwamDSBb6U8JFoZizuLXiARLLASgyHrrCedNIZdWSx0z0iHEpZIelA2ih AGLiSMtmtikVEyrJICgO81DkKNCbBbPg+7fi23V6M24+3syHk3IdQibTtBMxinIPyLFF0byJ aGm0fmjefhnmVJyCIl/FDkCHprVhTme57G2/WdoGnUvnT7mcwDRb8XY5nNRkOJsqqLPemKjz kx8mXdQbunXtX9bKyVgd1gIl+LLsxbdzRCch773UBVoortPdK3kMyLtZ4uMeDX3comjx+6VL bztUdJ1Zc9/njwVG8fgmQ+0Kj5+bzQfUY+MmX0HTXIx3B4R1I1a8QoOwi1N+iZNdewV5Zfq+ 29NlQLnVPjCRCKbaz9k6RJ2oIti55YUI6zSsL3lmlOXsRbXN5bRswFczkNSCJxJMlDiyAUIC WOay7ymzvgzPa+BY/mYn94vRaurDQ4/ljOfj6oqgfjts+dJev4Jj89vp8MQI3KJpZPEAEQEA AcLBZQQYAQIADwUCTmyjaAIbDAUJEswDAAAKCRCuJQ1VHU50km4xEACho45PZrUjY4Zl2opR DFNo5a6roTOPpgwO9PcBb3I5F8yX2Dnew+9OhgWXbBhAFq4DCx+9Gjs43Bn60qbZTDbLGJ/m 8N4PwEiq0e5MKceYcbetEdEUWhm5L6psU9ZZ82GR3UGxPXYe+oifEoJjOXQ39avf9S8p3yKP Diil0E79rn7LbJjMcgMLyjFg9SDoJ6pHLtniJoDhEAaSSgeV7Y745+gyMIdtQmrFHfqrFdjq D6G0HE+Z68ywc5KN67YxhvhBmSycs1ZSKAXv1zLDlXdmjHDHkU3xMcB+RkuiTba8yRFYwb/n j62CC4NhFTuIKOc4ta3dJsyXTGh/hO9UjWUnmAGfd0fnzTBZF8Qlnw/8ftx5lt4/O+eqY1EN RITScnPzXE/wMOlTtdkddQ+QN6xt6jyR2XtAIi7aAFHypIqA3lLI9hF9x+lj4UQ2yA9LqpoX 6URpPOd13JhAyDe47cwsP1u9Y+OBvQTVLSvw7Liu2b4KjqL4lx++VdBi7dXsjJ6kjIRjI6Lb WVpxe8LumMCuVDepTafBZ49gr7Fgc4F9ZSCo6ChgQNLn6WDzIkqFX+42KuHz90AHWhuW+KZR 1aJylERWeTcMCGUSBptd48KniWmD6kPKpzwoMkJtEXTuO2lVuborxzwuqOTNuYg9lWDl7zKt wPI9brGzquUHy4qRrA==
Message-ID: <bcbdfd68-1331-4966-e4e0-c402bb6ad703@si6networks.com>
Date: Mon, 3 Sep 2018 22:05:39 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <a0736784-77f7-5d09-f961-a5b4428e684e@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rBVqEyJ91QzJW9pMfqK9PeK7-Sw>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 04 Sep 2018 01:48:59 -0000

On 09/03/2018 09:43 PM, Brian E Carpenter wrote:
> On 2018-09-04 07:00, Fernando Gont wrote:
>> On 09/02/2018 07:08 PM, Ole Troan wrote:
>>> George is making an important point here. 
>>> If nothing else, the IPv6 only flag can be used to trigger IPv6 only testing and compliance. 
>>
>> In order for that to be possible, shouldn't reaction to the flag need to
>> be compulsory, rather than simply advisory?
> 
> There's no such thing as compulsory in the Internet ;-).
> 
> It's a SHOULD in the draft**.

Ack. FWIW, I have not checked a recent version of the I-D, and was
assuming (based on list discussion) that the requirement level was less
than SHOULD.



> Any node that emits IPv4 traffic when the bit
> is set is either a legacy host or a dual stack host that's not entered
> a v6-only mode. So that means it's a host worth checking as part of
> the v6-only test.
> 
> **"Dual stack hosts that have a good reason to use IPv4, for example for
>    a specific IPv4 link-local service, can continue to do so.  This is
>    consistent with the SHOULD language in this document."

But... is that IPv6 only? At the end of the day, it would seem that for
most home and enterprise networks, you will always have a reason for
doing some IPv4.. so I wonder when one would see this bit have practical
effect. -- most enterprise and home networks will normally do DNS-SD or
LLMNR, and associated sevices. Also, think about e.g. printers that are
likely going to remain IPv4-only till they eventually beak and get replaced.

Put another way: Is the above "exception" really expected to be an
exception, or actually more like a norm (normal scenario)?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Sep  3 19:03:34 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8076612785F for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 19:03:33 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 fZwGOCLWgvnq for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 19:03:31 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 DB023127333 for <v6ops@ietf.org>; Mon,  3 Sep 2018 19:03:31 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id x17-v6so866087pfh.5 for <v6ops@ietf.org>; Mon, 03 Sep 2018 19:03:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=K9R8GNO8ME+dCEHQNFd9goAfFp3aLlPvnVrMhDhQcTw=; b=kKKt7MIigKx83vSF9xe7g2J7L9RLO/vqRQ7uOBaZXwknGmhPF405akdG05ppJB12vC ogW7RjCnYmddCWFeOxSAmDJw6/S80sAwS2PDFm7Hbwu5zcJq1eXxwRD+gcf15U3fBKoo GeuYPNCFqQ9+qsDUvtgheMo4gkwybBCrdkG0NVlW+DCFAYSyi2m+lhkce28x/o2+2DAd IaS5P9OroN1ItEwhFGT1t7u2Cq00hmd8bSkzVAYD6gSgyAM2MRjMaqIGAa1rTmAsfCeM +HkUzBknWWTUW5x3db1VE+rKTOuknVfgZI+n6npGjI5OHQBiD9Ev7XVK6L/mG18SQsb2 0bgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=K9R8GNO8ME+dCEHQNFd9goAfFp3aLlPvnVrMhDhQcTw=; b=FzYYrHkR4YFgx9zuB353x+do4B49rhK6vwxgVawsZXNZ+eOWQ7/yaoaSltWppnEX0T Wvl5m2ULXxqy7DYD8H0zoiih/PKGAm1BFNCretgzPZ9cnZO0GSdtXSQrNbfsYqTSPMzd X1iCiFP+STP1DotMBKdtZ+KWZJYSQOAgMIsVb8qFaPNnSdm8Y6WeTeCRWMG8a4DyLrmm EIvX2ZunCEwSKUynGAM25uFoyP3QUN6pWDVTblcoFdQVXIteDhYmlOxVW7Jw/cmpt26j K+RqfEEKh/duBamcWNPNaExMcw9LmUDmH1PIH0x9FFQp8GQWYN8U0pXFjCjyDNqjLORs ZfsQ==
X-Gm-Message-State: APzg51AF04XakwTwE66BVJey50CYB7VRaZkx38Uv7z6YQwxfoZExWOsL /KwwZCwrz5MVMgscHFUMX3c69Up0
X-Google-Smtp-Source: ANB0VdZCV7COezEzxibjrQnKPeD7wvfZS98vviMRN4eeY1B/wLnGn87Qyg6LjhwTcOsxEAfTIzqx7g==
X-Received: by 2002:a63:1d3:: with SMTP id 202-v6mr28973051pgb.136.1536026611045;  Mon, 03 Sep 2018 19:03:31 -0700 (PDT)
Received: from [10.100.96.213] (125-236-219-163.adsl.xtra.co.nz. [125.236.219.163]) by smtp.gmail.com with ESMTPSA id u11-v6sm30649535pfd.117.2018.09.03.19.03.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Sep 2018 19:03:30 -0700 (PDT)
To: Fernando Gont <fgont@si6networks.com>, Ole Troan <otroan@employees.org>, George Michaelson <ggm@algebras.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com> <4645850B-9496-49F0-A284-09E01C0ED820@employees.org> <68a76cb2-911f-186d-dc78-7d6116dcb790@si6networks.com> <a0736784-77f7-5d09-f961-a5b4428e684e@gmail.com> <bcbdfd68-1331-4966-e4e0-c402bb6ad703@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <21e9805c-7c2e-3261-4bf6-04fb21f60f41@gmail.com>
Date: Tue, 4 Sep 2018 14:03:26 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <bcbdfd68-1331-4966-e4e0-c402bb6ad703@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_CQMuJRfjPrFMmYfo_hgFCRjiKM>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 04 Sep 2018 02:03:34 -0000

On 2018-09-04 08:05, Fernando Gont wrote:
> On 09/03/2018 09:43 PM, Brian E Carpenter wrote:
>> On 2018-09-04 07:00, Fernando Gont wrote:
>>> On 09/02/2018 07:08 PM, Ole Troan wrote:
>>>> George is making an important point here. 
>>>> If nothing else, the IPv6 only flag can be used to trigger IPv6 only testing and compliance. 
>>>
>>> In order for that to be possible, shouldn't reaction to the flag need to
>>> be compulsory, rather than simply advisory?
>>
>> There's no such thing as compulsory in the Internet ;-).
>>
>> It's a SHOULD in the draft**.
> 
> Ack. FWIW, I have not checked a recent version of the I-D, and was
> assuming (based on list discussion) that the requirement level was less
> than SHOULD.
> 
> 
> 
>> Any node that emits IPv4 traffic when the bit
>> is set is either a legacy host or a dual stack host that's not entered
>> a v6-only mode. So that means it's a host worth checking as part of
>> the v6-only test.
>>
>> **"Dual stack hosts that have a good reason to use IPv4, for example for
>>    a specific IPv4 link-local service, can continue to do so.  This is
>>    consistent with the SHOULD language in this document."
> 
> But... is that IPv6 only? At the end of the day, it would seem that for
> most home and enterprise networks, you will always have a reason for
> doing some IPv4.. so I wonder when one would see this bit have practical
> effect. -- most enterprise and home networks will normally do DNS-SD or

DNS-SD works for IPv6 too afaik

> LLMNR, and associated sevices. Also, think about e.g. printers that are
> likely going to remain IPv4-only till they eventually beak and get replaced.

Indeed. This is a long-term play; I would expect that if the IPv6only bit is
approved and deployed, it will become increasingly relevant as the legacy
nodes slowly vanish. And at the end it will become irrelevant again.
 
> Put another way: Is the above "exception" really expected to be an
> exception, or actually more like a norm (normal scenario)?

I think it will be common behaviour in the short term. Certainly my
current home printer requires IPv4, for example.

    Brian


From nobody Mon Sep  3 20:05:52 2018
Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97B8F130E02 for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 20:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.1
X-Spam-Level: 
X-Spam-Status: No, score=-6.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Rpcrg4YSu1el for <v6ops@ietfa.amsl.com>; Mon,  3 Sep 2018 20:05:50 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED5E127333 for <v6ops@ietf.org>; Mon,  3 Sep 2018 20:05:49 -0700 (PDT)
Received: from kiev.delong.com (kiev.delong.com [IPv6:2620:0:930:0:0:0:200:5]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id w8433VmR012270 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 3 Sep 2018 20:03:34 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com w8433VmR012270
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <bcbdfd68-1331-4966-e4e0-c402bb6ad703@si6networks.com>
Date: Mon, 3 Sep 2018 20:03:31 -0700
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ole Troan <otroan@employees.org>, George Michaelson <ggm@algebras.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B75FA40C-5C9D-41F0-AE39-CB1BA2A99DF0@delong.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com> <4645850B-9496-49F0-A284-09E01C0ED820@employees.org> <68a76cb2-911f-186d-dc78-7d6116dcb790@si6networks.com> <a0736784-77f7-5d09-f961-a5b4428e684e@gmail.com> <bcbdfd68-1331-4966-e4e0-c402bb6ad703@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Mon, 03 Sep 2018 20:03:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Etz1dTD6-JpPVnRDgSMcYFgR4BE>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 04 Sep 2018 03:05:52 -0000

> On Sep 3, 2018, at 13:05 , Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> On 09/03/2018 09:43 PM, Brian E Carpenter wrote:
>> On 2018-09-04 07:00, Fernando Gont wrote:
>>> On 09/02/2018 07:08 PM, Ole Troan wrote:
>>>> George is making an important point here.=20
>>>> If nothing else, the IPv6 only flag can be used to trigger IPv6 =
only testing and compliance.=20
>>>=20
>>> In order for that to be possible, shouldn't reaction to the flag =
need to
>>> be compulsory, rather than simply advisory?
>>=20
>> There's no such thing as compulsory in the Internet ;-).
>>=20
>> It's a SHOULD in the draft**.
>=20
> Ack. FWIW, I have not checked a recent version of the I-D, and was
> assuming (based on list discussion) that the requirement level was =
less
> than SHOULD.
>=20
>=20
>=20
>> Any node that emits IPv4 traffic when the bit
>> is set is either a legacy host or a dual stack host that's not =
entered
>> a v6-only mode. So that means it's a host worth checking as part of
>> the v6-only test.
>>=20
>> **"Dual stack hosts that have a good reason to use IPv4, for example =
for
>>   a specific IPv4 link-local service, can continue to do so.  This is
>>   consistent with the SHOULD language in this document."
>=20
> But... is that IPv6 only? At the end of the day, it would seem that =
for
> most home and enterprise networks, you will always have a reason for
> doing some IPv4.. so I wonder when one would see this bit have =
practical
> effect. -- most enterprise and home networks will normally do DNS-SD =
or
> LLMNR, and associated sevices. Also, think about e.g. printers that =
are
> likely going to remain IPv4-only till they eventually beak and get =
replaced.

Why?

I have a few legacy devices that force me back to IPv4 for a few things,
but I presume that they will age out in the next few years.

Other than that, it=E2=80=99s just the hold-out web sites like Amazon =
that are preventing
me from dropping IPv4 on my home networks altogether. Presumably those
will also fade with time (the sooner the better).

> Put another way: Is the above "exception" really expected to be an
> exception, or actually more like a norm (normal scenario)?

Today, it=E2=80=99s certainly the norm. However, I certainly hope that =
in a few years
it becomes more exceptional. Certainly over the course of some time =
period,
it will become progressively more exceptional.

More importantly, I think IETF should be planning for and addressing =
that which
is within the IETF=E2=80=99s purview towards making that possible, =
achievable, feasible,
and desirable.

Owen



From nobody Tue Sep  4 08:28:38 2018
Return-Path: <dmudric@avaya.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0903A130EFF for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 08:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.998
X-Spam-Level: 
X-Spam-Status: No, score=-4.998 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] 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 BrGMjuJO4eEg for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 08:28:33 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (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 96A6A130EF2 for <v6ops@ietf.org>; Tue,  4 Sep 2018 08:28:32 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2GlAAATpI5b/wUHmMZaGwEBAQEDAQEBC?= =?us-ascii?q?QEBAYJXI1RlbRIoCoMpP4gSjC+CDYhYjVWBPzsLIwkChD4CF4MfITQYAQIBAQE?= =?us-ascii?q?BAQECAgJpHAyCaC8BAQQHAwwvCQIDAQEBAQEBAU8CD0cBARgBAQEBAgEMBhEKQ?= =?us-ascii?q?QsFBwQCAQYCDQQEAQELFgEGAwICAh8FDBQJCAIEDgQBCBqDAIEdTAMNCAEOh2i?= =?us-ascii?q?RXIlvgS4aAocGDYJJBYpYF4FCPoFYgh4uglZFBBiBMRgVH4JLMYImAogthHKFW?= =?us-ascii?q?Ig0KwkChjKGM4MpgUCEN4JqA4V1hm2EOmSHWoFBOYFVcBU7gmyGAYpSbwGBFYp?= =?us-ascii?q?8AYEbAQE?=
X-IPAS-Result: =?us-ascii?q?A2GlAAATpI5b/wUHmMZaGwEBAQEDAQEBCQEBAYJXI1RlbRI?= =?us-ascii?q?oCoMpP4gSjC+CDYhYjVWBPzsLIwkChD4CF4MfITQYAQIBAQEBAQECAgJpHAyCa?= =?us-ascii?q?C8BAQQHAwwvCQIDAQEBAQEBAU8CD0cBARgBAQEBAgEMBhEKQQsFBwQCAQYCDQQ?= =?us-ascii?q?EAQELFgEGAwICAh8FDBQJCAIEDgQBCBqDAIEdTAMNCAEOh2iRXIlvgS4aAocGD?= =?us-ascii?q?YJJBYpYF4FCPoFYgh4uglZFBBiBMRgVH4JLMYImAogthHKFWIg0KwkChjKGM4M?= =?us-ascii?q?pgUCEN4JqA4V1hm2EOmSHWoFBOYFVcBU7gmyGAYpSbwGBFYp8AYEbAQE?=
X-IronPort-AV: E=Sophos;i="5.53,329,1531800000";  d="scan'208,217";a="302398831"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 04 Sep 2018 11:28:30 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC04.global.avaya.com) ([135.11.85.15]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;  04 Sep 2018 11:28:30 -0400
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC04.global.avaya.com ([135.11.85.15]) with mapi id 14.03.0382.000; Tue, 4 Sep 2018 11:28:29 -0400
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: Owen DeLong <owen@delong.com>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, David Farmer <farmer@umn.edu>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Thinking about problems in IPv6-only networks
Thread-Index: AQHUQL/ygyT9kwsoz02Ikgn5fOjK1aTaS9DAgAC6YYCABTsmIA==
Date: Tue, 4 Sep 2018 15:28:28 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com>
In-Reply-To: <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.11.85.50]
Content-Type: multipart/alternative; boundary="_000_9142206A0C5BF24CB22755C8EC422E459CB4B6F5AZUS1EXMB03glob_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Kg-x-7iC9kxLm-MosbV-FTMW7AM>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Sep 2018 15:28:36 -0000

--_000_9142206A0C5BF24CB22755C8EC422E459CB4B6F5AZUS1EXMB03glob_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCkZyb206IE93ZW4gRGVMb25nIDxvd2VuQGRlbG9uZy5jb20+DQpTZW50OiBGcmlkYXksIEF1
Z3VzdCAzMSwgMjAxOCAxMToxOCBQTQ0KVG86IE11ZHJpYywgRHVzYW4gKER1c2FuKSA8ZG11ZHJp
Y0BhdmF5YS5jb20+DQpDYzogQnJpYW4gRSBDYXJwZW50ZXIgPGJyaWFuLmUuY2FycGVudGVyQGdt
YWlsLmNvbT47IERhdmlkIEZhcm1lciA8ZmFybWVyQHVtbi5lZHU+OyB2Nm9wc0BpZXRmLm9yZw0K
U3ViamVjdDogUmU6IFt2Nm9wc10gVGhpbmtpbmcgYWJvdXQgcHJvYmxlbXMgaW4gSVB2Ni1vbmx5
IG5ldHdvcmtzDQoNCg0KDQoNCk9uIEF1ZyAzMSwgMjAxOCwgYXQgMTM6MjEgLCBNdWRyaWMsIER1
c2FuIChEdXNhbikgPGRtdWRyaWNAYXZheWEuY29tPG1haWx0bzpkbXVkcmljQGF2YXlhLmNvbT4+
IHdyb3RlOg0KDQpUaGUgTyBmbGFnIHdpbGwgY2F1c2UgaG9zdHMgdG8gc2VlayBpbmZvcm1hdGlv
biBmcm9tIGEgREhDUHY2IHNlcnZlciwNCmhhbmdpbmcgKHBvc3NpYmx5IGluZGVmaW5pdGVseSkg
dW50aWwgdGhhdCBpbmZvcm1hdGlvbiBpcyByZWNlaXZlZC4gSWYgdGhlcmUgaXMgbm8NCkRIQ1B2
NiBzZXJ2ZXIgYXZhaWxhYmxlIHRvIHByb3ZpZGUgdGhhdCBpbmZvcm1hdGlvbiwgeW91IGhhdmUg
bm93IGJyb2tlbg0KdGhlIG5ldHdvcmsgYnkgY2hhbmdpbmcgdGhlIE8gZmxhZyB3aXRob3V0IGFu
eSByZWFzb24gdG8gZG8gc28uDQoNClBvc3NpYmxlIGJ1dCBpdCBpcyBub3QgcmVxdWlyZWQsIGJ5
IGFueSBzdGFuZGFyZCB0aGF0IEkga25vdyBhYm91dCwgdGhhdCBhcHBsaWNhdGlvbnMgc2hvdWxk
IHdhaXQgaW5kZWZpbml0ZWx5IGZvciBESENQdjYgc2VydmVyIHJlc3BvbnNlLg0KDQpXaGV0aGVy
IGl04oCZcyByZXF1aXJlZCBvciBub3QsIGl0IF9JU18gdGhlIGFjdHVhbCBpbXBsZW1lbnRhdGlv
biBpbiBhIG51bWJlciBvZiBleGlzdGluZyBzeXN0ZW1zLg0KDQpTT+KApiBDaGFuZ2luZyB0aGUg
ZGVmYXVsdCB2YWx1ZSBpbiB0aGlzIHdheSBicmVha3MgYSBsb3Qgb2Ygc3R1ZmYgdGhhdCBhbHJl
YWR5IGV4aXN0cy4gSeKAmW0gbm90IHNheWluZyB3ZSBzaG91bGQgbmV2ZXINCmRvIHRoYXQsIGJ1
dCB0aGVyZSBjZXJ0YWlubHkgbmVlZHMgdG8gYmUgYSBjb21wZWxsaW5nIHJlYXNvbiB0byBkbyBz
byBvciB3ZSBzaG91bGRu4oCZdCBkbyBpdC4NCg0KU28gZmFyLCB5b3UgaGF2ZSB5ZXQgdG8gcHJv
dmlkZSBhbnl0aGluZyByZW1vdGVseSByZXNlbWJsaW5nIGEgY29tcGVsbGluZyByZWFzb24uDQpb
W0R1c2FuXV0NCg0KPiBBbiAidW5tYW5hZ2VkIG5ldHdvcmsiIHRoYXQgaXMgImJhc2VkIG9uIHRo
ZSBuZXR3b3JrIGRlZmF1bHRzIiBzb3VuZHMNCg0KPiBsaWtlIGl0J3MgaW4gY29uZmxpY3Qgd2l0
aCBhIHNlcnZlciBiZWluZyAiYWRkZWQgdG8gdGhlIG5ldHdvcmsuIg0KDQorDQoNCkl0IHdvdWxk
IGJlIHBvc3NpYmxlIGZvciBhIHJvdXRlciBtYW51ZmFjdHVyZXIgdG8gb2JmdXNjYXRlIHRoaXMg
YnkgcHJvdmlkaW5nIGEgc3VpdGFibGUgR1VJIHRvIGNvbmZpZ3VyZSBhbmQgZW5hYmxlIGEgREhD
UCBzZXJ2ZXIsIGFuZCBhcyBhIHNpZGUgZWZmZWN0LCB0dXJuIG9uIHRoZSBNIGFuZC9vciBPIGJp
dHMgaW4gdGhlIFJBcyBpc3N1ZWQgYnkgKip0aGF0IHJvdXRlcioqLg0KDQorDQoNCj4gT3BlbldS
VCBlbmFibGVzIGJvdGggYnkgZGVmYXVsdCwgYW5kIGEgaG9zdCB0aGF0IHN1cHBvcnRzIGJvdGgg
U0xBQUMgYW5kIERIQ1B2NiBlLmcuIEZlZG9yYSBMaW51eCwgd2lsbCBnZXQgYWRkcmVzc2VzIHVz
aW5nIGJvdGguDQoNCltbRHVzYW5dXQ0KSSB1bmRlcnN0YW5kIHRoZSB2aWV3IGFib3V0IGFkZGlu
ZyBhIHNlcnZlciB0byBhIG5ldHdvcmsgbWFrZXMgdGhlIG5ldHdvcmsg4oCYdW5tYW5hZ2Vk4oCZ
LiBIb3dldmVyLCBJIGRvbuKAmXQgYWdyZWUgd2l0aCB0aGUgZGVmaW5pdGlvbi4gVGhlIGRlZmF1
bHQgc2VydmVyIGNvbmZpZ3VyYXRpb24gc2hvdWxkIG1ha2UgdGhlIG5ldHdvcmsg4oCYdW5tYW5h
Z2Vk4oCZIGFuZCB0aGUgYWRkZWQgc2VydmVyIHNob3VsZCB3b3JrIGluIHRoYXQgbmV0d29yay4g
VGhlIGZhY3QgdGhhdCBESENQdjYgc2VydmVyIGNhbm5vdCBiZSBlYXNpbHkgaW50ZWdyYXRlZCBp
biB0aGUgbmV0d29yayBhbmQgaXMgb3V0IG9mIHN5bmMgZm9yIG5ldHdvcmsgY2hhbmdlcywgc2hv
dWxkIG5vdCBjaGFuZ2UgdGhlIGRlZmluaXRpb24gZm9yIOKAmHVubWFuYWdlZOKAmSBuZXR3b3Jr
LiBXZSBzaG91bGQgcmF0aGVyIGZpeCBESENQdjYgaW50ZWdyYXRpb24uIFRoZXJlIGFyZSBpZGVh
cyBob3cgdG8gbWFrZSDigJhP4oCZIGJpdCBhdXRvbWF0aWNhbGx5IHNldCBmb3Igc29tZSByb3V0
ZXJzIChwbGVhc2Ugc2VlIGFib3ZlKS4gSSBzdXBwb3NlIGl0IGNhbiBiZSBkb25lIGZvciBhbGwg
cm91dGVycywgaWYgREhDUHY2IHNlcnZlciBpcyBiZXR0ZXIgaW50ZWdyYXRlZC4NCg0KSW4gYWRk
aXRpb24sIEkgYmVsaWV2ZSBob3N0IGRlZmF1bHQgc2hvdWxkIGFsbG93IHRoZSBob3N0IHRvIHdv
cmsg4oCYdW5tYW5hZ2Vk4oCZIGluIGFueSBraW5kIG9mIG5ldHdvcmsgKGhhdmUgbm90IHNlZW4g
dGhpcyBkZWZpbmVkIGluIGFueSBSRkM7IGlzIHRoZXJlIFJGQyB0aGF0IGRlZmluZXMgdGhpcyBi
ZWhhdmlvcj8pOg0KDQogICogICBTTEFBQyBvbmx5LA0KICAqICAgREhDUHY2IG9ubHksIG9yDQog
ICogICBTTEFBQyArIERIQ1B2Ng0KVGhhdCB2aWV3IGlzIHNoYXJlZCBieSBGZWRvcmEgYW5kIE9w
ZW5XUlQgKHNlZSBhYm92ZSkuIElmIGhvc3RzIHNlZWsgc3RhdGVsZXNzIERIQ1B2NiBjb25maWd1
cmF0aW9uIGJ5IGRlZmF1bHQsIHJvdXRlcnMgc2hvdWxkIG9mZmVyIGl0IGJ5IGRlZmF1bHQgKHNl
dCDigJhP4oCZIGJpdCB0byBUUlVFKS4NCg0KPiBPd2VuDQoNCg0KDQpEdXNhbg0KDQoNCi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBPd2VuIERlTG9uZyA8b3dlbkBkZWxvbmcuY29t
PG1haWx0bzpvd2VuQGRlbG9uZy5jb20+Pg0KU2VudDogVGh1cnNkYXksIEF1Z3VzdCAzMCwgMjAx
OCA4OjE3IFBNDQpUbzogTXVkcmljLCBEdXNhbiAoRHVzYW4pIDxkbXVkcmljQGF2YXlhLmNvbTxt
YWlsdG86ZG11ZHJpY0BhdmF5YS5jb20+Pg0KQ2M6IEJyaWFuIEUgQ2FycGVudGVyIDxicmlhbi5l
LmNhcnBlbnRlckBnbWFpbC5jb208bWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbT4+
OyBEYXZpZCBGYXJtZXINCjxmYXJtZXJAdW1uLmVkdTxtYWlsdG86ZmFybWVyQHVtbi5lZHU+Pjsg
djZvcHNAaWV0Zi5vcmc8bWFpbHRvOnY2b3BzQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFt2Nm9w
c10gVGhpbmtpbmcgYWJvdXQgcHJvYmxlbXMgaW4gSVB2Ni1vbmx5IG5ldHdvcmtzDQoNCg0KDQpP
biBBdWcgMzAsIDIwMTgsIGF0IDEyOjI2LCBNdWRyaWMsIER1c2FuIChEdXNhbikgPGRtdWRyaWNA
YXZheWEuY29tPG1haWx0bzpkbXVkcmljQGF2YXlhLmNvbT4+DQp3cm90ZToNCg0KDQpFeGFjdGx5
LiBXb3JraW5nIG91dCBvZiB0aGUgYm94IG9uIGFuIHVubWFuYWdlZCBuZXR3b3JrIGhhcyBhbHdh
eXMNCmJlZW4NCg0KYSBnb2FsIGZvciBJUHY2LA0KSSBleHBlY3RlZCBwbHVnLWFuZC1wbGF5LCBv
ciB1bm1hbmFnZWQgbmV0d29yaywgbWVhbnMgZGV2aWNlcw0KZGVwbG95ZWQgdG8gdGhvc2UgbmV0
d29ya3Mgc2hvdWxkIHdvcmsgYmFzZWQgb24gdGhlIG5ldHdvcmsgZGVmYXVsdHMuIElmDQpESENQ
djYgaXMgYWRkZWQgdG8gdGhlIG5ldHdvcmssICdPJyBmbGFnIG5lZWRzIHRvIGJlIHNldC4gVGhh
dCBtZWFucw0KbWFuYWdpbmcgdGhlIG5ldHdvcmsuDQoNCg0KDQpJZiBJIGRvbid0IHByb3ZpZGUg
YSBESENQdjYgSSBzaG91bGQNCm5vdCBoYXZlIHRvIGRvIGFueXRoaW5nLg0KUmlnaHQuIElmIG5v
dGhpbmcgaXMgYWRkZWQgdG8gdGhlIG5ldHdvcmssIHRoZXJlIGlzIG5vIG5lZWQgdG8gY2hhbmdl
IHRoZQ0KbmV0d29yayBjb25maWd1cmF0aW9uLiBCdXQgdGhhdCBpcyBub3QgdGhlIHBvaW50LiBQ
bHVnLWFuZC1wbGF5IGlzIHVzZWQgd2hlbg0Kc29tZXRoaW5nIGlzIGFkZGVkIHRvIHRoZSBuZXR3
b3JrLiBUaGVyZSBzaG91bGQgbm90IGJlIGEgbmVlZCB0byBjaGFuZ2UNCidPJyBiaXQgd2hlbiBE
SENQdjYgc2VydmVyIGFuZCBESENQdjYgY2FwYWJsZSBob3N0cyBhcmUgYWRkZWQgdG8gdGhlDQpu
ZXR3b3JrLiBBbmQsIGlmIHRoZXJlIGFyZSBubyBESENQdjYgc2VydmVycyBhbmQgREhDUHY2IGNh
cGFibGUgaG9zdHMgaW4NCnRoYXQgbmV0d29yaywgc2VuZGluZyAnTyc9VFJVRSB3aWxsIG5vdCBp
bXBhY3QgIHRoZSBuZXR3b3JrLg0KDQpZb3UgYXJlIGJhZGx5IG1pc3Rha2VuLg0KDQpUaGUgTyBm
bGFnIHdpbGwgY2F1c2UgaG9zdHMgdG8gc2VlayBpbmZvcm1hdGlvbiBmcm9tIGEgREhDUHY2IHNl
cnZlciwNCmhhbmdpbmcgKHBvc3NpYmx5IGluZGVmaW5pdGVseSkgdW50aWwgdGhhdCBpbmZvcm1h
dGlvbiBpcyByZWNlaXZlZC4gSWYgdGhlcmUgaXMgbm8NCkRIQ1B2NiBzZXJ2ZXIgYXZhaWxhYmxl
IHRvIHByb3ZpZGUgdGhhdCBpbmZvcm1hdGlvbiwgeW91IGhhdmUgbm93IGJyb2tlbg0KdGhlIG5l
dHdvcmsgYnkgY2hhbmdpbmcgdGhlIE8gZmxhZyB3aXRob3V0IGFueSByZWFzb24gdG8gZG8gc28u
DQoNCk93ZW4NCg0KDQoNCkR1c2FuDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IEJyaWFuIEUgQ2FycGVudGVyIDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb208bWFpbHRv
OmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbT4+DQpTZW50OiBXZWRuZXNkYXksIEF1Z3VzdCAy
OSwgMjAxOCA2OjI0IFBNDQpUbzogRGF2aWQgRmFybWVyIDxmYXJtZXJAdW1uLmVkdTxtYWlsdG86
ZmFybWVyQHVtbi5lZHU+PjsgTXVkcmljLCBEdXNhbiAoRHVzYW4pDQo8ZG11ZHJpY0BhdmF5YS5j
b208bWFpbHRvOmRtdWRyaWNAYXZheWEuY29tPj4NCkNjOiB2Nm9wc0BpZXRmLm9yZzxtYWlsdG86
djZvcHNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW3Y2b3BzXSBUaGlua2luZyBhYm91dCBwcm9i
bGVtcyBpbiBJUHY2LW9ubHkgbmV0d29ya3MNCg0KDQpPbiAyMDE4LTA4LTMwIDA4OjUyLCBEYXZp
ZCBGYXJtZXIgd3JvdGU6DQpPbiBXZWQsIEF1ZyAyOSwgMjAxOCBhdCAzOjM3IFBNLCBNdWRyaWMs
IER1c2FuIChEdXNhbikNCjxkbXVkcmljQGF2YXlhLmNvbTxtYWlsdG86ZG11ZHJpY0BhdmF5YS5j
b20+Pg0KDQp3cm90ZToNCg0KDQpUaGV5IGNvbnRyb2wgdGhlIGRlZmF1bHRzIGZvciBob3cgUm91
dGVycyBjb25zdHJ1Y3QgUm91dGVyDQpBZHZlcnRpc2VtZW50cy4NCg0KQW5kIGRlZmF1bHQgJ08n
IGZsYWcgc2V0IHRvIFRSVUUgc2hvdWxkIGVuYWJsZWQgc3RhdGVsZXNzIERIQ1B2NiB0bw0Kb2J0
YWluDQoNCmNvbmZpZ3VyYXRpb24gZm9yIGhvc3RzLg0KDQoNCk9ubHkgaWYgdGhlcmUgaXMsIGlu
IGZhY3QsIGEgREhDUHY2IHNlcnZlciBhbmQgaXQgaXMgY29uZmlndXJlZCB3aXRoDQphcHByb3By
aWF0ZSBpbmZvcm1hdGlvbi4gIE1heWJlIHlvdSB3aXNoIHRvIHJlY29tbWVuZCBuZXQgb3BlcmF0
b3JzDQpkZXBsb3kNCg0KREhDUHY2LCBidXQgY2hhbmdlIHRoZSBkZWZhdWx0IGZvciB0aGUgTyBm
bGFnIGluIFJBcyBpcyBtb3JlIHRoYXQuDQoNCldoaWxlIEkgY291bGQgYmUgc3ltcGF0aGV0aWMg
dG8gcmVjb21tZW5kYXRpb25zIHRvIHByb3ZpZGUgREhDUHY2DQpzZXJ2ZXJzDQoNCm9uIG5ldHdv
cmtzLiBIb3dldmVyLCBjaGFuZ2luZyB0aGUgZGVmYXVsdHMgZm9yIHRoZSBNIG9yIE8gZmxhZ3Mg
aXMgbm90DQpzb21ldGhpbmcgSSBjYW4gc3VwcG9ydC4gIElmIEkgcHJvdmlkZSBhIERIQ1B2NiBz
ZXJ2ZXIgdGhlbiBpdCBpcyBteSBqb2IgdG8NCnNldCB0aGUgZmxhZ3MgYXBwcm9wcmlhdGVseSBp
biB0aGUgUkEuIElmIEkgZG9uJ3QgcHJvdmlkZSBhIERIQ1B2NiBJIHNob3VsZA0Kbm90IGhhdmUg
dG8gZG8gYW55dGhpbmcuIFRoaXMgaXMgaG93IHRoZSBkZWZhdWx0cyBmb3IgdGhlIE0gYW5kIE8g
ZmxhZyBhcmUNCmN1cnJlbnRseSBzZXQuDQoNCkV4YWN0bHkuIFdvcmtpbmcgb3V0IG9mIHRoZSBi
b3ggb24gYW4gdW5tYW5hZ2VkIG5ldHdvcmsgaGFzIGFsd2F5cw0KYmVlbg0KDQphIGdvYWwgZm9y
IElQdjYsIGV2ZW4gYmFjayB3aGVuIGl0IHdhcyBjYWxsZWQgSVBuZy4gVGhlIGRlZmF1bHRzIGFy
ZQ0Kc2V0IGFwcHJvcHJpYXRlbHkgZm9yIHRoYXQgZ29hbC4NCg0KICAgQnJpYW4NCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQp2Nm9wcyBtYWlsaW5nIGxp
c3QNCnY2b3BzQGlldGYub3JnPG1haWx0bzp2Nm9wc0BpZXRmLm9yZz4NCmh0dHBzOi8vdXJsZGVm
ZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCjNBX193d3cuaWV0Zi5vcmdfbWFp
bG1hbl9saXN0aW5mb192Nm9wcyZkPUR3SUZBZyZjPUJGcFdRdzhic3VLcGwNCjFTZ2laSDY0USZy
PVVUM0JrOWNiTGVhSnhoZjNpQ3JoSW9VV0I4WUxaVTIzMDI5c01RR1Eya1kmbT03TUgNCnR2bWU2
bkFXWUY0dURNSDNnT19hdW9fcXhwQThWc2N0eWlnUzNOZXcmcz1VQVIxdkN6WjdlWUhVS2RnbA0K
eGVuc05QcGhRYjlJRW9vbDBoejFvektJRnMmZT0NCg0K

--_000_9142206A0C5BF24CB22755C8EC422E459CB4B6F5AZUS1EXMB03glob_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IlByb2dJZCIg
Y29udGVudD0iV29yZC5Eb2N1bWVudCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRlbnQ9
Ik1pY3Jvc29mdCBXb3JkIDE1Ij4NCjxtZXRhIG5hbWU9Ik9yaWdpbmF0b3IiIGNvbnRlbnQ9Ik1p
Y3Jvc29mdCBXb3JkIDE1Ij4NCjxsaW5rIHJlbD0iRmlsZS1MaXN0IiBocmVmPSJjaWQ6ZmlsZWxp
c3QueG1sQDAxRDQ0NDQyLjY2MjE1REEwIj48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOk9m
ZmljZURvY3VtZW50U2V0dGluZ3M+DQo8bzpBbGxvd1BORy8+DQo8L286T2ZmaWNlRG9jdW1lbnRT
ZXR0aW5ncz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPHc6
V29yZERvY3VtZW50Pg0KPHc6U3BlbGxpbmdTdGF0ZT5DbGVhbjwvdzpTcGVsbGluZ1N0YXRlPg0K
PHc6RG9jdW1lbnRLaW5kPkRvY3VtZW50RW1haWw8L3c6RG9jdW1lbnRLaW5kPg0KPHc6VHJhY2tN
b3Zlcy8+DQo8dzpUcmFja0Zvcm1hdHRpbmcvPg0KPHc6RW52ZWxvcGVWaXMvPg0KPHc6VmFsaWRh
dGVBZ2FpbnN0U2NoZW1hcy8+DQo8dzpTYXZlSWZYTUxJbnZhbGlkPmZhbHNlPC93OlNhdmVJZlhN
TEludmFsaWQ+DQo8dzpJZ25vcmVNaXhlZENvbnRlbnQ+ZmFsc2U8L3c6SWdub3JlTWl4ZWRDb250
ZW50Pg0KPHc6QWx3YXlzU2hvd1BsYWNlaG9sZGVyVGV4dD5mYWxzZTwvdzpBbHdheXNTaG93UGxh
Y2Vob2xkZXJUZXh0Pg0KPHc6RG9Ob3RQcm9tb3RlUUYvPg0KPHc6TGlkVGhlbWVPdGhlcj5FTi1V
UzwvdzpMaWRUaGVtZU90aGVyPg0KPHc6TGlkVGhlbWVBc2lhbj5YLU5PTkU8L3c6TGlkVGhlbWVB
c2lhbj4NCjx3OkxpZFRoZW1lQ29tcGxleFNjcmlwdD5YLU5PTkU8L3c6TGlkVGhlbWVDb21wbGV4
U2NyaXB0Pg0KPHc6Q29tcGF0aWJpbGl0eT4NCjx3OkRvTm90RXhwYW5kU2hpZnRSZXR1cm4vPg0K
PHc6QnJlYWtXcmFwcGVkVGFibGVzLz4NCjx3OlNwbGl0UGdCcmVha0FuZFBhcmFNYXJrLz4NCjx3
OkVuYWJsZU9wZW5UeXBlS2VybmluZy8+DQo8L3c6Q29tcGF0aWJpbGl0eT4NCjx3OkJyb3dzZXJM
ZXZlbD5NaWNyb3NvZnRJbnRlcm5ldEV4cGxvcmVyNDwvdzpCcm93c2VyTGV2ZWw+DQo8bTptYXRo
UHI+DQo8bTptYXRoRm9udCBtOnZhbD0iQ2FtYnJpYSBNYXRoIi8+DQo8bTpicmtCaW4gbTp2YWw9
ImJlZm9yZSIvPg0KPG06YnJrQmluU3ViIG06dmFsPSImIzQ1Oy0iLz4NCjxtOnNtYWxsRnJhYyBt
OnZhbD0ib2ZmIi8+DQo8bTpkaXNwRGVmLz4NCjxtOmxNYXJnaW4gbTp2YWw9IjAiLz4NCjxtOnJN
YXJnaW4gbTp2YWw9IjAiLz4NCjxtOmRlZkpjIG06dmFsPSJjZW50ZXJHcm91cCIvPg0KPG06d3Jh
cEluZGVudCBtOnZhbD0iMTQ0MCIvPg0KPG06aW50TGltIG06dmFsPSJzdWJTdXAiLz4NCjxtOm5h
cnlMaW0gbTp2YWw9InVuZE92ciIvPg0KPC9tOm1hdGhQcj48L3c6V29yZERvY3VtZW50Pg0KPC94
bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8dzpMYXRlbnRTdHlsZXMg
RGVmTG9ja2VkU3RhdGU9ImZhbHNlIiBEZWZVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIERlZlNlbWlI
aWRkZW49ImZhbHNlIiBEZWZRRm9ybWF0PSJmYWxzZSIgRGVmUHJpb3JpdHk9Ijk5IiBMYXRlbnRT
dHlsZUNvdW50PSIzNzUiPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSIwIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJOb3JtYWwiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVhZGluZyAxIi8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjkiIFNlbWlIaWRkZW49
InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5n
IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgU2VtaUhp
ZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIFFGb3JtYXQ9InRydWUiIE5hbWU9Imhl
YWRpbmcgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBT
ZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgUUZvcm1hdD0idHJ1ZSIgTmFt
ZT0iaGVhZGluZyA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjkiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBRRm9ybWF0PSJ0cnVl
IiBOYW1lPSJoZWFkaW5nIDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iOSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIFFGb3JtYXQ9
InRydWUiIE5hbWU9ImhlYWRpbmcgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI5IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgUUZv
cm1hdD0idHJ1ZSIgTmFtZT0iaGVhZGluZyA3Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjkiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVl
IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDgiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9
InRydWUiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgOSIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBO
YW1lPSJpbmRleCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRl
bj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9ImluZGV4IDIiLz4NCjx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0i
dHJ1ZSIgTmFtZT0iaW5kZXggMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNl
bWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJpbmRleCA0Ii8+DQo8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hl
blVzZWQ9InRydWUiIE5hbWU9ImluZGV4IDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iaW5kZXgg
NiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVu
aGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJpbmRleCA3Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9
ImluZGV4IDgiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0
cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iaW5kZXggOSIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRl
V2hlblVzZWQ9InRydWUiIE5hbWU9InRvYyAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjM5IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1
ZSIgTmFtZT0idG9jIDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iMzkiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJ0b2Mg
MyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgU2VtaUhp
ZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9InRvYyA0Ii8+DQo8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBTZW1pSGlkZGVuPSJ0cnVlIiBV
bmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0idG9jIDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2Vk
PSJ0cnVlIiBOYW1lPSJ0b2MgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSIzOSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9
InRvYyA3Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBT
ZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0idG9jIDgiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIFNlbWlIaWRkZW49InRy
dWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJ0b2MgOSIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBO
YW1lPSJOb3JtYWwgSW5kZW50Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2Vt
aUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9ImZvb3Rub3RlIHRleHQi
Lz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhp
ZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iYW5ub3RhdGlvbiB0ZXh0Ii8+DQo8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUi
IE5hbWU9ImhlYWRlciIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRk
ZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJmb290ZXIiLz4NCjx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0i
dHJ1ZSIgTmFtZT0iaW5kZXggaGVhZGluZyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSIzNSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUi
IFFGb3JtYXQ9InRydWUiIE5hbWU9ImNhcHRpb24iLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0idGFi
bGUgb2YgZmlndXJlcyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRk
ZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJlbnZlbG9wZSBhZGRyZXNzIi8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRl
V2hlblVzZWQ9InRydWUiIE5hbWU9ImVudmVsb3BlIHJldHVybiIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBO
YW1lPSJmb290bm90ZSByZWZlcmVuY2UiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iYW5ub3RhdGlv
biByZWZlcmVuY2UiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVu
PSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0ibGluZSBudW1iZXIiLz4NCjx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNl
ZD0idHJ1ZSIgTmFtZT0icGFnZSBudW1iZXIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iZW5kbm90
ZSByZWZlcmVuY2UiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVu
PSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iZW5kbm90ZSB0ZXh0Ii8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVz
ZWQ9InRydWUiIE5hbWU9InRhYmxlIG9mIGF1dGhvcml0aWVzIi8+DQo8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5h
bWU9Im1hY3JvIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0i
dHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9InRvYSBoZWFkaW5nIi8+DQo8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9
InRydWUiIE5hbWU9Ikxpc3QiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1p
SGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCBCdWxsZXQiLz4N
Cjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVX
aGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCBOdW1iZXIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0i
TGlzdCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1
ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9Ikxpc3QgMyIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBO
YW1lPSJMaXN0IDQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVu
PSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCA1Ii8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRy
dWUiIE5hbWU9Ikxpc3QgQnVsbGV0IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCBCdWxs
ZXQgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUi
IFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJMaXN0IEJ1bGxldCA0Ii8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRy
dWUiIE5hbWU9Ikxpc3QgQnVsbGV0IDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCBOdW1i
ZXIgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUi
IFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJMaXN0IE51bWJlciAzIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRy
dWUiIE5hbWU9Ikxpc3QgTnVtYmVyIDQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCBOdW1i
ZXIgNSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIxMCIgUUZv
cm1hdD0idHJ1ZSIgTmFtZT0iVGl0bGUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iQ2xvc2luZyIv
Pg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlk
ZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJTaWduYXR1cmUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iMSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9
InRydWUiIE5hbWU9IkRlZmF1bHQgUGFyYWdyYXBoIEZvbnQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFt
ZT0iQm9keSBUZXh0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRl
bj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IkJvZHkgVGV4dCBJbmRlbnQiLz4N
Cjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVX
aGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCBDb250aW51ZSIvPg0KPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1l
PSJMaXN0IENvbnRpbnVlIDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1p
SGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTGlzdCBDb250aW51ZSAz
Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5o
aWRlV2hlblVzZWQ9InRydWUiIE5hbWU9Ikxpc3QgQ29udGludWUgNCIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVl
IiBOYW1lPSJMaXN0IENvbnRpbnVlIDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTWVzc2FnZSBI
ZWFkZXIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMTEiIFFG
b3JtYXQ9InRydWUiIE5hbWU9IlN1YnRpdGxlIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IlNhbHV0
YXRpb24iLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVl
IiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iRGF0ZSIvPg0KPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1l
PSJCb2R5IFRleHQgRmlyc3QgSW5kZW50Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IkJvZHkgVGV4
dCBGaXJzdCBJbmRlbnQgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlI
aWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJOb3RlIEhlYWRpbmciLz4N
Cjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVX
aGVuVXNlZD0idHJ1ZSIgTmFtZT0iQm9keSBUZXh0IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0i
Qm9keSBUZXh0IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVu
PSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iQm9keSBUZXh0IEluZGVudCAyIi8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRl
V2hlblVzZWQ9InRydWUiIE5hbWU9IkJvZHkgVGV4dCBJbmRlbnQgMyIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVl
IiBOYW1lPSJCbG9jayBUZXh0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2Vt
aUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9Ikh5cGVybGluayIvPg0K
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdo
ZW5Vc2VkPSJ0cnVlIiBOYW1lPSJGb2xsb3dlZEh5cGVybGluayIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyMiIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iU3Ryb25n
Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjIwIiBRRm9ybWF0
PSJ0cnVlIiBOYW1lPSJFbXBoYXNpcyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJEb2N1bWVudCBN
YXAiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBV
bmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iUGxhaW4gVGV4dCIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBO
YW1lPSJFLW1haWwgU2lnbmF0dXJlIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
U2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IkhUTUwgVG9wIG9m
IEZvcm0iLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVl
IiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iSFRNTCBCb3R0b20gb2YgRm9ybSIvPg0KPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5V
c2VkPSJ0cnVlIiBOYW1lPSJOb3JtYWwgKFdlYikiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iSFRN
TCBBY3JvbnltIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0i
dHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IkhUTUwgQWRkcmVzcyIvPg0KPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2Vk
PSJ0cnVlIiBOYW1lPSJIVE1MIENpdGUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iSFRNTCBDb2Rl
Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5o
aWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IkhUTUwgRGVmaW5pdGlvbiIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVl
IiBOYW1lPSJIVE1MIEtleWJvYXJkIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
U2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IkhUTUwgUHJlZm9y
bWF0dGVkIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1
ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IkhUTUwgU2FtcGxlIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRy
dWUiIE5hbWU9IkhUTUwgVHlwZXdyaXRlciIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJIVE1MIFZh
cmlhYmxlIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1
ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9Ik5vcm1hbCBUYWJsZSIvPg0KPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0
cnVlIiBOYW1lPSJhbm5vdGF0aW9uIHN1YmplY3QiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTm8g
TGlzdCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUi
IFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJPdXRsaW5lIExpc3QgMSIvPg0KPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0
cnVlIiBOYW1lPSJPdXRsaW5lIExpc3QgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJPdXRsaW5l
IExpc3QgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRy
dWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJUYWJsZSBTaW1wbGUgMSIvPg0KPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2Vk
PSJ0cnVlIiBOYW1lPSJUYWJsZSBTaW1wbGUgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJUYWJs
ZSBTaW1wbGUgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49
InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJUYWJsZSBDbGFzc2ljIDEiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVu
VXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgQ2xhc3NpYyAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9
IlRhYmxlIENsYXNzaWMgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlI
aWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJUYWJsZSBDbGFzc2ljIDQi
Lz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhp
ZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgQ29sb3JmdWwgMSIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVl
IiBOYW1lPSJUYWJsZSBDb2xvcmZ1bCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxlIENv
bG9yZnVsIDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0
cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgQ29sdW1ucyAxIi8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVz
ZWQ9InRydWUiIE5hbWU9IlRhYmxlIENvbHVtbnMgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJU
YWJsZSBDb2x1bW5zIDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlk
ZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgQ29sdW1ucyA0Ii8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRl
V2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxlIENvbHVtbnMgNSIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBO
YW1lPSJUYWJsZSBHcmlkIDEiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1p
SGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgR3JpZCAyIi8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRl
V2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxlIEdyaWQgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1l
PSJUYWJsZSBHcmlkIDQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlk
ZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgR3JpZCA1Ii8+DQo8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hl
blVzZWQ9InRydWUiIE5hbWU9IlRhYmxlIEdyaWQgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJU
YWJsZSBHcmlkIDciLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVu
PSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgR3JpZCA4Ii8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVz
ZWQ9InRydWUiIE5hbWU9IlRhYmxlIExpc3QgMSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJUYWJs
ZSBMaXN0IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0
cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgTGlzdCAzIi8+DQo8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9
InRydWUiIE5hbWU9IlRhYmxlIExpc3QgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJUYWJsZSBM
aXN0IDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVl
IiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgTGlzdCA2Ii8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRy
dWUiIE5hbWU9IlRhYmxlIExpc3QgNyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJUYWJsZSBMaXN0
IDgiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBV
bmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgM0QgZWZmZWN0cyAxIi8+DQo8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9
InRydWUiIE5hbWU9IlRhYmxlIDNEIGVmZmVjdHMgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJU
YWJsZSAzRCBlZmZlY3RzIDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1p
SGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iVGFibGUgQ29udGVtcG9y
YXJ5Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIg
VW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxlIEVsZWdhbnQiLz4NCjx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1
ZSIgTmFtZT0iVGFibGUgUHJvZmVzc2lvbmFsIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxl
IFN1YnRsZSAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0i
dHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxlIFN1YnRsZSAyIi8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVz
ZWQ9InRydWUiIE5hbWU9IlRhYmxlIFdlYiAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxl
IFdlYiAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1
ZSIgVW5oaWRlV2hlblVzZWQ9InRydWUiIE5hbWU9IlRhYmxlIFdlYiAzIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVzZWQ9InRy
dWUiIE5hbWU9IkJhbGxvb24gVGV4dCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI1OSIgTmFtZT0iVGFibGUgR3JpZCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJU
YWJsZSBUaGVtZSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49
InRydWUiIE5hbWU9IlBsYWNlaG9sZGVyIFRleHQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iMSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iTm8gU3BhY2luZyIvPg0K
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MCIgTmFtZT0iTGlnaHQg
U2hhZGluZyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MSIg
TmFtZT0iTGlnaHQgTGlzdCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2MiIgTmFtZT0iTGlnaHQgR3JpZCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI2MyIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMSIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMiIv
Pg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgTmFtZT0iTWVk
aXVtIExpc3QgMSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
NiIgTmFtZT0iTWVkaXVtIExpc3QgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI2NyIgTmFtZT0iTWVkaXVtIEdyaWQgMSIvPg0KPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgTmFtZT0iTWVkaXVtIEdyaWQgMiIvPg0KPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgTmFtZT0iTWVkaXVtIEdyaWQg
MyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MCIgTmFtZT0i
RGFyayBMaXN0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9Ijcx
IiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjcyIiBOYW1lPSJDb2xvcmZ1bCBMaXN0Ii8+DQo8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBOYW1lPSJDb2xvcmZ1bCBHcmlkIi8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYwIiBOYW1lPSJMaWdodCBTaGFk
aW5nIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjYxIiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjYyIiBOYW1lPSJMaWdodCBHcmlkIEFjY2VudCAxIi8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBOYW1lPSJNZWRpdW0gU2hh
ZGluZyAxIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjY0IiBOYW1lPSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY1IiBOYW1lPSJNZWRpdW0gTGlzdCAxIEFjY2Vu
dCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgU2VtaUhpZGRlbj0idHJ1ZSIg
TmFtZT0iUmV2aXNpb24iLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iMzQiIFFGb3JtYXQ9InRydWUiIE5hbWU9Ikxpc3QgUGFyYWdyYXBoIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjI5IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJR
dW90ZSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzMCIgUUZv
cm1hdD0idHJ1ZSIgTmFtZT0iSW50ZW5zZSBRdW90ZSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI2NiIgTmFtZT0iTWVkaXVtIExpc3QgMiBBY2NlbnQgMSIvPg0K
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NyIgTmFtZT0iTWVkaXVt
IEdyaWQgMSBBY2NlbnQgMSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2OCIgTmFtZT0iTWVkaXVtIEdyaWQgMiBBY2NlbnQgMSIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgTmFtZT0iTWVkaXVtIEdyaWQgMyBBY2NlbnQg
MSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MCIgTmFtZT0i
RGFyayBMaXN0IEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjcxIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcyIiBOYW1lPSJDb2xvcmZ1bCBMaXN0IEFj
Y2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBO
YW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjYwIiBOYW1lPSJMaWdodCBTaGFkaW5nIEFjY2VudCAyIi8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBOYW1lPSJMaWdodCBMaXN0
IEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYy
IiBOYW1lPSJMaWdodCBHcmlkIEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjYzIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2VudCAyIi8+DQo8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBOYW1lPSJNZWRpdW0g
U2hhZGluZyAyIEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjY1IiBOYW1lPSJNZWRpdW0gTGlzdCAxIEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY2IiBOYW1lPSJNZWRpdW0gTGlzdCAyIEFjY2Vu
dCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBOYW1l
PSJNZWRpdW0gR3JpZCAxIEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjY4IiBOYW1lPSJNZWRpdW0gR3JpZCAyIEFjY2VudCAyIi8+DQo8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY5IiBOYW1lPSJNZWRpdW0gR3JpZCAz
IEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9Ijcw
IiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNzEiIE5hbWU9IkNvbG9yZnVsIFNoYWRpbmcgQWNjZW50IDIiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzIiIE5hbWU9IkNvbG9yZnVs
IExpc3QgQWNjZW50IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNzMiIE5hbWU9IkNvbG9yZnVsIEdyaWQgQWNjZW50IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIE5hbWU9IkxpZ2h0IFNoYWRpbmcgQWNjZW50IDMi
Lz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjEiIE5hbWU9Ikxp
Z2h0IExpc3QgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNjIiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50
IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjQiIE5hbWU9
Ik1lZGl1bSBTaGFkaW5nIDIgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNjUiIE5hbWU9Ik1lZGl1bSBMaXN0IDEgQWNjZW50IDMiLz4NCjx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIE5hbWU9Ik1lZGl1bSBMaXN0
IDIgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjciIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgiIE5hbWU9Ik1lZGl1bSBHcmlkIDIgQWNjZW50IDMiLz4N
Cjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjkiIE5hbWU9Ik1lZGl1
bSBHcmlkIDMgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNzAiIE5hbWU9IkRhcmsgTGlzdCBBY2NlbnQgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MSIgTmFtZT0iQ29sb3JmdWwgU2hhZGluZyBBY2NlbnQg
MyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIgTmFtZT0i
Q29sb3JmdWwgTGlzdCBBY2NlbnQgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI3MyIgTmFtZT0iQ29sb3JmdWwgR3JpZCBBY2NlbnQgMyIvPg0KPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MCIgTmFtZT0iTGlnaHQgU2hhZGluZyBB
Y2NlbnQgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MSIg
TmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI2MiIgTmFtZT0iTGlnaHQgR3JpZCBBY2NlbnQgNCIvPg0KPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MyIgTmFtZT0iTWVkaXVtIFNoYWRpbmcg
MSBBY2NlbnQgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
NCIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMiBBY2NlbnQgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgTmFtZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQgNCIv
Pg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NiIgTmFtZT0iTWVk
aXVtIExpc3QgMiBBY2NlbnQgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI2NyIgTmFtZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQgNCIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgTmFtZT0iTWVkaXVtIEdyaWQgMiBBY2Nl
bnQgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgTmFt
ZT0iTWVkaXVtIEdyaWQgMyBBY2NlbnQgNCIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI3MCIgTmFtZT0iRGFyayBMaXN0IEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5n
IEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9Ijcy
IiBOYW1lPSJDb2xvcmZ1bCBMaXN0IEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjczIiBOYW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCA0Ii8+DQo8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYwIiBOYW1lPSJMaWdodCBT
aGFkaW5nIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjYxIiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYyIiBOYW1lPSJMaWdodCBHcmlkIEFjY2VudCA1Ii8+DQo8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBOYW1lPSJNZWRpdW0g
U2hhZGluZyAxIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjY0IiBOYW1lPSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY1IiBOYW1lPSJNZWRpdW0gTGlzdCAxIEFj
Y2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY2IiBO
YW1lPSJNZWRpdW0gTGlzdCAyIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjY3IiBOYW1lPSJNZWRpdW0gR3JpZCAxIEFjY2VudCA1Ii8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4IiBOYW1lPSJNZWRpdW0gR3Jp
ZCAyIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjY5IiBOYW1lPSJNZWRpdW0gR3JpZCAzIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcwIiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDUiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzEiIE5hbWU9IkNvbG9yZnVs
IFNoYWRpbmcgQWNjZW50IDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNzIiIE5hbWU9IkNvbG9yZnVsIExpc3QgQWNjZW50IDUiLz4NCjx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzMiIE5hbWU9IkNvbG9yZnVsIEdyaWQgQWNjZW50
IDUiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIE5hbWU9
IkxpZ2h0IFNoYWRpbmcgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNjEiIE5hbWU9IkxpZ2h0IExpc3QgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjIiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50
IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIE5hbWU9
Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNjQiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDIgQWNjZW50IDYiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjUiIE5hbWU9Ik1lZGl1bSBM
aXN0IDEgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNjYiIE5hbWU9Ik1lZGl1bSBMaXN0IDIgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjciIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDYi
Lz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgiIE5hbWU9Ik1l
ZGl1bSBHcmlkIDIgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNjkiIE5hbWU9Ik1lZGl1bSBHcmlkIDMgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzAiIE5hbWU9IkRhcmsgTGlzdCBBY2NlbnQg
NiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MSIgTmFtZT0i
Q29sb3JmdWwgU2hhZGluZyBBY2NlbnQgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI3MiIgTmFtZT0iQ29sb3JmdWwgTGlzdCBBY2NlbnQgNiIvPg0KPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MyIgTmFtZT0iQ29sb3JmdWwgR3Jp
ZCBBY2NlbnQgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIx
OSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iU3VidGxlIEVtcGhhc2lzIi8+DQo8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjIxIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJJbnRl
bnNlIEVtcGhhc2lzIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjMxIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJTdWJ0bGUgUmVmZXJlbmNlIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjMyIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJJ
bnRlbnNlIFJlZmVyZW5jZSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSIzMyIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iQm9vayBUaXRsZSIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzNyIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRl
V2hlblVzZWQ9InRydWUiIE5hbWU9IkJpYmxpb2dyYXBoeSIvPg0KPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgU2VtaUhpZGRlbj0idHJ1ZSIgVW5oaWRlV2hlblVz
ZWQ9InRydWUiIFFGb3JtYXQ9InRydWUiIE5hbWU9IlRPQyBIZWFkaW5nIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQxIiBOYW1lPSJQbGFpbiBUYWJsZSAxIi8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQyIiBOYW1lPSJQbGFp
biBUYWJsZSAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQz
IiBOYW1lPSJQbGFpbiBUYWJsZSAzIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjQ0IiBOYW1lPSJQbGFpbiBUYWJsZSA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ1IiBOYW1lPSJQbGFpbiBUYWJsZSA1Ii8+DQo8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQwIiBOYW1lPSJHcmlkIFRhYmxlIExp
Z2h0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ2IiBOYW1l
PSJHcmlkIFRhYmxlIDEgTGlnaHQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNDciIE5hbWU9IkdyaWQgVGFibGUgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI0OCIgTmFtZT0iR3JpZCBUYWJsZSAzIi8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ5IiBOYW1lPSJHcmlkIFRhYmxlIDQiLz4N
Cjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTAiIE5hbWU9IkdyaWQg
VGFibGUgNSBEYXJrIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjUxIiBOYW1lPSJHcmlkIFRhYmxlIDYgQ29sb3JmdWwiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTIiIE5hbWU9IkdyaWQgVGFibGUgNyBDb2xvcmZ1bCIvPg0K
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0NiIgTmFtZT0iR3JpZCBU
YWJsZSAxIExpZ2h0IEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjQ3IiBOYW1lPSJHcmlkIFRhYmxlIDIgQWNjZW50IDEiLz4NCjx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDgiIE5hbWU9IkdyaWQgVGFibGUgMyBBY2Nl
bnQgMSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0OSIgTmFt
ZT0iR3JpZCBUYWJsZSA0IEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjUwIiBOYW1lPSJHcmlkIFRhYmxlIDUgRGFyayBBY2NlbnQgMSIvPg0KPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI1MSIgTmFtZT0iR3JpZCBUYWJs
ZSA2IENvbG9yZnVsIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjUyIiBOYW1lPSJHcmlkIFRhYmxlIDcgQ29sb3JmdWwgQWNjZW50IDEiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDYiIE5hbWU9IkdyaWQgVGFi
bGUgMSBMaWdodCBBY2NlbnQgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI0NyIgTmFtZT0iR3JpZCBUYWJsZSAyIEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ4IiBOYW1lPSJHcmlkIFRhYmxlIDMgQWNjZW50
IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDkiIE5hbWU9
IkdyaWQgVGFibGUgNCBBY2NlbnQgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI1MCIgTmFtZT0iR3JpZCBUYWJsZSA1IERhcmsgQWNjZW50IDIiLz4NCjx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTEiIE5hbWU9IkdyaWQgVGFibGUg
NiBDb2xvcmZ1bCBBY2NlbnQgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI1MiIgTmFtZT0iR3JpZCBUYWJsZSA3IENvbG9yZnVsIEFjY2VudCAyIi8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ2IiBOYW1lPSJHcmlkIFRhYmxl
IDEgTGlnaHQgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNDciIE5hbWU9IkdyaWQgVGFibGUgMiBBY2NlbnQgMyIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0OCIgTmFtZT0iR3JpZCBUYWJsZSAzIEFjY2VudCAz
Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ5IiBOYW1lPSJH
cmlkIFRhYmxlIDQgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNTAiIE5hbWU9IkdyaWQgVGFibGUgNSBEYXJrIEFjY2VudCAzIi8+DQo8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjUxIiBOYW1lPSJHcmlkIFRhYmxlIDYg
Q29sb3JmdWwgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNTIiIE5hbWU9IkdyaWQgVGFibGUgNyBDb2xvcmZ1bCBBY2NlbnQgMyIvPg0KPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0NiIgTmFtZT0iR3JpZCBUYWJsZSAx
IExpZ2h0IEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjQ3IiBOYW1lPSJHcmlkIFRhYmxlIDIgQWNjZW50IDQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDgiIE5hbWU9IkdyaWQgVGFibGUgMyBBY2NlbnQgNCIv
Pg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0OSIgTmFtZT0iR3Jp
ZCBUYWJsZSA0IEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjUwIiBOYW1lPSJHcmlkIFRhYmxlIDUgRGFyayBBY2NlbnQgNCIvPg0KPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI1MSIgTmFtZT0iR3JpZCBUYWJsZSA2IENv
bG9yZnVsIEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjUyIiBOYW1lPSJHcmlkIFRhYmxlIDcgQ29sb3JmdWwgQWNjZW50IDQiLz4NCjx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDYiIE5hbWU9IkdyaWQgVGFibGUgMSBM
aWdodCBBY2NlbnQgNSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI0NyIgTmFtZT0iR3JpZCBUYWJsZSAyIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ4IiBOYW1lPSJHcmlkIFRhYmxlIDMgQWNjZW50IDUiLz4N
Cjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDkiIE5hbWU9IkdyaWQg
VGFibGUgNCBBY2NlbnQgNSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI1MCIgTmFtZT0iR3JpZCBUYWJsZSA1IERhcmsgQWNjZW50IDUiLz4NCjx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTEiIE5hbWU9IkdyaWQgVGFibGUgNiBDb2xv
cmZ1bCBBY2NlbnQgNSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI1MiIgTmFtZT0iR3JpZCBUYWJsZSA3IENvbG9yZnVsIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ2IiBOYW1lPSJHcmlkIFRhYmxlIDEgTGln
aHQgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NDciIE5hbWU9IkdyaWQgVGFibGUgMiBBY2NlbnQgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI0OCIgTmFtZT0iR3JpZCBUYWJsZSAzIEFjY2VudCA2Ii8+DQo8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ5IiBOYW1lPSJHcmlkIFRh
YmxlIDQgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNTAiIE5hbWU9IkdyaWQgVGFibGUgNSBEYXJrIEFjY2VudCA2Ii8+DQo8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjUxIiBOYW1lPSJHcmlkIFRhYmxlIDYgQ29sb3Jm
dWwgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NTIiIE5hbWU9IkdyaWQgVGFibGUgNyBDb2xvcmZ1bCBBY2NlbnQgNiIvPg0KPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0NiIgTmFtZT0iTGlzdCBUYWJsZSAxIExpZ2h0
Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ3IiBOYW1lPSJM
aXN0IFRhYmxlIDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NDgiIE5hbWU9Ikxpc3QgVGFibGUgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI0OSIgTmFtZT0iTGlzdCBUYWJsZSA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjUwIiBOYW1lPSJMaXN0IFRhYmxlIDUgRGFyayIvPg0KPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI1MSIgTmFtZT0iTGlzdCBUYWJs
ZSA2IENvbG9yZnVsIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjUyIiBOYW1lPSJMaXN0IFRhYmxlIDcgQ29sb3JmdWwiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDYiIE5hbWU9Ikxpc3QgVGFibGUgMSBMaWdodCBBY2NlbnQg
MSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0NyIgTmFtZT0i
TGlzdCBUYWJsZSAyIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjQ4IiBOYW1lPSJMaXN0IFRhYmxlIDMgQWNjZW50IDEiLz4NCjx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDkiIE5hbWU9Ikxpc3QgVGFibGUgNCBBY2Nl
bnQgMSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI1MCIgTmFt
ZT0iTGlzdCBUYWJsZSA1IERhcmsgQWNjZW50IDEiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNTEiIE5hbWU9Ikxpc3QgVGFibGUgNiBDb2xvcmZ1bCBBY2NlbnQg
MSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI1MiIgTmFtZT0i
TGlzdCBUYWJsZSA3IENvbG9yZnVsIEFjY2VudCAxIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjQ2IiBOYW1lPSJMaXN0IFRhYmxlIDEgTGlnaHQgQWNjZW50IDIi
Lz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDciIE5hbWU9Ikxp
c3QgVGFibGUgMiBBY2NlbnQgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI0OCIgTmFtZT0iTGlzdCBUYWJsZSAzIEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ5IiBOYW1lPSJMaXN0IFRhYmxlIDQgQWNjZW50
IDIiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTAiIE5hbWU9
Ikxpc3QgVGFibGUgNSBEYXJrIEFjY2VudCAyIi8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjUxIiBOYW1lPSJMaXN0IFRhYmxlIDYgQ29sb3JmdWwgQWNjZW50IDIi
Lz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTIiIE5hbWU9Ikxp
c3QgVGFibGUgNyBDb2xvcmZ1bCBBY2NlbnQgMiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI0NiIgTmFtZT0iTGlzdCBUYWJsZSAxIExpZ2h0IEFjY2VudCAzIi8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ3IiBOYW1lPSJMaXN0
IFRhYmxlIDIgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNDgiIE5hbWU9Ikxpc3QgVGFibGUgMyBBY2NlbnQgMyIvPg0KPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0OSIgTmFtZT0iTGlzdCBUYWJsZSA0IEFjY2VudCAz
Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjUwIiBOYW1lPSJM
aXN0IFRhYmxlIDUgRGFyayBBY2NlbnQgMyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI1MSIgTmFtZT0iTGlzdCBUYWJsZSA2IENvbG9yZnVsIEFjY2VudCAzIi8+
DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjUyIiBOYW1lPSJMaXN0
IFRhYmxlIDcgQ29sb3JmdWwgQWNjZW50IDMiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNDYiIE5hbWU9Ikxpc3QgVGFibGUgMSBMaWdodCBBY2NlbnQgNCIvPg0K
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI0NyIgTmFtZT0iTGlzdCBU
YWJsZSAyIEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjQ4IiBOYW1lPSJMaXN0IFRhYmxlIDMgQWNjZW50IDQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDkiIE5hbWU9Ikxpc3QgVGFibGUgNCBBY2NlbnQgNCIv
Pg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI1MCIgTmFtZT0iTGlz
dCBUYWJsZSA1IERhcmsgQWNjZW50IDQiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNTEiIE5hbWU9Ikxpc3QgVGFibGUgNiBDb2xvcmZ1bCBBY2NlbnQgNCIvPg0K
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI1MiIgTmFtZT0iTGlzdCBU
YWJsZSA3IENvbG9yZnVsIEFjY2VudCA0Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjQ2IiBOYW1lPSJMaXN0IFRhYmxlIDEgTGlnaHQgQWNjZW50IDUiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNDciIE5hbWU9Ikxpc3QgVGFi
bGUgMiBBY2NlbnQgNSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI0OCIgTmFtZT0iTGlzdCBUYWJsZSAzIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ5IiBOYW1lPSJMaXN0IFRhYmxlIDQgQWNjZW50IDUiLz4N
Cjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTAiIE5hbWU9Ikxpc3Qg
VGFibGUgNSBEYXJrIEFjY2VudCA1Ii8+DQo8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjUxIiBOYW1lPSJMaXN0IFRhYmxlIDYgQ29sb3JmdWwgQWNjZW50IDUiLz4NCjx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTIiIE5hbWU9Ikxpc3QgVGFi
bGUgNyBDb2xvcmZ1bCBBY2NlbnQgNSIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI0NiIgTmFtZT0iTGlzdCBUYWJsZSAxIExpZ2h0IEFjY2VudCA2Ii8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjQ3IiBOYW1lPSJMaXN0IFRhYmxl
IDIgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NDgiIE5hbWU9Ikxpc3QgVGFibGUgMyBBY2NlbnQgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI0OSIgTmFtZT0iTGlzdCBUYWJsZSA0IEFjY2VudCA2Ii8+DQo8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjUwIiBOYW1lPSJMaXN0IFRh
YmxlIDUgRGFyayBBY2NlbnQgNiIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI1MSIgTmFtZT0iTGlzdCBUYWJsZSA2IENvbG9yZnVsIEFjY2VudCA2Ii8+DQo8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjUyIiBOYW1lPSJMaXN0IFRhYmxl
IDcgQ29sb3JmdWwgQWNjZW50IDYiLz4NCjx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBT
ZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFtZT0iTWVudGlvbiIvPg0K
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49InRydWUiIFVuaGlkZVdo
ZW5Vc2VkPSJ0cnVlIiBOYW1lPSJTbWFydCBIeXBlcmxpbmsiLz4NCjx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBTZW1pSGlkZGVuPSJ0cnVlIiBVbmhpZGVXaGVuVXNlZD0idHJ1ZSIgTmFt
ZT0iSGFzaHRhZyIvPg0KPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFNlbWlIaWRkZW49
InRydWUiIFVuaGlkZVdoZW5Vc2VkPSJ0cnVlIiBOYW1lPSJVbnJlc29sdmVkIE1lbnRpb24iLz4N
CjwvdzpMYXRlbnRTdHlsZXM+DQo8L3htbD48IVtlbmRpZl0tLT48c3R5bGU+PCEtLQ0KLyogRm9u
dCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpIZWx2ZXRpY2E7DQoJ
cGFub3NlLTE6MiAxMSA2IDQgMiAyIDIgMiAyIDQ7DQoJbXNvLWZvbnQtYWx0OkFyaWFsOw0KCW1z
by1mb250LWNoYXJzZXQ6MDsNCgltc28tZ2VuZXJpYy1mb250LWZhbWlseTpzd2lzczsNCgltc28t
Zm9udC1waXRjaDp2YXJpYWJsZTsNCgltc28tZm9udC1zaWduYXR1cmU6MyAwIDAgMCAxIDA7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAw
IDAgMCAwIDAgMDsNCgltc28tZm9udC1jaGFyc2V0OjI7DQoJbXNvLWdlbmVyaWMtZm9udC1mYW1p
bHk6YXV0bzsNCgltc28tZm9udC1waXRjaDp2YXJpYWJsZTsNCgltc28tZm9udC1zaWduYXR1cmU6
MCAyNjg0MzU0NTYgMCAwIC0yMTQ3NDgzNjQ4IDA7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0Ow0KCW1zby1m
b250LWFsdDoiQ2FsaXN0byBNVCI7DQoJbXNvLWZvbnQtY2hhcnNldDowOw0KCW1zby1nZW5lcmlj
LWZvbnQtZmFtaWx5OnJvbWFuOw0KCW1zby1mb250LXBpdGNoOnZhcmlhYmxlOw0KCW1zby1mb250
LXNpZ25hdHVyZTotNTM2ODcwMTQ1IDExMDczMDU3MjcgMCAwIDQxNSAwO30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDsN
Cgltc28tZm9udC1hbHQ6IlRpbWVzIE5ldyBSb21hbiI7DQoJbXNvLWZvbnQtY2hhcnNldDowOw0K
CW1zby1nZW5lcmljLWZvbnQtZmFtaWx5OnN3aXNzOw0KCW1zby1mb250LXBpdGNoOnZhcmlhYmxl
Ow0KCW1zby1mb250LXNpZ25hdHVyZTotNTM2ODU5OTA1IC0xMDczNzMyNDg1IDkgMCA1MTEgMDt9
DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2
Lk1zb05vcm1hbA0KCXttc28tc3R5bGUtdW5oaWRlOm5vOw0KCW1zby1zdHlsZS1xZm9ybWF0Onll
czsNCgltc28tc3R5bGUtcGFyZW50OiIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTou
MDAwMXB0Ow0KCW1zby1wYWdpbmF0aW9uOndpZG93LW9ycGhhbjsNCglmb250LXNpemU6MTEuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWZvbnQt
ZmFtaWx5OkNhbGlicmk7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUt
bm9zaG93OnllczsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lOw0KCXRleHQtdW5kZXJsaW5lOnNpbmdsZTt9DQphOnZpc2l0
ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLW5vc2hvdzp5ZXM7DQoJ
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246
dW5kZXJsaW5lOw0KCXRleHQtdW5kZXJsaW5lOnNpbmdsZTt9DQpwLk1zb1BsYWluVGV4dCwgbGku
TXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHlsZS1ub3Nob3c6eWVzOw0K
CW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFy
IjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgltc28tcGFnaW5hdGlv
bjp3aWRvdy1vcnBoYW47DQoJZm9udC1zaXplOjExLjBwdDsNCgltc28tYmlkaS1mb250LXNpemU6
MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0
LWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBS
b21hbiI7fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNv
TGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbXNvLXN0eWxlLXVuaGlk
ZTpubzsNCgltc28tc3R5bGUtcWZvcm1hdDp5ZXM7DQoJbWFyZ2luLXRvcDowaW47DQoJbWFyZ2lu
LXJpZ2h0OjBpbjsNCgltYXJnaW4tYm90dG9tOjBpbjsNCgltYXJnaW4tbGVmdDouNWluOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCgltc28tcGFnaW5hdGlvbjp3aWRvdy1vcnBoYW47DQoJZm9u
dC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgltc28t
ZmFyZWFzdC1mb250LWZhbWlseTpDYWxpYnJpO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFs
MCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1zdHls
ZS11bmhpZGU6bm87DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBp
bjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJbXNv
LXBhZ2luYXRpb246d2lkb3ctb3JwaGFuOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6Q2FsaWJy
aTt9DQpzcGFuLmFwcGxlLWNvbnZlcnRlZC1zcGFjZQ0KCXttc28tc3R5bGUtbmFtZTphcHBsZS1j
b252ZXJ0ZWQtc3BhY2U7DQoJbXNvLXN0eWxlLXVuaGlkZTpubzt9DQpzcGFuLkVtYWlsU3R5bGUx
OQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCgltc28tc3R5bGUtbm9zaG93Onll
czsNCgltc28tc3R5bGUtdW5oaWRlOm5vOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMS4wcHQ7DQoJ
bXNvLWJpZGktZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgltc28tYXNjaWktZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgltc28tZmFyZWFzdC1mb250
LWZhbWlseTpDYWxpYnJpOw0KCW1zby1oYW5zaS1mb250LWZhbWlseTpDYWxpYnJpOw0KCW1zby1i
aWRpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0K
c3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0IENoYXIiOw0K
CW1zby1zdHlsZS1ub3Nob3c6eWVzOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5
bGUtdW5oaWRlOm5vOw0KCW1zby1zdHlsZS1sb2NrZWQ6eWVzOw0KCW1zby1zdHlsZS1saW5rOiJQ
bGFpbiBUZXh0IjsNCgltc28tYW5zaS1mb250LXNpemU6MTEuMHB0Ow0KCW1zby1iaWRpLWZvbnQt
c2l6ZToxMC41cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWFz
Y2lpLWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6Q2FsaWJy
aTsNCgltc28taGFuc2ktZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIjt9DQpzcGFuLlNwZWxsRQ0KCXttc28tc3R5bGUtbmFtZToiIjsN
Cgltc28tc3BsLWU6eWVzO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9y
dC1vbmx5Ow0KCW1zby1kZWZhdWx0LXByb3BzOnllczsNCglmb250LXNpemU6MTAuMHB0Ow0KCW1z
by1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJbXNvLWJpZGktZm9udC1zaXplOjEwLjBwdDt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEu
MGluIDEuMGluIDEuMGluOw0KCW1zby1oZWFkZXItbWFyZ2luOi41aW47DQoJbXNvLWZvb3Rlci1t
YXJnaW46LjVpbjsNCgltc28tcGFwZXItc291cmNlOjA7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtw
YWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXtt
c28tbGlzdC1pZDoxNjY5NzUxMzI2Ow0KCW1zby1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0
LXRlbXBsYXRlLWlkczotMjU4NTg2NDQ2IDIwODk1ODg1ODQgNjc2OTg2OTEgNjc2OTg2OTMgNjc2
OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxp
c3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1zdGFydC1hdDo4Ow0KCW1zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtZm9u
dC1mYW1pbHk6Q2FsaWJyaTt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVp
bjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28t
bGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1s
ZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0
ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxl
dmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
74K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBs
aXN0IGwwOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxl
dmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVy
LXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3Vy
aWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglm
b250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1z
dG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1s
ZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZl
bC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0
LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDps
ZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0
Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9
DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQot
LT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyAxMF0+PHN0eWxlPi8qIFN0eWxlIERlZmluaXRpb25z
ICovDQp0YWJsZS5Nc29Ob3JtYWxUYWJsZQ0KCXttc28tc3R5bGUtbmFtZToiVGFibGUgTm9ybWFs
IjsNCgltc28tdHN0eWxlLXJvd2JhbmQtc2l6ZTowOw0KCW1zby10c3R5bGUtY29sYmFuZC1zaXpl
OjA7DQoJbXNvLXN0eWxlLW5vc2hvdzp5ZXM7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1wYXJlbnQ6IiI7DQoJbXNvLXBhZGRpbmctYWx0OjBpbiA1LjRwdCAwaW4gNS40cHQ7
DQoJbXNvLXBhcmEtbWFyZ2luOjBpbjsNCgltc28tcGFyYS1tYXJnaW4tYm90dG9tOi4wMDAxcHQ7
DQoJbXNvLXBhZ2luYXRpb246d2lkb3ctb3JwaGFuOw0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9u
dC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0KPC9zdHlsZT48IVtlbmRpZl0tLT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNw
aWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBk
YXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0K
PGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiIHN0eWxlPSJ0YWIt
aW50ZXJ2YWw6LjVpbiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1hc2NpaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1o
YW5zaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1RpbWVz
IE5ldyBSb21hbiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1hc2NpaS1mb250LWZhbWlseTpDYWxpYnJpO21z
by1oYW5zaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBp
biAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
dG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6
JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+IE93
ZW4gRGVMb25nICZsdDtvd2VuQGRlbG9uZy5jb20mZ3Q7DQo8YnI+DQo8Yj5TZW50OjwvYj4gRnJp
ZGF5LCBBdWd1c3QgMzEsIDIwMTggMTE6MTggUE08YnI+DQo8Yj5Ubzo8L2I+IE11ZHJpYywgRHVz
YW4gKER1c2FuKSAmbHQ7ZG11ZHJpY0BhdmF5YS5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBCcmlh
biBFIENhcnBlbnRlciAmbHQ7YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tJmd0OzsgRGF2aWQg
RmFybWVyICZsdDtmYXJtZXJAdW1uLmVkdSZndDs7IHY2b3BzQGlldGYub3JnPGJyPg0KPGI+U3Vi
amVjdDo8L2I+IFJlOiBbdjZvcHNdIFRoaW5raW5nIGFib3V0IHByb2JsZW1zIGluIElQdjYtb25s
eSBuZXR3b3JrczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9t
YW4mcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGlt
ZXMgTmV3IFJvbWFuJnF1b3Q7Ij48YnIgc3R5bGU9Im1zby1zcGVjaWFsLWNoYXJhY3RlcjpsaW5l
LWJyZWFrIj4NCjwhW2lmICFzdXBwb3J0TGluZUJyZWFrTmV3TGluZV0+PGJyIHN0eWxlPSJtc28t
c3BlY2lhbC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8IVtlbmRpZl0+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRv
bTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1m
YXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+T24gQXVnIDMx
LCAyMDE4LCBhdCAxMzoyMSAsIE11ZHJpYywgRHVzYW4gKER1c2FuKSAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmRtdWRyaWNAYXZheWEuY29tIj5kbXVkcmljQGF2YXlhLmNvbTwvYT4mZ3Q7IHdyb3RlOjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90
OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90
ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0O2ZvbnQtdmFyaWFu
dC1jYXBzOiBub3JtYWw7b3JwaGFuczogYXV0bzt0ZXh0LWFsaWduOnN0YXJ0O3dpZG93czogYXV0
bzstd2Via2l0LXRleHQtc2l6ZS1hZGp1c3Q6IGF1dG87LXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0
aDogMHB4O3dvcmQtc3BhY2luZzowcHgiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDsiPlRoZSBPIGZsYWcgd2lsbCBjYXVzZSBob3N0cyB0byBzZWVrIGluZm9ybWF0aW9uIGZyb20g
YSBESENQdjYgc2VydmVyLDxicj4NCmhhbmdpbmcgKHBvc3NpYmx5IGluZGVmaW5pdGVseSkgdW50
aWwgdGhhdCBpbmZvcm1hdGlvbiBpcyByZWNlaXZlZC4gSWYgdGhlcmUgaXMgbm88YnI+DQpESENQ
djYgc2VydmVyIGF2YWlsYWJsZSB0byBwcm92aWRlIHRoYXQgaW5mb3JtYXRpb24sIHlvdSBoYXZl
IG5vdyBicm9rZW48YnI+DQp0aGUgbmV0d29yayBieSBjaGFuZ2luZyB0aGUgTyBmbGFnIHdpdGhv
dXQgYW55IHJlYXNvbiB0byBkbyBzby48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVv
dGU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWZv
bnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+PGJyPg0KUG9zc2libGUgYnV0
IGl0IGlzIG5vdCByZXF1aXJlZCwgYnkgYW55IHN0YW5kYXJkIHRoYXQgSSBrbm93IGFib3V0LCB0
aGF0IGFwcGxpY2F0aW9ucyBzaG91bGQgd2FpdCBpbmRlZmluaXRlbHkgZm9yIERIQ1B2NiBzZXJ2
ZXIgcmVzcG9uc2UuPC9zcGFuPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWlseTom
cXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZx
dW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMg
TmV3IFJvbWFuJnF1b3Q7Ij5XaGV0aGVyIGl04oCZcyByZXF1aXJlZCBvciBub3QsIGl0IF9JU18g
dGhlIGFjdHVhbCBpbXBsZW1lbnRhdGlvbiBpbiBhIG51bWJlciBvZiBleGlzdGluZyBzeXN0ZW1z
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcg
Um9tYW4mcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWls
eTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPlNP4oCmIENoYW5naW5nIHRoZSBkZWZhdWx0
IHZhbHVlIGluIHRoaXMgd2F5IGJyZWFrcyBhIGxvdCBvZiBzdHVmZiB0aGF0IGFscmVhZHkgZXhp
c3RzLiBJ4oCZbSBub3Qgc2F5aW5nIHdlIHNob3VsZCBuZXZlcjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28t
ZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPmRvIHRoYXQs
IGJ1dCB0aGVyZSBjZXJ0YWlubHkgbmVlZHMgdG8gYmUgYSBjb21wZWxsaW5nIHJlYXNvbiB0byBk
byBzbyBvciB3ZSBzaG91bGRu4oCZdCBkbyBpdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3Qt
Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0ibXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7
Ij5TbyBmYXIsIHlvdSBoYXZlIHlldCB0byBwcm92aWRlIGFueXRoaW5nIHJlbW90ZWx5IHJlc2Vt
YmxpbmcgYSBjb21wZWxsaW5nIHJlYXNvbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48YiBzdHlsZT0ibXNvLWJpZGktZm9udC13ZWlnaHQ6bm9ybWFsIj48aSBz
dHlsZT0ibXNvLWJpZGktZm9udC1zdHlsZTpub3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYXNjaWkt
Zm9udC1mYW1pbHk6Q2FsaWJyaTttc28taGFuc2ktZm9udC1mYW1pbHk6Q2FsaWJyaTttc28tYmlk
aS1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPltbRHVzYW5dXQ0KPG86
cD48L286cD48L3NwYW4+PC9pPjwvYj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7
IEFuICZxdW90O3VubWFuYWdlZCBuZXR3b3JrJnF1b3Q7IHRoYXQgaXMgJnF1b3Q7YmFzZWQgb24g
dGhlIG5ldHdvcmsgZGVmYXVsdHMmcXVvdDsgc291bmRzPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IGxpa2UgaXQncyBpbiBjb25mbGljdCB3aXRoIGEgc2VydmVy
IGJlaW5nICZxdW90O2FkZGVkIHRvIHRoZSBuZXR3b3JrLiZxdW90OzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1hc2NpaS1mb250LWZhbWlseTpD
YWxpYnJpO21zby1oYW5zaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1iaWRpLWZvbnQtZmFtaWx5
OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1hc2NpaS1mb250LWZhbWls
eTpDYWxpYnJpO21zby1oYW5zaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1iaWRpLWZvbnQtZmFt
aWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+JiM0Mzs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWFzY2lpLWZvbnQtZmFt
aWx5OkNhbGlicmk7bXNvLWhhbnNpLWZvbnQtZmFtaWx5OkNhbGlicmk7bXNvLWJpZGktZm9udC1m
YW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JdCB3b3VsZCBiZSBwb3NzaWJsZSBmb3IgYSBy
b3V0ZXIgbWFudWZhY3R1cmVyIHRvIG9iZnVzY2F0ZSB0aGlzIGJ5IHByb3ZpZGluZyBhIHN1aXRh
YmxlIEdVSSB0byBjb25maWd1cmUgYW5kIGVuYWJsZSBhIERIQ1Agc2VydmVyLCBhbmQgYXMgYSBz
aWRlIGVmZmVjdCwgdHVybiBvbiB0aGUgTSBhbmQvb3IgTyBiaXRzIGluIHRoZSBSQXMgaXNzdWVk
IGJ5ICoqdGhhdCByb3V0ZXIqKi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+JiM0Mzs8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYXNjaWktZm9u
dC1mYW1pbHk6Q2FsaWJyaTttc28taGFuc2ktZm9udC1mYW1pbHk6Q2FsaWJyaTttc28tYmlkaS1m
b250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsgPHNwYW4gY2xhc3M9IlNwZWxs
RSI+T3BlbldSVDwvc3Bhbj4gZW5hYmxlcyBib3RoIGJ5IGRlZmF1bHQsIGFuZCBhIGhvc3QgdGhh
dCBzdXBwb3J0cyBib3RoIFNMQUFDIGFuZCBESENQdjYgZS5nLiBGZWRvcmEgTGludXgsIHdpbGwg
Z2V0IGFkZHJlc3NlcyB1c2luZyBib3RoLjxzcGFuIHN0eWxlPSJtc28tYXNjaWktZm9udC1mYW1p
bHk6Q2FsaWJyaTttc28taGFuc2ktZm9udC1mYW1pbHk6Q2FsaWJyaTttc28tYmlkaS1mb250LWZh
bWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiIHN0eWxlPSJtc28tYmlk
aS1mb250LXdlaWdodDpub3JtYWwiPjxpIHN0eWxlPSJtc28tYmlkaS1mb250LXN0eWxlOm5vcm1h
bCI+PHNwYW4gc3R5bGU9Im1zby1hc2NpaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1oYW5zaS1m
b250LWZhbWlseTpDYWxpYnJpO21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBS
b21hbiZxdW90OyI+W1tEdXNhbl1dDQo8bzpwPjwvbzpwPjwvc3Bhbj48L2k+PC9iPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYXNjaWktZm9udC1mYW1pbHk6Q2Fs
aWJyaTttc28taGFuc2ktZm9udC1mYW1pbHk6Q2FsaWJyaTttc28tYmlkaS1mb250LWZhbWlseTom
cXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPkkgdW5kZXJzdGFuZCB0aGUgdmlldyBhYm91dCBh
ZGRpbmcgYSBzZXJ2ZXIgdG8gYSBuZXR3b3JrIG1ha2VzIHRoZSBuZXR3b3JrIOKAmHVubWFuYWdl
ZOKAmS4gSG93ZXZlciwgSSBkb27igJl0IGFncmVlIHdpdGggdGhlIGRlZmluaXRpb24uDQogVGhl
IGRlZmF1bHQgc2VydmVyIGNvbmZpZ3VyYXRpb24gc2hvdWxkIG1ha2UgdGhlIG5ldHdvcmsg4oCY
dW5tYW5hZ2Vk4oCZIGFuZCB0aGUgYWRkZWQgc2VydmVyIHNob3VsZCB3b3JrIGluIHRoYXQgbmV0
d29yay4gVGhlIGZhY3QgdGhhdCBESENQdjYgc2VydmVyIGNhbm5vdCBiZSBlYXNpbHkgaW50ZWdy
YXRlZCBpbiB0aGUgbmV0d29yayBhbmQgaXMgb3V0IG9mIHN5bmMgZm9yIG5ldHdvcmsgY2hhbmdl
cywgc2hvdWxkIG5vdCBjaGFuZ2UgdGhlIGRlZmluaXRpb24NCiBmb3Ig4oCYdW5tYW5hZ2Vk4oCZ
IG5ldHdvcmsuIFdlIHNob3VsZCByYXRoZXIgZml4IERIQ1B2NiBpbnRlZ3JhdGlvbi4gVGhlcmUg
YXJlIGlkZWFzIGhvdyB0byBtYWtlIOKAmE/igJkgYml0IGF1dG9tYXRpY2FsbHkgc2V0IGZvciBz
b21lIHJvdXRlcnMgKHBsZWFzZSBzZWUgYWJvdmUpLiBJIHN1cHBvc2UgaXQgY2FuIGJlIGRvbmUg
Zm9yIGFsbCByb3V0ZXJzLCBpZiBESENQdjYgc2VydmVyIGlzIGJldHRlciBpbnRlZ3JhdGVkLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJt
c28tYXNjaWktZm9udC1mYW1pbHk6Q2FsaWJyaTttc28taGFuc2ktZm9udC1mYW1pbHk6Q2FsaWJy
aTttc28tYmlkaS1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJtc28tYXNjaWktZm9udC1mYW1pbHk6Q2FsaWJyaTttc28taGFuc2ktZm9udC1mYW1pbHk6Q2Fs
aWJyaTttc28tYmlkaS1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPklu
IGFkZGl0aW9uLCBJIGJlbGlldmUgaG9zdCBkZWZhdWx0IHNob3VsZCBhbGxvdyB0aGUgaG9zdCB0
byB3b3JrIOKAmHVubWFuYWdlZOKAmSBpbiBhbnkga2luZCBvZiBuZXR3b3JrIChoYXZlIG5vdCBz
ZWVuIHRoaXMgZGVmaW5lZA0KIGluIGFueSBSRkM7IGlzIHRoZXJlIFJGQyB0aGF0IGRlZmluZXMg
dGhpcyBiZWhhdmlvcj8pOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjx1bCBzdHlsZT0ibWFyZ2lu
LXRvcDowaW4iIHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MGluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj48c3BhbiBzdHlsZT0i
bXNvLWFzY2lpLWZvbnQtZmFtaWx5OkNhbGlicmk7bXNvLWhhbnNpLWZvbnQtZmFtaWx5OkNhbGli
cmk7bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5TTEFB
QyBvbmx5LDxvOnA+PC9vOnA+PC9zcGFuPjwvbGk+PGxpIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBo
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MGluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj48c3BhbiBz
dHlsZT0ibXNvLWFzY2lpLWZvbnQtZmFtaWx5OkNhbGlicmk7bXNvLWhhbnNpLWZvbnQtZmFtaWx5
OkNhbGlicmk7bXNvLWJpZGktZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7
Ij5ESENQdjYgb25seSwgb3I8bzpwPjwvbzpwPjwvc3Bhbj48L2xpPjxsaSBjbGFzcz0iTXNvTGlz
dFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjBpbjttc28tbGlzdDpsMCBsZXZlbDEgbGZv
MSI+PHNwYW4gc3R5bGU9Im1zby1hc2NpaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1oYW5zaS1m
b250LWZhbWlseTpDYWxpYnJpO21zby1iaWRpLWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBS
b21hbiZxdW90OyI+U0xBQUMgJiM0MzsgREhDUHY2PG86cD48L286cD48L3NwYW4+PC9saT48L3Vs
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1hc2NpaS1mb250LWZhbWls
eTpDYWxpYnJpO21zby1oYW5zaS1mb250LWZhbWlseTpDYWxpYnJpO21zby1iaWRpLWZvbnQtZmFt
aWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+VGhhdCB2aWV3IGlzIHNoYXJlZCBieSBG
ZWRvcmEgYW5kDQo8c3BhbiBjbGFzcz0iU3BlbGxFIj5PcGVuV1JUPC9zcGFuPiAoc2VlIGFib3Zl
KS4gSWYgaG9zdHMgc2VlayBzdGF0ZWxlc3MgREhDUHY2IGNvbmZpZ3VyYXRpb24gYnkgZGVmYXVs
dCwgcm91dGVycyBzaG91bGQgb2ZmZXIgaXQgYnkgZGVmYXVsdCAoc2V0IOKAmE/igJkgYml0IHRv
IFRSVUUpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJtc28tYXNjaWktZm9udC1mYW1pbHk6Q2FsaWJyaTttc28taGFuc2ktZm9udC1mYW1p
bHk6Q2FsaWJyaTttc28tYmlkaS1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxiIHN0eWxlPSJtc28tYmlkaS1mb250LXdlaWdodDpub3JtYWwiPjxpIHN0
eWxlPSJtc28tYmlkaS1mb250LXN0eWxlOm5vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0
LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+PC9zcGFuPjwvaT48L2I+
PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21h
biZxdW90OyI+Jmd0OyBPd2VuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+PGJyIHN0eWxlPSJtc28tc3BlY2lhbC1jaGFy
YWN0ZXI6bGluZS1icmVhayI+DQo8IVtpZiAhc3VwcG9ydExpbmVCcmVha05ld0xpbmVdPjxiciBz
dHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJlYWsiPg0KPCFbZW5kaWZdPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBS
b21hbiZxdW90OyI+PGJyPg0KRHVzYW48YnI+DQo8YnIgc3R5bGU9Im1zby1zcGVjaWFsLWNoYXJh
Y3RlcjpsaW5lLWJyZWFrO2NhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7Zm9udC12YXJpYW50LWNh
cHM6IG5vcm1hbDt0ZXh0LWFsaWduOnN0YXJ0Oy13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBw
eDt3b3JkLXNwYWNpbmc6MHB4Ij4NCjwhW2lmICFzdXBwb3J0TGluZUJyZWFrTmV3TGluZV0+PGJy
IHN0eWxlPSJtc28tc3BlY2lhbC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8IVtlbmRpZl0+PC9z
cGFuPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcg
Um9tYW4mcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJt
YXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1vdXRsaW5lLWxldmVsOjEiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVh
c3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4tLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IE93ZW4gRGVMb25nICZsdDs8YSBocmVmPSJtYWlsdG86
b3dlbkBkZWxvbmcuY29tIj5vd2VuQGRlbG9uZy5jb208L2E+Jmd0Ozxicj4NClNlbnQ6IFRodXJz
ZGF5LCBBdWd1c3QgMzAsIDIwMTggODoxNyBQTTxicj4NClRvOiBNdWRyaWMsIER1c2FuIChEdXNh
bikgJmx0OzxhIGhyZWY9Im1haWx0bzpkbXVkcmljQGF2YXlhLmNvbSI+ZG11ZHJpY0BhdmF5YS5j
b208L2E+Jmd0Ozxicj4NCkNjOiBCcmlhbiBFIENhcnBlbnRlciAmbHQ7PGEgaHJlZj0ibWFpbHRv
OmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbSI+YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29t
PC9hPiZndDs7IERhdmlkIEZhcm1lcjxicj4NCiZsdDs8YSBocmVmPSJtYWlsdG86ZmFybWVyQHVt
bi5lZHUiPmZhcm1lckB1bW4uZWR1PC9hPiZndDs7PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRl
ZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzp2Nm9wc0BpZXRmLm9yZyI+djZv
cHNAaWV0Zi5vcmc8L2E+PGJyPg0KU3ViamVjdDogUmU6IFt2Nm9wc10gVGhpbmtpbmcgYWJvdXQg
cHJvYmxlbXMgaW4gSVB2Ni1vbmx5IG5ldHdvcmtzPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KT24g
QXVnIDMwLCAyMDE4LCBhdCAxMjoyNiwgTXVkcmljLCBEdXNhbiAoRHVzYW4pICZsdDs8YSBocmVm
PSJtYWlsdG86ZG11ZHJpY0BhdmF5YS5jb20iPmRtdWRyaWNAYXZheWEuY29tPC9hPiZndDs8YnI+
DQp3cm90ZTo8YnI+DQo8YnIgc3R5bGU9Im1zby1zcGVjaWFsLWNoYXJhY3RlcjpsaW5lLWJyZWFr
Ij4NCjwhW2lmICFzdXBwb3J0TGluZUJyZWFrTmV3TGluZV0+PGJyIHN0eWxlPSJtc28tc3BlY2lh
bC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8IVtlbmRpZl0+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBw
dCI+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUu
MHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3Qt
Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5FeGFjdGx5LiBXb3JraW5n
IG91dCBvZiB0aGUgYm94IG9uIGFuIHVubWFuYWdlZCBuZXR3b3JrIGhhcyBhbHdheXM8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90
O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+YmVlbjxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFj
dGVyOmxpbmUtYnJlYWsiPg0KPCFbaWYgIXN1cHBvcnRMaW5lQnJlYWtOZXdMaW5lXT48YnIgc3R5
bGU9Im1zby1zcGVjaWFsLWNoYXJhY3RlcjpsaW5lLWJyZWFrIj4NCjwhW2VuZGlmXT48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp
Zjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPmEg
Z29hbCBmb3IgSVB2Niw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+SSBleHBlY3RlZCBwbHVnLWFuZC1wbGF5LCBv
ciB1bm1hbmFnZWQgbmV0d29yaywgbWVhbnMgZGV2aWNlczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNv
LWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5kZXBsb3ll
ZCB0byB0aG9zZSBuZXR3b3JrcyBzaG91bGQgd29yayBiYXNlZCBvbiB0aGUgbmV0d29yayBkZWZh
dWx0cy4gSWY8YnI+DQpESENQdjYgaXMgYWRkZWQgdG8gdGhlIG5ldHdvcmssICdPJyBmbGFnIG5l
ZWRzIHRvIGJlIHNldC4gVGhhdCBtZWFuczxicj4NCm1hbmFnaW5nIHRoZSBuZXR3b3JrLjxiciBz
dHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJlYWsiPg0KPCFbaWYgIXN1cHBvcnRM
aW5lQnJlYWtOZXdMaW5lXT48YnIgc3R5bGU9Im1zby1zcGVjaWFsLWNoYXJhY3RlcjpsaW5lLWJy
ZWFrIj4NCjwhW2VuZGlmXT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHls
ZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVs
dmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGlt
ZXMgTmV3IFJvbWFuJnF1b3Q7Ij48YnIgc3R5bGU9Im1zby1zcGVjaWFsLWNoYXJhY3RlcjpsaW5l
LWJyZWFrIj4NCjwhW2lmICFzdXBwb3J0TGluZUJyZWFrTmV3TGluZV0+PGJyIHN0eWxlPSJtc28t
c3BlY2lhbC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8IVtlbmRpZl0+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRv
bTo1LjBwdCI+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90
dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZh
cmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5JZiBJIGRvbid0
IHByb3ZpZGUgYSBESENQdjYgSSBzaG91bGQ8YnI+DQpub3QgaGF2ZSB0byBkbyBhbnl0aGluZy48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+UmlnaHQuIElmIG5vdGhpbmcgaXMgYWRkZWQg
dG8gdGhlIG5ldHdvcmssIHRoZXJlIGlzIG5vIG5lZWQgdG8gY2hhbmdlIHRoZTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNh
bnMtc2VyaWY7bXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1
b3Q7Ij5uZXR3b3JrIGNvbmZpZ3VyYXRpb24uIEJ1dCB0aGF0IGlzIG5vdCB0aGUgcG9pbnQuIFBs
dWctYW5kLXBsYXkgaXMgdXNlZCB3aGVuPGJyPg0Kc29tZXRoaW5nIGlzIGFkZGVkIHRvIHRoZSBu
ZXR3b3JrLiBUaGVyZSBzaG91bGQgbm90IGJlIGEgbmVlZCB0byBjaGFuZ2U8YnI+DQonTycgYml0
IHdoZW4gREhDUHY2IHNlcnZlciBhbmQgREhDUHY2IGNhcGFibGUgaG9zdHMgYXJlIGFkZGVkIHRv
IHRoZTxicj4NCm5ldHdvcmsuIEFuZCwgaWYgdGhlcmUgYXJlIG5vIERIQ1B2NiBzZXJ2ZXJzIGFu
ZCBESENQdjYgY2FwYWJsZSBob3N0cyBpbjxicj4NCnRoYXQgbmV0d29yaywgc2VuZGluZyAnTyc9
VFJVRSB3aWxsIG5vdCBpbXBhY3QgJm5ic3A7dGhlIG5ldHdvcmsuPGJyPg0KPGJyPg0KWW91IGFy
ZSBiYWRseSBtaXN0YWtlbi48YnI+DQo8YnI+DQpUaGUgTyBmbGFnIHdpbGwgY2F1c2UgaG9zdHMg
dG8gc2VlayBpbmZvcm1hdGlvbiBmcm9tIGEgREhDUHY2IHNlcnZlciw8YnI+DQpoYW5naW5nIChw
b3NzaWJseSBpbmRlZmluaXRlbHkpIHVudGlsIHRoYXQgaW5mb3JtYXRpb24gaXMgcmVjZWl2ZWQu
IElmIHRoZXJlIGlzIG5vPGJyPg0KREhDUHY2IHNlcnZlciBhdmFpbGFibGUgdG8gcHJvdmlkZSB0
aGF0IGluZm9ybWF0aW9uLCB5b3UgaGF2ZSBub3cgYnJva2VuPGJyPg0KdGhlIG5ldHdvcmsgYnkg
Y2hhbmdpbmcgdGhlIE8gZmxhZyB3aXRob3V0IGFueSByZWFzb24gdG8gZG8gc28uPGJyPg0KPGJy
Pg0KT3dlbjxicj4NCjxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJlYWsi
Pg0KPCFbaWYgIXN1cHBvcnRMaW5lQnJlYWtOZXdMaW5lXT48YnIgc3R5bGU9Im1zby1zcGVjaWFs
LWNoYXJhY3RlcjpsaW5lLWJyZWFrIj4NCjwhW2VuZGlmXT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtZm9u
dC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij48YnI+DQpEdXNhbjxicj4NCjxi
ciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJlYWsiPg0KPCFbaWYgIXN1cHBv
cnRMaW5lQnJlYWtOZXdMaW5lXT48YnIgc3R5bGU9Im1zby1zcGVjaWFsLWNoYXJhY3RlcjpsaW5l
LWJyZWFrIj4NCjwhW2VuZGlmXT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBz
dHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tb3V0bGluZS1sZXZlbDoxIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21z
by1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+LS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQpGcm9tOiBCcmlhbiBFIENhcnBlbnRlciAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbSI+YnJpYW4uZS5jYXJwZW50
ZXJAZ21haWwuY29tPC9hPiZndDs8YnI+DQpTZW50OiBXZWRuZXNkYXksIEF1Z3VzdCAyOSwgMjAx
OCA2OjI0IFBNPGJyPg0KVG86IERhdmlkIEZhcm1lciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZhcm1l
ckB1bW4uZWR1Ij5mYXJtZXJAdW1uLmVkdTwvYT4mZ3Q7OyBNdWRyaWMsIER1c2FuIChEdXNhbik8
YnI+DQombHQ7PGEgaHJlZj0ibWFpbHRvOmRtdWRyaWNAYXZheWEuY29tIj5kbXVkcmljQGF2YXlh
LmNvbTwvYT4mZ3Q7PGJyPg0KQ2M6IDxhIGhyZWY9Im1haWx0bzp2Nm9wc0BpZXRmLm9yZyI+djZv
cHNAaWV0Zi5vcmc8L2E+PGJyPg0KU3ViamVjdDogUmU6IFt2Nm9wc10gVGhpbmtpbmcgYWJvdXQg
cHJvYmxlbXMgaW4gSVB2Ni1vbmx5IG5ldHdvcmtzPGJyPg0KPGJyIHN0eWxlPSJtc28tc3BlY2lh
bC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8IVtpZiAhc3VwcG9ydExpbmVCcmVha05ld0xpbmVd
PjxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJlYWsiPg0KPCFbZW5kaWZd
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUu
MHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDsiPk9uIDIwMTgtMDgtMzAgMDg6NTIsIERhdmlkIEZhcm1lciB3cm90ZTo8YnI+DQpPbiBXZWQs
IEF1ZyAyOSwgMjAxOCBhdCAzOjM3IFBNLCBNdWRyaWMsIER1c2FuIChEdXNhbik8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90Oyxz
YW5zLXNlcmlmO21zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZx
dW90OyI+Jmx0OzxhIGhyZWY9Im1haWx0bzpkbXVkcmljQGF2YXlhLmNvbSI+ZG11ZHJpY0BhdmF5
YS5jb208L2E+Jmd0OzxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJlYWsi
Pg0KPCFbaWYgIXN1cHBvcnRMaW5lQnJlYWtOZXdMaW5lXT48YnIgc3R5bGU9Im1zby1zcGVjaWFs
LWNoYXJhY3RlcjpsaW5lLWJyZWFrIj4NCjwhW2VuZGlmXT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtZm9u
dC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij53cm90ZTo8YnI+DQo8YnIgc3R5
bGU9Im1zby1zcGVjaWFsLWNoYXJhY3RlcjpsaW5lLWJyZWFrIj4NCjwhW2lmICFzdXBwb3J0TGlu
ZUJyZWFrTmV3TGluZV0+PGJyIHN0eWxlPSJtc28tc3BlY2lhbC1jaGFyYWN0ZXI6bGluZS1icmVh
ayI+DQo8IVtlbmRpZl0+PG86cD48L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9
Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8YmxvY2txdW90ZSBzdHls
ZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVs
dmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGlt
ZXMgTmV3IFJvbWFuJnF1b3Q7Ij5UaGV5IGNvbnRyb2wgdGhlIGRlZmF1bHRzIGZvciBob3cgUm91
dGVycyBjb25zdHJ1Y3QgUm91dGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3Rl
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250
LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1mb250
LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPkFkdmVydGlzZW1lbnRzLjxicj4N
Cjxicj4NCkFuZCBkZWZhdWx0ICdPJyBmbGFnIHNldCB0byBUUlVFIHNob3VsZCBlbmFibGVkIHN0
YXRlbGVzcyBESENQdjYgdG88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8
L2Jsb2NrcXVvdGU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21zby1m
YXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+b2J0YWluPGJy
IHN0eWxlPSJtc28tc3BlY2lhbC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8IVtpZiAhc3VwcG9y
dExpbmVCcmVha05ld0xpbmVdPjxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUt
YnJlYWsiPg0KPCFbZW5kaWZdPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0
eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGJsb2NrcXVvdGUg
c3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90
O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Y29uZmlndXJhdGlvbiBmb3IgaG9zdHMuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDss
c2Fucy1zZXJpZjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4m
cXVvdDsiPjxicj4NCjxicj4NCk9ubHkgaWYgdGhlcmUgaXMsIGluIGZhY3QsIGEgREhDUHY2IHNl
cnZlciBhbmQgaXQgaXMgY29uZmlndXJlZCB3aXRoPGJyPg0KYXBwcm9wcmlhdGUgaW5mb3JtYXRp
b24uICZuYnNwO01heWJlIHlvdSB3aXNoIHRvIHJlY29tbWVuZCBuZXQgb3BlcmF0b3JzPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVv
dDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9t
YW4mcXVvdDsiPmRlcGxveTxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJl
YWsiPg0KPCFbaWYgIXN1cHBvcnRMaW5lQnJlYWtOZXdMaW5lXT48YnIgc3R5bGU9Im1zby1zcGVj
aWFsLWNoYXJhY3RlcjpsaW5lLWJyZWFrIj4NCjwhW2VuZGlmXT48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUu
MHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3Qt
Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5ESENQdjYsIGJ1dCBjaGFu
Z2UgdGhlIGRlZmF1bHQgZm9yIHRoZSBPIGZsYWcgaW4gUkFzIGlzIG1vcmUgdGhhdC48YnI+DQo8
YnI+DQpXaGlsZSBJIGNvdWxkIGJlIHN5bXBhdGhldGljIHRvIHJlY29tbWVuZGF0aW9ucyB0byBw
cm92aWRlIERIQ1B2NjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6
JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij5zZXJ2ZXJzPGJyIHN0eWxlPSJtc28tc3BlY2lh
bC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8IVtpZiAhc3VwcG9ydExpbmVCcmVha05ld0xpbmVd
PjxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOmxpbmUtYnJlYWsiPg0KPCFbZW5kaWZd
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUu
MHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDsiPm9uIG5ldHdvcmtzLiBIb3dldmVyLCBjaGFuZ2luZyB0aGUgZGVmYXVsdHMgZm9yIHRoZSBN
IG9yIE8gZmxhZ3MgaXMgbm90PGJyPg0Kc29tZXRoaW5nIEkgY2FuIHN1cHBvcnQuICZuYnNwO0lm
IEkgcHJvdmlkZSBhIERIQ1B2NiBzZXJ2ZXIgdGhlbiBpdCBpcyBteSBqb2IgdG88YnI+DQpzZXQg
dGhlIGZsYWdzIGFwcHJvcHJpYXRlbHkgaW4gdGhlIFJBLiBJZiBJIGRvbid0IHByb3ZpZGUgYSBE
SENQdjYgSSBzaG91bGQ8YnI+DQpub3QgaGF2ZSB0byBkbyBhbnl0aGluZy4gVGhpcyBpcyBob3cg
dGhlIGRlZmF1bHRzIGZvciB0aGUgTSBhbmQgTyBmbGFnIGFyZTxicj4NCmN1cnJlbnRseSBzZXQu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtUaW1lcyBO
ZXcgUm9tYW4mcXVvdDsiPjxicj4NCkV4YWN0bHkuIFdvcmtpbmcgb3V0IG9mIHRoZSBib3ggb24g
YW4gdW5tYW5hZ2VkIG5ldHdvcmsgaGFzIGFsd2F5czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
YmxvY2txdW90ZT4NCjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNh
bnMtc2VyaWY7bXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1
b3Q7Ij5iZWVuPGJyIHN0eWxlPSJtc28tc3BlY2lhbC1jaGFyYWN0ZXI6bGluZS1icmVhayI+DQo8
IVtpZiAhc3VwcG9ydExpbmVCcmVha05ld0xpbmVdPjxiciBzdHlsZT0ibXNvLXNwZWNpYWwtY2hh
cmFjdGVyOmxpbmUtYnJlYWsiPg0KPCFbZW5kaWZdPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0K
PGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWZvbnQt
ZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+YSBnb2FsIGZvciBJUHY2LCBldmVu
IGJhY2sgd2hlbiBpdCB3YXMgY2FsbGVkIElQbmcuIFRoZSBkZWZhdWx0cyBhcmU8YnI+DQpzZXQg
YXBwcm9wcmlhdGVseSBmb3IgdGhhdCBnb2FsLjxicj4NCjxicj4NCiZuYnNwOyZuYnNwOyZuYnNw
O0JyaWFuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtI
ZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1mb250LWZhbWlseTomcXVvdDtU
aW1lcyBOZXcgUm9tYW4mcXVvdDsiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPGJyPg0KdjZvcHMgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRv
OnY2b3BzQGlldGYub3JnIj52Nm9wc0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczov
L3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtIj5odHRwczovL3VybGRl
ZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtPC9hPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2Vy
aWY7bXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4z
QV9fd3d3LmlldGYub3JnX21haWxtYW5fbGlzdGluZm9fdjZvcHMmYW1wO2Q9RHdJRkFnJmFtcDtj
PUJGcFdRdzhic3VLcGw8YnI+DQoxU2dpWkg2NFEmYW1wO3I9VVQzQms5Y2JMZWFKeGhmM2lDcmhJ
b1VXQjhZTFpVMjMwMjlzTVFHUTJrWSZhbXA7bT03TUg8YnI+DQp0dm1lNm5BV1lGNHVETUgzZ09f
YXVvX3F4cEE4VnNjdHlpZ1MzTmV3JmFtcDtzPVVBUjF2Q3paN2VZSFVLZGdsPGJyPg0KeGVuc05Q
cGhRYjlJRW9vbDBoejFvektJRnMmYW1wO2U9PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9j
a3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_9142206A0C5BF24CB22755C8EC422E459CB4B6F5AZUS1EXMB03glob_--


From nobody Tue Sep  4 10:29:10 2018
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0920130F86 for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 10:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] 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 nZ3LgtCOcrui for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 10:29:07 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 550C0126DBF for <v6ops@ietf.org>; Tue,  4 Sep 2018 10:29:07 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.43.177] (unknown [213.205.241.2]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 993991A071 for <v6ops@ietf.org>; Tue,  4 Sep 2018 17:28:59 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com>
Date: Tue, 4 Sep 2018 18:28:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Nec_ZpVNNHtxNVWK5TMg5YTfMjE>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Sep 2018 17:29:10 -0000

Mudric, Dusan (Dusan) <dmudric@avaya.com> wrote:

Something jumbled up in a hard to decipher manner, it would be a lot =
easier if you a) quoted properly, and b) trimmed properly. It's just =
good manners that if you expect people to read what you are saying, then =
you don't make it hard for them to do so.


> I understand the view about adding a server to a network makes the =
network =E2=80=98unmanaged=E2=80=99.

I assume you meant "managed" there.

> However, I don=E2=80=99t agree with the definition.

Agree or not, it's the position (sort of) that most people are working =
with, and how things are written in the existing standards. I rather =
think that the scope for changing that is long gone - unless we want to =
throw more interoperability spanners in the way of IPv6 adoption.

FWIW, I'm more on the side of DHCP - but I can see the reasons some =
camps are "somewhat against it" for their usage cases.

> The default server configuration should make the network =
=E2=80=98unmanaged=E2=80=99 and the added server should work in that =
network. The fact that DHCPv6 server cannot be easily integrated in the =
network

Why can't it be easily integrated ?
If you have the technical skills to run up a DHCP server then you have =
the technical skills to set teh relevant bits according to how you want =
it to be used by clients. If you lack the admin privileges to change =
those bits, then arguably you should not have privileges to be adding =
servers that will affect how connected clients will work.

> In addition, I believe host default should allow the host to work =
=E2=80=98unmanaged=E2=80=99 in any kind of network (have not seen this =
defined in any RFC; is there RFC that defines this behavior?):
> 	=E2=80=A2 SLAAC only,
> 	=E2=80=A2 DHCPv6 only, or
> 	=E2=80=A2 SLAAC + DHCPv6

Well hosts *should* work in any network - all it needs is for the RAs to =
correctly describe the network. So, if the RAs say to use stateful DHCP =
only for addressing, then that's what the hosts should do. So if the =
network admin correctly configures the router, the hosts should "just =
work".

> That view is shared by Fedora and OpenWRT (see above). If hosts seek =
stateless DHCPv6 configuration by default, routers should offer it by =
default (set =E2=80=98O=E2=80=99 bit to TRUE).

It's arguable that a host using DHCP when the RAs say not to is in the =
wrong.



From nobody Tue Sep  4 11:34:46 2018
Return-Path: <dmudric@avaya.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA73F130DC7 for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 11:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] 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 EJezmGMEHCai for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 11:34:41 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (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 59302130F4A for <v6ops@ietf.org>; Tue,  4 Sep 2018 11:34:41 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2G8BwBwz45b/wUHmMZbGwEBAQEDAQEBC?= =?us-ascii?q?QEBAYJ6VGVtEigKgyk/lEKCDYM9lC87CyMJAoQ+AheDISE3FQECAQEBAQEBAgI?= =?us-ascii?q?CaRwMgmgvAQEEBwMMLwkCAwEBAQEBAQFPAg9HAQEYAQEBAQIBDAYREToQBwQCA?= =?us-ascii?q?QYCDQEDBAEBAQICBiACAgIwFQgIAgQBEggagwCBeQgBDod5kVyJb4EuGgKJYQW?= =?us-ascii?q?BC4lNF4FCPoESRoIeLoMbBBiBMRiCfzGCJgKbVgkChjKJXIFAhyEDD4VmiyeIP?= =?us-ascii?q?oFXI4FVcBU7gmyGAYpSb4EWinwBgRsBAQ?=
X-IPAS-Result: =?us-ascii?q?A2G8BwBwz45b/wUHmMZbGwEBAQEDAQEBCQEBAYJ6VGVtEig?= =?us-ascii?q?Kgyk/lEKCDYM9lC87CyMJAoQ+AheDISE3FQECAQEBAQEBAgICaRwMgmgvAQEEB?= =?us-ascii?q?wMMLwkCAwEBAQEBAQFPAg9HAQEYAQEBAQIBDAYREToQBwQCAQYCDQEDBAEBAQI?= =?us-ascii?q?CBiACAgIwFQgIAgQBEggagwCBeQgBDod5kVyJb4EuGgKJYQWBC4lNF4FCPoESR?= =?us-ascii?q?oIeLoMbBBiBMRiCfzGCJgKbVgkChjKJXIFAhyEDD4VmiyeIPoFXI4FVcBU7gmy?= =?us-ascii?q?GAYpSb4EWinwBgRsBAQ?=
X-IronPort-AV: E=Sophos;i="5.53,330,1531800000"; d="scan'208";a="296311407"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Sep 2018 14:34:38 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC04.global.avaya.com) ([135.11.85.15]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;  04 Sep 2018 14:34:38 -0400
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC04.global.avaya.com ([135.11.85.15]) with mapi id 14.03.0382.000; Tue, 4 Sep 2018 14:34:37 -0400
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Thinking about problems in IPv6-only networks
Thread-Index: AQHUQL/ygyT9kwsoz02Ikgn5fOjK1aTaS9DAgAYcVXWAABB24A==
Date: Tue, 4 Sep 2018 18:34:36 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com> <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk>
In-Reply-To: <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.11.85.50]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/xlYorHKizeLanPu-ZkwkUgdujss>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Sep 2018 18:34:45 -0000

PiBJdCdzIGFyZ3VhYmxlIHRoYXQgYSBob3N0IHVzaW5nIERIQ1Agd2hlbiB0aGUgUkFzIHNheSBu
b3QgdG8gaXMgaW4gdGhlIHdyb25nLg0KDQpBZ3JlZS4gQnV0IGlmICdPJyBiaXQgaXMgbm90IHN1
cHBvcnRlZCBvbiBob3N0cywgaG9zdHMgc2hvdWxkIGhhdmUgREhDUHY2IGVuYWJsZWQgYnkgZGVm
YXVsdC4gVGhlcmUgYXJlIG1pbGxpb25zIG9mIElQdjQgcGhvbmVzIHRoYXQgdXNlIERIQ1B2NCBm
b3IgYXV0b2NvbmZpZ3VyYXRpb24gKGZvciBwaG9uZSBhcHBsaWNhdGlvbnMpLCBmb3IgZXhhbXBs
ZS4gV2hlbiB0aGV5IG1pZ3JhdGUgdG8gSVB2NiwgdGhleSBzaG91bGQgZ2V0IHRoZSBjb25maWd1
cmF0aW9uIGZyb20gREhDUHY2IHNlcnZlci4gREhDUHY2IHNob3VsZCBub3QgYmUgZGlzYWJsZWQg
YnkgZGVmYXVsdCB3aGVuIG1pZ3JhdGluZyB0aG9zZSBwaG9uZSB0byBJUHY2LiBUaGF0IGlzIHdo
eSBJIHRoaW5rICdPJyBzaG91bGQgYmUgVFJVRSBieSBkZWZhdWx0LCBzbyB0aGUgcGhvbmUgYXBw
bGljYXRpb25zIGNhbiBiZSBhdXRvbWF0aWNhbGx5IGNvbmZpZ3VyZWQgYnkgREhDUHY2IHNlcnZl
ci4gQnkgZGVmYXVsdCwgcGhvbmVzIGNhbiB1c2UgU0xBQUMgdG8gZ2V0IHRoZSBhZGRyZXNzZXMu
DQoNCkR1c2FuDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogdjZvcHMg
PHY2b3BzLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBTaW1vbiBIb2Jzb24NCj4gU2Vu
dDogVHVlc2RheSwgU2VwdGVtYmVyIDA0LCAyMDE4IDE6MjkgUE0NCj4gVG86IHY2b3BzQGlldGYu
b3JnDQo+IFN1YmplY3Q6IFJlOiBbdjZvcHNdIFRoaW5raW5nIGFib3V0IHByb2JsZW1zIGluIElQ
djYtb25seSBuZXR3b3Jrcw0KPiANCj4gTXVkcmljLCBEdXNhbiAoRHVzYW4pIDxkbXVkcmljQGF2
YXlhLmNvbT4gd3JvdGU6DQo+IA0KPiBTb21ldGhpbmcganVtYmxlZCB1cCBpbiBhIGhhcmQgdG8g
ZGVjaXBoZXIgbWFubmVyLCBpdCB3b3VsZCBiZSBhIGxvdCBlYXNpZXINCj4gaWYgeW91IGEpIHF1
b3RlZCBwcm9wZXJseSwgYW5kIGIpIHRyaW1tZWQgcHJvcGVybHkuIEl0J3MganVzdCBnb29kIG1h
bm5lcnMNCj4gdGhhdCBpZiB5b3UgZXhwZWN0IHBlb3BsZSB0byByZWFkIHdoYXQgeW91IGFyZSBz
YXlpbmcsIHRoZW4geW91IGRvbid0IG1ha2UgaXQNCj4gaGFyZCBmb3IgdGhlbSB0byBkbyBzby4N
Cj4gDQo+IA0KPiA+IEkgdW5kZXJzdGFuZCB0aGUgdmlldyBhYm91dCBhZGRpbmcgYSBzZXJ2ZXIg
dG8gYSBuZXR3b3JrIG1ha2VzIHRoZQ0KPiBuZXR3b3JrIOKAmHVubWFuYWdlZOKAmS4NCj4gDQo+
IEkgYXNzdW1lIHlvdSBtZWFudCAibWFuYWdlZCIgdGhlcmUuDQo+IA0KPiA+IEhvd2V2ZXIsIEkg
ZG9u4oCZdCBhZ3JlZSB3aXRoIHRoZSBkZWZpbml0aW9uLg0KPiANCj4gQWdyZWUgb3Igbm90LCBp
dCdzIHRoZSBwb3NpdGlvbiAoc29ydCBvZikgdGhhdCBtb3N0IHBlb3BsZSBhcmUgd29ya2luZyB3
aXRoLA0KPiBhbmQgaG93IHRoaW5ncyBhcmUgd3JpdHRlbiBpbiB0aGUgZXhpc3Rpbmcgc3RhbmRh
cmRzLiBJIHJhdGhlciB0aGluayB0aGF0IHRoZQ0KPiBzY29wZSBmb3IgY2hhbmdpbmcgdGhhdCBp
cyBsb25nIGdvbmUgLSB1bmxlc3Mgd2Ugd2FudCB0byB0aHJvdyBtb3JlDQo+IGludGVyb3BlcmFi
aWxpdHkgc3Bhbm5lcnMgaW4gdGhlIHdheSBvZiBJUHY2IGFkb3B0aW9uLg0KPiANCj4gRldJVywg
SSdtIG1vcmUgb24gdGhlIHNpZGUgb2YgREhDUCAtIGJ1dCBJIGNhbiBzZWUgdGhlIHJlYXNvbnMg
c29tZSBjYW1wcw0KPiBhcmUgInNvbWV3aGF0IGFnYWluc3QgaXQiIGZvciB0aGVpciB1c2FnZSBj
YXNlcy4NCj4gDQo+ID4gVGhlIGRlZmF1bHQgc2VydmVyIGNvbmZpZ3VyYXRpb24gc2hvdWxkIG1h
a2UgdGhlIG5ldHdvcmsg4oCYdW5tYW5hZ2Vk4oCZDQo+IGFuZCB0aGUgYWRkZWQgc2VydmVyIHNo
b3VsZCB3b3JrIGluIHRoYXQgbmV0d29yay4gVGhlIGZhY3QgdGhhdCBESENQdjYNCj4gc2VydmVy
IGNhbm5vdCBiZSBlYXNpbHkgaW50ZWdyYXRlZCBpbiB0aGUgbmV0d29yaw0KPiANCj4gV2h5IGNh
bid0IGl0IGJlIGVhc2lseSBpbnRlZ3JhdGVkID8NCj4gSWYgeW91IGhhdmUgdGhlIHRlY2huaWNh
bCBza2lsbHMgdG8gcnVuIHVwIGEgREhDUCBzZXJ2ZXIgdGhlbiB5b3UgaGF2ZSB0aGUNCj4gdGVj
aG5pY2FsIHNraWxscyB0byBzZXQgdGVoIHJlbGV2YW50IGJpdHMgYWNjb3JkaW5nIHRvIGhvdyB5
b3Ugd2FudCBpdCB0byBiZQ0KPiB1c2VkIGJ5IGNsaWVudHMuIElmIHlvdSBsYWNrIHRoZSBhZG1p
biBwcml2aWxlZ2VzIHRvIGNoYW5nZSB0aG9zZSBiaXRzLCB0aGVuDQo+IGFyZ3VhYmx5IHlvdSBz
aG91bGQgbm90IGhhdmUgcHJpdmlsZWdlcyB0byBiZSBhZGRpbmcgc2VydmVycyB0aGF0IHdpbGwg
YWZmZWN0DQo+IGhvdyBjb25uZWN0ZWQgY2xpZW50cyB3aWxsIHdvcmsuDQo+IA0KPiA+IEluIGFk
ZGl0aW9uLCBJIGJlbGlldmUgaG9zdCBkZWZhdWx0IHNob3VsZCBhbGxvdyB0aGUgaG9zdCB0byB3
b3JrDQo+IOKAmHVubWFuYWdlZOKAmSBpbiBhbnkga2luZCBvZiBuZXR3b3JrIChoYXZlIG5vdCBz
ZWVuIHRoaXMgZGVmaW5lZCBpbiBhbnkgUkZDOw0KPiBpcyB0aGVyZSBSRkMgdGhhdCBkZWZpbmVz
IHRoaXMgYmVoYXZpb3I/KToNCj4gPiAJ4oCiIFNMQUFDIG9ubHksDQo+ID4gCeKAoiBESENQdjYg
b25seSwgb3INCj4gPiAJ4oCiIFNMQUFDICsgREhDUHY2DQo+IA0KPiBXZWxsIGhvc3RzICpzaG91
bGQqIHdvcmsgaW4gYW55IG5ldHdvcmsgLSBhbGwgaXQgbmVlZHMgaXMgZm9yIHRoZSBSQXMgdG8N
Cj4gY29ycmVjdGx5IGRlc2NyaWJlIHRoZSBuZXR3b3JrLiBTbywgaWYgdGhlIFJBcyBzYXkgdG8g
dXNlIHN0YXRlZnVsIERIQ1Agb25seQ0KPiBmb3IgYWRkcmVzc2luZywgdGhlbiB0aGF0J3Mgd2hh
dCB0aGUgaG9zdHMgc2hvdWxkIGRvLiBTbyBpZiB0aGUgbmV0d29yayBhZG1pbg0KPiBjb3JyZWN0
bHkgY29uZmlndXJlcyB0aGUgcm91dGVyLCB0aGUgaG9zdHMgc2hvdWxkICJqdXN0IHdvcmsiLg0K
PiANCj4gPiBUaGF0IHZpZXcgaXMgc2hhcmVkIGJ5IEZlZG9yYSBhbmQgT3BlbldSVCAoc2VlIGFi
b3ZlKS4gSWYgaG9zdHMgc2Vlaw0KPiBzdGF0ZWxlc3MgREhDUHY2IGNvbmZpZ3VyYXRpb24gYnkg
ZGVmYXVsdCwgcm91dGVycyBzaG91bGQgb2ZmZXIgaXQgYnkgZGVmYXVsdA0KPiAoc2V0IOKAmE/i
gJkgYml0IHRvIFRSVUUpLg0KPiANCj4gSXQncyBhcmd1YWJsZSB0aGF0IGEgaG9zdCB1c2luZyBE
SENQIHdoZW4gdGhlIFJBcyBzYXkgbm90IHRvIGlzIGluIHRoZSB3cm9uZy4NCj4gDQo+IA0KPiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB2Nm9wcyBt
YWlsaW5nIGxpc3QNCj4gdjZvcHNAaWV0Zi5vcmcNCj4gaHR0cHM6Ly91cmxkZWZlbnNlLnByb29m
cG9pbnQuY29tL3YyL3VybD91PWh0dHBzLQ0KPiAzQV9fd3d3LmlldGYub3JnX21haWxtYW5fbGlz
dGluZm9fdjZvcHMmZD1Ed0lHYVEmYz1CRnBXUXc4YnN1S3ANCj4gbDFTZ2laSDY0USZyPVVUM0Jr
OWNiTGVhSnhoZjNpQ3JoSW9VV0I4WUxaVTIzMDI5c01RR1Eya1kmbT0xWjANCj4gdVRaX1ZVTzVV
eFhYMUFvcjk3RW9SNmYydVAxY1VYdVBYOXowSS0NCj4geFEmcz1wYmg4S0xUYjh6YmZDRDE5Nld1
VzhGWVEtak82S0p5dFJvTHpPTlhkN0V3JmU9DQo=


From nobody Tue Sep  4 11:39:56 2018
Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E492B130F0E for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 11:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 FfchUBld3gHU for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 11:39:53 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 129AD12F1A6 for <v6ops@ietf.org>; Tue,  4 Sep 2018 11:39:52 -0700 (PDT)
Received: from [10.1.10.74] (c-67-164-27-6.hsd1.ca.comcast.net [67.164.27.6]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id w84IclRN022816 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 4 Sep 2018 11:38:47 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com w84IclRN022816
From: Owen DeLong <owen@delong.com>
Message-Id: <FE7CA366-6CC2-4BB5-9EB0-21499341FE99@delong.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2BF635F7-623C-405A-9020-2E9A1869F99C"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 4 Sep 2018 11:38:46 -0700
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, David Farmer <farmer@umn.edu>, "v6ops@ietf.org" <v6ops@ietf.org>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [192.159.10.2]); Tue, 04 Sep 2018 11:38:48 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1Eet-1YrGTYIMzllnPYq4un9Uhs>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Sep 2018 18:39:55 -0000

--Apple-Mail=_2BF635F7-623C-405A-9020-2E9A1869F99C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On Aug 31, 2018, at 13:21 , Mudric, Dusan (Dusan) <dmudric@avaya.com =
<mailto:dmudric@avaya.com>> wrote:
> =20
> The O flag will cause hosts to seek information from a DHCPv6 server,
> hanging (possibly indefinitely) until that information is received. If =
there is no
> DHCPv6 server available to provide that information, you have now =
broken
> the network by changing the O flag without any reason to do so.
>=20
> Possible but it is not required, by any standard that I know about, =
that applications should wait indefinitely for DHCPv6 server response.
> =20
> Whether it=E2=80=99s required or not, it _IS_ the actual =
implementation in a number of existing systems.
> =20
> SO=E2=80=A6 Changing the default value in this way breaks a lot of =
stuff that already exists. I=E2=80=99m not saying we should never
> do that, but there certainly needs to be a compelling reason to do so =
or we shouldn=E2=80=99t do it.
> =20
> So far, you have yet to provide anything remotely resembling a =
compelling reason.
> [[Dusan]]
> > An "unmanaged network" that is "based on the network defaults" =
sounds
> > like it's in conflict with a server being "added to the network."
> =20
> +
> =20
> It would be possible for a router manufacturer to obfuscate this by =
providing a suitable GUI to configure and enable a DHCP server, and as a =
side effect, turn on the M and/or O bits in the RAs issued by **that =
router**.
> =20
> +
> =20

There=E2=80=99s nothing in the RFCs today which prohibits or prevents =
this. A router manufacturer who wants to do make this kind of integrated =
service configuration automatic is completely free to do so now.

That=E2=80=99s not what you proposed, however.

What you proposed was making the O=3D1 bit default across the board. =
That=E2=80=99s an absurd proposal that will only cause grief and has no =
benefit.

> > OpenWRT enables both by default, and a host that supports both SLAAC =
and DHCPv6 e.g. Fedora Linux, will get addresses using both.
> =20
> [[Dusan]]
> I understand the view about adding a server to a network makes the =
network =E2=80=98unmanaged=E2=80=99. However, I don=E2=80=99t agree with =
the definition. The default server configuration should make the network =
=E2=80=98unmanaged=E2=80=99 and the added server should work in that =
network. The fact that DHCPv6 server cannot be easily integrated in the =
network and is out of sync for network changes, should not change the =
definition for =E2=80=98unmanaged=E2=80=99 network. We should rather fix =
DHCPv6 integration. There are ideas how to make =E2=80=98O=E2=80=99 bit =
automatically set for some routers (please see above). I suppose it can =
be done for all routers, if DHCPv6 server is better integrated.
> =20
> In addition, I believe host default should allow the host to work =
=E2=80=98unmanaged=E2=80=99 in any kind of network (have not seen this =
defined in any RFC; is there RFC that defines this behavior?):
> SLAAC only,
> DHCPv6 only, or
> SLAAC + DHCPv6
> That view is shared by Fedora and OpenWRT (see above). If hosts seek =
stateless DHCPv6 configuration by default, routers should offer it by =
default (set =E2=80=98O=E2=80=99 bit to TRUE).

Let=E2=80=99s move away from using the word Managed due to the obvious =
ambiguity now present in how different people in this conversation are =
using the term.

Instead, let=E2=80=99s talk about Default, and non-Default meanings and =
configurations, in terms of how bits are configured in RAs.

The following assumptions are inherent in any rational default =
definition:

	1.	Absent configuration by the administrator, the router =
does not know whether or not an external
		DHCPv6 server is present on the network. The only safe =
assumptions are:
		A.	An external DHCPv6 server may not be present. =
Absent administrator configuration
			otherwise, RAs emitted by the router should be =
M=3D0, O=3D0.
		B.	An external DHCPv6 server may be present. Absent =
administrator configuration
			otherwise, the router should not act as a DHCPv6 =
server.

	2.	If the network administrator chooses to deploy a DHCPv6 =
server, said administrator can
		reasonably be expected to also configure the router =
accordingly, setting the intended
		values for M (M=3D1 if IA_NA is the preferred and =
expected method of address distribution)
		and O (O=3D1 if DHCPv6 server is present and able to =
provide additional configuration
		information about the network environment and the =
administrator wants clients to obtain
		this information from said server).

Nothing in these assumptions supports your desired change, but neither =
does it preclude your desired
router manufacturer behavior.

If a router manufacturer wants to build a router which, when DHCPv6 =
server is turned on for a given link will also enable M and/or O bits in =
RAs on that interface, then said manufacturer is free to do so. This is =
no longer a default configuration, it=E2=80=99s just multiple items =
being changed away from default as a result of a  single user action. =
Absolutely permissible.

Owen


--Apple-Mail=_2BF635F7-623C-405A-9020-2E9A1869F99C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"border-style: none none none =
solid; border-left-width: 1.5pt; border-left-color: blue; padding: 0in =
0in 0in 4pt;" class=3D""><div class=3D""><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D""><div class=3D""><div style=3D"margin:=
 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D"">On Aug 31, 2018, at 13:21 , Mudric, Dusan =
(Dusan) &lt;<a href=3D"mailto:dmudric@avaya.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">dmudric@avaya.com</a>&gt; =
wrote:<o:p class=3D""></o:p></span></div></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
class=3D""><div class=3D""><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt; font-variant-caps: normal; text-align: start; =
-webkit-text-stroke-width: 0px; word-spacing: 0px;" class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 9pt; =
font-family: Helvetica, sans-serif;" class=3D"">The O flag will cause =
hosts to seek information from a DHCPv6 server,<br class=3D"">hanging =
(possibly indefinitely) until that information is received. If there is =
no<br class=3D"">DHCPv6 server available to provide that information, =
you have now broken<br class=3D"">the network by changing the O flag =
without any reason to do so.<o:p =
class=3D""></o:p></span></div></blockquote><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 9pt; font-family: Helvetica, =
sans-serif;" class=3D""><br class=3D"">Possible but it is not required, =
by any standard that I know about, that applications should wait =
indefinitely for DHCPv6 server response.</span><span class=3D""><o:p =
class=3D""></o:p></span></div></div></div></blockquote><div =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D"">Whether it=E2=80=99s required or not, it =
_IS_ the actual implementation in a number of existing systems.<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span class=3D"">SO=E2=80=A6 Changing =
the default value in this way breaks a lot of stuff that already exists. =
I=E2=80=99m not saying we should never<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D"">do that, but there certainly needs to be a =
compelling reason to do so or we shouldn=E2=80=99t do it.<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span class=3D"">So far, you have yet =
to provide anything remotely resembling a compelling reason.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><i class=3D""><span class=3D"">[[Dusan]]<o:p =
class=3D""></o:p></span></i></b></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">&gt; An "unmanaged network" that is "based on the network =
defaults" sounds<o:p class=3D""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">&gt; like it's in conflict with a server being "added to the =
network."<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span class=3D"">+<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">It would be possible for a router manufacturer to obfuscate =
this by providing a suitable GUI to configure and enable a DHCP server, =
and as a side effect, turn on the M and/or O bits in the RAs issued by =
**that router**.<o:p class=3D""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">+<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div></div></div></blockquote><=
div><br class=3D""></div>There=E2=80=99s nothing in the RFCs today which =
prohibits or prevents this. A router manufacturer who wants to do make =
this kind of integrated service configuration automatic is completely =
free to do so now.</div><div><br class=3D""></div><div>That=E2=80=99s =
not what you proposed, however.</div><div><br class=3D""></div><div>What =
you proposed was making the O=3D1 bit default across the board. That=E2=80=
=99s an absurd proposal that will only cause grief and has no =
benefit.</div><div><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"WordSection1" style=3D"page: =
WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div style=3D"border-style: none none none solid; =
border-left-width: 1.5pt; border-left-color: blue; padding: 0in 0in 0in =
4pt;" class=3D""><div class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"SpellE">OpenWRT</span><span =
class=3D"Apple-converted-space">&nbsp;</span>enables both by default, =
and a host that supports both SLAAC and DHCPv6 e.g. Fedora Linux, will =
get addresses using both.<span class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><b class=3D""><i class=3D""><span =
class=3D"">[[Dusan]]<o:p class=3D""></o:p></span></i></b></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span class=3D"">I understand the view =
about adding a server to a network makes the network =E2=80=98unmanaged=E2=
=80=99. However, I don=E2=80=99t agree with the definition. The default =
server configuration should make the network =E2=80=98unmanaged=E2=80=99 =
and the added server should work in that network. The fact that DHCPv6 =
server cannot be easily integrated in the network and is out of sync for =
network changes, should not change the definition for =E2=80=98unmanaged=E2=
=80=99 network. We should rather fix DHCPv6 integration. There are ideas =
how to make =E2=80=98O=E2=80=99 bit automatically set for some routers =
(please see above). I suppose it can be done for all routers, if DHCPv6 =
server is better integrated.<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D"">In addition, I believe host default should =
allow the host to work =E2=80=98unmanaged=E2=80=99 in any kind of =
network (have not seen this defined in any RFC; is there RFC that =
defines this behavior?):<o:p class=3D""></o:p></span></div><ul =
type=3D"disc" style=3D"margin-bottom: 0in; margin-top: 0in;" =
class=3D""><li class=3D"MsoListParagraph" style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">SLAAC only,<o:p class=3D""></o:p></span></li><li =
class=3D"MsoListParagraph" style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;"><span class=3D"">DHCPv6 only, =
or<o:p class=3D""></o:p></span></li><li class=3D"MsoListParagraph" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span class=3D"">SLAAC + DHCPv6<o:p =
class=3D""></o:p></span></li></ul><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D"">That view is shared by Fedora and<span =
class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"SpellE">OpenWRT</span><span =
class=3D"Apple-converted-space">&nbsp;</span>(see above). If hosts seek =
stateless DHCPv6 configuration by default, routers should offer it by =
default (set =E2=80=98O=E2=80=99 bit to =
TRUE).</span></div></div></div></div></div></blockquote><div><br =
class=3D""></div>Let=E2=80=99s move away from using the word Managed due =
to the obvious ambiguity now present in how different people in this =
conversation are using the term.</div><div><br =
class=3D""></div><div>Instead, let=E2=80=99s talk about Default, and =
non-Default meanings and configurations, in terms of how bits are =
configured in RAs.</div><div><br class=3D""></div><div>The following =
assumptions are inherent in any rational default =
definition:</div><div><br class=3D""></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>1.<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Absent =
configuration by the administrator, the router does not know whether or =
not an external</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>DHCPv6 server is present =
on the network. The only safe assumptions are:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>A.<span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>An external DHCPv6 server may not be present. Absent =
administrator configuration</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">			</span>otherwise, RAs =
emitted by the router should be M=3D0, O=3D0.</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>B.<span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>An external DHCPv6 server may be present. Absent administrator =
configuration</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">			</span>otherwise, the =
router should not act as a DHCPv6 server.</div><div><br =
class=3D""></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2.<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>If the network administrator =
chooses to deploy a DHCPv6 server, said administrator =
can</div><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>reasonably be expected to also configure the router accordingly, =
setting the intended</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>values for M (M=3D1 if =
IA_NA is the preferred and expected method of address =
distribution)</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>and O (O=3D1 if DHCPv6 =
server is present and able to provide additional =
configuration</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>information about the =
network environment and the administrator wants clients to =
obtain</div><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">=
		</span>this information from said server).</div><div><br =
class=3D""></div><div>Nothing in these assumptions supports your desired =
change, but neither does it preclude your desired</div><div>router =
manufacturer behavior.</div><div><br class=3D""></div><div>If a router =
manufacturer wants to build a router which, when DHCPv6 server is turned =
on for a given link will also enable M and/or O bits in RAs on that =
interface, then said manufacturer is free to do so. This is no longer a =
default configuration, it=E2=80=99s just multiple items being changed =
away from default as a result of a &nbsp;single user action. Absolutely =
permissible.</div><div><br class=3D""></div><div>Owen</div><div><br =
class=3D""></div></body></html>=

--Apple-Mail=_2BF635F7-623C-405A-9020-2E9A1869F99C--


From nobody Tue Sep  4 11:44:08 2018
Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D766A130EE9 for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 11:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.1
X-Spam-Level: 
X-Spam-Status: No, score=-6.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 5eaPACJtUuns for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 11:44:04 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 0BCD412F1A6 for <v6ops@ietf.org>; Tue,  4 Sep 2018 11:44:03 -0700 (PDT)
Received: from [10.1.10.74] (c-67-164-27-6.hsd1.ca.comcast.net [67.164.27.6]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id w84Ih1W0023329 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 4 Sep 2018 11:43:01 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com w84Ih1W0023329
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com>
Date: Tue, 4 Sep 2018 11:43:00 -0700
Cc: Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2A506CE-3C5A-4896-9A3C-81F1CB2BD80F@delong.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com> <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk> <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [192.159.10.2]); Tue, 04 Sep 2018 11:43:01 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/F6g7LpAwXmrxlX171qb5498Sb9U>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Sep 2018 18:44:07 -0000

> On Sep 4, 2018, at 11:34 AM, Mudric, Dusan (Dusan) <dmudric@avaya.com> =
wrote:
>=20
>> It's arguable that a host using DHCP when the RAs say not to is in =
the wrong.
>=20
> Agree. But if 'O' bit is not supported on hosts, hosts should have =
DHCPv6 enabled by default. There are millions of IPv4 phones that use =
DHCPv4 for autoconfiguration (for phone applications), for example. When =
they migrate to IPv6, they should get the configuration from DHCPv6 =
server. DHCPv6 should not be disabled by default when migrating those =
phone to IPv6. That is why I think 'O' should be TRUE by default, so the =
phone applications can be automatically configured by DHCPv6 server. By =
default, phones can use SLAAC to get the addresses.

???

DHCPv6 is OPTIONAL.

If you want to change that, go for it, but this isn=E2=80=99t the =
working group for that discussion. It=E2=80=99s not an operational =
matter, it=E2=80=99s a
protocol design issue. That debate has been had multiple times in =
multiple working groups and the consensus remains that
ND is mandatory and DHCPv6 is optional in terms of stack implementation.

There is not a question of cell phones that support DHCPv6 but ignore =
the O bit in RAs. It=E2=80=99s more a matter of cellphones (specifically =
Android in particular) which have no DHCPv6 code in the operating system =
in the phone at all.

It does not make sense to =E2=80=9Cenable DHCPv6=E2=80=9D by default, =
since it=E2=80=99s not even necessarily implemented in the protocol =
stack.

Owen

>=20
> Dusan
>=20
>> -----Original Message-----
>> From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Simon Hobson
>> Sent: Tuesday, September 04, 2018 1:29 PM
>> To: v6ops@ietf.org
>> Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
>>=20
>> Mudric, Dusan (Dusan) <dmudric@avaya.com> wrote:
>>=20
>> Something jumbled up in a hard to decipher manner, it would be a lot =
easier
>> if you a) quoted properly, and b) trimmed properly. It's just good =
manners
>> that if you expect people to read what you are saying, then you don't =
make it
>> hard for them to do so.
>>=20
>>=20
>>> I understand the view about adding a server to a network makes the
>> network =E2=80=98unmanaged=E2=80=99.
>>=20
>> I assume you meant "managed" there.
>>=20
>>> However, I don=E2=80=99t agree with the definition.
>>=20
>> Agree or not, it's the position (sort of) that most people are =
working with,
>> and how things are written in the existing standards. I rather think =
that the
>> scope for changing that is long gone - unless we want to throw more
>> interoperability spanners in the way of IPv6 adoption.
>>=20
>> FWIW, I'm more on the side of DHCP - but I can see the reasons some =
camps
>> are "somewhat against it" for their usage cases.
>>=20
>>> The default server configuration should make the network =
=E2=80=98unmanaged=E2=80=99
>> and the added server should work in that network. The fact that =
DHCPv6
>> server cannot be easily integrated in the network
>>=20
>> Why can't it be easily integrated ?
>> If you have the technical skills to run up a DHCP server then you =
have the
>> technical skills to set teh relevant bits according to how you want =
it to be
>> used by clients. If you lack the admin privileges to change those =
bits, then
>> arguably you should not have privileges to be adding servers that =
will affect
>> how connected clients will work.
>>=20
>>> In addition, I believe host default should allow the host to work
>> =E2=80=98unmanaged=E2=80=99 in any kind of network (have not seen =
this defined in any RFC;
>> is there RFC that defines this behavior?):
>>> 	=E2=80=A2 SLAAC only,
>>> 	=E2=80=A2 DHCPv6 only, or
>>> 	=E2=80=A2 SLAAC + DHCPv6
>>=20
>> Well hosts *should* work in any network - all it needs is for the RAs =
to
>> correctly describe the network. So, if the RAs say to use stateful =
DHCP only
>> for addressing, then that's what the hosts should do. So if the =
network admin
>> correctly configures the router, the hosts should "just work".
>>=20
>>> That view is shared by Fedora and OpenWRT (see above). If hosts seek
>> stateless DHCPv6 configuration by default, routers should offer it by =
default
>> (set =E2=80=98O=E2=80=99 bit to TRUE).
>>=20
>> It's arguable that a host using DHCP when the RAs say not to is in =
the wrong.
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-
>> 3A__www.ietf.org_mailman_listinfo_v6ops&d=3DDwIGaQ&c=3DBFpWQw8bsuKp
>> l1SgiZH64Q&r=3DUT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=3D1Z0
>> uTZ_VUO5UxXX1Aor97EoR6f2uP1cUXuPX9z0I-
>> xQ&s=3Dpbh8KLTb8zbfCD196WuW8FYQ-jO6KJytRoLzONXd7Ew&e=3D
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Tue Sep  4 13:35:04 2018
Return-Path: <bs7652@att.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8B38130F02 for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 13:35:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 3mOGKRLtCo6e for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 13:35:02 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 A2EDD127148 for <v6ops@ietf.org>; Tue,  4 Sep 2018 13:35:02 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w84KPfIZ001774; Tue, 4 Sep 2018 16:35:01 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049297.ppops.net-00191d01. with ESMTP id 2ma12br8g8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 04 Sep 2018 16:35:01 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w84KYxRs001727; Tue, 4 Sep 2018 16:35:00 -0400
Received: from zlp30485.vci.att.com (zlp30485.vci.att.com [135.47.91.178]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w84KYrJZ001619; Tue, 4 Sep 2018 16:34:53 -0400
Received: from zlp30485.vci.att.com (zlp30485.vci.att.com [127.0.0.1]) by zlp30485.vci.att.com (Service) with ESMTP id CD13D4048C30; Tue,  4 Sep 2018 20:34:53 +0000 (GMT)
Received: from GAALPA1MSGHUBAG.ITServices.sbc.com (unknown [130.8.218.156]) by zlp30485.vci.att.com (Service) with ESMTPS id BAD684048C2F; Tue,  4 Sep 2018 20:34:53 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.179]) by GAALPA1MSGHUBAG.ITServices.sbc.com ([130.8.218.156]) with mapi id 14.03.0415.000; Tue, 4 Sep 2018 16:34:53 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Mudric, Dusan (Dusan)'" <dmudric@avaya.com>, Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Thinking about problems in IPv6-only networks
Thread-Index: AQHUNlUUCvNME6skukaJ07srHl3Yk6TEhQ4AgAFeugCAAYKZgIACN7yAgAEN+4CADL/kAIAAGB2AgAACdwCAAAROAIAAGYWAgAFgsACAAFE1gIABUGEAgAB0XoCABYM4AIAAIasAgAASVgD//9f08A==
Date: Tue, 4 Sep 2018 20:34:52 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DE94036@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com> <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk> <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com>
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.253.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-04_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809040205
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RM4giHiEyToVhStTdLSth4EZM70>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Sep 2018 20:35:04 -0000

PiA+IEl0J3MgYXJndWFibGUgdGhhdCBhIGhvc3QgdXNpbmcgREhDUCB3aGVuIHRoZSBSQXMgc2F5
IG5vdCB0byBpcyBpbiB0aGUNCj4gd3JvbmcuDQo+IA0KPiBBZ3JlZS4gQnV0IGlmICdPJyBiaXQg
aXMgbm90IHN1cHBvcnRlZCBvbiBob3N0cywgaG9zdHMgc2hvdWxkIGhhdmUgREhDUHY2DQo+IGVu
YWJsZWQgYnkgZGVmYXVsdC4gVGhlcmUgYXJlIG1pbGxpb25zIG9mIElQdjQgcGhvbmVzIHRoYXQg
dXNlIERIQ1B2NCBmb3INCj4gYXV0b2NvbmZpZ3VyYXRpb24gKGZvciBwaG9uZSBhcHBsaWNhdGlv
bnMpLCBmb3IgZXhhbXBsZS4gV2hlbiB0aGV5IG1pZ3JhdGUNCj4gdG8gSVB2NiwgdGhleSBzaG91
bGQgZ2V0IHRoZSBjb25maWd1cmF0aW9uIGZyb20gREhDUHY2IHNlcnZlci4gREhDUHY2DQo+IHNo
b3VsZCBub3QgYmUgZGlzYWJsZWQgYnkgZGVmYXVsdCB3aGVuIG1pZ3JhdGluZyB0aG9zZSBwaG9u
ZSB0byBJUHY2LiBUaGF0DQo+IGlzIHdoeSBJIHRoaW5rICdPJyBzaG91bGQgYmUgVFJVRSBieSBk
ZWZhdWx0LCBzbyB0aGUgcGhvbmUgYXBwbGljYXRpb25zIGNhbiBiZQ0KPiBhdXRvbWF0aWNhbGx5
IGNvbmZpZ3VyZWQgYnkgREhDUHY2IHNlcnZlci4gQnkgZGVmYXVsdCwgcGhvbmVzIGNhbiB1c2UN
Cj4gU0xBQUMgdG8gZ2V0IHRoZSBhZGRyZXNzZXMuDQoNCkhpIER1c2FuLA0KDQpUaGVyZSBhcmUg
bWlsbGlvbnMgb2YgaG9zdHMgd2l0aCBubyBESENQdjYgc3VwcG9ydC4gVGhpcyBpcyB0aGUgY2Fz
ZSBhbmQgd2lsbCBjb250aW51ZSB0byBiZSB0aGUgY2FzZS4gSG9zdHMgdGhhdCBkbyBub3Qgc3Vw
cG9ydCBESENQdjYgY2xpZW50IHdpbGwgKm5ldmVyKiBoYXZlIERIQ1B2NiBlbmFibGVkIGJ5IGRl
ZmF1bHQsIG9yIG90aGVyd2lzZS4gTmV0d29ya3MgdGhhdCBhcmUgcHJpbWFyaWx5IGludGVuZGVk
IGZvciB0aGVzZSBzb3J0cyBvZiBkZXZpY2VzIHdpbGwgcmFyZWx5IChpZiBldmVyKSBoYXZlIERI
Q1B2NiBlbmFibGVkLg0KDQpBcyBmb3IgdGhlIG1pbGxpb25zIG9mIElQdjQgcGhvbmVzIC0tIHRo
ZXNlIG1pbGxpb25zIG9mIHBob25lcyBhcmUgbm90IGNvbm5lY3RpbmcgZGlyZWN0bHkgdG8gRFNM
L0RPQ1NJUy9QT04vM0dQUCBhY2Nlc3MgbmV0d29ya3MuIFRoZXkgYXJlIG5vdCBjb25uZWN0aW5n
IHRvICh1bm1hbmFnZWQpIGhvbWUgbmV0d29ya3MgYW5kIGdldHRpbmcgY29uZmlndXJhdGlvbiBi
eSBESENQdjQuIFRoZXkgYXJlIG5vdCBjb25uZWN0aW5nIGRpcmVjdGx5IHRvIGRhdGEgY2VudGVy
IG5ldHdvcmtzLiBUaGV5J3JlIGRlZmluaXRlbHkgbm90IGNvbm5lY3RpbmcgZGlyZWN0bHkgdG8g
Y29yZSBuZXR3b3JrIHJvdXRlcnMuIFRoZXkgKmFyZSogY29ubmVjdGluZyB0byBlbnRlcnByaXNl
IG5ldHdvcmtzLiBTdWdnZXN0aW5nIHRoYXQgYWxsIHJvdXRlcnMsIGluIGV2ZXJ5IHVzZSBjYXNl
IGFuZCBldmVyeSBzY2VuYXJpbywgbXVzdCBhbHdheXMgc3VwcG9ydCBESENQdjYgc2VydmVyIGFu
ZCBwcm92aWRlIHN0YXRlbGVzcyBjb25maWd1cmF0aW9uLCBqdXN0IGJlY2F1c2UgdGhlcmUgZXhp
c3Qgc29tZSBkZXZpY2VzIGluIHNwZWNpZmljIHVzZSBjYXNlcyB0aGF0IHJlcXVpcmUgY29uZmln
dXJhdGlvbiBpbmZvIGZyb20gREhDUCwgaXNuJ3QgcmVhc29uYWJsZS4NCg0KSWYgeW91IHdhbnQg
dGhpcyBzcGVjaWZpY2FsbHkgZm9yIGVudGVycHJpc2Ugcm91dGVycywgdGhlbiBwZXJoYXBzIHlv
dSBzaG91bGQgYmUgY29tbWVudGluZyBvbiBkcmFmdC1pZXRmLXY2b3BzLWlwdjZydHItcmVxcy4g
Tm90ZSB0aGF0IHRoaXMgZHJhZnQgZG9lcyByZXF1aXJlIERIQ1B2NiBzdXBwb3J0IChTZWN0aW9u
IDMuMywgZmlyc3QgYnVsbGV0KSBmb3IgdGhlIHJvdXRlcnMgaXQgZGVzY3JpYmVzIChzZWUgU2Vj
dGlvbiAxLjMgb24gVXNlIGFuZCBBcHBsaWNhYmlsaXR5KS4NCkJhcmJhcmENCg0KSQ0K


From nobody Tue Sep  4 13:56:41 2018
Return-Path: <dmudric@avaya.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE60130F02 for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 13:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] 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 J8l4qtMyoWaR for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 13:56:36 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (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 C25B8130DEB for <v6ops@ietf.org>; Tue,  4 Sep 2018 13:56:36 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2EoAQAY8I5b/yYyC4daGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJ6VGVtEigKgyk/iBKMMYINgz2ScIE/OwsjCQKEPgIXgyEhNBg?= =?us-ascii?q?BAgEBAQEBAQICAmkcDIJoLwEBBAcDDC8JAgMBAQEBAQEBJgEBAQEBASMCDzUSA?= =?us-ascii?q?QEYAQEBAQIBDAYREToLBQcEAgEGAg0EBAEBAQICBiACAgIwFQgIAgQOBQgagwC?= =?us-ascii?q?BeQgBDogSkVyJb4EuGgKJYQWBC4lNF4FCPoESRoIeLoMbAQECAReBMRiCfzGCJ?= =?us-ascii?q?gKbVgkChjKJXIFAhyEDD4VmiyeIPoFBOYFVcBU7gmyGAYUUhT5vAYEVinkBgRs?= =?us-ascii?q?BAQ?=
X-IPAS-Result: =?us-ascii?q?A2EoAQAY8I5b/yYyC4daGQEBAQEBAQEBAQEBAQcBAQEBAYJ?= =?us-ascii?q?6VGVtEigKgyk/iBKMMYINgz2ScIE/OwsjCQKEPgIXgyEhNBgBAgEBAQEBAQICA?= =?us-ascii?q?mkcDIJoLwEBBAcDDC8JAgMBAQEBAQEBJgEBAQEBASMCDzUSAQEYAQEBAQIBDAY?= =?us-ascii?q?REToLBQcEAgEGAg0EBAEBAQICBiACAgIwFQgIAgQOBQgagwCBeQgBDogSkVyJb?= =?us-ascii?q?4EuGgKJYQWBC4lNF4FCPoESRoIeLoMbAQECAReBMRiCfzGCJgKbVgkChjKJXIF?= =?us-ascii?q?AhyEDD4VmiyeIPoFBOYFVcBU7gmyGAYUUhT5vAYEVinkBgRsBAQ?=
X-IronPort-AV: E=Sophos;i="5.53,330,1531800000"; d="scan'208";a="296329960"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Sep 2018 16:56:35 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC04.global.avaya.com) ([135.11.85.15]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Sep 2018 16:56:35 -0400
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC04.global.avaya.com ([135.11.85.15]) with mapi id 14.03.0382.000; Tue, 4 Sep 2018 16:56:34 -0400
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: Owen DeLong <owen@delong.com>
CC: Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Thinking about problems in IPv6-only networks
Thread-Index: AQHUQL/ygyT9kwsoz02Ikgn5fOjK1aTaS9DAgAYw7tWAAB4GEA==
Date: Tue, 4 Sep 2018 20:56:33 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E459CB4BBE4@AZ-US1EXMB03.global.avaya.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com> <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk> <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com> <F2A506CE-3C5A-4896-9A3C-81F1CB2BD80F@delong.com>
In-Reply-To: <F2A506CE-3C5A-4896-9A3C-81F1CB2BD80F@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.11.85.50]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/w4JE6mR9unTuvwAAvP2WiZPO0y8>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 04 Sep 2018 20:56:39 -0000

SGkgT3dlbiwNCg0KPiBORCBpcyBtYW5kYXRvcnkgYW5kIERIQ1B2NiBpcyBvcHRpb25hbCBpbiB0
ZXJtcyBvZiBzdGFjayBpbXBsZW1lbnRhdGlvbi4NCg0KQWdyZWUgYnV0IG5vdGhpbmcgaXMgcGVy
ZmVjdDoNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM0ODYyI3NlY3Rpb24tNS41IA0K
InRoZSBwcm9jZXNzaW5nIGRlc2NyaWJlZCBiZWxvdyBNVVNUIGJlDQogICBlbmFibGVkIGJ5IGRl
ZmF1bHQuIg0KDQpUaGlzIGRvZXMgbm90IGd1YXJhbnRlZSB0aGF0IGEgcHJlZml4IHdpbGwgYmUg
YXNzaWduZWQgdG8gdGhlIGhvc3RzIChlLmcuIHBob25lcykgYW5kIHRoYXQgdGhleSB3aWxsIGhh
dmUgZ2xvYmFsIFNMQUFDIGFkZHJlc3Nlcy4gSWYgYSBnbG9iYWwgU0xBQUMgYWRkcmVzcyBpcyBu
b3QgY3JlYXRlZCAoZS5nLiBubyAnQScgZW5hYmxlZCBwcmVmaXggaXMgYXNzaWduZWQpLCBESENQ
djYgY2FuIGhlbHAuIEFzc3VtaW5nIERIQ1B2NiBzZXJ2ZXIgaXMgcHJlc2VudCwgaWYgdGhlIGRl
ZmF1bHQgbmV0d29yayBhbGxvd3MgJ00nPVRSVUUsIGFuZCBob3N0cyBzdXBwb3J0IERIQ1B2NiBh
bmQgJ00nIGJpdCwgdGhlIGhvc3RzIGNhbiBhc3NpZ24gREhDUHY2IGFkZHJlc3MgYXV0b21hdGlj
YWxseSBhbmQgaG9zdHMgd291bGQgaGF2ZSBESENQdjYgYW5kIG5vIFNMQUFDIGFkZHJlc3Nlcy4g
QW5kLCBob3N0cyBjYW4gZ2V0IG90aGVyIGNvbmZpZ3VyYXRpb24gZnJvbSBESENQdjYgc2VydmVy
LiBJZiBESENQdjYgc2VydmVyIGlzIG5vdCBwcmVzZW50LCBob3N0cyBzaG91bGQgbm90IGNob2tl
IG9uIGl0LiANCg0KV2l0aCAnTycgKGV2ZW4gJ00nKSBiaXQgc2V0LCB0aGUgZGVmYXVsdCBuZXR3
b3JrIGlzIERIQ1B2NiBpbmNsdXNpdmUuIElmIGl0IGlzIGtub3duIHRoYXQgdGhlIG5ldHdvcmsg
d2lsbCBub3Qgc3VwcG9ydCBESENQdjYsICdPJyBjYW4gYmUgc2V0IHRvIEZBTFNFLCB0byBkaXNh
YmxlIHN0YXRlbGVzcyBESENQdjYgb24gY2xpZW50cyB0aGF0IHJ1biBpdCBieSBkZWZhdWx0Lg0K
DQpJIGFtIGluY2xpbmVkIHRvICdpbmNsdXNpdmUnIG5ldHdvcmtzLiBTaW5jZSB3ZSBhcmUgdGFs
a2luZyBhYm91dCBvbmUgYml0LCBhbmQgaXQgaXMgbm90IHRoYXQgaGFyZCB0byBjaGFuZ2UgdGhl
IGRlZmF1bHQsIEkgd2lsbCBzdG9wIGhlcmUuDQoNClRoYW5rcyBmb3Igc2hhcmluZyB5b3VyIHZp
ZXdzLA0KRHVzYW4uDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogT3dl
biBEZUxvbmcgPG93ZW5AZGVsb25nLmNvbT4NCj4gU2VudDogVHVlc2RheSwgU2VwdGVtYmVyIDA0
LCAyMDE4IDI6NDMgUE0NCj4gVG86IE11ZHJpYywgRHVzYW4gKER1c2FuKSA8ZG11ZHJpY0BhdmF5
YS5jb20+DQo+IENjOiBTaW1vbiBIb2Jzb24gPGxpbnV4QHRoZWhvYnNvbnMuY28udWs+OyB2Nm9w
c0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW3Y2b3BzXSBUaGlua2luZyBhYm91dCBwcm9ibGVt
cyBpbiBJUHY2LW9ubHkgbmV0d29ya3MNCj4gDQo+IA0KPiANCj4gPiBPbiBTZXAgNCwgMjAxOCwg
YXQgMTE6MzQgQU0sIE11ZHJpYywgRHVzYW4gKER1c2FuKQ0KPiA8ZG11ZHJpY0BhdmF5YS5jb20+
IHdyb3RlOg0KPiA+DQo+ID4+IEl0J3MgYXJndWFibGUgdGhhdCBhIGhvc3QgdXNpbmcgREhDUCB3
aGVuIHRoZSBSQXMgc2F5IG5vdCB0byBpcyBpbiB0aGUNCj4gd3JvbmcuDQo+ID4NCj4gPiBBZ3Jl
ZS4gQnV0IGlmICdPJyBiaXQgaXMgbm90IHN1cHBvcnRlZCBvbiBob3N0cywgaG9zdHMgc2hvdWxk
IGhhdmUgREhDUHY2DQo+IGVuYWJsZWQgYnkgZGVmYXVsdC4gVGhlcmUgYXJlIG1pbGxpb25zIG9m
IElQdjQgcGhvbmVzIHRoYXQgdXNlIERIQ1B2NCBmb3INCj4gYXV0b2NvbmZpZ3VyYXRpb24gKGZv
ciBwaG9uZSBhcHBsaWNhdGlvbnMpLCBmb3IgZXhhbXBsZS4gV2hlbiB0aGV5IG1pZ3JhdGUNCj4g
dG8gSVB2NiwgdGhleSBzaG91bGQgZ2V0IHRoZSBjb25maWd1cmF0aW9uIGZyb20gREhDUHY2IHNl
cnZlci4gREhDUHY2DQo+IHNob3VsZCBub3QgYmUgZGlzYWJsZWQgYnkgZGVmYXVsdCB3aGVuIG1p
Z3JhdGluZyB0aG9zZSBwaG9uZSB0byBJUHY2LiBUaGF0DQo+IGlzIHdoeSBJIHRoaW5rICdPJyBz
aG91bGQgYmUgVFJVRSBieSBkZWZhdWx0LCBzbyB0aGUgcGhvbmUgYXBwbGljYXRpb25zIGNhbiBi
ZQ0KPiBhdXRvbWF0aWNhbGx5IGNvbmZpZ3VyZWQgYnkgREhDUHY2IHNlcnZlci4gQnkgZGVmYXVs
dCwgcGhvbmVzIGNhbiB1c2UNCj4gU0xBQUMgdG8gZ2V0IHRoZSBhZGRyZXNzZXMuDQo+IA0KPiA/
Pz8NCj4gDQo+IERIQ1B2NiBpcyBPUFRJT05BTC4NCj4gDQo+IElmIHlvdSB3YW50IHRvIGNoYW5n
ZSB0aGF0LCBnbyBmb3IgaXQsIGJ1dCB0aGlzIGlzbuKAmXQgdGhlIHdvcmtpbmcgZ3JvdXAgZm9y
IHRoYXQNCj4gZGlzY3Vzc2lvbi4gSXTigJlzIG5vdCBhbiBvcGVyYXRpb25hbCBtYXR0ZXIsIGl0
4oCZcyBhDQo+IHByb3RvY29sIGRlc2lnbiBpc3N1ZS4gVGhhdCBkZWJhdGUgaGFzIGJlZW4gaGFk
IG11bHRpcGxlIHRpbWVzIGluIG11bHRpcGxlDQo+IHdvcmtpbmcgZ3JvdXBzIGFuZCB0aGUgY29u
c2Vuc3VzIHJlbWFpbnMgdGhhdA0KPiBORCBpcyBtYW5kYXRvcnkgYW5kIERIQ1B2NiBpcyBvcHRp
b25hbCBpbiB0ZXJtcyBvZiBzdGFjayBpbXBsZW1lbnRhdGlvbi4NCj4gDQo+IFRoZXJlIGlzIG5v
dCBhIHF1ZXN0aW9uIG9mIGNlbGwgcGhvbmVzIHRoYXQgc3VwcG9ydCBESENQdjYgYnV0IGlnbm9y
ZSB0aGUgTw0KPiBiaXQgaW4gUkFzLiBJdOKAmXMgbW9yZSBhIG1hdHRlciBvZiBjZWxscGhvbmVz
IChzcGVjaWZpY2FsbHkgQW5kcm9pZCBpbiBwYXJ0aWN1bGFyKQ0KPiB3aGljaCBoYXZlIG5vIERI
Q1B2NiBjb2RlIGluIHRoZSBvcGVyYXRpbmcgc3lzdGVtIGluIHRoZSBwaG9uZSBhdCBhbGwuDQo+
IA0KPiBJdCBkb2VzIG5vdCBtYWtlIHNlbnNlIHRvIOKAnGVuYWJsZSBESENQdjbigJ0gYnkgZGVm
YXVsdCwgc2luY2UgaXTigJlzIG5vdCBldmVuDQo+IG5lY2Vzc2FyaWx5IGltcGxlbWVudGVkIGlu
IHRoZSBwcm90b2NvbCBzdGFjay4NCj4gDQo+IE93ZW4NCj4gDQo+ID4NCj4gPiBEdXNhbg0KPiA+
DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IHY2b3BzIDx2Nm9w
cy1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgU2ltb24gSG9ic29uDQo+ID4+IFNlbnQ6
IFR1ZXNkYXksIFNlcHRlbWJlciAwNCwgMjAxOCAxOjI5IFBNDQo+ID4+IFRvOiB2Nm9wc0BpZXRm
Lm9yZw0KPiA+PiBTdWJqZWN0OiBSZTogW3Y2b3BzXSBUaGlua2luZyBhYm91dCBwcm9ibGVtcyBp
biBJUHY2LW9ubHkgbmV0d29ya3MNCj4gPj4NCj4gPj4gTXVkcmljLCBEdXNhbiAoRHVzYW4pIDxk
bXVkcmljQGF2YXlhLmNvbT4gd3JvdGU6DQo+ID4+DQo+ID4+IFNvbWV0aGluZyBqdW1ibGVkIHVw
IGluIGEgaGFyZCB0byBkZWNpcGhlciBtYW5uZXIsIGl0IHdvdWxkIGJlIGEgbG90DQo+IGVhc2ll
cg0KPiA+PiBpZiB5b3UgYSkgcXVvdGVkIHByb3Blcmx5LCBhbmQgYikgdHJpbW1lZCBwcm9wZXJs
eS4gSXQncyBqdXN0IGdvb2QgbWFubmVycw0KPiA+PiB0aGF0IGlmIHlvdSBleHBlY3QgcGVvcGxl
IHRvIHJlYWQgd2hhdCB5b3UgYXJlIHNheWluZywgdGhlbiB5b3UgZG9uJ3QNCj4gbWFrZSBpdA0K
PiA+PiBoYXJkIGZvciB0aGVtIHRvIGRvIHNvLg0KPiA+Pg0KPiA+Pg0KPiA+Pj4gSSB1bmRlcnN0
YW5kIHRoZSB2aWV3IGFib3V0IGFkZGluZyBhIHNlcnZlciB0byBhIG5ldHdvcmsgbWFrZXMgdGhl
DQo+ID4+IG5ldHdvcmsg4oCYdW5tYW5hZ2Vk4oCZLg0KPiA+Pg0KPiA+PiBJIGFzc3VtZSB5b3Ug
bWVhbnQgIm1hbmFnZWQiIHRoZXJlLg0KPiA+Pg0KPiA+Pj4gSG93ZXZlciwgSSBkb27igJl0IGFn
cmVlIHdpdGggdGhlIGRlZmluaXRpb24uDQo+ID4+DQo+ID4+IEFncmVlIG9yIG5vdCwgaXQncyB0
aGUgcG9zaXRpb24gKHNvcnQgb2YpIHRoYXQgbW9zdCBwZW9wbGUgYXJlIHdvcmtpbmcgd2l0aCwN
Cj4gPj4gYW5kIGhvdyB0aGluZ3MgYXJlIHdyaXR0ZW4gaW4gdGhlIGV4aXN0aW5nIHN0YW5kYXJk
cy4gSSByYXRoZXIgdGhpbmsgdGhhdA0KPiB0aGUNCj4gPj4gc2NvcGUgZm9yIGNoYW5naW5nIHRo
YXQgaXMgbG9uZyBnb25lIC0gdW5sZXNzIHdlIHdhbnQgdG8gdGhyb3cgbW9yZQ0KPiA+PiBpbnRl
cm9wZXJhYmlsaXR5IHNwYW5uZXJzIGluIHRoZSB3YXkgb2YgSVB2NiBhZG9wdGlvbi4NCj4gPj4N
Cj4gPj4gRldJVywgSSdtIG1vcmUgb24gdGhlIHNpZGUgb2YgREhDUCAtIGJ1dCBJIGNhbiBzZWUg
dGhlIHJlYXNvbnMgc29tZQ0KPiBjYW1wcw0KPiA+PiBhcmUgInNvbWV3aGF0IGFnYWluc3QgaXQi
IGZvciB0aGVpciB1c2FnZSBjYXNlcy4NCj4gPj4NCj4gPj4+IFRoZSBkZWZhdWx0IHNlcnZlciBj
b25maWd1cmF0aW9uIHNob3VsZCBtYWtlIHRoZSBuZXR3b3JrIOKAmHVubWFuYWdlZOKAmQ0KPiA+
PiBhbmQgdGhlIGFkZGVkIHNlcnZlciBzaG91bGQgd29yayBpbiB0aGF0IG5ldHdvcmsuIFRoZSBm
YWN0IHRoYXQgREhDUHY2DQo+ID4+IHNlcnZlciBjYW5ub3QgYmUgZWFzaWx5IGludGVncmF0ZWQg
aW4gdGhlIG5ldHdvcmsNCj4gPj4NCj4gPj4gV2h5IGNhbid0IGl0IGJlIGVhc2lseSBpbnRlZ3Jh
dGVkID8NCj4gPj4gSWYgeW91IGhhdmUgdGhlIHRlY2huaWNhbCBza2lsbHMgdG8gcnVuIHVwIGEg
REhDUCBzZXJ2ZXIgdGhlbiB5b3UgaGF2ZSB0aGUNCj4gPj4gdGVjaG5pY2FsIHNraWxscyB0byBz
ZXQgdGVoIHJlbGV2YW50IGJpdHMgYWNjb3JkaW5nIHRvIGhvdyB5b3Ugd2FudCBpdCB0byBiZQ0K
PiA+PiB1c2VkIGJ5IGNsaWVudHMuIElmIHlvdSBsYWNrIHRoZSBhZG1pbiBwcml2aWxlZ2VzIHRv
IGNoYW5nZSB0aG9zZSBiaXRzLCB0aGVuDQo+ID4+IGFyZ3VhYmx5IHlvdSBzaG91bGQgbm90IGhh
dmUgcHJpdmlsZWdlcyB0byBiZSBhZGRpbmcgc2VydmVycyB0aGF0IHdpbGwNCj4gYWZmZWN0DQo+
ID4+IGhvdyBjb25uZWN0ZWQgY2xpZW50cyB3aWxsIHdvcmsuDQo+ID4+DQo+ID4+PiBJbiBhZGRp
dGlvbiwgSSBiZWxpZXZlIGhvc3QgZGVmYXVsdCBzaG91bGQgYWxsb3cgdGhlIGhvc3QgdG8gd29y
aw0KPiA+PiDigJh1bm1hbmFnZWTigJkgaW4gYW55IGtpbmQgb2YgbmV0d29yayAoaGF2ZSBub3Qg
c2VlbiB0aGlzIGRlZmluZWQgaW4gYW55DQo+IFJGQzsNCj4gPj4gaXMgdGhlcmUgUkZDIHRoYXQg
ZGVmaW5lcyB0aGlzIGJlaGF2aW9yPyk6DQo+ID4+PiAJ4oCiIFNMQUFDIG9ubHksDQo+ID4+PiAJ
4oCiIERIQ1B2NiBvbmx5LCBvcg0KPiA+Pj4gCeKAoiBTTEFBQyArIERIQ1B2Ng0KPiA+Pg0KPiA+
PiBXZWxsIGhvc3RzICpzaG91bGQqIHdvcmsgaW4gYW55IG5ldHdvcmsgLSBhbGwgaXQgbmVlZHMg
aXMgZm9yIHRoZSBSQXMgdG8NCj4gPj4gY29ycmVjdGx5IGRlc2NyaWJlIHRoZSBuZXR3b3JrLiBT
bywgaWYgdGhlIFJBcyBzYXkgdG8gdXNlIHN0YXRlZnVsIERIQ1ANCj4gb25seQ0KPiA+PiBmb3Ig
YWRkcmVzc2luZywgdGhlbiB0aGF0J3Mgd2hhdCB0aGUgaG9zdHMgc2hvdWxkIGRvLiBTbyBpZiB0
aGUgbmV0d29yaw0KPiBhZG1pbg0KPiA+PiBjb3JyZWN0bHkgY29uZmlndXJlcyB0aGUgcm91dGVy
LCB0aGUgaG9zdHMgc2hvdWxkICJqdXN0IHdvcmsiLg0KPiA+Pg0KPiA+Pj4gVGhhdCB2aWV3IGlz
IHNoYXJlZCBieSBGZWRvcmEgYW5kIE9wZW5XUlQgKHNlZSBhYm92ZSkuIElmIGhvc3RzIHNlZWsN
Cj4gPj4gc3RhdGVsZXNzIERIQ1B2NiBjb25maWd1cmF0aW9uIGJ5IGRlZmF1bHQsIHJvdXRlcnMg
c2hvdWxkIG9mZmVyIGl0IGJ5DQo+IGRlZmF1bHQNCj4gPj4gKHNldCDigJhP4oCZIGJpdCB0byBU
UlVFKS4NCj4gPj4NCj4gPj4gSXQncyBhcmd1YWJsZSB0aGF0IGEgaG9zdCB1c2luZyBESENQIHdo
ZW4gdGhlIFJBcyBzYXkgbm90IHRvIGlzIGluIHRoZQ0KPiB3cm9uZy4NCj4gPj4NCj4gPj4NCj4g
Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4g
djZvcHMgbWFpbGluZyBsaXN0DQo+ID4+IHY2b3BzQGlldGYub3JnDQo+ID4+IGh0dHBzOi8vdXJs
ZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCj4gPj4NCj4gM0FfX3d3dy5p
ZXRmLm9yZ19tYWlsbWFuX2xpc3RpbmZvX3Y2b3BzJmQ9RHdJR2FRJmM9QkZwV1F3OGJzdUtwDQo+
ID4+DQo+IGwxU2dpWkg2NFEmcj1VVDNCazljYkxlYUp4aGYzaUNyaElvVVdCOFlMWlUyMzAyOXNN
UUdRMmtZJm09MVowDQo+ID4+IHVUWl9WVU81VXhYWDFBb3I5N0VvUjZmMnVQMWNVWHVQWDl6MEkt
DQo+ID4+IHhRJnM9cGJoOEtMVGI4emJmQ0QxOTZXdVc4RllRLWpPNktKeXRSb0x6T05YZDdFdyZl
PQ0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
ID4gdjZvcHMgbWFpbGluZyBsaXN0DQo+ID4gdjZvcHNAaWV0Zi5vcmcNCj4gPiBodHRwczovL3Vy
bGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtDQo+IDNBX193d3cuaWV0Zi5v
cmdfbWFpbG1hbl9saXN0aW5mb192Nm9wcyZkPUR3SUZhUSZjPUJGcFdRdzhic3VLcGwNCj4gMVNn
aVpINjRRJnI9VVQzQms5Y2JMZWFKeGhmM2lDcmhJb1VXQjhZTFpVMjMwMjlzTVFHUTJrWSZtPVNI
cA0KPiBoSjhJUHNBcUJsYlozLUJlRTloN3lXX3FfQXlvVGlOTnlPX0UycVRzJnM9MG5xM05MNUpI
UWtEVjN3ODF5LQ0KPiBHWHdqX214dkljaFNoVWlKVHlRbm8xVXMmZT0NCg0K


From nobody Tue Sep  4 18:02:22 2018
Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95486130E5C for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 18:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.1
X-Spam-Level: 
X-Spam-Status: No, score=-6.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 rOG8qeE7_9m4 for <v6ops@ietfa.amsl.com>; Tue,  4 Sep 2018 18:02:19 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 30A17130DCB for <v6ops@ietf.org>; Tue,  4 Sep 2018 18:02:17 -0700 (PDT)
Received: from kiev.delong.com (kiev.delong.com [IPv6:2620:0:930:0:0:0:200:5]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id w85117BL013885 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 4 Sep 2018 18:01:09 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com w85117BL013885
From: Owen DeLong <owen@delong.com>
Message-Id: <1143981B-D19F-4C08-B74B-E186985A2F85@delong.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_14EFD72C-594C-45CC-B22D-E37D7729AE61"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 4 Sep 2018 18:01:07 -0700
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4BBE4@AZ-US1EXMB03.global.avaya.com>
Cc: Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com> <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk> <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com> <F2A506CE-3C5A-4896-9A3C-81F1CB2BD80F@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4BBE4@AZ-US1EXMB03.global.avaya.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Tue, 04 Sep 2018 18:01:15 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ET7fvoQRXgT84xZk4-N6QMwUXxw>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 01:02:21 -0000

--Apple-Mail=_14EFD72C-594C-45CC-B22D-E37D7729AE61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Sep 4, 2018, at 13:56 , Mudric, Dusan (Dusan) <dmudric@avaya.com> =
wrote:
>=20
> Hi Owen,
>=20
>> ND is mandatory and DHCPv6 is optional in terms of stack =
implementation.
>=20
> Agree but nothing is perfect:
> https://tools.ietf.org/html/rfc4862#section-5.5 =
<https://tools.ietf.org/html/rfc4862#section-5.5>=20
> "the processing described below MUST be
>   enabled by default."
>=20
> This does not guarantee that a prefix will be assigned to the hosts =
(e.g. phones) and that they will have global SLAAC addresses. If a =
global SLAAC address is not created (e.g. no 'A' enabled prefix is =
assigned), DHCPv6 can help. Assuming DHCPv6 server is present, if the =
default network allows 'M'=3DTRUE, and hosts support DHCPv6 and 'M' bit, =
the hosts can assign DHCPv6 address automatically and hosts would have =
DHCPv6 and no SLAAC addresses. And, hosts can get other configuration =
from DHCPv6 server. If DHCPv6 server is not present, hosts should not =
choke on it.=20

If there is no A enabled prefix in the RA, there are two possibilities:

	1.	The network administrator does not want devices to get =
addresses via SLAAC.
	2.	The network administrator has failed to configure his =
router correctly to achieve his desired result.

In either case, it is _NOT_ appropriate to demand that the phone or any =
other device make incorrect or different assumptions
about the intent of the network administrator. These problems are easily =
detected and easily corrected by the network
administrator and that is the correct behavior under this circumstance.

If you default to M=3DTRUE, then on every network that has NO DHCPv6 =
server, you just broke a LOT of things.

There=E2=80=99s NO valid reason and NO benefit to making M=3D1 default.
=20
> With 'O' (even 'M') bit set, the default network is DHCPv6 inclusive. =
If it is known that the network will not support DHCPv6, 'O' can be set =
to FALSE, to disable stateless DHCPv6 on clients that run it by default.

How is that an improvement over the current situation where I can =
literally reverse all of your statements and be in a good place=E2=80=A6

=E2=80=9CWith O=3D0 and M=3D0 as default, the network is SLAAC enabled. =
If it is known that the network will support DHCPv6, =E2=80=98O=E2=80=99 =
can be set to TRUE to enable stateless DHCPv6 or =E2=80=98M=E2=80=99 can =
be set to TRUE to enable stateful DHCPv6 on clients that are DHCPv6 =
capable.=E2=80=9D

Since clients are required to be SLAAC capable and support for DHCPv6 on =
the client side is OPTIONAL, this is the more rational default.

> I am inclined to 'inclusive' networks. Since we are talking about one =
bit, and it is not that hard to change the default, I will stop here.

Every router that has any reasonable support for IPv6 has a convenient =
way to turn on O and/or M bits as needed for a network which includes a =
DHCPv6 server. There=E2=80=99s no rationale here for changing the =
default. As pointed out repeatedly before, changing this default would =
break multiple existing implementations. You can say =E2=80=9Chosts =
should not choke on M=3D1 with no DHCPv6 server=E2=80=9D all you want, =
but the reality is that legitimate and valid interpretations of the =
existing RFCs and multiple existing implementations already do exactly =
that=E2=80=A6 Choke if M=3D1 and DHCPv6 server is not present. Certainly =
there is a valid argument that making DHCPv6 host participation =
mandatory (M=3D1) in a network with no DHCPv6 services is a =
misconfiguration.

Misconfiguration as a default setting seems ill-advised at best.


Owen



--Apple-Mail=_14EFD72C-594C-45CC-B22D-E37D7729AE61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Sep 4, 2018, at 13:56 , Mudric, Dusan (Dusan) &lt;<a =
href=3D"mailto:dmudric@avaya.com" class=3D"">dmudric@avaya.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Hi Owen,</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">ND is =
mandatory and DHCPv6 is optional in terms of stack implementation.<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Agree but nothing is perfect:</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><a =
href=3D"https://tools.ietf.org/html/rfc4862#section-5.5" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://tools.ietf.org/html/rfc4862#section-5.5</a><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">"the processing described below =
MUST be</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" =
class=3D"">&nbsp;&nbsp;enabled by default."</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">This does not guarantee that a =
prefix will be assigned to the hosts (e.g. phones) and that they will =
have global SLAAC addresses. If a global SLAAC address is not created =
(e.g. no 'A' enabled prefix is assigned), DHCPv6 can help. Assuming =
DHCPv6 server is present, if the default network allows 'M'=3DTRUE, and =
hosts support DHCPv6 and 'M' bit, the hosts can assign DHCPv6 address =
automatically and hosts would have DHCPv6 and no SLAAC addresses. And, =
hosts can get other configuration from DHCPv6 server. If DHCPv6 server =
is not present, hosts should not choke on it.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""></div></blockquote><div><br class=3D""></div>If there is no A =
enabled prefix in the RA, there are two possibilities:</div><div><br =
class=3D""></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>1.<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>The network administrator does =
not want devices to get addresses via SLAAC.</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>2.<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>The =
network administrator has failed to configure his router correctly to =
achieve his desired result.</div><div><br class=3D""></div><div>In =
either case, it is _NOT_ appropriate to demand that the phone or any =
other device make incorrect or different assumptions</div><div>about the =
intent of the network administrator. These problems are easily detected =
and easily corrected by the network</div><div>administrator and that is =
the correct behavior under this circumstance.</div><div><br =
class=3D""></div><div>If you default to M=3DTRUE, then on every network =
that has NO DHCPv6 server, you just broke a LOT of things.</div><div><br =
class=3D""></div><div>There=E2=80=99s NO valid reason and NO benefit to =
making M=3D1 default.</div><div>&nbsp;<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">With 'O' (even 'M') bit set, the default network is DHCPv6 =
inclusive. If it is known that the network will not support DHCPv6, 'O' =
can be set to FALSE, to disable stateless DHCPv6 on clients that run it =
by default.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""></div></blockquote><div><br class=3D""></div>How is =
that an improvement over the current situation where I can literally =
reverse all of your statements and be in a good place=E2=80=A6</div><div><=
br class=3D""></div><div>=E2=80=9CWith O=3D0 and M=3D0 as default, the =
network is SLAAC enabled. If it is known that the network will support =
DHCPv6, =E2=80=98O=E2=80=99 can be set to TRUE to enable stateless =
DHCPv6 or =E2=80=98M=E2=80=99 can be set to TRUE to enable stateful =
DHCPv6 on clients that are DHCPv6 capable.=E2=80=9D</div><div><br =
class=3D""></div><div>Since clients are required to be SLAAC capable and =
support for DHCPv6 on the client side is OPTIONAL, this is the more =
rational default.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><span style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">I am inclined to 'inclusive' networks. Since we are talking =
about one bit, and it is not that hard to change the default, I will =
stop here.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""></div></blockquote><div><br class=3D""></div>Every =
router that has any reasonable support for IPv6 has a convenient way to =
turn on O and/or M bits as needed for a network which includes a DHCPv6 =
server. There=E2=80=99s no rationale here for changing the default. As =
pointed out repeatedly before, changing this default would break =
multiple existing implementations. You can say =E2=80=9Chosts should not =
choke on M=3D1 with no DHCPv6 server=E2=80=9D all you want, but the =
reality is that legitimate and valid interpretations of the existing =
RFCs and multiple existing implementations already do exactly that=E2=80=A6=
 Choke if M=3D1 and DHCPv6 server is not present. Certainly there is a =
valid argument that making DHCPv6 host participation mandatory (M=3D1) =
in a network with no DHCPv6 services is a =
misconfiguration.</div><div><br class=3D""></div><div>Misconfiguration =
as a default setting seems ill-advised at best.</div><div><br =
class=3D""></div><div><br class=3D""></div><div>Owen</div><div><br =
class=3D""></div><br class=3D""></body></html>=

--Apple-Mail=_14EFD72C-594C-45CC-B22D-E37D7729AE61--


From nobody Wed Sep  5 04:13:07 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCFF130DFE for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 04:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 3YWJHsmi2TSq for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 04:13:03 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD1F1130DFB for <v6ops@ietf.org>; Wed,  5 Sep 2018 04:13:02 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 68A5D438D6 for <v6ops@ietf.org>; Wed,  5 Sep 2018 13:13:00 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 5A9B5438D5; Wed,  5 Sep 2018 13:13:00 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 55EC89A0E8; Wed,  5 Sep 2018 13:13:00 +0200 (CEST)
Date: Wed, 5 Sep 2018 13:13:00 +0200
From: Gert Doering <gert@space.net>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
Cc: Owen DeLong <owen@delong.com>, Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <20180905111300.GK11393@Space.Net>
References: <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB47368@AZ-US1EXMB03.global.avaya.com> <5BECF927-9AD4-49A4-BBF7-4D590F0F557C@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB483D1@AZ-US1EXMB03.global.avaya.com> <C4CB8586-41A7-4CC5-86BD-550668DE8F45@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4B6F5@AZ-US1EXMB03.global.avaya.com> <AC38DE50-A22E-4D50-9959-6DB45435F079@thehobsons.co.uk> <9142206A0C5BF24CB22755C8EC422E459CB4B9CD@AZ-US1EXMB03.global.avaya.com> <F2A506CE-3C5A-4896-9A3C-81F1CB2BD80F@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4BBE4@AZ-US1EXMB03.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4BBE4@AZ-US1EXMB03.global.avaya.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Im90mZZAc2vYhBV8lRLCJgGZP5s>
Subject: Re: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 11:13:06 -0000

Hi,

On Tue, Sep 04, 2018 at 08:56:33PM +0000, Mudric, Dusan (Dusan) wrote:
> I will stop here.

Thank you.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Wed Sep  5 06:36:18 2018
Return-Path: <dmudric@avaya.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C905127133 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 06:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 hxT1PUh7YTM1 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 06:36:10 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (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 45C97128D68 for <v6ops@ietf.org>; Wed,  5 Sep 2018 06:36:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2E/BQBS249b/wUHmMZaGwEBAQEDAQEBC?= =?us-ascii?q?QEBAYJ6VGVtEigKg2iIEowygg2DPZJygXoLJQcChD4CF4M3ITQYAQIBAQEBAQE?= =?us-ascii?q?CAgJpHAyCaEtqAQEBAQEBIwJELAEBAgITERFKBwYBFQQEAQEDAgYZBwIEMBUIC?= =?us-ascii?q?QEEARIIGoMAgXkIAQ6YZIlvgS4aAolmBYELiU0XgUI+gViFZwEBAgGBNxEYgn8?= =?us-ascii?q?xgiYCm1wJAoY0iV+IZQOFeosviEWBQTmBVXAVgyeCTYhIhT5vAYEViiCBLgGBH?= =?us-ascii?q?AEB?=
X-IPAS-Result: =?us-ascii?q?A2E/BQBS249b/wUHmMZaGwEBAQEDAQEBCQEBAYJ6VGVtEig?= =?us-ascii?q?Kg2iIEowygg2DPZJygXoLJQcChD4CF4M3ITQYAQIBAQEBAQECAgJpHAyCaEtqA?= =?us-ascii?q?QEBAQEBIwJELAEBAgITERFKBwYBFQQEAQEDAgYZBwIEMBUICQEEARIIGoMAgXk?= =?us-ascii?q?IAQ6YZIlvgS4aAolmBYELiU0XgUI+gViFZwEBAgGBNxEYgn8xgiYCm1wJAoY0i?= =?us-ascii?q?V+IZQOFeosviEWBQTmBVXAVgyeCTYhIhT5vAYEViiCBLgGBHAEB?=
X-IronPort-AV: E=Sophos;i="5.53,333,1531800000"; d="scan'208";a="254253024"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Sep 2018 09:36:05 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC01.global.avaya.com) ([135.11.85.12]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;  05 Sep 2018 09:36:05 -0400
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC01.global.avaya.com ([135.11.85.12]) with mapi id 14.03.0382.000; Wed, 5 Sep 2018 09:36:04 -0400
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: "STARK, BARBARA H" <bs7652@att.com>, Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
Thread-Index: AdRFHWOZHHYbWX1OT62jFlEWmsFm5w==
Date: Wed, 5 Sep 2018 13:36:04 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.11.85.50]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4QiKkB9C6XkN1v1tOPWUI235LOI>
Subject: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 13:36:17 -0000

SGkgQmFyYmFyYSwNCg0KPiBBcyBmb3IgdGhlIG1pbGxpb25zIG9mIElQdjQgcGhvbmVzIC0tIHRo
ZXNlIG1pbGxpb25zIG9mIHBob25lcyBhcmUgbm90DQo+IGNvbm5lY3RpbmcgZGlyZWN0bHkgdG8g
RFNML0RPQ1NJUy9QT04vM0dQUCBhY2Nlc3MgbmV0d29ya3MuIFRoZXkgYXJlIG5vdA0KPiBjb25u
ZWN0aW5nIHRvICh1bm1hbmFnZWQpIGhvbWUgbmV0d29ya3MgYW5kIGdldHRpbmcgY29uZmlndXJh
dGlvbiBieQ0KPiBESENQdjQuIFRoZXkgYXJlIG5vdCBjb25uZWN0aW5nIGRpcmVjdGx5IHRvIGRh
dGEgY2VudGVyIG5ldHdvcmtzLiBUaGV5J3JlDQo+IGRlZmluaXRlbHkgbm90IGNvbm5lY3Rpbmcg
ZGlyZWN0bHkgdG8gY29yZSBuZXR3b3JrIHJvdXRlcnMuIFRoZXkgKmFyZSoNCj4gY29ubmVjdGlu
ZyB0byBlbnRlcnByaXNlIG5ldHdvcmtzLiBTdWdnZXN0aW5nIHRoYXQgYWxsIHJvdXRlcnMsIGlu
IGV2ZXJ5IHVzZQ0KPiBjYXNlIGFuZCBldmVyeSBzY2VuYXJpbywgbXVzdCBhbHdheXMgc3VwcG9y
dCBESENQdjYgc2VydmVyIGFuZCBwcm92aWRlDQo+IHN0YXRlbGVzcyBjb25maWd1cmF0aW9uLCBq
dXN0IGJlY2F1c2UgdGhlcmUgZXhpc3Qgc29tZSBkZXZpY2VzIGluIHNwZWNpZmljIHVzZQ0KPiBj
YXNlcyB0aGF0IHJlcXVpcmUgY29uZmlndXJhdGlvbiBpbmZvIGZyb20gREhDUCwgaXNuJ3QgcmVh
c29uYWJsZS4NCj4gDQo+IElmIHlvdSB3YW50IHRoaXMgc3BlY2lmaWNhbGx5IGZvciBlbnRlcnBy
aXNlIHJvdXRlcnMsIHRoZW4gcGVyaGFwcyB5b3Ugc2hvdWxkDQo+IGJlIGNvbW1lbnRpbmcgb24g
ZHJhZnQtaWV0Zi12Nm9wcy1pcHY2cnRyLXJlcXMuIE5vdGUgdGhhdCB0aGlzIGRyYWZ0IGRvZXMN
Cj4gcmVxdWlyZSBESENQdjYgc3VwcG9ydCAoU2VjdGlvbiAzLjMsIGZpcnN0IGJ1bGxldCkgZm9y
IHRoZSByb3V0ZXJzIGl0IGRlc2NyaWJlcw0KPiAoc2VlIFNlY3Rpb24gMS4zIG9uIFVzZSBhbmQg
QXBwbGljYWJpbGl0eSkuDQoNCkdvb2QgcG9pbnQuIEkgYW0gdGFsa2luZyBhYm91dCB0aGUgcGhv
bmVzIGluIGVudGVycHJpc2UgZW52aXJvbm1lbnRzLiANCg0KSXQgaXMgbm90IGNsZWFyIHdoYXQg
dGhlIGN1cnJlbnQgY29uc2Vuc3VzIGlzOg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWlldGYtdjZvcHMtaXB2NnJ0ci1yZXFzLTA0I3NlY3Rpb24tMy4zICA6DQoNCkRIQ1B2NiBp
cyBtYW5kYXRvcnk6DQogICBvICBbSS1ELmlldGYtZGhjLXJmYzMzMTViaXNdOiBEeW5hbWljIENv
bmZpZ3VyYXRpb24gUHJvdG9jb2wgZm9yIElQdjYNCiAgICAgIG11c3QgYmUgc3VwcG9ydGVkLg0K
DQpvciBESENQdjYgaXMgb3B0aW9uYWw6ICANCiAgbyAgW1JGQzM2NDZdOiBETlMgQ29uZmlndXJh
dGlvbiBvcHRpb25zIGZvciBEeW5hbWljIEhvc3QNCiAgICAgIENvbmZpZ3VyYXRpb24gUHJvdG9j
b2wgZm9yIElQdjYgKERIQ1B2NikgaWYgREhDUHY2IGlzIHN1cHBvcnRlZC4NClNob3VsZCB0aGUg
bGFzdCBzZW50ZW5jZSBiZSAnaWYgREhDUHY2IGlzIGVuYWJsZWQnPw0KDQpNYXkgYmUgJ00nIGFu
ZCAnTycgY2FuIGJlIFRSVUUgYnkgZGVmYXVsdCBpbiB0aGUgZW50ZXJwcmlzZSBuZXR3b3Jrcywg
aWYgREhDUHY2IGlzIGVuYWJsZWQuIFRoYXQgd2F5IHRoZSBzY29wZSBvZiBlbmFibGVkICdNJyBh
bmQgJ08nIGlzIGxpbWl0ZWQgdG8gdGhlIGVudGVycHJpc2VzIHRoYXQgY29uZmlndXJlIHRoZWly
IHBob25lcyB1c2luZyBESENQdjYuIFNpbmNlIFNMQUFDIG11c3QgYmUgZW5hYmxlZCBhbmQgdGhl
IHBob25lcyBjYW4gY3JlYXRlIGdsb2JhbCBTTEFBQyBhZGRyZXNzZXMsIHRoZSBwaG9uZSBhcHBs
aWNhdGlvbnMgY2FuIGJlIGF1dG9jb25maWd1cmVkIGJ5IGVuYWJsaW5nICdPJyBiaXQgb25seSAo
ZGVmYXVsdCBmb3IgJ00nIHN0YXlzIEZBTFNFKS4gSWYgZW50ZXJwcmlzZXMgZG9uJ3QgdXNlIERI
Q1B2NiBmb3IgYXV0b2NvbmZpZ3VyYXRpb24gKERIQ1B2NiBpcyBkaXNhYmxlZCksICdPJyBiaXQg
c2hvdWxkIGJlIHNldCB0byBGQUxTRS4NCg0KVGhhbmtzLA0KRHVzYW4uDQoNCj4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogU1RBUkssIEJBUkJBUkEgSCA8YnM3NjUyQGF0dC5j
b20+DQo+IFNlbnQ6IFR1ZXNkYXksIFNlcHRlbWJlciAwNCwgMjAxOCA0OjM1IFBNDQo+IFRvOiBN
dWRyaWMsIER1c2FuIChEdXNhbikgPGRtdWRyaWNAYXZheWEuY29tPjsgU2ltb24gSG9ic29uDQo+
IDxsaW51eEB0aGVob2Jzb25zLmNvLnVrPjsgdjZvcHNAaWV0Zi5vcmcNCj4gU3ViamVjdDogUkU6
IFt2Nm9wc10gVGhpbmtpbmcgYWJvdXQgcHJvYmxlbXMgaW4gSVB2Ni1vbmx5IG5ldHdvcmtzDQo+
IA0KPiA+ID4gSXQncyBhcmd1YWJsZSB0aGF0IGEgaG9zdCB1c2luZyBESENQIHdoZW4gdGhlIFJB
cyBzYXkgbm90IHRvIGlzIGluIHRoZQ0KPiA+IHdyb25nLg0KPiA+DQo+ID4gQWdyZWUuIEJ1dCBp
ZiAnTycgYml0IGlzIG5vdCBzdXBwb3J0ZWQgb24gaG9zdHMsIGhvc3RzIHNob3VsZCBoYXZlIERI
Q1B2Ng0KPiA+IGVuYWJsZWQgYnkgZGVmYXVsdC4gVGhlcmUgYXJlIG1pbGxpb25zIG9mIElQdjQg
cGhvbmVzIHRoYXQgdXNlIERIQ1B2NCBmb3INCj4gPiBhdXRvY29uZmlndXJhdGlvbiAoZm9yIHBo
b25lIGFwcGxpY2F0aW9ucyksIGZvciBleGFtcGxlLiBXaGVuIHRoZXkNCj4gbWlncmF0ZQ0KPiA+
IHRvIElQdjYsIHRoZXkgc2hvdWxkIGdldCB0aGUgY29uZmlndXJhdGlvbiBmcm9tIERIQ1B2NiBz
ZXJ2ZXIuIERIQ1B2Ng0KPiA+IHNob3VsZCBub3QgYmUgZGlzYWJsZWQgYnkgZGVmYXVsdCB3aGVu
IG1pZ3JhdGluZyB0aG9zZSBwaG9uZSB0byBJUHY2Lg0KPiBUaGF0DQo+ID4gaXMgd2h5IEkgdGhp
bmsgJ08nIHNob3VsZCBiZSBUUlVFIGJ5IGRlZmF1bHQsIHNvIHRoZSBwaG9uZSBhcHBsaWNhdGlv
bnMgY2FuDQo+IGJlDQo+ID4gYXV0b21hdGljYWxseSBjb25maWd1cmVkIGJ5IERIQ1B2NiBzZXJ2
ZXIuIEJ5IGRlZmF1bHQsIHBob25lcyBjYW4gdXNlDQo+ID4gU0xBQUMgdG8gZ2V0IHRoZSBhZGRy
ZXNzZXMuDQo+IA0KPiBIaSBEdXNhbiwNCj4gDQo+IFRoZXJlIGFyZSBtaWxsaW9ucyBvZiBob3N0
cyB3aXRoIG5vIERIQ1B2NiBzdXBwb3J0LiBUaGlzIGlzIHRoZSBjYXNlIGFuZCB3aWxsDQo+IGNv
bnRpbnVlIHRvIGJlIHRoZSBjYXNlLiBIb3N0cyB0aGF0IGRvIG5vdCBzdXBwb3J0IERIQ1B2NiBj
bGllbnQgd2lsbA0KPiAqbmV2ZXIqIGhhdmUgREhDUHY2IGVuYWJsZWQgYnkgZGVmYXVsdCwgb3Ig
b3RoZXJ3aXNlLiBOZXR3b3JrcyB0aGF0IGFyZQ0KPiBwcmltYXJpbHkgaW50ZW5kZWQgZm9yIHRo
ZXNlIHNvcnRzIG9mIGRldmljZXMgd2lsbCByYXJlbHkgKGlmIGV2ZXIpIGhhdmUgREhDUHY2DQo+
IGVuYWJsZWQuDQo+IA0KPiBBcyBmb3IgdGhlIG1pbGxpb25zIG9mIElQdjQgcGhvbmVzIC0tIHRo
ZXNlIG1pbGxpb25zIG9mIHBob25lcyBhcmUgbm90DQo+IGNvbm5lY3RpbmcgZGlyZWN0bHkgdG8g
RFNML0RPQ1NJUy9QT04vM0dQUCBhY2Nlc3MgbmV0d29ya3MuIFRoZXkgYXJlIG5vdA0KPiBjb25u
ZWN0aW5nIHRvICh1bm1hbmFnZWQpIGhvbWUgbmV0d29ya3MgYW5kIGdldHRpbmcgY29uZmlndXJh
dGlvbiBieQ0KPiBESENQdjQuIFRoZXkgYXJlIG5vdCBjb25uZWN0aW5nIGRpcmVjdGx5IHRvIGRh
dGEgY2VudGVyIG5ldHdvcmtzLiBUaGV5J3JlDQo+IGRlZmluaXRlbHkgbm90IGNvbm5lY3Rpbmcg
ZGlyZWN0bHkgdG8gY29yZSBuZXR3b3JrIHJvdXRlcnMuIFRoZXkgKmFyZSoNCj4gY29ubmVjdGlu
ZyB0byBlbnRlcnByaXNlIG5ldHdvcmtzLiBTdWdnZXN0aW5nIHRoYXQgYWxsIHJvdXRlcnMsIGlu
IGV2ZXJ5IHVzZQ0KPiBjYXNlIGFuZCBldmVyeSBzY2VuYXJpbywgbXVzdCBhbHdheXMgc3VwcG9y
dCBESENQdjYgc2VydmVyIGFuZCBwcm92aWRlDQo+IHN0YXRlbGVzcyBjb25maWd1cmF0aW9uLCBq
dXN0IGJlY2F1c2UgdGhlcmUgZXhpc3Qgc29tZSBkZXZpY2VzIGluIHNwZWNpZmljIHVzZQ0KPiBj
YXNlcyB0aGF0IHJlcXVpcmUgY29uZmlndXJhdGlvbiBpbmZvIGZyb20gREhDUCwgaXNuJ3QgcmVh
c29uYWJsZS4NCj4gDQo+IElmIHlvdSB3YW50IHRoaXMgc3BlY2lmaWNhbGx5IGZvciBlbnRlcnBy
aXNlIHJvdXRlcnMsIHRoZW4gcGVyaGFwcyB5b3Ugc2hvdWxkDQo+IGJlIGNvbW1lbnRpbmcgb24g
ZHJhZnQtaWV0Zi12Nm9wcy1pcHY2cnRyLXJlcXMuIE5vdGUgdGhhdCB0aGlzIGRyYWZ0IGRvZXMN
Cj4gcmVxdWlyZSBESENQdjYgc3VwcG9ydCAoU2VjdGlvbiAzLjMsIGZpcnN0IGJ1bGxldCkgZm9y
IHRoZSByb3V0ZXJzIGl0IGRlc2NyaWJlcw0KPiAoc2VlIFNlY3Rpb24gMS4zIG9uIFVzZSBhbmQg
QXBwbGljYWJpbGl0eSkuDQo+IEJhcmJhcmENCj4gDQo+IEkNCg==


From nobody Wed Sep  5 07:09:10 2018
Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C31B1130E08 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 07:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.101
X-Spam-Level: 
X-Spam-Status: No, score=-6.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 oYbLilwUEvkM for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 07:09:07 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 86ECA126CC7 for <v6ops@ietf.org>; Wed,  5 Sep 2018 07:09:06 -0700 (PDT)
Received: from [IPv6:2620::930:0:c15b:8f56:808:ca35] ([IPv6:2620:0:930:0:c15b:8f56:808:ca35]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id w85E7omX015477 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 5 Sep 2018 07:07:50 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com w85E7omX015477
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Owen DeLong <owen@delong.com>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com>
Date: Wed, 5 Sep 2018 07:07:49 -0700
Cc: "STARK, BARBARA H" <bs7652@att.com>, Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com>
References: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Wed, 05 Sep 2018 07:07:54 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kcvkCnHgWXWdIcia4fK9x1BuHVQ>
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 14:09:10 -0000

You are continuing to confuse implementation and operation requirements. You=
 are also ignoring reality...

There=E2=80=99s no way for a router to know whether it is deployed in an ent=
erprise environment or not at time of manufacture.=20

Further, I don=E2=80=99t believe for one second that ALL enterprises will re=
quire or use DHCPv6. Perhaps most, but certainly not all.=20

The current situation is that implementation of DHCPv6 in the protocol stack=
 on ANY device is optional. There is a proposal to make it mandatory on rout=
ers only. There is no proposal that I know of to make it mandatory on hosts.=
 Any such proposal would be a major change to IPv6 architecture that I am ce=
rtain would face substantial opposition.=20

Therefore there is no conflict between the ID you referenced and the RFC you=
 referenced. Your proposed change to the RFC would be nonsensical absent an a=
cross the board requirement for DHCPv6 implementation in all protocol stacks=
. That=E2=80=99s not likely to happen, nor is DHCPv6 support in Android base=
d phones.=20

Since a router can=E2=80=99t know at manufacture time whether it is deployed=
 in an enterprise or not, and since it is not universally true that enterpri=
ses will want DHCPv6, it is impossible to set M and O defaults in the manner=
 you propose.

The good news is that it=E2=80=99s also utterly unnecessary to do so.=20

Owen


> On Sep 5, 2018, at 06:36, Mudric, Dusan (Dusan) <dmudric@avaya.com> wrote:=

>=20
> Hi Barbara,
>=20
>> As for the millions of IPv4 phones -- these millions of phones are not
>> connecting directly to DSL/DOCSIS/PON/3GPP access networks. They are not
>> connecting to (unmanaged) home networks and getting configuration by
>> DHCPv4. They are not connecting directly to data center networks. They're=

>> definitely not connecting directly to core network routers. They *are*
>> connecting to enterprise networks. Suggesting that all routers, in every u=
se
>> case and every scenario, must always support DHCPv6 server and provide
>> stateless configuration, just because there exist some devices in specifi=
c use
>> cases that require configuration info from DHCP, isn't reasonable.
>>=20
>> If you want this specifically for enterprise routers, then perhaps you sh=
ould
>> be commenting on draft-ietf-v6ops-ipv6rtr-reqs. Note that this draft does=

>> require DHCPv6 support (Section 3.3, first bullet) for the routers it des=
cribes
>> (see Section 1.3 on Use and Applicability).
>=20
> Good point. I am talking about the phones in enterprise environments.=20
>=20
> It is not clear what the current consensus is:
> https://tools.ietf.org/html/draft-ietf-v6ops-ipv6rtr-reqs-04#section-3.3  :=

>=20
> DHCPv6 is mandatory:
>   o  [I-D.ietf-dhc-rfc3315bis]: Dynamic Configuration Protocol for IPv6
>      must be supported.
>=20
> or DHCPv6 is optional: =20
>  o  [RFC3646]: DNS Configuration options for Dynamic Host
>      Configuration Protocol for IPv6 (DHCPv6) if DHCPv6 is supported.
> Should the last sentence be 'if DHCPv6 is enabled'?
>=20
> May be 'M' and 'O' can be TRUE by default in the enterprise networks, if D=
HCPv6 is enabled. That way the scope of enabled 'M' and 'O' is limited to th=
e enterprises that configure their phones using DHCPv6. Since SLAAC must be e=
nabled and the phones can create global SLAAC addresses, the phone applicati=
ons can be autoconfigured by enabling 'O' bit only (default for 'M' stays FA=
LSE). If enterprises don't use DHCPv6 for autoconfiguration (DHCPv6 is disab=
led), 'O' bit should be set to FALSE.
>=20
> Thanks,
> Dusan.
>=20
>> -----Original Message-----
>> From: STARK, BARBARA H <bs7652@att.com>
>> Sent: Tuesday, September 04, 2018 4:35 PM
>> To: Mudric, Dusan (Dusan) <dmudric@avaya.com>; Simon Hobson
>> <linux@thehobsons.co.uk>; v6ops@ietf.org
>> Subject: RE: [v6ops] Thinking about problems in IPv6-only networks
>>=20
>>>> It's arguable that a host using DHCP when the RAs say not to is in the
>>> wrong.
>>>=20
>>> Agree. But if 'O' bit is not supported on hosts, hosts should have DHCPv=
6
>>> enabled by default. There are millions of IPv4 phones that use DHCPv4 fo=
r
>>> autoconfiguration (for phone applications), for example. When they
>> migrate
>>> to IPv6, they should get the configuration from DHCPv6 server. DHCPv6
>>> should not be disabled by default when migrating those phone to IPv6.
>> That
>>> is why I think 'O' should be TRUE by default, so the phone applications c=
an
>> be
>>> automatically configured by DHCPv6 server. By default, phones can use
>>> SLAAC to get the addresses.
>>=20
>> Hi Dusan,
>>=20
>> There are millions of hosts with no DHCPv6 support. This is the case and w=
ill
>> continue to be the case. Hosts that do not support DHCPv6 client will
>> *never* have DHCPv6 enabled by default, or otherwise. Networks that are
>> primarily intended for these sorts of devices will rarely (if ever) have D=
HCPv6
>> enabled.
>>=20
>> As for the millions of IPv4 phones -- these millions of phones are not
>> connecting directly to DSL/DOCSIS/PON/3GPP access networks. They are not
>> connecting to (unmanaged) home networks and getting configuration by
>> DHCPv4. They are not connecting directly to data center networks. They're=

>> definitely not connecting directly to core network routers. They *are*
>> connecting to enterprise networks. Suggesting that all routers, in every u=
se
>> case and every scenario, must always support DHCPv6 server and provide
>> stateless configuration, just because there exist some devices in specifi=
c use
>> cases that require configuration info from DHCP, isn't reasonable.
>>=20
>> If you want this specifically for enterprise routers, then perhaps you sh=
ould
>> be commenting on draft-ietf-v6ops-ipv6rtr-reqs. Note that this draft does=

>> require DHCPv6 support (Section 3.3, first bullet) for the routers it des=
cribes
>> (see Section 1.3 on Use and Applicability).
>> Barbara
>>=20
>> I
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Wed Sep  5 07:14:28 2018
Return-Path: <twinters@iol.unh.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2591A130E6E for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 07:14:20 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 Fw3MdCv2rmyV for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 07:14:15 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 E3301130E85 for <v6ops@ietf.org>; Wed,  5 Sep 2018 07:14:14 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id v90-v6so7889004wrc.0 for <v6ops@ietf.org>; Wed, 05 Sep 2018 07:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=19YmBzCj+4dl9kKVsTBQzlw29TogzjjSYvSzgs1H8KQ=; b=KiJf2oChGFrsBY2cA6rpzGo6WNqUY0RzP/6OlimfpHK+uJPQ/K2jZ3JcVq90Pl5m3E 5vQ8/hd9/IIigYMqSI0VSWW/CzcfcNDnDKaFL8DqniVnBEp5+W0s+zzeTwK636jbc2mQ 2Gb8AJzFK2ceydxakSmrmMMYlBB9JCiMVqA5M=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=19YmBzCj+4dl9kKVsTBQzlw29TogzjjSYvSzgs1H8KQ=; b=aynak9iO4rioy4tXaPBTxAuh7v5D5XCygpp+SFgt9kbPJ8dDtIATOtgaTBszDfPafm CjzUoGboiZUibqIhigMu2sSTg5wWlcdyzZaqpIvaCS6odBVD9B2BaEmyl65fk9Qr/lpL q1Mv5jK3nEPttWHtD6zy57E4CL9VxH+zadlajYMcMGomMG5mzowVaOdopJwyBNW2FTdC p79d+bg9v/+xNwbBFo7p3Wp81S3ZTzBviu/gv84h/aMnhEf2FoIy7/xNbZqiiblG+7NY 81abd4Z2IOiB+F5Lrq8FVlB09nVUCOW3IxsLrB1geA2vUepY7WOU6VCJbnVNehGIbbu3 qPOg==
X-Gm-Message-State: APzg51B1MCAUkfyjq0snBaeDRh4bHAiUmGA+mGVfNd2Uzta0rOADpCR7 4geQyMwR5FZy00ooKXD8RyXP5HUuiuOz9xh+R+q7HA==
X-Google-Smtp-Source: ANB0VdYgTbrQEKKWfJwZZkrElpLcJDv1FEFqGgGxRBLJTz1pebmIfJ5FkLDU0qN9O5tSAcBbSn5LKZSHeDHBBOWDR60=
X-Received: by 2002:adf:b2b5:: with SMTP id g50-v6mr25432161wrd.218.1536156853185;  Wed, 05 Sep 2018 07:14:13 -0700 (PDT)
MIME-Version: 1.0
References: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com> <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com>
In-Reply-To: <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Wed, 5 Sep 2018 10:14:00 -0400
Message-ID: <CAOSSMjU83++zqMp8bwmoZExKfxn1Eow3-WWkd3E80oToY1cPZQ@mail.gmail.com>
To: owen@delong.com
Cc: dmudric@avaya.com, Simon Hobson <linux@thehobsons.co.uk>,  IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008dde6805752063e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PQznjUXc0HJUsNPVZUzAj9jt5uc>
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 14:14:27 -0000

--0000000000008dde6805752063e6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I would also mention that IPv6 nodes requirements (
https://tools.ietf.org/html/draft-ietf-6man-rfc6434-bis-09) updates have
DHCPv6 is a SHOULD in all IPv6 nodes.

~Tim

On Wed, Sep 5, 2018 at 10:09 AM Owen DeLong <owen@delong.com> wrote:

> You are continuing to confuse implementation and operation requirements.
> You are also ignoring reality...
>
> There=E2=80=99s no way for a router to know whether it is deployed in an
> enterprise environment or not at time of manufacture.
>
> Further, I don=E2=80=99t believe for one second that ALL enterprises will=
 require
> or use DHCPv6. Perhaps most, but certainly not all.
>
> The current situation is that implementation of DHCPv6 in the protocol
> stack on ANY device is optional. There is a proposal to make it mandatory
> on routers only. There is no proposal that I know of to make it mandatory
> on hosts. Any such proposal would be a major change to IPv6 architecture
> that I am certain would face substantial opposition.
>
> Therefore there is no conflict between the ID you referenced and the RFC
> you referenced. Your proposed change to the RFC would be nonsensical abse=
nt
> an across the board requirement for DHCPv6 implementation in all protocol
> stacks. That=E2=80=99s not likely to happen, nor is DHCPv6 support in And=
roid based
> phones.
>
> Since a router can=E2=80=99t know at manufacture time whether it is deplo=
yed in an
> enterprise or not, and since it is not universally true that enterprises
> will want DHCPv6, it is impossible to set M and O defaults in the manner
> you propose.
>
> The good news is that it=E2=80=99s also utterly unnecessary to do so.
>
> Owen
>
>
> > On Sep 5, 2018, at 06:36, Mudric, Dusan (Dusan) <dmudric@avaya.com>
> wrote:
> >
> > Hi Barbara,
> >
> >> As for the millions of IPv4 phones -- these millions of phones are not
> >> connecting directly to DSL/DOCSIS/PON/3GPP access networks. They are n=
ot
> >> connecting to (unmanaged) home networks and getting configuration by
> >> DHCPv4. They are not connecting directly to data center networks.
> They're
> >> definitely not connecting directly to core network routers. They *are*
> >> connecting to enterprise networks. Suggesting that all routers, in
> every use
> >> case and every scenario, must always support DHCPv6 server and provide
> >> stateless configuration, just because there exist some devices in
> specific use
> >> cases that require configuration info from DHCP, isn't reasonable.
> >>
> >> If you want this specifically for enterprise routers, then perhaps you
> should
> >> be commenting on draft-ietf-v6ops-ipv6rtr-reqs. Note that this draft
> does
> >> require DHCPv6 support (Section 3.3, first bullet) for the routers it
> describes
> >> (see Section 1.3 on Use and Applicability).
> >
> > Good point. I am talking about the phones in enterprise environments.
> >
> > It is not clear what the current consensus is:
> > https://tools.ietf.org/html/draft-ietf-v6ops-ipv6rtr-reqs-04#section-3.=
3
> :
> >
> > DHCPv6 is mandatory:
> >   o  [I-D.ietf-dhc-rfc3315bis]: Dynamic Configuration Protocol for IPv6
> >      must be supported.
> >
> > or DHCPv6 is optional:
> >  o  [RFC3646]: DNS Configuration options for Dynamic Host
> >      Configuration Protocol for IPv6 (DHCPv6) if DHCPv6 is supported.
> > Should the last sentence be 'if DHCPv6 is enabled'?
> >
> > May be 'M' and 'O' can be TRUE by default in the enterprise networks, i=
f
> DHCPv6 is enabled. That way the scope of enabled 'M' and 'O' is limited t=
o
> the enterprises that configure their phones using DHCPv6. Since SLAAC mus=
t
> be enabled and the phones can create global SLAAC addresses, the phone
> applications can be autoconfigured by enabling 'O' bit only (default for
> 'M' stays FALSE). If enterprises don't use DHCPv6 for autoconfiguration
> (DHCPv6 is disabled), 'O' bit should be set to FALSE.
> >
> > Thanks,
> > Dusan.
> >
> >> -----Original Message-----
> >> From: STARK, BARBARA H <bs7652@att.com>
> >> Sent: Tuesday, September 04, 2018 4:35 PM
> >> To: Mudric, Dusan (Dusan) <dmudric@avaya.com>; Simon Hobson
> >> <linux@thehobsons.co.uk>; v6ops@ietf.org
> >> Subject: RE: [v6ops] Thinking about problems in IPv6-only networks
> >>
> >>>> It's arguable that a host using DHCP when the RAs say not to is in t=
he
> >>> wrong.
> >>>
> >>> Agree. But if 'O' bit is not supported on hosts, hosts should have
> DHCPv6
> >>> enabled by default. There are millions of IPv4 phones that use DHCPv4
> for
> >>> autoconfiguration (for phone applications), for example. When they
> >> migrate
> >>> to IPv6, they should get the configuration from DHCPv6 server. DHCPv6
> >>> should not be disabled by default when migrating those phone to IPv6.
> >> That
> >>> is why I think 'O' should be TRUE by default, so the phone
> applications can
> >> be
> >>> automatically configured by DHCPv6 server. By default, phones can use
> >>> SLAAC to get the addresses.
> >>
> >> Hi Dusan,
> >>
> >> There are millions of hosts with no DHCPv6 support. This is the case
> and will
> >> continue to be the case. Hosts that do not support DHCPv6 client will
> >> *never* have DHCPv6 enabled by default, or otherwise. Networks that ar=
e
> >> primarily intended for these sorts of devices will rarely (if ever)
> have DHCPv6
> >> enabled.
> >>
> >> As for the millions of IPv4 phones -- these millions of phones are not
> >> connecting directly to DSL/DOCSIS/PON/3GPP access networks. They are n=
ot
> >> connecting to (unmanaged) home networks and getting configuration by
> >> DHCPv4. They are not connecting directly to data center networks.
> They're
> >> definitely not connecting directly to core network routers. They *are*
> >> connecting to enterprise networks. Suggesting that all routers, in
> every use
> >> case and every scenario, must always support DHCPv6 server and provide
> >> stateless configuration, just because there exist some devices in
> specific use
> >> cases that require configuration info from DHCP, isn't reasonable.
> >>
> >> If you want this specifically for enterprise routers, then perhaps you
> should
> >> be commenting on draft-ietf-v6ops-ipv6rtr-reqs. Note that this draft
> does
> >> require DHCPv6 support (Section 3.3, first bullet) for the routers it
> describes
> >> (see Section 1.3 on Use and Applicability).
> >> Barbara
> >>
> >> I
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--0000000000008dde6805752063e6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">I would also mention that IPv6 nodes requ=
irements (<a href=3D"https://tools.ietf.org/html/draft-ietf-6man-rfc6434-bi=
s-09">https://tools.ietf.org/html/draft-ietf-6man-rfc6434-bis-09</a>) updat=
es have DHCPv6 is a SHOULD in all IPv6 nodes.</div><div dir=3D"ltr"><div><b=
r></div><div>~Tim</div></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr">On Wed, Sep 5, 2018 at 10:09 AM Owen DeLong &lt;<a href=3D"mailto:=
owen@delong.com">owen@delong.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">You are continuing to confuse implementation and operation re=
quirements. You are also ignoring reality...<br>
<br>
There=E2=80=99s no way for a router to know whether it is deployed in an en=
terprise environment or not at time of manufacture. <br>
<br>
Further, I don=E2=80=99t believe for one second that ALL enterprises will r=
equire or use DHCPv6. Perhaps most, but certainly not all. <br>
<br>
The current situation is that implementation of DHCPv6 in the protocol stac=
k on ANY device is optional. There is a proposal to make it mandatory on ro=
uters only. There is no proposal that I know of to make it mandatory on hos=
ts. Any such proposal would be a major change to IPv6 architecture that I a=
m certain would face substantial opposition. <br>
<br>
Therefore there is no conflict between the ID you referenced and the RFC yo=
u referenced. Your proposed change to the RFC would be nonsensical absent a=
n across the board requirement for DHCPv6 implementation in all protocol st=
acks. That=E2=80=99s not likely to happen, nor is DHCPv6 support in Android=
 based phones. <br>
<br>
Since a router can=E2=80=99t know at manufacture time whether it is deploye=
d in an enterprise or not, and since it is not universally true that enterp=
rises will want DHCPv6, it is impossible to set M and O defaults in the man=
ner you propose.<br>
<br>
The good news is that it=E2=80=99s also utterly unnecessary to do so. <br>
<br>
Owen<br>
<br>
<br>
&gt; On Sep 5, 2018, at 06:36, Mudric, Dusan (Dusan) &lt;<a href=3D"mailto:=
dmudric@avaya.com" target=3D"_blank">dmudric@avaya.com</a>&gt; wrote:<br>
&gt; <br>
&gt; Hi Barbara,<br>
&gt; <br>
&gt;&gt; As for the millions of IPv4 phones -- these millions of phones are=
 not<br>
&gt;&gt; connecting directly to DSL/DOCSIS/PON/3GPP access networks. They a=
re not<br>
&gt;&gt; connecting to (unmanaged) home networks and getting configuration =
by<br>
&gt;&gt; DHCPv4. They are not connecting directly to data center networks. =
They&#39;re<br>
&gt;&gt; definitely not connecting directly to core network routers. They *=
are*<br>
&gt;&gt; connecting to enterprise networks. Suggesting that all routers, in=
 every use<br>
&gt;&gt; case and every scenario, must always support DHCPv6 server and pro=
vide<br>
&gt;&gt; stateless configuration, just because there exist some devices in =
specific use<br>
&gt;&gt; cases that require configuration info from DHCP, isn&#39;t reasona=
ble.<br>
&gt;&gt; <br>
&gt;&gt; If you want this specifically for enterprise routers, then perhaps=
 you should<br>
&gt;&gt; be commenting on draft-ietf-v6ops-ipv6rtr-reqs. Note that this dra=
ft does<br>
&gt;&gt; require DHCPv6 support (Section 3.3, first bullet) for the routers=
 it describes<br>
&gt;&gt; (see Section 1.3 on Use and Applicability).<br>
&gt; <br>
&gt; Good point. I am talking about the phones in enterprise environments. =
<br>
&gt; <br>
&gt; It is not clear what the current consensus is:<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-v6ops-ipv6rtr-reqs-0=
4#section-3.3" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/=
html/draft-ietf-v6ops-ipv6rtr-reqs-04#section-3.3</a>=C2=A0 :<br>
&gt; <br>
&gt; DHCPv6 is mandatory:<br>
&gt;=C2=A0 =C2=A0o=C2=A0 [I-D.ietf-dhc-rfc3315bis]: Dynamic Configuration P=
rotocol for IPv6<br>
&gt;=C2=A0 =C2=A0 =C2=A0 must be supported.<br>
&gt; <br>
&gt; or DHCPv6 is optional:=C2=A0 <br>
&gt;=C2=A0 o=C2=A0 [RFC3646]: DNS Configuration options for Dynamic Host<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0 Configuration Protocol for IPv6 (DHCPv6) if DHCPv6=
 is supported.<br>
&gt; Should the last sentence be &#39;if DHCPv6 is enabled&#39;?<br>
&gt; <br>
&gt; May be &#39;M&#39; and &#39;O&#39; can be TRUE by default in the enter=
prise networks, if DHCPv6 is enabled. That way the scope of enabled &#39;M&=
#39; and &#39;O&#39; is limited to the enterprises that configure their pho=
nes using DHCPv6. Since SLAAC must be enabled and the phones can create glo=
bal SLAAC addresses, the phone applications can be autoconfigured by enabli=
ng &#39;O&#39; bit only (default for &#39;M&#39; stays FALSE). If enterpris=
es don&#39;t use DHCPv6 for autoconfiguration (DHCPv6 is disabled), &#39;O&=
#39; bit should be set to FALSE.<br>
&gt; <br>
&gt; Thanks,<br>
&gt; Dusan.<br>
&gt; <br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: STARK, BARBARA H &lt;<a href=3D"mailto:bs7652@att.com" targe=
t=3D"_blank">bs7652@att.com</a>&gt;<br>
&gt;&gt; Sent: Tuesday, September 04, 2018 4:35 PM<br>
&gt;&gt; To: Mudric, Dusan (Dusan) &lt;<a href=3D"mailto:dmudric@avaya.com"=
 target=3D"_blank">dmudric@avaya.com</a>&gt;; Simon Hobson<br>
&gt;&gt; &lt;<a href=3D"mailto:linux@thehobsons.co.uk" target=3D"_blank">li=
nux@thehobsons.co.uk</a>&gt;; <a href=3D"mailto:v6ops@ietf.org" target=3D"_=
blank">v6ops@ietf.org</a><br>
&gt;&gt; Subject: RE: [v6ops] Thinking about problems in IPv6-only networks=
<br>
&gt;&gt; <br>
&gt;&gt;&gt;&gt; It&#39;s arguable that a host using DHCP when the RAs say =
not to is in the<br>
&gt;&gt;&gt; wrong.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Agree. But if &#39;O&#39; bit is not supported on hosts, hosts=
 should have DHCPv6<br>
&gt;&gt;&gt; enabled by default. There are millions of IPv4 phones that use=
 DHCPv4 for<br>
&gt;&gt;&gt; autoconfiguration (for phone applications), for example. When =
they<br>
&gt;&gt; migrate<br>
&gt;&gt;&gt; to IPv6, they should get the configuration from DHCPv6 server.=
 DHCPv6<br>
&gt;&gt;&gt; should not be disabled by default when migrating those phone t=
o IPv6.<br>
&gt;&gt; That<br>
&gt;&gt;&gt; is why I think &#39;O&#39; should be TRUE by default, so the p=
hone applications can<br>
&gt;&gt; be<br>
&gt;&gt;&gt; automatically configured by DHCPv6 server. By default, phones =
can use<br>
&gt;&gt;&gt; SLAAC to get the addresses.<br>
&gt;&gt; <br>
&gt;&gt; Hi Dusan,<br>
&gt;&gt; <br>
&gt;&gt; There are millions of hosts with no DHCPv6 support. This is the ca=
se and will<br>
&gt;&gt; continue to be the case. Hosts that do not support DHCPv6 client w=
ill<br>
&gt;&gt; *never* have DHCPv6 enabled by default, or otherwise. Networks tha=
t are<br>
&gt;&gt; primarily intended for these sorts of devices will rarely (if ever=
) have DHCPv6<br>
&gt;&gt; enabled.<br>
&gt;&gt; <br>
&gt;&gt; As for the millions of IPv4 phones -- these millions of phones are=
 not<br>
&gt;&gt; connecting directly to DSL/DOCSIS/PON/3GPP access networks. They a=
re not<br>
&gt;&gt; connecting to (unmanaged) home networks and getting configuration =
by<br>
&gt;&gt; DHCPv4. They are not connecting directly to data center networks. =
They&#39;re<br>
&gt;&gt; definitely not connecting directly to core network routers. They *=
are*<br>
&gt;&gt; connecting to enterprise networks. Suggesting that all routers, in=
 every use<br>
&gt;&gt; case and every scenario, must always support DHCPv6 server and pro=
vide<br>
&gt;&gt; stateless configuration, just because there exist some devices in =
specific use<br>
&gt;&gt; cases that require configuration info from DHCP, isn&#39;t reasona=
ble.<br>
&gt;&gt; <br>
&gt;&gt; If you want this specifically for enterprise routers, then perhaps=
 you should<br>
&gt;&gt; be commenting on draft-ietf-v6ops-ipv6rtr-reqs. Note that this dra=
ft does<br>
&gt;&gt; require DHCPv6 support (Section 3.3, first bullet) for the routers=
 it describes<br>
&gt;&gt; (see Section 1.3 on Use and Applicability).<br>
&gt;&gt; Barbara<br>
&gt;&gt; <br>
&gt;&gt; I<br>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div>

--0000000000008dde6805752063e6--


From nobody Wed Sep  5 07:53:34 2018
Return-Path: <bs7652@att.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D17B1130EA6 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 07:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 60oKulpTPczZ for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 07:53:23 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 6D6D5130EA2 for <v6ops@ietf.org>; Wed,  5 Sep 2018 07:53:22 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w85Ek0mA029125; Wed, 5 Sep 2018 10:53:19 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049295.ppops.net-00191d01. with ESMTP id 2maf0fcyfr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 05 Sep 2018 10:53:18 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w85ErHPo022207; Wed, 5 Sep 2018 10:53:17 -0400
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [135.47.91.179]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w85ErCdu022052; Wed, 5 Sep 2018 10:53:12 -0400
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [127.0.0.1]) by zlp30484.vci.att.com (Service) with ESMTP id E7DF2404C951; Wed,  5 Sep 2018 14:53:12 +0000 (GMT)
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (unknown [130.8.218.154]) by zlp30484.vci.att.com (Service) with ESMTPS id D042E4000378; Wed,  5 Sep 2018 14:53:12 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.179]) by GAALPA1MSGHUBAE.ITServices.sbc.com ([130.8.218.154]) with mapi id 14.03.0415.000; Wed, 5 Sep 2018 10:53:12 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Mudric, Dusan (Dusan)'" <dmudric@avaya.com>, Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
Thread-Index: AdRFHWOZHHYbWX1OT62jFlEWmsFm5wABFKIQ
Date: Wed, 5 Sep 2018 14:53:11 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DE94EE3@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com>
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.61.166.227]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-05_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809050155
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dqZpzHc301GMTzmY3JcIfE2aO98>
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 14:53:32 -0000

SGkgRHVzYW4sDQpUaGFua3MgZm9yIGNoYW5naW5nIHRoZSBzdWJqZWN0IGxpbmUgc28gZHJhZnQt
aWV0Zi12Nm9wcy1pcHY2cnRyLXJlcXMtMDQgYXV0aG9ycyBhcmUgYWxlcnRlZCB0byBjb21tZW50
cyBvbiB0aGVpciBkcmFmdC4NCk1vcmUgY29tbWVudHMgaW4tbGluZS4NCkJhcmJhcmENCg0KPiBI
aSBCYXJiYXJhLA0KPg0KPiA+IEFzIGZvciB0aGUgbWlsbGlvbnMgb2YgSVB2NCBwaG9uZXMgLS0g
dGhlc2UgbWlsbGlvbnMgb2YgcGhvbmVzIGFyZSBub3QNCj4gPiBjb25uZWN0aW5nIGRpcmVjdGx5
IHRvIERTTC9ET0NTSVMvUE9OLzNHUFAgYWNjZXNzIG5ldHdvcmtzLiBUaGV5IGFyZQ0KPiBub3QN
Cj4gPiBjb25uZWN0aW5nIHRvICh1bm1hbmFnZWQpIGhvbWUgbmV0d29ya3MgYW5kIGdldHRpbmcg
Y29uZmlndXJhdGlvbiBieQ0KPiA+IERIQ1B2NC4gVGhleSBhcmUgbm90IGNvbm5lY3RpbmcgZGly
ZWN0bHkgdG8gZGF0YSBjZW50ZXIgbmV0d29ya3MuIFRoZXkncmUNCj4gPiBkZWZpbml0ZWx5IG5v
dCBjb25uZWN0aW5nIGRpcmVjdGx5IHRvIGNvcmUgbmV0d29yayByb3V0ZXJzLiBUaGV5ICphcmUq
DQo+ID4gY29ubmVjdGluZyB0byBlbnRlcnByaXNlIG5ldHdvcmtzLiBTdWdnZXN0aW5nIHRoYXQg
YWxsIHJvdXRlcnMsIGluIGV2ZXJ5IHVzZQ0KPiA+IGNhc2UgYW5kIGV2ZXJ5IHNjZW5hcmlvLCBt
dXN0IGFsd2F5cyBzdXBwb3J0IERIQ1B2NiBzZXJ2ZXIgYW5kIHByb3ZpZGUNCj4gPiBzdGF0ZWxl
c3MgY29uZmlndXJhdGlvbiwganVzdCBiZWNhdXNlIHRoZXJlIGV4aXN0IHNvbWUgZGV2aWNlcyBp
biBzcGVjaWZpYw0KPiB1c2UNCj4gPiBjYXNlcyB0aGF0IHJlcXVpcmUgY29uZmlndXJhdGlvbiBp
bmZvIGZyb20gREhDUCwgaXNuJ3QgcmVhc29uYWJsZS4NCj4gPg0KPiA+IElmIHlvdSB3YW50IHRo
aXMgc3BlY2lmaWNhbGx5IGZvciBlbnRlcnByaXNlIHJvdXRlcnMsIHRoZW4gcGVyaGFwcyB5b3Ug
c2hvdWxkDQo+ID4gYmUgY29tbWVudGluZyBvbiBkcmFmdC1pZXRmLXY2b3BzLWlwdjZydHItcmVx
cy4gTm90ZSB0aGF0IHRoaXMgZHJhZnQgZG9lcw0KPiA+IHJlcXVpcmUgREhDUHY2IHN1cHBvcnQg
KFNlY3Rpb24gMy4zLCBmaXJzdCBidWxsZXQpIGZvciB0aGUgcm91dGVycyBpdA0KPiBkZXNjcmli
ZXMNCj4gPiAoc2VlIFNlY3Rpb24gMS4zIG9uIFVzZSBhbmQgQXBwbGljYWJpbGl0eSkuDQo+IA0K
PiBHb29kIHBvaW50LiBJIGFtIHRhbGtpbmcgYWJvdXQgdGhlIHBob25lcyBpbiBlbnRlcnByaXNl
IGVudmlyb25tZW50cy4NCj4gDQo+IEl0IGlzIG5vdCBjbGVhciB3aGF0IHRoZSBjdXJyZW50IGNv
bnNlbnN1cyBpczoNCj4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtdjZv
cHMtaXB2NnJ0ci1yZXFzLTA0I3NlY3Rpb24tMy4zICANCj4gREhDUHY2IGlzIG1hbmRhdG9yeToN
Cj4gICAgbyAgW0ktRC5pZXRmLWRoYy1yZmMzMzE1YmlzXTogRHluYW1pYyBDb25maWd1cmF0aW9u
IFByb3RvY29sIGZvciBJUHY2DQo+ICAgICAgIG11c3QgYmUgc3VwcG9ydGVkLg0KPiANCj4gb3Ig
REhDUHY2IGlzIG9wdGlvbmFsOg0KPiAgIG8gIFtSRkMzNjQ2XTogRE5TIENvbmZpZ3VyYXRpb24g
b3B0aW9ucyBmb3IgRHluYW1pYyBIb3N0DQo+ICAgICAgIENvbmZpZ3VyYXRpb24gUHJvdG9jb2wg
Zm9yIElQdjYgKERIQ1B2NikgaWYgREhDUHY2IGlzIHN1cHBvcnRlZC4NCj4gDQo+IFNob3VsZCB0
aGUgbGFzdCBzZW50ZW5jZSBiZSAnaWYgREhDUHY2IGlzIGVuYWJsZWQnPw0KDQpUaGUgZmlyc3Qg
cmVxdWlyZW1lbnQgY2xlYXJseSBtYWtlcyBESENQdjYgc3VwcG9ydCBtYW5kYXRvcnkuIFNvIEkg
YWdyZWUgdGhlICJpZiIgY2xhdXNlIGluIHRoZSBETlMgcmVxdWlyZW1lbnQgaXMgY29uZnVzaW5n
LiBNeSByZWNvbW1lbmRhdGlvbiB0byB0aGUgZHJhZnQgYXV0aG9ycyB3b3VsZCBiZSB0byBkZWxl
dGUgImlmIERIQ1B2NiBpcyBzdXBwb3J0ZWQiIGZyb20gdGhlIEROUyBDb25maWd1cmF0aW9uIHJl
cXVpcmVtZW50LiBUaGlzIGxhbmd1YWdlIGRpc3Bhcml0eSBtYXkgaGF2ZSBjb21lIGFib3V0IGJl
Y2F1c2UgZWFybGllciBkcmFmdHMgbWFkZSBESENQdjYgc3VwcG9ydCBvcHRpb25hbC4gSSBkbyBu
b3QgYmVsaWV2ZSB0aGUgbGFzdCBzZW50ZW5jZSBzaG91bGQgYmUgImlmIERIQ1B2NiBpcyBlbmFi
bGVkIiwgYW5kIGRvbid0IHRoaW5rIHRoYXQgd2FzIHRoZSBpbnRlbnQuDQogDQo+IE1heSBiZSAn
TScgYW5kICdPJyBjYW4gYmUgVFJVRSBieSBkZWZhdWx0IGluIHRoZSBlbnRlcnByaXNlIG5ldHdv
cmtzLCBpZg0KPiBESENQdjYgaXMgZW5hYmxlZC4gVGhhdCB3YXkgdGhlIHNjb3BlIG9mIGVuYWJs
ZWQgJ00nIGFuZCAnTycgaXMgbGltaXRlZCB0bw0KPiB0aGUgZW50ZXJwcmlzZXMgdGhhdCBjb25m
aWd1cmUgdGhlaXIgcGhvbmVzIHVzaW5nIERIQ1B2Ni4gU2luY2UgU0xBQUMgbXVzdA0KPiBiZSBl
bmFibGVkIGFuZCB0aGUgcGhvbmVzIGNhbiBjcmVhdGUgZ2xvYmFsIFNMQUFDIGFkZHJlc3Nlcywg
dGhlIHBob25lDQo+IGFwcGxpY2F0aW9ucyBjYW4gYmUgYXV0b2NvbmZpZ3VyZWQgYnkgZW5hYmxp
bmcgJ08nIGJpdCBvbmx5IChkZWZhdWx0IGZvciAnTScNCj4gc3RheXMgRkFMU0UpLiBJZiBlbnRl
cnByaXNlcyBkb24ndCB1c2UgREhDUHY2IGZvciBhdXRvY29uZmlndXJhdGlvbiAoREhDUHY2DQo+
IGlzIGRpc2FibGVkKSwgJ08nIGJpdCBzaG91bGQgYmUgc2V0IHRvIEZBTFNFLg0KDQpTaW5jZSBl
bmFibGluZyBESENQdjYgYW5kIHByb3ZpZGluZyBESENQdjYgRE5TIG9wdGlvbnMgKGFuZCBTSVAg
Y29uZmlndXJhdGlvbiBvcHRpb25zKSByZXF1aXJlcyBhY3RpdmUgY29uZmlndXJhdGlvbiBpbiBt
YW55IGVudGVycHJpc2UgZW52aXJvbm1lbnRzIChlc3BlY2lhbGx5IG9mIHRoZSBzdHJpbmdzIHRv
IGluY2x1ZGUgaW4gdGhvc2Ugb3B0aW9ucyksIEkgdGhpbmsgaXQgd291bGQgYmUgaGlnaGx5IGlu
YXBwcm9wcmlhdGUgdG8gcmVjb21tZW5kIHJvdXRlcnMgc2V0IGVpdGhlciBNIG9yIE8gdG8gMSBi
eSBkZWZhdWx0LiBFbnRlcnByaXNlIG5ldHdvcmsgYWRtaW5pc3RyYXRvcnMgbmVlZCB0byBiZSBl
eHBlY3RlZCB0byBkbyB0aGVpciBqb2JzIGFuZCBwcm9wZXJseSBhZG1pbmlzdGVyIChhbmQgY29u
ZmlndXJlKSB0aGVpciBuZXR3b3Jrcy4gV2UgbmVlZCB0byBtYWtlIHN1cmUgdGhlIGVxdWlwbWVu
dCB0aGV5IGdldCBwcm92aWRlcyB0aGVtIHdpdGggdGhlIHRvb2xzIChpLmUuLCBpbmNsdWRlcyB0
aGUgbmVlZGVkIGZ1bmN0aW9uYWxpdHkpLiANCg0KSWYgeW91IHdhbnRlZCB0byBzdWdnZXN0IHRo
YXQgImEgcm91dGVyIHdpdGggUkEgZW5hYmxlZCBNQVkgYXV0b21hdGljYWxseSBzZXQgTz0xIHdo
ZW4gREhDUHY2IGlzIGVuYWJsZWQgKG9uIHRoZSBzYW1lIHJvdXRlcikgd2l0aCBhdCBsZWFzdCBv
bmUgbm9uLWFkZHJlc3MtYXNzaWdubWVudCBvcHRpb24iLCB0aGF0IG1pZ2h0IHdvcmsuIEJ1dCB3
aGVyZSB0aGUgcm91dGVyIGRvaW5nIFJBIGhhcyBubyBrbm93bGVkZ2Ugb2YgdGhlIGV4aXN0ZW5j
ZSBvZiBhbnkgZW5hYmxlZCBESENQdjYgc2VydmVyLCBpdCB3b3VsZCBiZSBoaWdobHkgaW5hcHBy
b3ByaWF0ZSBmb3IgTSBvciBPIHRvIGJlIGRlZmF1bHRlZCB0byBhbnkgdmFsdWUgb3RoZXIgdGhh
biB6ZXJvLiBUaGUgZW50ZXJwcmlzZSBuZXR3b3JrIGFkbWluaXN0cmF0b3IgbmVlZHMgdG8gYmUg
ZXhwZWN0ZWQgdG8gaGF2ZSBzb21lIHVuZGVyc3RhbmRpbmcgb2YgUkEgTSBhbmQgTyBiaXRzIGlm
IHRoZXkgYXJlIGRlcGxveWluZyBJUHY2IGluIHRoZWlyIG5ldHdvcmsuIEl0IHdvdWxkIGFsc28g
YmUgZ29vZCBpZiB0aGV5IGtuZXcgd2hldGhlciB0aGVpciAiSVB2NCBwaG9uZXMiIGFsc28gc3Vw
cG9ydGVkIElQdjYgYmVmb3JlIGV4cGVjdGluZyB0aGVzZSBwaG9uZXMgdG8gZ2V0IGFueSBjb25m
aWd1cmF0aW9uIGluZm9ybWF0aW9uLCB3aGF0c29ldmVyLCBmcm9tIFJBIG9yIERIQ1B2Ni4NCg0K
PiBUaGFua3MsDQo+IA0KPiBEdXNhbi4NCj4gDQo+IA0KPiANCj4gPiAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPiANCj4gPiBGcm9tOiBTVEFSSywgQkFSQkFSQSBIIDxiczc2NTJAYXR0LmNv
bT4NCj4gDQo+ID4gU2VudDogVHVlc2RheSwgU2VwdGVtYmVyIDA0LCAyMDE4IDQ6MzUgUE0NCj4g
DQo+ID4gVG86IE11ZHJpYywgRHVzYW4gKER1c2FuKSA8ZG11ZHJpY0BhdmF5YS5jb20+OyBTaW1v
biBIb2Jzb24NCj4gDQo+ID4gPGxpbnV4QHRoZWhvYnNvbnMuY28udWs+OyB2Nm9wc0BpZXRmLm9y
Zw0KPiANCj4gPiBTdWJqZWN0OiBSRTogW3Y2b3BzXSBUaGlua2luZyBhYm91dCBwcm9ibGVtcyBp
biBJUHY2LW9ubHkgbmV0d29ya3MNCj4gDQo+ID4NCj4gDQo+ID4gPiA+IEl0J3MgYXJndWFibGUg
dGhhdCBhIGhvc3QgdXNpbmcgREhDUCB3aGVuIHRoZSBSQXMgc2F5IG5vdCB0byBpcyBpbiB0aGUN
Cj4gDQo+ID4gPiB3cm9uZy4NCj4gDQo+ID4gPg0KPiANCj4gPiA+IEFncmVlLiBCdXQgaWYgJ08n
IGJpdCBpcyBub3Qgc3VwcG9ydGVkIG9uIGhvc3RzLCBob3N0cyBzaG91bGQgaGF2ZSBESENQdjYN
Cj4gDQo+ID4gPiBlbmFibGVkIGJ5IGRlZmF1bHQuIFRoZXJlIGFyZSBtaWxsaW9ucyBvZiBJUHY0
IHBob25lcyB0aGF0IHVzZSBESENQdjQNCj4gZm9yDQo+IA0KPiA+ID4gYXV0b2NvbmZpZ3VyYXRp
b24gKGZvciBwaG9uZSBhcHBsaWNhdGlvbnMpLCBmb3IgZXhhbXBsZS4gV2hlbiB0aGV5DQo+IA0K
PiA+IG1pZ3JhdGUNCj4gDQo+ID4gPiB0byBJUHY2LCB0aGV5IHNob3VsZCBnZXQgdGhlIGNvbmZp
Z3VyYXRpb24gZnJvbSBESENQdjYgc2VydmVyLiBESENQdjYNCj4gDQo+ID4gPiBzaG91bGQgbm90
IGJlIGRpc2FibGVkIGJ5IGRlZmF1bHQgd2hlbiBtaWdyYXRpbmcgdGhvc2UgcGhvbmUgdG8gSVB2
Ni4NCj4gDQo+ID4gVGhhdA0KPiANCj4gPiA+IGlzIHdoeSBJIHRoaW5rICdPJyBzaG91bGQgYmUg
VFJVRSBieSBkZWZhdWx0LCBzbyB0aGUgcGhvbmUgYXBwbGljYXRpb25zIGNhbg0KPiANCj4gPiBi
ZQ0KPiANCj4gPiA+IGF1dG9tYXRpY2FsbHkgY29uZmlndXJlZCBieSBESENQdjYgc2VydmVyLiBC
eSBkZWZhdWx0LCBwaG9uZXMgY2FuIHVzZQ0KPiANCj4gPiA+IFNMQUFDIHRvIGdldCB0aGUgYWRk
cmVzc2VzLg0KPiANCj4gPg0KPiANCj4gPiBIaSBEdXNhbiwNCj4gDQo+ID4NCj4gDQo+ID4gVGhl
cmUgYXJlIG1pbGxpb25zIG9mIGhvc3RzIHdpdGggbm8gREhDUHY2IHN1cHBvcnQuIFRoaXMgaXMg
dGhlIGNhc2UgYW5kIHdpbGwNCj4gDQo+ID4gY29udGludWUgdG8gYmUgdGhlIGNhc2UuIEhvc3Rz
IHRoYXQgZG8gbm90IHN1cHBvcnQgREhDUHY2IGNsaWVudCB3aWxsDQo+IA0KPiA+ICpuZXZlciog
aGF2ZSBESENQdjYgZW5hYmxlZCBieSBkZWZhdWx0LCBvciBvdGhlcndpc2UuIE5ldHdvcmtzIHRo
YXQgYXJlDQo+IA0KPiA+IHByaW1hcmlseSBpbnRlbmRlZCBmb3IgdGhlc2Ugc29ydHMgb2YgZGV2
aWNlcyB3aWxsIHJhcmVseSAoaWYgZXZlcikgaGF2ZQ0KPiBESENQdjYNCj4gDQo+ID4gZW5hYmxl
ZC4NCj4gDQo+ID4NCj4gDQo+ID4gQXMgZm9yIHRoZSBtaWxsaW9ucyBvZiBJUHY0IHBob25lcyAt
LSB0aGVzZSBtaWxsaW9ucyBvZiBwaG9uZXMgYXJlIG5vdA0KPiANCj4gPiBjb25uZWN0aW5nIGRp
cmVjdGx5IHRvIERTTC9ET0NTSVMvUE9OLzNHUFAgYWNjZXNzIG5ldHdvcmtzLiBUaGV5IGFyZQ0K
PiBub3QNCj4gDQo+ID4gY29ubmVjdGluZyB0byAodW5tYW5hZ2VkKSBob21lIG5ldHdvcmtzIGFu
ZCBnZXR0aW5nIGNvbmZpZ3VyYXRpb24gYnkNCj4gDQo+ID4gREhDUHY0LiBUaGV5IGFyZSBub3Qg
Y29ubmVjdGluZyBkaXJlY3RseSB0byBkYXRhIGNlbnRlciBuZXR3b3Jrcy4gVGhleSdyZQ0KPiAN
Cj4gPiBkZWZpbml0ZWx5IG5vdCBjb25uZWN0aW5nIGRpcmVjdGx5IHRvIGNvcmUgbmV0d29yayBy
b3V0ZXJzLiBUaGV5ICphcmUqDQo+IA0KPiA+IGNvbm5lY3RpbmcgdG8gZW50ZXJwcmlzZSBuZXR3
b3Jrcy4gU3VnZ2VzdGluZyB0aGF0IGFsbCByb3V0ZXJzLCBpbiBldmVyeSB1c2UNCj4gDQo+ID4g
Y2FzZSBhbmQgZXZlcnkgc2NlbmFyaW8sIG11c3QgYWx3YXlzIHN1cHBvcnQgREhDUHY2IHNlcnZl
ciBhbmQgcHJvdmlkZQ0KPiANCj4gPiBzdGF0ZWxlc3MgY29uZmlndXJhdGlvbiwganVzdCBiZWNh
dXNlIHRoZXJlIGV4aXN0IHNvbWUgZGV2aWNlcyBpbiBzcGVjaWZpYw0KPiB1c2UNCj4gDQo+ID4g
Y2FzZXMgdGhhdCByZXF1aXJlIGNvbmZpZ3VyYXRpb24gaW5mbyBmcm9tIERIQ1AsIGlzbid0IHJl
YXNvbmFibGUuDQo+IA0KPiA+DQo+IA0KPiA+IElmIHlvdSB3YW50IHRoaXMgc3BlY2lmaWNhbGx5
IGZvciBlbnRlcnByaXNlIHJvdXRlcnMsIHRoZW4gcGVyaGFwcyB5b3Ugc2hvdWxkDQo+IA0KPiA+
IGJlIGNvbW1lbnRpbmcgb24gZHJhZnQtaWV0Zi12Nm9wcy1pcHY2cnRyLXJlcXMuIE5vdGUgdGhh
dCB0aGlzIGRyYWZ0IGRvZXMNCj4gDQo+ID4gcmVxdWlyZSBESENQdjYgc3VwcG9ydCAoU2VjdGlv
biAzLjMsIGZpcnN0IGJ1bGxldCkgZm9yIHRoZSByb3V0ZXJzIGl0DQo+IGRlc2NyaWJlcw0KPiAN
Cj4gPiAoc2VlIFNlY3Rpb24gMS4zIG9uIFVzZSBhbmQgQXBwbGljYWJpbGl0eSkuDQo+IA0KPiA+
IEJhcmJhcmENCj4gDQo+ID4NCj4gDQo+ID4gSQ0KDQo=


From nobody Wed Sep  5 08:28:46 2018
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 159AD126CC7 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 08:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 DtmFHvaObGo4 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 08:28:43 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 4E74B1252B7 for <v6ops@ietf.org>; Wed,  5 Sep 2018 08:28:43 -0700 (PDT)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w85FO06r029561 for <v6ops@ietf.org>; Wed, 5 Sep 2018 08:28:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=cnmLveLsDbujNTl3v4JlzZPjUq6f/OU1NPvztSXfFN8=; b=WwWBoRpiNBYCRg3137bFPN7Irvdc24s3aoOeySTSJRMkS1qk4/Pu416hxYKv/jPRnFJ+ ktDjKl/7mmygTYDVzt+4Th6//aqCtXMJAySpS/0o8zo+I1LOywkb4IFHtjSk5PeXK42L Nx9s7Ws3PaWWP8uOb0PiI4SimoEAQeUZkJzbsGa1PPJPuT+awe87RFq0YV74oAxcpfu8 c056AdMazKaozzSg1hOHWGOw2BykZO6hvYGaFCn0EGUyQO3oSMPtiFaQp7uZjTVlzW2+ 4n/SvJXkzh/XtXkvZSVd2KSyH7b5J+TIIMPV+sWqZGaIbbmDwA9GRAOoKtd+uAFpebp6 vA== 
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp0015.outbound.protection.outlook.com [207.46.163.15]) by mx0b-00273201.pphosted.com with ESMTP id 2mab378u3u-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <v6ops@ietf.org>; Wed, 05 Sep 2018 08:28:42 -0700
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by CO1PR05MB411.namprd05.prod.outlook.com (10.141.74.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.1122.9; Wed, 5 Sep 2018 15:28:39 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com ([fe80::990e:3cb2:ad57:cd42]) by CO1PR05MB443.namprd05.prod.outlook.com ([fe80::990e:3cb2:ad57:cd42%18]) with mapi id 15.20.1101.016; Wed, 5 Sep 2018 15:28:39 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: draft-byrne-v6ops-dnssecaaaa 
Thread-Index: AdRFLRaRiSevdVfRR1yuHRNkcg68jg==
Date: Wed, 5 Sep 2018 15:28:39 +0000
Message-ID: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [66.129.241.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO1PR05MB411; 6:TI8xCjPa5kwx5s12E3sNhEWIa+56yjhUqrf+3Gjdhc9McLyPenNsle86E1Nw0q0VvHfG4h8gOuoReBgnzEPHjlOejyKzaOe59gNN+2AaxQDWfubPzcdQTk1gzXjcaFl7xPercNjnvVESxn/euHCVVs4GygBdx06nAwkIMLr7fLIO8w7M111IJcF7LGBwarSb+2cpPYxXBZCreminrGdLXmSaasxJeGuHKhk19ytVFrd/Ctc0zAHiN7UEkJn95wTGsspC/BzUULM6mp4XzTHztEX0zHfFRzjyeBd5NaMNpeFV9tXg1vNWRx9wvhXrwGU1bbFJLhufPjUAot6Oif9/EfFFihH3eXik98gL0bVSJaNBID0ASD/vjdRqc12GG1Whg0iqU7/I1cVf3Ag947RtHYxIXdxASRI3MIrrmQlEnvKk9obiqx18m8Oi4Vn5wJT2mOj4I12t90ADMSlHH6NRbA==; 5:3bdXb7iBDcPwX6wlAcn6CoduuuDtJm2uO0t6QeWKaxQD82lz2B2dVrPwODCSNPAF4e2qsOuNFKXEsK1nLGDdoYO+R4h5m3JK0oNVlQ227ZNELK5WvbpzOKFEZcPSQKbueg47X+X267E7Uy4zIg+HPp7sOi8uuLXSYZh42aBs1+0=; 7:G05hMhpTfQtSKU6N5k3JjmbaCqrnDVWmAbo+JMY+EZ/Zys9cX3IW09G9OKKkIIy57kGCVZPVrV5lwrZNg72kpeTzUrrFN3Pdq/b4UEsy/wQnRnHdT/8I/eiCeyaz9/RbmtnNtyyKxdMec0d6rt7G1pZNJr3XPY4fU8DHwPJ4jbikzJ3C+u+HKFi6duseZbf6yFeqsKPyJA8WU5cIDRFM84fhEz00Q4x5vSnYnni8GiX8Ca6L57dX/3ZLtZcV01jR
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 570a6f82-5bf3-4007-33c6-08d613444154
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:CO1PR05MB411; 
x-ms-traffictypediagnostic: CO1PR05MB411:
x-microsoft-antispam-prvs: <CO1PR05MB4116807A17AC0084DF0CB30AE020@CO1PR05MB411.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231344)(944501410)(52105095)(3002001)(10201501046)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201708071742011)(7699049)(76991033); SRVR:CO1PR05MB411; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB411; 
x-forefront-prvs: 078693968A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(376002)(346002)(366004)(39860400002)(189003)(199004)(2906002)(53936002)(106356001)(105586002)(2900100001)(3846002)(66066001)(68736007)(6116002)(5250100002)(2351001)(6916009)(305945005)(86362001)(99286004)(5660300001)(7696005)(33656002)(8676002)(25786009)(6436002)(97736004)(14454004)(8936002)(7736002)(486006)(476003)(81156014)(81166006)(2501003)(5640700003)(316002)(102836004)(74316002)(6506007)(558084003)(478600001)(256004)(4743002)(9686003)(186003)(26005)(55016002); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB411; H:CO1PR05MB443.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: eWEaKxcqhr8lgChhWttiHYIXdTmIFMjJNf2qUGJ/e/0F9RJKuLT12F6wWl3ROrIdhHkkJEcevNLBnXpkkiM7Q3DWh5Q7lzQS5XkC+OvIV+Oyi/OOeqf/ff1M6Yk4tBa4BVzb+PU2ph7HFNltRWRogzPOR6xGPCvV0IzZaiV45JKFW8IHxaCstjh2KTD4qkNCJtwgzGYc/yNNovHu+ohnwqFiECa5d6SYikRr6PC4EquxyxK5ocF7QADUoWA91SKliZiua0w4Hbeq27pfvVT3dXUfLbu/iR5Rv3CqcUnPnpUTZnklaDGSjh4Wmtkngd+NTr+Jw3xUbHwB9gAuBNgMGUIlzTf3S8uUMZhSm+qODKk=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 570a6f82-5bf3-4007-33c6-08d613444154
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Sep 2018 15:28:39.0963 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB411
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-05_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=369 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809050161
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/sRLpCPSptUrOu7uRfW-B5RTpmjI>
Subject: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 15:28:45 -0000

Folks,

Each week between now and IETF 103, we will review and discuss one draft wi=
th an eye towards progressing it.

This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.

                                      Fred and Ron


From nobody Wed Sep  5 10:53:56 2018
Return-Path: <lencse@hit.bme.hu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E225412426A for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 10:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 qW6giQde3-iF for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 10:52:51 -0700 (PDT)
Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [IPv6:2001:738:2001:4020::2c]) (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 1324B130D7A for <v6ops@ietf.org>; Wed,  5 Sep 2018 10:52:50 -0700 (PDT)
Received: from [192.168.1.134] (host-79-121-42-32.kabelnet.hu [79.121.42.32]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id w85HqdQp019888 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <v6ops@ietf.org>; Wed, 5 Sep 2018 19:52:45 +0200 (CEST) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-42-32.kabelnet.hu [79.121.42.32] claimed to be [192.168.1.134]
To: v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com>
From: =?UTF-8?Q?Lencse_G=c3=a1bor?= <lencse@hit.bme.hu>
Message-ID: <b58d94e7-f724-a5ec-97bc-c4b796a6531e@hit.bme.hu>
Date: Wed, 5 Sep 2018 19:52:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------7DB70DC82A79574769221E38"
X-Virus-Scanned: clamav-milter 0.100.1 at frogstar.hit.bme.hu
X-Virus-Status: Clean
Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.42.32; helo=[192.168.1.134]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; 
X-DCC--Metrics: frogstar.hit.bme.hu; whitelist
X-Scanned-By: MIMEDefang 2.79 on 152.66.248.44
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wGH1EzI3-YPwE4-tBnDNIGw1r3A>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 17:52:56 -0000

This is a multi-part message in MIME format.
--------------7DB70DC82A79574769221E38
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Dear All,

I have read the draft and I agree both with its intention to reconcile 
DNS64 and DNSSEC and also with the recommended solution.

I have found one nit:

    DNS64 is a key part of widely deployed IPv6-only transition mechanism
    such as 464XLAT [RFC6877 <https://tools.ietf.org/html/rfc6877>] and Happy Eyeballs Version 2 [RFC8305 <https://tools.ietf.org/html/rfc8305>].


Maybe I misunderstand something, but I think DNS64 is _not a part of_ 
464XLAT. Of course they can be used together in a sense that:
- native IPv6 clients communicate with native IPv6 servers using native IPv6
- native IPv6 clients communicate with IPv4 only servers using DNS64 + 
stateful NAT64
- IPv4 only applications/clients in an "IPv6 only environment" (where 
only IPv6 is used in the ISP core network) communicate with IPv4 servers 
using 464XLAT
Thus the two solutions (DNS64 and 464XLAT) can complement each other 
well, but DNS64 is not a part of 464XLAT.

Best regards,

Gábor Lencse


9/5/2018 5:28 PM keltezéssel, Ron Bonica írta:
> Folks,
>
> Each week between now and IETF 103, we will review and discuss one draft with an eye towards progressing it.
>
> This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
>
>                                        Fred and Ron
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--------------7DB70DC82A79574769221E38
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear All, <br>
    <br>
    I have read the draft and I agree both with its intention to
    reconcile DNS64 and DNSSEC and also with the recommended solution.<br>
    <br>
    I have found one nit:<br>
    <br>
    <pre class="newpage">   DNS64 is a key part of widely deployed IPv6-only transition mechanism
   such as 464XLAT [<a href="https://tools.ietf.org/html/rfc6877">RFC6877</a>] and Happy Eyeballs Version 2 [<a href="https://tools.ietf.org/html/rfc8305">RFC8305</a>].
</pre>
    <br>
    Maybe I misunderstand something, but I think DNS64 is <u>not a part
      of</u> 464XLAT. Of course they can be used together in a sense
    that:<br>
    - native IPv6 clients communicate with native IPv6 servers using
    native IPv6<br>
    - native IPv6 clients communicate with IPv4 only servers using DNS64
    + stateful NAT64<br>
    - IPv4 only applications/clients in an "IPv6 only environment"
    (where only IPv6 is used in the ISP core network) communicate with
    IPv4 servers using 464XLAT<br>
    Thus the two solutions (DNS64 and 464XLAT) can complement each other
    well, but DNS64 is not a part of 464XLAT.<br>
    <br>
    Best regards,<br>
    <br>
    Gábor Lencse<br>
    <br>
    <br>
    <div class="moz-cite-prefix">9/5/2018 5:28 PM keltezéssel, Ron
      Bonica írta:<br>
    </div>
    <blockquote
cite="mid:CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com"
      type="cite">
      <pre wrap="">Folks,

Each week between now and IETF 103, we will review and discuss one draft with an eye towards progressing it.

This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.

                                      Fred and Ron

_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------7DB70DC82A79574769221E38--


From nobody Wed Sep  5 11:07:16 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4D612F1A5 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 11:07:14 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 w5PLutfjYcCb for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 11:07:13 -0700 (PDT)
Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 E04FB130DE2 for <v6ops@ietf.org>; Wed,  5 Sep 2018 11:07:12 -0700 (PDT)
Received: by mail-yw1-xc31.google.com with SMTP id y134-v6so3012306ywg.1 for <v6ops@ietf.org>; Wed, 05 Sep 2018 11:07:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5P3OiRR+xrZGtexsu9ZOVVaq+WtSgMDoLrNzEEhEIg8=; b=atHD4rpdJ0Y8FXlhjWr+v84vfd0SMBnqph30LLtZ41QeofJrzhqWCjCIPA9o52eq5+ RxqHlnox2ExOE87D/jodgZsYt4du/4ENG/5l2NoKYNkT+7AMcyREYCTwgYIL6XDBeBP5 URckLdRsp//+fH7WI/BPmvb4HghmAn4fRrwTPHFdm59xfQBn+Ldvc+YCfSOM3u093ARv 5aUfQ1L3PsaozHKBvp4Xvu0hRShZ8Nl9lb8fGWp4qVzbYW7EjpBLu1ym2rhvN9f7TXjj A6VKdwGLtltdj/1Lu5/k7ST9LM3vMqgG5r1X0D7dLIXvBwx5nhm0f1ivW/rEL781AfEH 6XaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5P3OiRR+xrZGtexsu9ZOVVaq+WtSgMDoLrNzEEhEIg8=; b=DGaPb0cGe4ViYfc6GfuKzXSgwAe/2QOdoIq3m0xkDPhnORWGjTrsEgIYauU+mvkDJ8 3DgEh+J7FlPuLqmKzmpnV9uzI4X0qh4Vm1PYE/DWhu16tSKu/S0dtWpo6eA2TQuJR5En EXnRygzBG1MSv1Fib0ET+AzkIFkZpntQyrs99XpGvyek6+wFzaea0I8sYZhipLAvf5rX fwSbPaj6AVFmS9Fbfv+WJF/0vFMLSbkoqO0/OJT9xik1UvdMB+cnqgucIhNUyrS30mvb TBHABcdarg9zDtyrRwIfjEP6ienHlNRcC4DAE5n039umfek/pgdvf+vSyw4bnuMpc6xC ICSg==
X-Gm-Message-State: APzg51C8meSFddd+W/juaQ/1IbKfmAgh/hONar+s9xFi0597JtI6+nWk ///Fctwkde1JRlTM9cuFauA4qTbT786o8sh6xbdbRQ==
X-Google-Smtp-Source: ANB0Vdbos9SxZCsrbpmrrWLxuqGPlECTTdKeD37VhxDoOkW69/tZIGdbeGArG/3uKdYwX2tSFXFbpKKOO4ysbnHtbJE=
X-Received: by 2002:a81:59c3:: with SMTP id n186-v6mr22493524ywb.54.1536170832042;  Wed, 05 Sep 2018 11:07:12 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b58d94e7-f724-a5ec-97bc-c4b796a6531e@hit.bme.hu>
In-Reply-To: <b58d94e7-f724-a5ec-97bc-c4b796a6531e@hit.bme.hu>
From: Ca By <cb.list6@gmail.com>
Date: Wed, 5 Sep 2018 11:07:00 -0700
Message-ID: <CAD6AjGRxBzRFsZ5wUvmsmcnbiUzXsPKHoY1X7LKeaOcaMycarg@mail.gmail.com>
To: =?UTF-8?Q?Lencse_G=C3=A1bor?= <lencse@hit.bme.hu>
Cc: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c22460057523a46f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pTTBKSrHmy1Z7mrFr1tfLLUM6r8>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 18:07:14 -0000

--000000000000c22460057523a46f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 5, 2018 at 10:53 AM Lencse G=C3=A1bor <lencse@hit.bme.hu> wrote=
:

> Dear All,
>
> I have read the draft and I agree both with its intention to reconcile
> DNS64 and DNSSEC and also with the recommended solution.
>
> I have found one nit:
>
>    DNS64 is a key part of widely deployed IPv6-only transition mechanism
>    such as 464XLAT [RFC6877 <https://tools.ietf.org/html/rfc6877>] and Ha=
ppy Eyeballs Version 2 [RFC8305 <https://tools.ietf.org/html/rfc8305>].
>
>
> Maybe I misunderstand something, but I think DNS64 is *not a part of*
> 464XLAT. Of course they can be used together in a sense that:
> - native IPv6 clients communicate with native IPv6 servers using native
> IPv6
> - native IPv6 clients communicate with IPv4 only servers using DNS64 +
> stateful NAT64
> - IPv4 only applications/clients in an "IPv6 only environment" (where onl=
y
> IPv6 is used in the ISP core network) communicate with IPv4 servers using
> 464XLAT
> Thus the two solutions (DNS64 and 464XLAT) can complement each other well=
,
> but DNS64 is not a part of 464XLAT.
>
> Best regards,
>
> G=C3=A1bor Lencse
>

>
The key word is *widely deployed*

The largest 464xlat deployments use dns64


>
> 9/5/2018 5:28 PM keltez=C3=A9ssel, Ron Bonica =C3=ADrta:
>
> Folks,
>
> Each week between now and IETF 103, we will review and discuss one draft =
with an eye towards progressing it.
>
> This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
>
>                                       Fred and Ron
>
> _______________________________________________
> v6ops mailing listv6ops@ietf.orghttps://www.ietf.org/mailman/listinfo/v6o=
ps
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--000000000000c22460057523a46f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed,=
 Sep 5, 2018 at 10:53 AM Lencse G=C3=A1bor &lt;<a href=3D"mailto:lencse@hit=
.bme.hu">lencse@hit.bme.hu</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    Dear All, <br>
    <br>
    I have read the draft and I agree both with its intention to
    reconcile DNS64 and DNSSEC and also with the recommended solution.<br>
    <br>
    I have found one nit:<br>
    <br>
    <pre class=3D"m_-4183710085081233352newpage">   DNS64 is a key part of =
widely deployed IPv6-only transition mechanism
   such as 464XLAT [<a href=3D"https://tools.ietf.org/html/rfc6877" target=
=3D"_blank">RFC6877</a>] and Happy Eyeballs Version 2 [<a href=3D"https://t=
ools.ietf.org/html/rfc8305" target=3D"_blank">RFC8305</a>].
</pre>
    <br>
    Maybe I misunderstand something, but I think DNS64 is <u>not a part
      of</u> 464XLAT. Of course they can be used together in a sense
    that:<br>
    - native IPv6 clients communicate with native IPv6 servers using
    native IPv6<br>
    - native IPv6 clients communicate with IPv4 only servers using DNS64
    + stateful NAT64<br>
    - IPv4 only applications/clients in an &quot;IPv6 only environment&quot=
;
    (where only IPv6 is used in the ISP core network) communicate with
    IPv4 servers using 464XLAT<br>
    Thus the two solutions (DNS64 and 464XLAT) can complement each other
    well, but DNS64 is not a part of 464XLAT.<br>
    <br>
    Best regards,<br>
    <br>
    G=C3=A1bor Lencse</div></blockquote><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div=
 bgcolor=3D"#FFFFFF" text=3D"#000000"></div><div bgcolor=3D"#FFFFFF" text=
=3D"#000000"><br>
    </div></blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">The ke=
y word is *widely deployed*=C2=A0</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">The largest 464xlat deployments use dns64</div><div dir=3D"auto">=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#=
000000"><br>
    <br>
    <div class=3D"m_-4183710085081233352moz-cite-prefix">9/5/2018 5:28 PM k=
eltez=C3=A9ssel, Ron
      Bonica =C3=ADrta:<br>
    </div>
    <blockquote type=3D"cite">
      <pre>Folks,

Each week between now and IETF 103, we will review and discuss one draft wi=
th an eye towards progressing it.

This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.

                                      Fred and Ron

_______________________________________________
v6ops mailing list
<a class=3D"m_-4183710085081233352moz-txt-link-abbreviated" href=3D"mailto:=
v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a>
<a class=3D"m_-4183710085081233352moz-txt-link-freetext" href=3D"https://ww=
w.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">https://www.ietf.org/m=
ailman/listinfo/v6ops</a>
</pre>
    </blockquote>
    <br>
  </div>

_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div>

--000000000000c22460057523a46f--


From nobody Wed Sep  5 11:34:48 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19B8E12F1A5 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 11:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 9jqUHsb8kEmw for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 11:34:45 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B365B130DC6 for <v6ops@ietf.org>; Wed,  5 Sep 2018 11:34:45 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id A4D1FFECBB94; Wed,  5 Sep 2018 18:34:44 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CAD6AjGRxBzRFsZ5wUvmsmcnbiUzXsPKHoY1X7LKeaOcaMycarg@mail.gmail.com>
Date: Wed, 5 Sep 2018 20:34:41 +0200
Cc: =?utf-8?Q?Lencse_G=C3=A1bor?= <lencse@hit.bme.hu>, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FED85591-D2FF-4482-8633-773FD409ACDD@employees.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b58d94e7-f724-a5ec-97bc-c4b796a6531e@hit.bme.hu> <CAD6AjGRxBzRFsZ5wUvmsmcnbiUzXsPKHoY1X7LKeaOcaMycarg@mail.gmail.com>
To: Ca By <cb.list6@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/n5bCaTk9z7k67PECeZtvwu5xDVU>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 18:34:47 -0000

> On 5 Sep 2018, at 20:07, Ca By <cb.list6@gmail.com> wrote:
>=20
> The largest 464xlat deployments use dns64

Why wouldn=E2=80=99t you more precisely refer to that as a nat64+dns64 deplo=
yment and a 464xlat deployment? Sharing the NAT64.=20

Ole=


From nobody Wed Sep  5 12:53:30 2018
Return-Path: <rajiva@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5E9A130DD6 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 12:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 RdFZvNfErygQ for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 12:53:26 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEB2F130DC7 for <v6ops@ietf.org>; Wed,  5 Sep 2018 12:53:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22770; q=dns/txt; s=iport; t=1536177205; x=1537386805; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=E5sWJLrrM0buLk7bJ32Vy7VT1+1U89CrEwWbVguXD8o=; b=eDJFZhb09d3QSJWAsyUPfe/fWan78g6270oK/pYQDoq+d35flt834A/H psLzNI+6lQmfMaqn1GLuoeiRIGkrqqZK9wXzQ8/urx+eZ8WU5pDnHZ1Pa UijHOgFRHYXY09zYPS+YuLcoQDLFUs5t+vKKUAAaZIMyUMkl8bYz8hCpI E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DOBAC/M5Bb/5xdJa1aGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJXd2V/KAqDaJQpGoINli+BJANTCxgBDIRHAhc1AQSCfyE?= =?us-ascii?q?1FwECAQECAQECbRwMgieDEAEBAQEDAQEhBAZBGQICAQgRAwECKAMCAgIZDAs?= =?us-ascii?q?UCQgCBAESG4MGAYEdZA+iTXszhC4BhVMFBYotJheBQT+BEicfgh4ugxsBAQI?= =?us-ascii?q?BAYF0CRaCSzGCJgKNIBOFSIhhCQKGNIlIF4FAjSKIQYJuiB4CERSBJB8BNTS?= =?us-ascii?q?BDA0IcBU7KgGCQYIlF4hZhT5vAQGMY4EdAQE?=
X-IronPort-AV: E=Sophos;i="5.53,334,1531785600";  d="scan'208,217";a="230198469"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Sep 2018 19:53:02 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id w85Jr2OW003745 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 5 Sep 2018 19:53:02 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 5 Sep 2018 14:53:02 -0500
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1367.000; Wed, 5 Sep 2018 14:53:01 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Lee Howard <lee@asgard.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] How my Android phone got assigned with IPv6 address via 4G LTE?
Thread-Index: AQHUPaAhXfa+N1TBsUuyyhgO2s7rHaTSy0g0gABVxoCAAAJJAIAACcaAgAAckICAAAPhAIAAB12A///ArR6AAP35AIAAxkqAgAAD74CAAAQIgIAACHyAgAAsB/2AAHqrgIAMqJ2A
Date: Wed, 5 Sep 2018 19:53:01 +0000
Message-ID: <7B6307F1-19C8-4D80-A32A-973E0F3CA4F7@cisco.com>
References: <CAAObRXLe35KoONVsSO_oU+SRhMzMrKRE_SU-QNf2pGHYKpUrxA@mail.gmail.com> <2018082709132233449033@chinatelecom.cn> <CAKD1Yr3PFKC06vwALL9Pjyd8Ji-RnqPR-HMvLA6CS6cyDadzVw@mail.gmail.com> <CAAObRXJx-8cPYuU-5gSMCvoOX-m29Q5BZg1-GANXBV-2Zmjv0A@mail.gmail.com> <CAKD1Yr24fXHsRTwFErNGc+RYzXDfHFpF6zG5QFjfjS+xx5-9Mg@mail.gmail.com> <CAAObRXK3jx_FXi-Rt5W3iSkOrf8zmc2z0NC1hUoET=AMFj2sig@mail.gmail.com> <CAAedzxouJUY1-R2NQH8sMDA0vrkOSznOWUaykBtdMy5a5Cup4g@mail.gmail.com> <34329770-1e00-be97-8443-79448be367cb@gmail.com> <201808271339136864338@chinatelecom.cn> <CAD6AjGReSzm0GHwFO74KL8R0F5Ahwd6c0s3bn2PtCyDTo-MPCw@mail.gmail.com> <CAAedzxrDjTO=BSsBGdgbaDRmhCUuB6frtV_oRE-+vNu5tsA5+Q@mail.gmail.com> <48B470F2-3F62-4D3F-90ED-C80A752AB61F@isc.org> <CAAedzxqfmODSBbnzSEg0hH+W+ovoDXcgmUjo+XUySiZFrxVcUg@mail.gmail.com> <D02DED65-CFDB-4ABE-A2C1-AA75440F19A8@isc.org> <7BC525AA-90F2-4477-BF1A-FB1FC80B8AF5@cisco.com> <c3df5aa5-4070-d16f-9c0d-684adb5f40e8@asgard.org>
In-Reply-To: <c3df5aa5-4070-d16f-9c0d-684adb5f40e8@asgard.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.e.1.180613
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.190.148]
Content-Type: multipart/alternative; boundary="_000_7B6307F119C84D80A32A973E0F3CA4F7ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-tp7upgxxzEszjeXxN0L6Ja74V4>
Subject: Re: [v6ops] How my Android phone got assigned with IPv6 address via 4G LTE?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 19:53:29 -0000

--_000_7B6307F119C84D80A32A973E0F3CA4F7ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QlRXLCBzZWN0aW9uIDIuMy4yIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRm
LWRuc29wLWlzcC1pcDZyZG5zLTA1I3NlY3Rpb24tMi4zLjIgcmVtaW5kZWQgbWUgb2YgdGhlIHNv
bHV0aW9uIGRlc2NyaWJlZCBoZXJlIGZvciB0cmFja2luZyBNQUMtSVAgYWRkcmVzcyBjb3VwbGlu
ZyBpbiBlbnZpcm9ubWVudHMgc3VjaCBhcyB0aG9zZSBvZiBlbnRlcnByaXNlcyBldGMuDQoNCmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1hc2F0aS1kaGMtaXB2Ni1hdXRvY29uZmln
LWFkZHJlc3MtdHJhY2tpbmcNCg0KLS0NCkNoZWVycywNClJhaml2DQoNCg0KRnJvbTogdjZvcHMg
PHY2b3BzLWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBMZWUgSG93YXJkIDxsZWVAYXNn
YXJkLm9yZz4NCkRhdGU6IFR1ZXNkYXksIEF1Z3VzdCAyOCwgMjAxOCBhdCAxMDozNSBBTQ0KVG86
ICJ2Nm9wc0BpZXRmLm9yZyIgPHY2b3BzQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFt2Nm9wc10g
SG93IG15IEFuZHJvaWQgcGhvbmUgZ290IGFzc2lnbmVkIHdpdGggSVB2NiBhZGRyZXNzIHZpYSA0
RyBMVEU/DQoNCg0KDQpPbiAwOC8yOC8yMDE4IDA4OjE1IEFNLCBSYWppdiBBc2F0aSAocmFqaXZh
KSB3cm90ZToNCldpdGggSVB2NiwgdXNhZ2Ugb2YgREROUyBzaG91bGQgYmUgcmVjb21tZW5kZWQg
YXMgYSBnb29kIHByYWN0aWNlIHRvIGdldCBob3N0bmFtZSAtIElQIG1hcHBpbmcuIEFsc28gaW1w
b3J0YW50IGlzIHRvIGZvcm11bGF0ZSB0aGUgaG9zdCBuYW1lcyB0aGF0IGNvbXBseSB3aXRoIHNh
bml0eS4NCg0KT25seSBpZiB5b3UgY2FyZSBhYm91dCBob3N0bmFtZSAtIElQIG1hcHBpbmcuIEl0
IG1hdHRlcnMgZm9yIHNvbWUga2luZHMNCm9mIHNlcnZlcnMsIGFuZCBpcyBoYW5keSBmb3IgdHJh
Y2Vyb3V0ZXMuIEhvc3RzIHRoYXQgYXJlIGNsaWVudHMgZG9uJ3QNCmdlbmVyYWxseSBnZXQgbG9v
a2VkIHVwIGJ5IG5hbWUuDQoNCk9mIGNvdXJzZSwgdGhlIHR5cGljYWwgdjQgcHJhY3RpY2Ugb2Yg
Zm9ybXVsYXRpbmcgaG9zdG5hbWVzIGJ5IGVuY29kaW5nIHRoZSBlbnRpcmUgdjQgYWRkcmVzcyBp
biB0aGUgaG9zdCBuYW1lIG11c3Qgbm90IGJlIGZvbGxvd2VkLg0KDQpJdCBjb3VsZCBiZS4gIlNh
bml0eSIgKGFzIHlvdSBzYWlkIGFib3ZlKSBpcyBoYXJkIHRvIGRlZmluZSwgZXNwZWNpYWxseQ0K
d2hlbiB5b3UgZG9uJ3Qgd2FudCB0byBnaXZlIGF3YXkgcHJpdmF0ZSB1c2VyIGluZm9ybWF0aW9u
Lg0KDQoNClBlcmhhcHMsIGEgdG9waWMgZm9yIGEgZGlmZmVyZW50IHRocmVhZC4NCg0KVGhpcyBk
cmFmdCBpcyB2ZXJ5IGNsb3NlIHRvIHB1YmxpY2F0aW9uOg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1kbnNvcC1pc3AtaXA2cmRucy8NClRoZSBBRCBoYXMgZm9y
IGEgdmVyeSBmZXcgbWlub3IgY2hhbmdlcywgd2hpY2ggSSBob3BlIHRvIG1ha2UgaW4gdGhlDQpu
ZXh0IDQ4IGhvdXJzLiBJdCBzdGlsbCBuZWVkcyBJRVRGIExhc3QgQ2FsbC4NCg0KTGVlDQoNCkNo
ZWVycywNClJhaml2DQoNCg0KT24gQXVnIDI4LCAyMDE4LCBhdCAxMjozOCBBTSwgTWFyayBBbmRy
ZXdzIDxtYXJrYUBpc2Mub3JnPG1haWx0bzptYXJrYUBpc2Mub3JnPj4gd3JvdGU6DQoNCg0KDQpP
biAyOCBBdWcgMjAxOCwgYXQgMjowNyBwbSwgRXJpayBLbGluZSA8ZWtAZ29vZ2xlLmNvbTxtYWls
dG86ZWtAZ29vZ2xlLmNvbT4+IHdyb3RlOg0KDQpZdXAsIGFncmVlZC4gIEkgd2Fzbid0IGltcGx5
aW5nIGEgcHJvdG9jb2wgZGlkbid0IGV4aXN0LCBvbmx5IHRoYXQgaXQNCndhc24ndCBiZWluZyB1
c2VkLg0KDQpUbyBiZSBob25lc3QsIEkndmUgbmV2ZXIgdHJ5IHRvIHVzZSBETlMgVVBEQVRFIGFz
IGEgY2xpZW50L2luIGFuDQphcHBsaWNhdGlvbiwgc28gSSBkb24ndCBrbm93IGlmIHRoZXJlIGFy
ZSBhbnkgdW5hZGRyZXNzZWQgYXNwZWN0cyB0bw0KaXRzIHVzZSAqb3RoZXIqIHRoYW4gc2ltcGx5
IHRyeWluZyBpbiB0aGUgZmlyc3QgcGxhY2UuDQoqIEROUyBVUERBVEUgaXMgdXNlZCBieSBBY3Rp
dmUgRGlyZWN0b3J5ICh1c2luZyBHU1MtVFNJRyB0byBhdXRoZW50aWNhdGUpLg0KKiBETlMgVVBE
QVRFIGlzIHVzZWQgYnkgREhDUCBzZXJ2ZXJzIHdpdGggVFNJRyBpbiBlbnRlcnByaXNlcyB0byB1
cGRhdGUNCiAgIGZvcndhcmQgYW5kIHJldmVyc2Ugem9uZXMuDQoqIEROUyBVUERBVEUgaXMvd2Fz
IHVzZWQgYnkgRHluRE5TIHdpdGggVFNJRyBhbmQgU1JWIHRvIHVwZGF0ZSBmb3J3YXJkIHpvbmVz
DQogICBmcm9tIENQRSByb3V0ZXJzIHVzdWFsbHkuDQoqIE1hY09TIHVzZXMgRE5TIFVQREFURSB3
aXRoIFRTSUcgYW5kIFNSViB0byB1cGRhdGUgZm9yd2FyZCB6b25lcy4NCiAgIChTeXN0ZW0gUHJl
ZmVyZW5jZXMgLT4gU2hhcmluZyAtPiBFZGl0IC0+IFVzZSBEeW5hbWljIEdsb2JhbCBIb3N0bmFt
ZSkNCg0KVGhlcmUgaXMgYWN0dWFsbHkgYSBnb29kIGNoYW5jZSB0aGF0IGl0IHdhcyB1c2VkIGJl
aGluZCB0aGUgc2NlbmVzIHdpdGgNCmVxdWlwbWVudCB0aGF0IHlvdSBoYXZlIHVzZWQuIEl04oCZ
cyBqdXN0IG5vdCB1c2VkIHViaXF1aXRvdXNseSBhbmQgaXQgc2hvdWxkDQpiZS4NCg0KTWFyaw0K
LS0NCk1hcmsgQW5kcmV3cywgSVNDDQoxIFNleW1vdXIgU3QuLCBEdW5kYXMgVmFsbGV5LCBOU1cg
MjExNywgQXVzdHJhbGlhDQpQSE9ORTogKzYxIDIgOTg3MSA0NzQyICAgICAgICAgICAgICBJTlRF
Uk5FVDogbWFya2FAaXNjLm9yZzxtYWlsdG86bWFya2FAaXNjLm9yZz4NCg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnY2b3BzIG1haWxpbmcgbGlzdA0K
djZvcHNAaWV0Zi5vcmc8bWFpbHRvOnY2b3BzQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCnY2b3BzIG1haWxpbmcgbGlzdA0KdjZvcHNAaWV0Zi5vcmc8bWFp
bHRvOnY2b3BzQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by92Nm9wcw0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KdjZvcHMgbWFpbGluZyBsaXN0DQp2Nm9wc0BpZXRmLm9yZzxtYWlsdG86djZvcHNAaWV0Zi5v
cmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzDQoNCg==

--_000_7B6307F119C84D80A32A973E0F3CA4F7ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <1DC048644780214997E73511ED5991BC@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw
bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v
cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlv
bjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGlu
O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNw
aWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBk
YXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0K
PGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFz
cz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkJUVywgc2VjdGlvbiAyLjMu
MiA8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kbnNvcC1p
c3AtaXA2cmRucy0wNSNzZWN0aW9uLTIuMy4yIj4NCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1pZXRmLWRuc29wLWlzcC1pcDZyZG5zLTA1I3NlY3Rpb24tMi4zLjI8L2E+IHJlbWlu
ZGVkIG1lIG9mIHRoZSBzb2x1dGlvbiBkZXNjcmliZWQgaGVyZSBmb3IgdHJhY2tpbmcgTUFDLUlQ
IGFkZHJlc3MgY291cGxpbmcgaW4gZW52aXJvbm1lbnRzIHN1Y2ggYXMgdGhvc2Ugb2YgZW50ZXJw
cmlzZXMgZXRjLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5odHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtYXNhdGktZGhjLWlwdjYtYXV0b2NvbmZpZy1hZGRyZXNzLXRyYWNraW5nPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLSZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+UmFqaXYgJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk
ICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj52Nm9wcyAmbHQ7djZvcHMtYm91bmNlc0BpZXRmLm9y
ZyZndDsgb24gYmVoYWxmIG9mIExlZSBIb3dhcmQgJmx0O2xlZUBhc2dhcmQub3JnJmd0Ozxicj4N
CjxiPkRhdGU6IDwvYj5UdWVzZGF5LCBBdWd1c3QgMjgsIDIwMTggYXQgMTA6MzUgQU08YnI+DQo8
Yj5UbzogPC9iPiZxdW90O3Y2b3BzQGlldGYub3JnJnF1b3Q7ICZsdDt2Nm9wc0BpZXRmLm9yZyZn
dDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IFt2Nm9wc10gSG93IG15IEFuZHJvaWQgcGhvbmUg
Z290IGFzc2lnbmVkIHdpdGggSVB2NiBhZGRyZXNzIHZpYSA0RyBMVEU/PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1s
ZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPk9uIDA4LzI4LzIwMTggMDg6MTUg
QU0sIFJhaml2IEFzYXRpIChyYWppdmEpIHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0I1QzRERiA0
LjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJnaW4t
cmlnaHQ6MGluIiBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05fQkxPQ0tRVU9URSI+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPldpdGggSVB2
NiwgdXNhZ2Ugb2YgREROUyBzaG91bGQgYmUgcmVjb21tZW5kZWQgYXMgYSBnb29kIHByYWN0aWNl
IHRvIGdldCBob3N0bmFtZSAtIElQIG1hcHBpbmcuIEFsc28gaW1wb3J0YW50IGlzIHRvIGZvcm11
bGF0ZSB0aGUgaG9zdCBuYW1lcyB0aGF0IGNvbXBseSB3aXRoIHNhbml0eS48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5Pbmx5IGlm
IHlvdSBjYXJlIGFib3V0IGhvc3RuYW1lIC0gSVAgbWFwcGluZy4gSXQgbWF0dGVycyBmb3Igc29t
ZSBraW5kcw0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+b2Ygc2VydmVycywgYW5kIGlzIGhhbmR5IGZv
ciB0cmFjZXJvdXRlcy4gSG9zdHMgdGhhdCBhcmUgY2xpZW50cyBkb24ndA0KPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6LjVpbiI+Z2VuZXJhbGx5IGdldCBsb29rZWQgdXAgYnkgbmFtZS48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNCNUM0REYgNC41cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdDttYXJnaW4tbGVmdDozLjc1
cHQ7bWFyZ2luLXJpZ2h0OjBpbiIgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVP
VEUiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWlu
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5PZiBjb3Vyc2UsIHRoZSB0eXBpY2FsIHY0IHBy
YWN0aWNlIG9mIGZvcm11bGF0aW5nIGhvc3RuYW1lcyBieSBlbmNvZGluZyB0aGUgZW50aXJlIHY0
IGFkZHJlc3MgaW4gdGhlIGhvc3QgbmFtZSBtdXN0IG5vdCBiZSBmb2xsb3dlZC48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5JdCBj
b3VsZCBiZS4gJnF1b3Q7U2FuaXR5JnF1b3Q7IChhcyB5b3Ugc2FpZCBhYm92ZSkgaXMgaGFyZCB0
byBkZWZpbmUsIGVzcGVjaWFsbHkNCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPndoZW4geW91IGRvbid0
IHdhbnQgdG8gZ2l2ZSBhd2F5IHByaXZhdGUgdXNlciBpbmZvcm1hdGlvbi48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVm
dDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNCNUM0REYgNC41cHQ7cGFkZGluZzowaW4g
MGluIDBpbiA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7bWFyZ2luLXJpZ2h0OjBpbiIgaWQ9Ik1B
Q19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWlu
Ij5QZXJoYXBzLCBhIHRvcGljIGZvciBhIGRpZmZlcmVudCB0aHJlYWQuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+VGhpcyBkcmFm
dCBpcyB2ZXJ5IGNsb3NlIHRvIHB1YmxpY2F0aW9uOg0KPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PGEg
aHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1kbnNvcC1p
c3AtaXA2cmRucy8iPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYt
ZG5zb3AtaXNwLWlwNnJkbnMvPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPlRoZSBBRCBoYXMgZm9y
IGEgdmVyeSBmZXcgbWlub3IgY2hhbmdlcywgd2hpY2ggSSBob3BlIHRvIG1ha2UgaW4gdGhlDQo8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDouNWluIj5uZXh0IDQ4IGhvdXJzLiBJdCBzdGlsbCBuZWVkcyBJRVRGIExh
c3QgQ2FsbC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5M
ZWU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNCNUM0REYgNC41
cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7bWFyZ2luLXJp
Z2h0OjBpbiIgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5DaGVlcnMsPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luLWxlZnQ6LjVpbiI+UmFqaXY8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNCNUM0REYgNC41cHQ7cGFkZGlu
ZzowaW4gMGluIDBpbiA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7bWFyZ2luLXJpZ2h0OjBpbiIg
aWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5PbiBBdWcgMjgsIDIwMTgsIGF0
IDEyOjM4IEFNLCBNYXJrIEFuZHJld3MgJmx0OzxhIGhyZWY9Im1haWx0bzptYXJrYUBpc2Mub3Jn
Ij5tYXJrYUBpc2Mub3JnPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjQjVDNERGIDQuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQ7bWFy
Z2luLWxlZnQ6My43NXB0O21hcmdpbi1yaWdodDowaW4iIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJV
VElPTl9CTE9DS1FVT1RFIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWxlZnQ6LjVpbiI+T24gMjggQXVnIDIwMTgsIGF0IDI6MDcgcG0sIEVyaWsgS2xpbmUgJmx0
OzxhIGhyZWY9Im1haWx0bzpla0Bnb29nbGUuY29tIj5la0Bnb29nbGUuY29tPC9hPiZndDsgd3Jv
dGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+WXVwLCBh
Z3JlZWQuJm5ic3A7Jm5ic3A7SSB3YXNuJ3QgaW1wbHlpbmcgYSBwcm90b2NvbCBkaWRuJ3QgZXhp
c3QsIG9ubHkgdGhhdCBpdDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPndhc24ndCBiZWluZyB1c2VkLjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1sZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPlRvIGJlIGhvbmVz
dCwgSSd2ZSBuZXZlciB0cnkgdG8gdXNlIEROUyBVUERBVEUgYXMgYSBjbGllbnQvaW4gYW48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
YXJnaW4tbGVmdDouNWluIj5hcHBsaWNhdGlvbiwgc28gSSBkb24ndCBrbm93IGlmIHRoZXJlIGFy
ZSBhbnkgdW5hZGRyZXNzZWQgYXNwZWN0cyB0bzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPml0cyB1c2Ug
Km90aGVyKiB0aGFuIHNpbXBseSB0cnlpbmcgaW4gdGhlIGZpcnN0IHBsYWNlLjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPiogRE5TIFVQREFURSBpcyB1c2VkIGJ5IEFjdGl2ZSBE
aXJlY3RvcnkgKHVzaW5nIEdTUy1UU0lHIHRvIGF1dGhlbnRpY2F0ZSkuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
LjVpbiI+KiBETlMgVVBEQVRFIGlzIHVzZWQgYnkgREhDUCBzZXJ2ZXJzIHdpdGggVFNJRyBpbiBl
bnRlcnByaXNlcyB0byB1cGRhdGU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj4mbmJzcDsmbmJzcDsgZm9y
d2FyZCBhbmQgcmV2ZXJzZSB6b25lcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj4qIEROUyBVUERBVEUg
aXMvd2FzIHVzZWQgYnkgRHluRE5TIHdpdGggVFNJRyBhbmQgU1JWIHRvIHVwZGF0ZSBmb3J3YXJk
IHpvbmVzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+Jm5ic3A7Jm5ic3A7IGZyb20gQ1BFIHJvdXRlcnMg
dXN1YWxseS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj4qIE1hY09TIHVzZXMgRE5TIFVQREFURSB3aXRo
IFRTSUcgYW5kIFNSViB0byB1cGRhdGUgZm9yd2FyZCB6b25lcy48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWlu
Ij4mbmJzcDsmbmJzcDsgKFN5c3RlbSBQcmVmZXJlbmNlcyAtJmd0OyBTaGFyaW5nIC0mZ3Q7IEVk
aXQgLSZndDsgVXNlIER5bmFtaWMgR2xvYmFsIEhvc3RuYW1lKTxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4i
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPlRoZXJlIGlzIGFjdHVhbGx5IGEgZ29vZCBjaGFu
Y2UgdGhhdCBpdCB3YXMgdXNlZCBiZWhpbmQgdGhlIHNjZW5lcyB3aXRoPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
LjVpbiI+ZXF1aXBtZW50IHRoYXQgeW91IGhhdmUgdXNlZC4gSXTigJlzIGp1c3Qgbm90IHVzZWQg
dWJpcXVpdG91c2x5IGFuZCBpdCBzaG91bGQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5iZS48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5NYXJrPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6LjVpbiI+LS0gPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+TWFyayBBbmRyZXdzLCBJU0M8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDouNWluIj4xIFNleW1vdXIgU3QuLCBEdW5kYXMgVmFsbGV5LCBOU1cgMjExNywgQXVz
dHJhbGlhPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+UEhPTkU6ICYjNDM7NjEgMiA5ODcxIDQ3NDImbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtJTlRFUk5FVDoNCjxhIGhyZWY9Im1haWx0bzptYXJrYUBp
c2Mub3JnIj5tYXJrYUBpc2Mub3JnPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1sZWZ0Oi41aW4iPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+djZvcHMgbWFpbGluZyBsaXN0PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6LjVpbiI+PGEgaHJlZj0ibWFpbHRvOnY2b3BzQGlldGYub3JnIj52Nm9wc0BpZXRmLm9yZzwv
YT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tbGVmdDouNWluIj48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3Y2b3BzIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L3Y2b3BzPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+
djZvcHMgbWFpbGluZyBsaXN0PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PGEgaHJlZj0ibWFpbHRvOnY2
b3BzQGlldGYub3JnIj52Nm9wc0BpZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48YSBo
cmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzIj5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzPC9hPjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1sZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+
djZvcHMgbWFpbGluZyBsaXN0PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PGEgaHJlZj0ibWFpbHRvOnY2
b3BzQGlldGYub3JnIj52Nm9wc0BpZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48YSBo
cmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzIj5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzPC9hPjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41
aW4iPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRt
bD4NCg==

--_000_7B6307F119C84D80A32A973E0F3CA4F7ciscocom_--


From nobody Wed Sep  5 13:34:29 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C194130DC9 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 13:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 FkmSZ_79tLSH for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 13:34:25 -0700 (PDT)
Received: from atl4mhob04.registeredsite.com (atl4mhob04.registeredsite.com [209.17.115.42]) (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 EB883130DC7 for <v6ops@ietf.org>; Wed,  5 Sep 2018 13:34:24 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob04.registeredsite.com (8.14.4/8.14.4) with ESMTP id w85KYLRG031124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Wed, 5 Sep 2018 16:34:21 -0400
Received: (qmail 32124 invoked by uid 0); 5 Sep 2018 20:34:21 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 5 Sep 2018 20:34:21 -0000
To: v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <a82ff425-5f15-e0d7-50ae-3f72137f73d3@asgard.org>
Date: Wed, 5 Sep 2018 16:34:20 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------7CF2C3AF40E1321BCEEF3218"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hJbpJn1We_k-63UC3FPbv_OCXDg>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 20:34:28 -0000

This is a multi-part message in MIME format.
--------------7CF2C3AF40E1321BCEEF3218
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

I think this document should be BCP, not Informational.

Section 2

s/mechanism/mechanisms in the first instance in the first sentence.

How is HEv2 a transition mechanism?

I'd rephrase to say, "DNS64 is a key part of widely deployed IPv6-only 
transition mechanisms, including several large 464xlat [RFC6877] 
deployments, and all NAT64 deployments." I think that clarifies that 
we're talking about specific deployments here.

Since the discussion of DNSSEC in RFC6147 is so brief, I think it's 
worth discussing here, so the explanation of why it is an insufficient 
workaround is sufficient. I'd like to replace the last sentence of 
section 2 with a new paragraph:

RFC6147 ("DNSSEC") outlines how validation may occur in the presence of 
DNSSEC:

An existing DNSSEC validator (i.e., one that is unaware of DNS64)

    might reject all the data that comes from DNS64 as having been
    tampered with (even if it did not set CD when querying).  If it is
    necessary to have validation behind the DNS64, then the validator
    must know how to perform the DNS64 function itself.  Alternatively,
    the validating host may establish a trusted connection with a DNS64,
    and allow the DNS64 recursive resolver to do all validation on its
    behalf. [RFC6147 - DNS64]


However, the domain administrator has no control over the client doing 
the validating, and clients (or their validating resolvers) cannot be 
expected to know about the presence of DNS64 a priori. Clients who might 
trust an authoritative name server for some content may not be as 
trusting of their carrier's DNS64 server.

Section 3

s/to changes/to change
s/not recommend/not recommended
To soften the blow, I'd suggest adding a sentence, after "in tandem."  
"The IPv6 deployment may be as light weight as a translator, such as 
SIIT-DC [RFC7755]."


There's more I'd add to the document, and it's the "So what?"

For instance, in Security Considerations:
"If clients trust RRs that fail validation (because they were invented 
by an DNS64 server), there is increased risk that they will trust other 
RRs that fail validation. Further, a compromised or hostile 
man-in-the-middle DNS64 server will be undetected, despite DNSSEC signing."
In Section 2, I admit I don't know what a client actually sees, if 
anything. Do browsers or other applications warn that a name failed 
validation? I'm sure I can test it tomorrow. I don't know how to inform 
users or their content providers that "This record cannot be guaranteed 
to be accurate, since it failed DNS Security validation. It appears to 
be a synthetic record, since the name only has an IPv4 record."


Even though my comments are longer than the draft, I like this effort, 
and wish I had initiated it.

Lee


On 09/05/2018 11:28 AM, Ron Bonica wrote:
> Folks,
>
> Each week between now and IETF 103, we will review and discuss one draft with an eye towards progressing it.
>
> This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
>
>                                        Fred and Ron
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--------------7CF2C3AF40E1321BCEEF3218
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I think this document should be BCP, not Informational.</p>
    <p>Section 2</p>
    <p>s/mechanism/mechanisms in the first instance in the first
      sentence.<br>
    </p>
    <p>How is HEv2 a transition mechanism?</p>
    <p>I'd rephrase to say, "DNS64 is a key part of widely deployed
      IPv6-only transition mechanisms, including several large 464xlat
      [RFC6877] deployments, and all NAT64 deployments." I think that
      clarifies that we're talking about specific deployments here.</p>
    <p>Since the discussion of DNSSEC in RFC6147 is so brief, I think
      it's worth discussing here, so the explanation of why it is an
      insufficient workaround is sufficient. I'd like to replace the
      last sentence of section 2 with a new paragraph:<br>
      <br>
    </p>
    <p>RFC6147 ("DNSSEC") outlines how validation may occur in the
      presence of DNSSEC:</p>
    An existing DNSSEC validator (i.e., one that is unaware of DNS64)
    <pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">   might reject all the data that comes from DNS64 as having been
   tampered with (even if it did not set CD when querying).  If it is
   necessary to have validation behind the DNS64, then the validator
   must know how to perform the DNS64 function itself.  Alternatively,
   the validating host may establish a trusted connection with a DNS64,
   and allow the DNS64 recursive resolver to do all validation on its
   behalf. [RFC6147 - DNS64]</pre>
    <br>
    However, the domain administrator has no control over the client
    doing the validating, and clients (or their validating resolvers)
    cannot be expected to know about the presence of DNS64 a priori.
    Clients who might trust an authoritative name server for some
    content may not be as trusting of their carrier's DNS64 server.<br>
    <br>
    Section 3<br>
    <br>
    s/to changes/to change<br>
    s/not recommend/not recommended<br>
    To soften the blow, I'd suggest adding a sentence, after "in
    tandem."  "The IPv6 deployment may be as light weight as a
    translator, such as SIIT-DC [RFC7755]."<br>
    <br>
    <br>
    There's more I'd add to the document, and it's the "So what?"<br>
    <br>
    For instance, in Security Considerations:<br>
    "If clients trust RRs that fail validation (because they were
    invented by an DNS64 server), there is increased risk that they will
    trust other RRs that fail validation. Further, a compromised or
    hostile man-in-the-middle DNS64 server will be undetected, despite
    DNSSEC signing."<br>
    In Section 2, I admit I don't know what a client actually sees, if
    anything. Do browsers or other applications warn that a name failed
    validation? I'm sure I can test it tomorrow. I don't know how to
    inform users or their content providers that "This record cannot be
    guaranteed to be accurate, since it failed DNS Security validation.
    It appears to be a synthetic record, since the name only has an IPv4
    record."<br>
    <br>
    <br>
    Even though my comments are longer than the draft, I like this
    effort, and wish I had initiated it.<br>
    <br>
    Lee<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 09/05/2018 11:28 AM, Ron Bonica
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com">
      <pre wrap="">Folks,

Each week between now and IETF 103, we will review and discuss one draft with an eye towards progressing it.

This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.

                                      Fred and Ron

_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------7CF2C3AF40E1321BCEEF3218--


From nobody Wed Sep  5 14:33:16 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8C6A130DC9 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 14:33:13 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 hNcsAxD7TG0B for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 14:33:12 -0700 (PDT)
Received: from mail-yw1-xc2d.google.com (mail-yw1-xc2d.google.com [IPv6:2607:f8b0:4864:20::c2d]) (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 7C686127332 for <v6ops@ietf.org>; Wed,  5 Sep 2018 14:33:12 -0700 (PDT)
Received: by mail-yw1-xc2d.google.com with SMTP id j131-v6so3242099ywc.13 for <v6ops@ietf.org>; Wed, 05 Sep 2018 14:33:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MbOV1R27gXLAR64hTuezAxNLkHZvde7t/5GPzOpYnPM=; b=mUnUJVEuThwpY7Q7FAlxdce9cj0qMihaQJgWpkBuWkf2p7H0FU9m+GuwKNWj2ZcRzQ LeF12/NjCdcK+vpKpTtFJjJAxYDWlGNm5hbXXQ+4yWks8EsHn+rUizHyt/1c2NyiD2ZE W+qNs2teX5AukKhNTl/yXljPCWn4AYuM+TWRWZQFnZyRFg2FEKHYVa+urt1fO7jRgAm7 1vLEEsRZo7WdFXL/AqIsieDHxsRPBaeQcL7B0dVT/Vg1cZ9z/0DMe/ZQk2PMwa04Vg7u dwgjeQz/a3L5g2+rv01CEh2rIbd/vJBzbFpuNMVsZqZrMWf/u81we9+XuRsgr9r8QKg1 l4cw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MbOV1R27gXLAR64hTuezAxNLkHZvde7t/5GPzOpYnPM=; b=V0oZUDtgEbNxhykEJUPx1up364vfpyf1u4eBT95qIYuyS7fPjLsbm9Ab8GkY0ANszb TZknp8FDFUSUtYxgE4VDlOpg5DBUgc6tHXHxdqh9npnrShpajHV3iWPhaeP/lQ/0Akm3 N5qN/8FFFD8W6oMthcm8fJNuYnmxH+kzWWRoAQp4PTP8Kkn1r/j+Ex4adKNvcP+JZ+x3 WmT9z4hswhE+h/IpwOKuN909eLmuiqDS4/RgMlegmJOHnjMrXtNzHDbWoctpaUUJnGzP +NEwfQ8jTeYzovX3ZYNSNPWCOL6qCP3CbYvZ8EMWBHfTN7Y3/QHrDbzWBFVjzG2RWL75 wr1Q==
X-Gm-Message-State: APzg51AbNesX74GQ2cbAzCs/y7FT4t9BOuVpP8PStI5urxE+u+fR94gz D1eSte2BXUvYENTXarb8sDlo0LXomv8oDemY44U=
X-Google-Smtp-Source: ANB0VdbRHwuAFDXgUBwFBu9HCWYdezDDkn7c1GoEquomz4YhASHbfv9iePdKRUeQiuMHQ1FvE26mHdlP+Dd7eGDLWkk=
X-Received: by 2002:a81:8087:: with SMTP id q129-v6mr22002310ywf.184.1536183191674;  Wed, 05 Sep 2018 14:33:11 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b58d94e7-f724-a5ec-97bc-c4b796a6531e@hit.bme.hu> <CAD6AjGRxBzRFsZ5wUvmsmcnbiUzXsPKHoY1X7LKeaOcaMycarg@mail.gmail.com> <FED85591-D2FF-4482-8633-773FD409ACDD@employees.org>
In-Reply-To: <FED85591-D2FF-4482-8633-773FD409ACDD@employees.org>
From: Ca By <cb.list6@gmail.com>
Date: Wed, 5 Sep 2018 14:33:00 -0700
Message-ID: <CAD6AjGSKFcnn5Dc5XjCBxkyUrNS4DK9HWeGO5+e1wEiGMY1jiQ@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: =?UTF-8?Q?Lencse_G=C3=A1bor?= <lencse@hit.bme.hu>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007323ee0575268590"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/FkwifO5co6t2XHQP3RuWrSTfIBc>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 21:33:14 -0000

--0000000000007323ee0575268590
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 5, 2018 at 11:34 AM Ole Troan <otroan@employees.org> wrote:

>
>
> > On 5 Sep 2018, at 20:07, Ca By <cb.list6@gmail.com> wrote:
> >
> > The largest 464xlat deployments use dns64
>
> Why wouldn=E2=80=99t you more precisely refer to that as a nat64+dns64 de=
ployment
> and a 464xlat deployment? Sharing the NAT64.
>
> Ole


I believe the document is about dns64. There is a statement in the i-d that
there exist dns64 deployments that are  large that happen to be 464xlat ,
to provide context to the reader. The reader would properly assume a large
dns64/nat64-only deployment would be laughable.


>

--0000000000007323ee0575268590
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed,=
 Sep 5, 2018 at 11:34 AM Ole Troan &lt;<a href=3D"mailto:otroan@employees.o=
rg">otroan@employees.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><br>
<br>
&gt; On 5 Sep 2018, at 20:07, Ca By &lt;<a href=3D"mailto:cb.list6@gmail.co=
m" target=3D"_blank">cb.list6@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; The largest 464xlat deployments use dns64<br>
<br>
Why wouldn=E2=80=99t you more precisely refer to that as a nat64+dns64 depl=
oyment and a 464xlat deployment? Sharing the NAT64. <br>
<br>
Ole</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">I believe the=
 document is about dns64. There is a statement in the i-d that there exist =
dns64 deployments that are =C2=A0large that happen to be 464xlat , to provi=
de context to the reader. The reader would properly assume a large dns64/na=
t64-only deployment would be laughable.=C2=A0</div><div dir=3D"auto"><br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><br>
</blockquote></div></div>

--0000000000007323ee0575268590--


From nobody Wed Sep  5 14:51:00 2018
Return-Path: <nygren@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D46E6130E27 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 14:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.146, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=no 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 2Z69eGmo-tEu for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 14:50:57 -0700 (PDT)
Received: from mail-it0-f65.google.com (mail-it0-f65.google.com [209.85.214.65]) (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 65569130E16 for <v6ops@ietf.org>; Wed,  5 Sep 2018 14:50:57 -0700 (PDT)
Received: by mail-it0-f65.google.com with SMTP id e14-v6so12048394itf.1 for <v6ops@ietf.org>; Wed, 05 Sep 2018 14:50:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KpJg++vQbRBZYcB5fHmAl2r49wcv+7azXErruep6x0E=; b=DHV9HLMysZWGCZb5CdDB69XmavkNzhyeNTEmhI5EY87ZX/x6yeTXUl10hnFxff0RyS qj9P2Dlia3n9Jusz5HYh1EhN+6EQq+THgZBXqyzAveyYJ8othG5LJr1fzkcD+3Rg+8IN p1tcn+OMlHeSfUiyOd4Ul7UmPpvadbR6tGAcoWc9vkChDsfUd1zaGv1ui0h1gKPoHZJL bCEMYXnf53GiK0D8b4YVDzIrAOPm+TT3ZhFvKQ4/oQAcD9+9Vic1eOh7mHtmeMJ61oFe c/5M50a0ccvINTk6UJB/Gq+5ghM6nyyP8iTS1J9K39blvVz8vPVeVmltvCeU8BU5Fm/B 2hcw==
X-Gm-Message-State: APzg51A9sL6eJsqUoRPar7aTy8jX3nQdHs06oVWWGcn8dMEUUw4eQLll AUfMAF0ucnYDyyprgf3gPRUh7esFCxbCDLjX5dQ=
X-Google-Smtp-Source: ANB0VdZ9LEdjpKQLpsDneBNM8JBXN8JQHicr7HjBLI5lmg9QLa7CLoPXN9xbJjeCe+ptAAvXjfWMBE15MOS6WoaF19A=
X-Received: by 2002:a24:17d2:: with SMTP id 201-v6mr373772ith.0.1536184256517;  Wed, 05 Sep 2018 14:50:56 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com>
From: Erik Nygren <erik+ietf@nygren.org>
Date: Wed, 5 Sep 2018 17:50:44 -0400
Message-ID: <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com>
To: rbonica@juniper.net
Cc: "v6ops@ietf.org list" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eb5cce057526c4a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mm0mVn1yEgXluX_miRr_vulVmp4>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 21:50:59 -0000

--000000000000eb5cce057526c4a0
Content-Type: text/plain; charset="UTF-8"

DNSSEC isn't the only threat here.  Clients implementing protocols such as
DoH also bypass the DNS64.
draft-ietf-doh-dns-over-https-14 does say:

   Local policy considerations and similar factors mean different DNS
   servers may provide different results to the same query, for instance
   in split DNS configurations [RFC6950].  It logically follows that the
   server that is queried can influence the end result.  Therefore a
   client's choice of DNS server may affect the responses it gets to its
   queries.  For example, in the case of DNS64 [RFC6147], the choice
   could affect whether IPv6/IPv4 translation will work at all.

I'm not sure what the best way to approach this is in this draft.  For
example:

* Acknowledge that DNS64 is a shortish-term hack that only works in
constrained environments.     If this is the case, that might argue that
this draft should be at most Informational and not BCP?

* Commit to DNS64 being a robust part of the architecture and cover topics
more broadly than just DNSSEC?   Is there a way to handle the DOH case
short of mandating that clients implementing DOH also do bump-in-the-API or
client-side DNS64 synthesis or 464xlat?  If this is the case, should there
be more firm wording in draft-ietf-doh-dns-over-https-14.  I suspect other
conflicts will also appear over time.

Is there really value in picking some middle ground between these?

Is there concrete data on how often DNSSEC and DNS64 cause interaction
issues and where?  They shouldn't on the recursive resolver itself.  How
often are clients redoing DNSSEC validation and running into issues here?

A separate pragmatic/cynic question is whether we think this will influence
behavior?  I don't have a positive feeling that those who control whether a
zone has DNSSEC enabled also have control over whether AAAA records are
present for dual-stacked content in the zone.  Those are often separate
actors.  Will a recommendation here have any substantive impact, and is
there an audience who will be able to take action on this?

       Erik




On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica <rbonica@juniper.net> wrote:

> Folks,
>
> Each week between now and IETF 103, we will review and discuss one draft
> with an eye towards progressing it.
>
> This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
>
>                                       Fred and Ron
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--000000000000eb5cce057526c4a0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">DNSSEC isn&#39;t the only threat here.=C2=A0 Clients imple=
menting protocols such as DoH also bypass the DNS64.<br>draft-ietf-doh-dns-=
over-https-14 does say:<br><br>=C2=A0 =C2=A0Local policy considerations and=
 similar factors mean different DNS<br>=C2=A0 =C2=A0servers may provide dif=
ferent results to the same query, for instance<br>=C2=A0 =C2=A0in split DNS=
 configurations [RFC6950].=C2=A0 It logically follows that the<br>=C2=A0 =
=C2=A0server that is queried can influence the end result.=C2=A0 Therefore =
a<br>=C2=A0 =C2=A0client&#39;s choice of DNS server may affect the response=
s it gets to its<br>=C2=A0 =C2=A0queries.=C2=A0 For example, in the case of=
 DNS64 [RFC6147], the choice<br>=C2=A0 =C2=A0could affect whether IPv6/IPv4=
 translation will work at all.<br><br>I&#39;m not sure what the best way to=
 approach this is in this draft.=C2=A0 For example:<br><br>* Acknowledge th=
at DNS64 is a shortish-term hack that only works in constrained environment=
s. =C2=A0 =C2=A0 If this is the case, that might argue that this draft shou=
ld be at most Informational and not BCP? <br><br>* Commit to DNS64 being a =
robust part of the architecture and cover topics more broadly than just DNS=
SEC? =C2=A0 Is there a way to handle the DOH case short of mandating that c=
lients implementing DOH also do bump-in-the-API or client-side DNS64 synthe=
sis or 464xlat?=C2=A0 If this is the case, should there be more firm wordin=
g in draft-ietf-doh-dns-over-https-14.=C2=A0 I suspect other conflicts will=
 also appear over time.<br><br>Is there really value in picking some middle=
 ground between these?<br><br>Is there concrete data on how often DNSSEC an=
d DNS64 cause interaction issues and where?=C2=A0 They shouldn&#39;t on the=
 recursive resolver itself.=C2=A0 How often are clients redoing DNSSEC vali=
dation and running into issues here?<br><br>A separate pragmatic/cynic ques=
tion is whether we think this will influence behavior?=C2=A0 I don&#39;t ha=
ve a positive feeling that those who control whether a zone has DNSSEC enab=
led also have control over whether AAAA records are present for dual-stacke=
d content in the zone.=C2=A0 Those are often separate actors.=C2=A0 Will a =
recommendation here have any substantive impact, and is there an audience w=
ho will be able to take action on this?<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0E=
rik<div dir=3D"ltr"><br><div class=3D"gmail_default" style=3D"font-family:t=
ahoma,sans-serif"><pre class=3D"gmail-newpage"> <br></pre><pre class=3D"gma=
il-newpage"><br></pre></div></div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr">On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica &lt;<a href=3D"mail=
to:rbonica@juniper.net">rbonica@juniper.net</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">Folks,<br>
<br>
Each week between now and IETF 103, we will review and discuss one draft wi=
th an eye towards progressing it.<br>
<br>
This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Fred and Ron<br=
>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div>

--000000000000eb5cce057526c4a0--


From nobody Wed Sep  5 14:55:42 2018
Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0FF5130E0C for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 14:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 w16jgnUqAhxC for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 14:55:37 -0700 (PDT)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 9B586127332 for <v6ops@ietf.org>; Wed,  5 Sep 2018 14:55:37 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 21809FBC for <v6ops@ietf.org>; Wed,  5 Sep 2018 21:55:36 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWBI52YuydsG for <v6ops@ietf.org>; Wed,  5 Sep 2018 16:55:35 -0500 (CDT)
Received: from mail-vk0-f70.google.com (mail-vk0-f70.google.com [209.85.213.70]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id C4789C9C for <v6ops@ietf.org>; Wed,  5 Sep 2018 16:55:35 -0500 (CDT)
Received: by mail-vk0-f70.google.com with SMTP id o62-v6so3233688vko.1 for <v6ops@ietf.org>; Wed, 05 Sep 2018 14:55:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Q91wPtfzSV4c6ZbiIPdDq/xaNdqBDvZ29r7XYEikAfE=; b=C6sLl5lNJCCoMh7xYma9IYBbYB8g4B2B0oomFB1R7QPseLXAawnmVdbi1sjJilHRAj l7isRfcF9JsTFPfsM08wTkhNdxziz0++uWg2SBhMqNXorJTCxp4ceueKbP29NfpQfUhC Q3Yhq5MXYuWBTj+V1ulRe608KFxoJ9VfizipFSYoEcMDaBCSk4sCMe4F4DqpOZVMpiij yZ5vGz6guLcIoUam/9vBEQmdCODzZJ2BJF8CiBpso/ICxTe3AXHnIlo8LsfWzR+H9hpV fZ+l+jAfGdrrWOAOFrzQN6anXnPWYtfPUgNXsisPn6UW+blG+T3GMFG0n/GNidT6ZVPj qxaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Q91wPtfzSV4c6ZbiIPdDq/xaNdqBDvZ29r7XYEikAfE=; b=eTYcOYBbvSdkKejwhxcGr93zrgcyriAdUWMA+HGXuK7djXuC7or46CrUomLCvlr3QY K+vJFu7bVbKEp71kkRZDeovLL+QK53OjvvS+qeqd1n2shBqvta/+Bas8rrSW6PcjcZso AKDwrGoZsiNDm2fPm3tY940b9CYnkGtcXUreYxX2CEpFpBOcxJcs57nxPCB6IP48sHQS joVOlyw0KZrPIZPwOrWdFKdr9HWYqfwei23CZxNOjupuAAR9lDsD/dSXUDHbP/lczNBf dYF7Q7E6I1C8mlgdRItCbJWZLx0m04Dhd2f4Brw4/sJp3502Tu0E9qONeAjHoqDXsfo5 AsIQ==
X-Gm-Message-State: APzg51C1OxeGb+pYbvT7uXHBiVHrMayXujpntxANFErIrWe5Fg6HdA5X Xlq2u/EZ5bDVYgx6eAWlOZtDDKM5MOlKc52fW7OsTAIlZylakQFj4joA/USCl1EiysdM55HUPGQ fX7tfFAw7jfxQu+Pfz0XEU/c7WA==
X-Received: by 2002:ab0:5339:: with SMTP id x54-v6mr20209770uax.187.1536184534855;  Wed, 05 Sep 2018 14:55:34 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdbZoC4USErQvxjP/EXQe8ZZE0lWDfHIG9o1ZnyqcPRkz+AWmgl2YwCVgmWPvy8Cmse5Aus9mRhD7x1o6k/uqgI=
X-Received: by 2002:ab0:5339:: with SMTP id x54-v6mr20209760uax.187.1536184534449;  Wed, 05 Sep 2018 14:55:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a67:6042:0:0:0:0:0 with HTTP; Wed, 5 Sep 2018 14:55:33 -0700 (PDT)
In-Reply-To: <a82ff425-5f15-e0d7-50ae-3f72137f73d3@asgard.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <a82ff425-5f15-e0d7-50ae-3f72137f73d3@asgard.org>
From: David Farmer <farmer@umn.edu>
Date: Wed, 5 Sep 2018 16:55:33 -0500
Message-ID: <CAN-Dau17RMv=Rdf71O8sU0KF_xk8Yi_Y4Smb5W4hv-Nv_99GNw@mail.gmail.com>
To: Lee Howard <lee@asgard.org>
Cc: V6 Ops List <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007c588c057526d560"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mEznlSCcHxLG30f96gklyuKMYGI>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 21:55:40 -0000

--0000000000007c588c057526d560
Content-Type: text/plain; charset="UTF-8"

I like this draft, I also agree with Lee's suggestions, I was going to make
one or two of them myself. I think changing it to BCP is a great idea and
making it a normative recommendation too boot. It probably wouldn't hurt to
pass it by the DNS guys too. It is really both an IPv6 and DNS (DNSSEC) BCP.

One comment below.

On Wed, Sep 5, 2018 at 3:34 PM, Lee Howard <lee@asgard.org> wrote:

> I think this document should be BCP, not Informational.
>
...


> For instance, in Security Considerations:
> "If clients trust RRs that fail validation (because they were invented by
> an DNS64 server), there is increased risk that they will trust other RRs
> that fail validation. Further, a compromised or hostile man-in-the-middle
> DNS64 server will be undetected, despite DNSSEC signing."
> In Section 2, I admit I don't know what a client actually sees, if
> anything. Do browsers or other applications warn that a name failed
> validation?
>

I use a browser plugin, it gives you a green icon if DNSSEC validates. It
is grey most of the time as most sites don't do DNSSEC signing. RED icon if
DNSSEC is invalid.  To be honest I don't pay as much attention to it as I
should since it is grey most of the time.

https://www.dnssec-validator.cz/


> I'm sure I can test it tomorrow. I don't know how to inform users or their
> content providers that "This record cannot be guaranteed to be accurate,
> since it failed DNS Security validation. It appears to be a synthetic
> record, since the name only has an IPv4 record."
>

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

--0000000000007c588c057526d560
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">I like this draft, I als=
o agree with Lee&#39;s suggestions, I was going to make one or two of them =
myself. I think changing it to BCP is a great idea and making it a normativ=
e recommendation too boot. It probably wouldn&#39;t hurt to pass it by the =
DNS guys too. It is really both an IPv6 and DNS (DNSSEC) BCP.<br><br>One co=
mment below.<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Sep 5, 2018 at 3:34 PM, Lee Howard <span dir=3D"ltr">&l=
t;<a href=3D"mailto:lee@asgard.org" target=3D"_blank">lee@asgard.org</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <p>I think this document should be BCP, not Informational.</p></div></b=
lockquote><div>...</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div bgcolor=3D"#FFFFFF">
    For instance, in Security Considerations:<br>
    &quot;If clients trust RRs that fail validation (because they were
    invented by an DNS64 server), there is increased risk that they will
    trust other RRs that fail validation. Further, a compromised or
    hostile man-in-the-middle DNS64 server will be undetected, despite
    DNSSEC signing.&quot;<br>
    In Section 2, I admit I don&#39;t know what a client actually sees, if
    anything. Do browsers or other applications warn that a name failed
    validation? </div></blockquote><div><div><br></div><div>I use a browser=
 plugin, it gives you a green icon if DNSSEC validates. It is grey most of =
the time as most sites don&#39;t do DNSSEC signing. RED icon if DNSSEC is i=
nvalid.=C2=A0 To be honest I don&#39;t pay as much attention to it as I sho=
uld since it is grey most of the time.</div><div><br></div><div><a href=3D"=
https://www.dnssec-validator.cz/">https://www.dnssec-validator.cz/</a></div=
></div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div bgcolor=3D"#FFFFFF">I&#39;m sure I can test it tomorrow. I don&#39;=
t know how to
    inform users or their content providers that &quot;This record cannot b=
e
    guaranteed to be accurate, since it failed DNS Security validation.
    It appears to be a synthetic record, since the name only has an IPv4
    record.&quot;<br></div></blockquote></div><div><br></div>-- <br><div cl=
ass=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Em=
ail:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>Of=
fice of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2=
218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Min=
neapolis, MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
</div></div></div></div></div>

--0000000000007c588c057526d560--


From nobody Wed Sep  5 15:14:55 2018
Return-Path: <prvs=1786a3a8e2=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E768130DC2 for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 15:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 e-hQ6c3q0gNh for <v6ops@ietfa.amsl.com>; Wed,  5 Sep 2018 15:14:50 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98407127332 for <v6ops@ietf.org>; Wed,  5 Sep 2018 15:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1536185682; x=1536790482; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type; bh=sHu8K+Eg+c6O7joqXCvRignPRFtE4eAMjV Kl08ZMf9g=; b=Xn54xSaUpfipmImkcOdu2gepg83pL+e2Ev+TiXFu/D+nZmFEhz p3fl3iPyyNVtAqQLIu8x6hUU5OA1pyhhzM3YNCyxTIo1bqIT97WWkNDYc722ziIr leoMavgbM6PtEAQwxF7huMvASqbEBcjuKeJM1mhEc2ub1m16ybMmSkH9s=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 06 Sep 2018 00:14:42 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 06 Sep 2018 00:14:41 +0200
Received: from [10.10.0.101] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005872570.msg for <v6ops@ietf.org>; Thu, 06 Sep 2018 00:14:41 +0200
X-MDRemoteIP: 2404:2200:ff00:1:250:b6ff:fe19:7b3e
X-MDHelo: [10.10.0.101]
X-MDArrival-Date: Thu, 06 Sep 2018 00:14:41 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1786a3a8e2=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.0.180812
Date: Thu, 06 Sep 2018 09:14:31 +1100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Lee Howard <lee@asgard.org>, <v6ops@ietf.org>
Message-ID: <8B7A91D7-EF42-46E9-A9DF-FF6B2A8BE091@consulintel.es>
Thread-Topic: [v6ops] draft-byrne-v6ops-dnssecaaaa
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <a82ff425-5f15-e0d7-50ae-3f72137f73d3@asgard.org>
In-Reply-To: <a82ff425-5f15-e0d7-50ae-3f72137f73d3@asgard.org>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3619070075_2068428495"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/EkHpsBT4jinN7y7ufzT22ayGTL0>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Sep 2018 22:14:53 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3619070075_2068428495
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

I=E2=80=99ve a similar document in sunset4.

=20

Maybe we want to combine both of them, now that sunset4 is sleeping ...

=20

https://tools.ietf.org/html/draft-palet-sunset4-ipv6-ready-dns-00


Regards,

Jordi

=20

=20

=20

De: v6ops <v6ops-bounces@ietf.org> en nombre de Lee Howard <lee@asgard.org>
Fecha: jueves, 6 de septiembre de 2018, 7:35
Para: <v6ops@ietf.org>
Asunto: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa

=20

I think this document should be BCP, not Informational.

Section 2

s/mechanism/mechanisms in the first instance in the first sentence.

How is HEv2 a transition mechanism?

I'd rephrase to say, "DNS64 is a key part of widely deployed IPv6-only tran=
sition mechanisms, including several large 464xlat [RFC6877] deployments, a=
nd all NAT64 deployments." I think that clarifies that we're talking about =
specific deployments here.

Since the discussion of DNSSEC in RFC6147 is so brief, I think it's worth d=
iscussing here, so the explanation of why it is an insufficient workaround =
is sufficient. I'd like to replace the last sentence of section 2 with a ne=
w paragraph:

RFC6147 ("DNSSEC") outlines how validation may occur in the presence of DNS=
SEC:

An existing DNSSEC validator (i.e., one that is unaware of DNS64)=20
=C2=A0=C2=A0=C2=A0might reject all the data that comes from DNS64 as having=
 been
=C2=A0=C2=A0 tampered with (even if it did not set CD when querying).=C2=A0=
 If it is
=C2=A0=C2=A0 necessary to have validation behind the DNS64, then the valida=
tor
=C2=A0=C2=A0 must know how to perform the DNS64 function itself.=C2=A0 Alte=
rnatively,
=C2=A0=C2=A0 the validating host may establish a trusted connection with a =
DNS64,
=C2=A0=C2=A0 and allow the DNS64 recursive resolver to do all validation on=
 its
=C2=A0=C2=A0 behalf. [RFC6147 - DNS64]

However, the domain administrator has no control over the client doing the =
validating, and clients (or their validating resolvers) cannot be expected =
to know about the presence of DNS64 a priori. Clients who might trust an au=
thoritative name server for some content may not be as trusting of their ca=
rrier's DNS64 server.

Section 3

s/to changes/to change
s/not recommend/not recommended
To soften the blow, I'd suggest adding a sentence, after "in tandem."  "The=
 IPv6 deployment may be as light weight as a translator, such as SIIT-DC [R=
FC7755]."


There's more I'd add to the document, and it's the "So what?"

For instance, in Security Considerations:
"If clients trust RRs that fail validation (because they were invented by a=
n DNS64 server), there is increased risk that they will trust other RRs tha=
t fail validation. Further, a compromised or hostile man-in-the-middle DNS6=
4 server will be undetected, despite DNSSEC signing."
In Section 2, I admit I don't know what a client actually sees, if anything=
. Do browsers or other applications warn that a name failed validation? I'm=
 sure I can test it tomorrow. I don't know how to inform users or their con=
tent providers that "This record cannot be guaranteed to be accurate, since=
 it failed DNS Security validation. It appears to be a synthetic record, si=
nce the name only has an IPv4 record."


Even though my comments are longer than the draft, I like this effort, and =
wish I had initiated it.

Lee

On 09/05/2018 11:28 AM, Ron Bonica wrote:
Folks,
=20
Each week between now and IETF 103, we will review and discuss one draft wi=
th an eye towards progressing it.
=20
This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
=20
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Fr=
ed and Ron
=20
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

_______________________________________________ v6ops mailing list v6ops@ie=
tf.org https://www.ietf.org/mailman/listinfo/v6ops=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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.


--B_3619070075_2068428495
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft=
 Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML con formato previo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.HTMLconformatoprevioCar
	{mso-style-name:"HTML con formato previo Car";
	mso-style-priority:99;
	mso-style-link:"HTML con formato previo";
	font-family:Consolas;}
span.EstiloCorreo21
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue vlink=
=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US=
 style=3D'mso-fareast-language:EN-US'>I=E2=80=99ve a similar document in su=
nset4.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=
=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span lang=3DEN-US style=3D'mso-fareast-language:EN-US'>Maybe we want=
 to combine both of them, now that sunset4 is sleeping ...<o:p></o:p></span=
></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-language:=
EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:EN-US'>https://tools.ietf.org/html/draft-pale=
t-sunset4-ipv6-ready-dns-00<o:p></o:p></span></p><div><p class=3DMsoNormal>=
<span lang=3DEN-US style=3D'font-size:10.5pt;color:black'><br></span><span =
lang=3DES-TRAD style=3D'font-size:10.5pt;color:black'>Regards,<o:p></o:p></=
span></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span lang=3DE=
S-TRAD style=3D'font-size:10.5pt;color:black;mso-fareast-language:EN-US'>Jo=
rdi<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt=
'><span lang=3DES-TRAD style=3D'font-size:10.5pt;color:black;mso-fareast-la=
nguage:EN-US'><o:p>&nbsp;</o:p></span></p></div><p class=3DMsoNormal><span =
lang=3DES-TRAD style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span lang=3DES-TRAD style=3D'mso-fareast-languag=
e:EN-US'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-top:s=
olid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal style=3D=
'margin-left:35.4pt'><b><span style=3D'font-size:12.0pt;color:black'>De: </=
span></b><span style=3D'font-size:12.0pt;color:black'>v6ops &lt;v6ops-bounc=
es@ietf.org&gt; en nombre de Lee Howard &lt;lee@asgard.org&gt;<br><b>Fecha:=
 </b>jueves, 6 de septiembre de 2018, 7:35<br><b>Para: </b>&lt;v6ops@ietf.o=
rg&gt;<br><b>Asunto: </b>Re: [v6ops] draft-byrne-v6ops-dnssecaaaa<o:p></o:p=
></span></p></div><div><p class=3DMsoNormal style=3D'margin-left:35.4pt'><o=
:p>&nbsp;</o:p></p></div><p style=3D'margin-left:35.4pt'>I think this docum=
ent should be BCP, not Informational.<o:p></o:p></p><p style=3D'margin-left=
:35.4pt'>Section 2<o:p></o:p></p><p style=3D'margin-left:35.4pt'>s/mechanis=
m/mechanisms in the first instance in the first sentence.<o:p></o:p></p><p =
style=3D'margin-left:35.4pt'>How is HEv2 a transition mechanism?<o:p></o:p>=
</p><p style=3D'margin-left:35.4pt'>I'd rephrase to say, &quot;DNS64 is a k=
ey part of widely deployed IPv6-only transition mechanisms, including sever=
al large 464xlat [RFC6877] deployments, and all NAT64 deployments.&quot; I =
think that clarifies that we're talking about specific deployments here.<o:=
p></o:p></p><p style=3D'mso-margin-top-alt:5.0pt;margin-right:0cm;margin-bo=
ttom:12.0pt;margin-left:35.4pt'>Since the discussion of DNSSEC in RFC6147 i=
s so brief, I think it's worth discussing here, so the explanation of why i=
t is an insufficient workaround is sufficient. I'd like to replace the last=
 sentence of section 2 with a new paragraph:<o:p></o:p></p><p style=3D'marg=
in-left:35.4pt'>RFC6147 (&quot;DNSSEC&quot;) outlines how validation may oc=
cur in the presence of DNSSEC:<o:p></o:p></p><p class=3DMsoNormal style=3D'=
margin-left:35.4pt'>An existing DNSSEC validator (i.e., one that is unaware=
 of DNS64) <o:p></o:p></p><pre style=3D'margin-left:35.4pt'><span style=3D'=
color:black'>=C2=A0=C2=A0=C2=A0might reject all the data that comes from DN=
S64 as having been<o:p></o:p></span></pre><pre style=3D'margin-left:35.4pt'=
><span style=3D'color:black'>=C2=A0=C2=A0 tampered with (even if it did not=
 set CD when querying).=C2=A0 If it is<o:p></o:p></span></pre><pre style=3D=
'margin-left:35.4pt'><span style=3D'color:black'>=C2=A0=C2=A0 necessary to =
have validation behind the DNS64, then the validator<o:p></o:p></span></pre=
><pre style=3D'margin-left:35.4pt'><span style=3D'color:black'>=C2=A0=C2=A0=
 must know how to perform the DNS64 function itself.=C2=A0 Alternatively,<o=
:p></o:p></span></pre><pre style=3D'margin-left:35.4pt'><span style=3D'colo=
r:black'>=C2=A0=C2=A0 the validating host may establish a trusted connectio=
n with a DNS64,<o:p></o:p></span></pre><pre style=3D'margin-left:35.4pt'><s=
pan style=3D'color:black'>=C2=A0=C2=A0 and allow the DNS64 recursive resolver to d=
o all validation on its<o:p></o:p></span></pre><pre style=3D'margin-left:35=
.4pt'><span style=3D'color:black'>=C2=A0=C2=A0 behalf. [RFC6147 - DNS64]<o:=
p></o:p></span></pre><p class=3DMsoNormal style=3D'mso-margin-top-alt:0cm;m=
argin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><br>However, the d=
omain administrator has no control over the client doing the validating, an=
d clients (or their validating resolvers) cannot be expected to know about =
the presence of DNS64 a priori. Clients who might trust an authoritative na=
me server for some content may not be as trusting of their carrier's DNS64 =
server.<br><br>Section 3<br><br>s/to changes/to change<br>s/not recommend/n=
ot recommended<br>To soften the blow, I'd suggest adding a sentence, after =
&quot;in tandem.&quot;&nbsp; &quot;The IPv6 deployment may be as light weig=
ht as a translator, such as SIIT-DC [RFC7755].&quot;<br><br><br>There's mor=
e I'd add to the document, and it's the &quot;So what?&quot;<br><br>For ins=
tance, in Security Considerations:<br>&quot;If clients trust RRs that fail =
validation (because they were invented by an DNS64 server), there is increa=
sed risk that they will trust other RRs that fail validation. Further, a co=
mpromised or hostile man-in-the-middle DNS64 server will be undetected, des=
pite DNSSEC signing.&quot;<br>In Section 2, I admit I don't know what a cli=
ent actually sees, if anything. Do browsers or other applications warn that=
 a name failed validation? I'm sure I can test it tomorrow. I don't know ho=
w to inform users or their content providers that &quot;This record cannot =
be guaranteed to be accurate, since it failed DNS Security validation. It a=
ppears to be a synthetic record, since the name only has an IPv4 record.&qu=
ot;<br><br><br>Even though my comments are longer than the draft, I like th=
is effort, and wish I had initiated it.<br><br>Lee<br><br><o:p></o:p></p><d=
iv><p class=3DMsoNormal style=3D'margin-left:35.4pt'>On 09/05/2018 11:28 AM=
, Ron Bonica wrote:<o:p></o:p></p></div><blockquote style=3D'margin-top:5.0=
pt;margin-bottom:5.0pt'><pre style=3D'margin-left:35.4pt'>Folks,<o:p></o:p>=
</pre><pre style=3D'margin-left:35.4pt'><o:p>&nbsp;</o:p></pre><pre style=
=3D'margin-left:35.4pt'>Each week between now and IETF 103, we will review =
and discuss one draft with an eye towards progressing it.<o:p></o:p></pre><=
pre style=3D'margin-left:35.4pt'><o:p>&nbsp;</o:p></pre><pre style=3D'margi=
n-left:35.4pt'>This week, please review and comment on draft-byrne-v6ops-dn=
ssecaaaa.<o:p></o:p></pre><pre style=3D'margin-left:35.4pt'><o:p>&nbsp;</o:=
p></pre><pre style=3D'margin-left:35.4pt'>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Fred and Ron<o:p></o:p></pre><pre s=
tyle=3D'margin-left:35.4pt'><o:p>&nbsp;</o:p></pre><pre style=3D'margin-lef=
t:35.4pt'>_______________________________________________<o:p></o:p></pre><=
pre style=3D'margin-left:35.4pt'>v6ops mailing list<o:p></o:p></pre><pre st=
yle=3D'margin-left:35.4pt'><a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org=
</a><o:p></o:p></pre><pre style=3D'margin-left:35.4pt'><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v=
6ops</a><o:p></o:p></pre></blockquote><p class=3DMsoNormal style=3D'margin-=
left:35.4pt'><br>_______________________________________________ v6ops mail=
ing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops <o:p></=
o:p></p></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.consulintel.es<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.<br>
<br>
</body></html>

--B_3619070075_2068428495--


From nobody Thu Sep  6 03:27:27 2018
Return-Path: <lorenzo@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B11E130E5E for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 03:27:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level: 
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 mM5iwLlRzLMO for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 03:27:23 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 9C310130E5A for <v6ops@ietf.org>; Thu,  6 Sep 2018 03:27:23 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id h3-v6so14031860ita.2 for <v6ops@ietf.org>; Thu, 06 Sep 2018 03:27:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wCidJl5AD5tUsJvHuBAxdVZBj0tKL8OmJTCxphY8M9I=; b=JELO95B8cWUvN/qU5DktxCXCq+BIs17MgUWsf0PMeeTF25xTgDk2lTVNiSCtEKeeDk EhVV6JY2r12edRudPsrpDc1EbKlSVIUfGajP3E0iW2+d5zKGpaoNlMeZkP2B+NjxkzG0 +XYbHdC+f9SmBEF0Z+LDLH3NOvTKjvqTWbkm5fnqtLPfhTIBdWSY8SwowD8DVkDJg7/q cTEo0Olnyy9+4LAk+LYKIWPa54T3gCV9E03C222ymdw+C3ER54FtdSjI/oDvwJoiQlk4 lQ0gb7lnbEih3vofMOLS8OgN5e5hwh0s+oC3jo6U1kbpkkuE7ewdueTTslNGTOtWwuYu B7Ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wCidJl5AD5tUsJvHuBAxdVZBj0tKL8OmJTCxphY8M9I=; b=S7oCKdeCPcImKz44yjPHwq4FVQh0xv60yWSHoUk4qVcaFxEtZS9qEV7H5PH/O0/4sr rzi7yULNDNeB02EcYv7Dgf62JJA/OeX7gsLIFzML/b3ltsWvFd2wxTNj5JtDGJoJHHk/ HKVmPfin5IaDeCSZ4VzO/z0Syeio1eFkp5q+KiQmFOhMi3CXW++dmtOkXW6g/5ApRVUF fAMCGm6XAdjGnW38c9DQlVWfLwBbFN7KrHVtwL2lZqwWMKu/9EFmgz3E2hwWKSrHfhL3 SIX3Ma+KCYtDlSVaO+icp1I9xquPYal68a+RcO813pF5cf9LXRNjnuFDXOVrQOfNFw44 +DnA==
X-Gm-Message-State: APzg51DrAaqPfNZxukAMnCFKPFbtPJEOg67nG2G6BJLgly8YctWO0/k4 0PvkNe9ngV1mxmkeTdy0qCGE5yiJVzq9X0gWpZcKMXtv3hNSeQ==
X-Google-Smtp-Source: ANB0VdYW6TRfPR5rM8GCToBkDk8+mXCDFUCI38T4Zvm1psR+/ej3a3/r7VVNeEYQmAey9EbyysppBHjrWaUw15kYaJ4=
X-Received: by 2002:a02:c4c6:: with SMTP id h6-v6mr1503624jaj.26.1536229642568;  Thu, 06 Sep 2018 03:27:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAAObRXLe35KoONVsSO_oU+SRhMzMrKRE_SU-QNf2pGHYKpUrxA@mail.gmail.com> <2018082709132233449033@chinatelecom.cn> <CAKD1Yr3PFKC06vwALL9Pjyd8Ji-RnqPR-HMvLA6CS6cyDadzVw@mail.gmail.com> <CAAObRXJx-8cPYuU-5gSMCvoOX-m29Q5BZg1-GANXBV-2Zmjv0A@mail.gmail.com> <CAKD1Yr24fXHsRTwFErNGc+RYzXDfHFpF6zG5QFjfjS+xx5-9Mg@mail.gmail.com> <CAAObRXK3jx_FXi-Rt5W3iSkOrf8zmc2z0NC1hUoET=AMFj2sig@mail.gmail.com> <CAAedzxouJUY1-R2NQH8sMDA0vrkOSznOWUaykBtdMy5a5Cup4g@mail.gmail.com> <34329770-1e00-be97-8443-79448be367cb@gmail.com> <201808271339136864338@chinatelecom.cn> <CAD6AjGReSzm0GHwFO74KL8R0F5Ahwd6c0s3bn2PtCyDTo-MPCw@mail.gmail.com> <CAAedzxrDjTO=BSsBGdgbaDRmhCUuB6frtV_oRE-+vNu5tsA5+Q@mail.gmail.com> <48B470F2-3F62-4D3F-90ED-C80A752AB61F@isc.org> <CAAedzxqfmODSBbnzSEg0hH+W+ovoDXcgmUjo+XUySiZFrxVcUg@mail.gmail.com> <D02DED65-CFDB-4ABE-A2C1-AA75440F19A8@isc.org> <7BC525AA-90F2-4477-BF1A-FB1FC80B8AF5@cisco.com> <c3df5aa5-4070-d16f-9c0d-684adb5f40e8@asgard.org> <7B6307F1-19C8-4D80-A32A-973E0F3CA4F7@cisco.com>
In-Reply-To: <7B6307F1-19C8-4D80-A32A-973E0F3CA4F7@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 6 Sep 2018 19:27:11 +0900
Message-ID: <CAKD1Yr0TzX_KUh_h71JJZwKSS_QknDsmVOqeCFmAZoW0Lz3OkQ@mail.gmail.com>
To: rajiva=40cisco.com@dmarc.ietf.org
Cc: Lee Howard <lee@asgard.org>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002406eb0575315620"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OXKF-ppVHR7804C2PChdt-Br-DA>
Subject: Re: [v6ops] How my Android phone got assigned with IPv6 address via 4G LTE?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 10:27:25 -0000

--0000000000002406eb0575315620
Content-Type: text/plain; charset="UTF-8"

On Thu, Sep 6, 2018 at 4:53 AM Rajiv Asati (rajiva) <rajiva=
40cisco.com@dmarc.ietf.org> wrote:

> BTW, section 2.3.2
> https://tools.ietf.org/html/draft-ietf-dnsop-isp-ip6rdns-05#section-2.3.2
> reminded me of the solution described here for tracking MAC-IP address
> coupling in environments such as those of enterprises etc.
>
>
>
>
> https://tools.ietf.org/html/draft-asati-dhc-ipv6-autoconfig-address-tracking
>

I wonder if it's time to revive that draft? It would seem to be the easiest
solution to support address tracking in existing architectures built around
DHCP, and could facilitate enterprise networks transitioning from IPv4 to
IPv6.

--0000000000002406eb0575315620
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"lt=
r">On Thu, Sep 6, 2018 at 4:53 AM Rajiv Asati (rajiva) &lt;rajiva=3D<a href=
=3D"mailto:40cisco.com@dmarc.ietf.org">40cisco.com@dmarc.ietf.org</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-3491792704977201122WordSection1">
<p class=3D"MsoNormal">BTW, section 2.3.2 <a href=3D"https://tools.ietf.org=
/html/draft-ietf-dnsop-isp-ip6rdns-05#section-2.3.2" target=3D"_blank">
https://tools.ietf.org/html/draft-ietf-dnsop-isp-ip6rdns-05#section-2.3.2</=
a> reminded me of the solution described here for tracking MAC-IP address c=
oupling in environments such as those of enterprises etc.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><a href=3D"https://tools.ietf.org/html/draft-asati-d=
hc-ipv6-autoconfig-address-tracking" target=3D"_blank">https://tools.ietf.o=
rg/html/draft-asati-dhc-ipv6-autoconfig-address-tracking</a></p></div></div=
></blockquote><div><br></div><div>I wonder if it&#39;s time to revive that =
draft? It would seem to be the easiest solution to support address tracking=
 in existing architectures built around DHCP, and could facilitate enterpri=
se networks transitioning from IPv4 to IPv6.</div></div></div></div>

--0000000000002406eb0575315620--


From nobody Thu Sep  6 05:01:29 2018
Return-Path: <lorenzo@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71B0130E6F for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 05:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level: 
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 d7dikj2HPm0d for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 05:01:25 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 1F36D130DFD for <v6ops@ietf.org>; Thu,  6 Sep 2018 05:01:25 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id t71-v6so3992246ybi.7 for <v6ops@ietf.org>; Thu, 06 Sep 2018 05:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2AkDAclQqbB1/R0bYpQzUUK/zwjoPADY/juA9WJcZQY=; b=QtA+UYfznGeed0o+6E7+siUJorUdnLt0Srfdr+q7zhPXbZks/y+mc46XrKesQlvK0w zL/MRvIDmAdGpLQYfRI27st0Js7UNsiR8/TMGGbvzsC/PQmoyzN3K+aJ8hleZLtxjyTk 4ME18cEsPqNr4xVba2oToPa+t4S+8YYdcbrVzr2BLHMd7r0X//w3DS7bZ5PzXUz2+n4R Asa9WuwKacQ2cIlquGUqV98hfERC2qCIIvdvPHxWG3ZYaBnW+lVlpAvkZQn0zHX3AjrS mbgoHq/qb4IGXeiG+EK/P0WRtV9aBITSa5YX4niSk5L7VlxhrQYjF2/vyfHmhZQAaB7d 4hxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2AkDAclQqbB1/R0bYpQzUUK/zwjoPADY/juA9WJcZQY=; b=VrUF4N7uHY/4CvBSZW5DqgQUa3CJ+49uZ//1fr5rUeJeUhCZeWyQ5l8JvZtg8hyOHj l7nIy+xhm+bIBkarUuKyU4x3evZHpHJ3bz0oeNSsG+t6ncfjZvXLqxk3GxEPcv/7t9eF PQl2Nz2dq29DevZbdMHxYZfKGuBiTBrECjZEOA4Y+PVjBcDszidAaAAKLk370QB2ujls 7WFQHpEa+84qlbG+icPu1v6sa1TC23/fE+7qdZZpgWh3NeLJgV4BT2oCHJ8zb1llGoCs hEsZK1oJOyd8Lzs3K1VPnb0jzxwWjlZoJVd2ezf+3HCOgnuLhB8xU040N0P9bNa8x50m vgxQ==
X-Gm-Message-State: APzg51A/UDtHo7mRoaL96RBoK6pR9Y++bvUqiTxhV/vcKTyB+4FQvBWd lGgqeSQRgrU4m//xFaVvnbT19aLfZWlrMeRrnwZl0g==
X-Google-Smtp-Source: ANB0VdbKb48bog4TRgxEekw1834JAg2+iGxFELXo8P7uxqEs7aufV/0VAE7VV5KV87m28Wn3U0VLF1mzzvzuK+/p6eU=
X-Received: by 2002:a25:1345:: with SMTP id 66-v6mr1106962ybt.171.1536235283632;  Thu, 06 Sep 2018 05:01:23 -0700 (PDT)
MIME-Version: 1.0
References: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com> <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com>
In-Reply-To: <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 6 Sep 2018 21:01:10 +0900
Message-ID: <CAKD1Yr3p3mh4OEn2Ai+RZLBGkhusU1Q+5qrjicEM5tjkxe2wiA@mail.gmail.com>
To: Owen DeLong <owen@delong.com>
Cc: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>, Simon Hobson <linux@thehobsons.co.uk>,  "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000601aa0057532a6db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3zsAcDeawUR5gQtrh2QwQv8cuoM>
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 12:01:28 -0000

--000000000000601aa0057532a6db
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 5, 2018 at 11:09 PM Owen DeLong <owen@delong.com> wrote:

> Further, I don=E2=80=99t believe for one second that ALL enterprises will=
 require
> or use DHCPv6. Perhaps most, but certainly not all.
>

+1. Ours doesn't.

--000000000000601aa0057532a6db
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Sep 5,=
 2018 at 11:09 PM Owen DeLong &lt;<a href=3D"mailto:owen@delong.com">owen@d=
elong.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Further,=
 I don=E2=80=99t believe for one second that ALL enterprises will require o=
r use DHCPv6. Perhaps most, but certainly not all. <br></blockquote><div><b=
r></div><div>+1. Ours doesn&#39;t.</div></div></div>

--000000000000601aa0057532a6db--


From nobody Thu Sep  6 07:24:54 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 283D6130E6B for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 07:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 bwzOOlKB3HOI for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 07:24:49 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 492FF120072 for <v6ops@ietf.org>; Thu,  6 Sep 2018 07:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1536243887; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=H4zY/teuyYLRNV7Jt5GkMub/2UQyN8At0xMC9ZgumYc=; b=YNCsY1wZNtCdB9QdoODMYwSIWND11vQXWL5+/53LshHGF1GXX/ajLUk2zpWTk+hSWwwNE46TAFMc1OVaHJjSOLy4RIlSSTTGj5n9t3+vbP6n3KrZHMbBiPFAd3YPFhQY0F8WLtFWuOKWYjB11qxOls+wkt45Rm5BbvYbuc2uXeY=
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-am5eur03lp0119.outbound.protection.outlook.com [213.199.154.119]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-133-0Tby7O8xMsa_UmduhL2C_g-2; Thu, 06 Sep 2018 15:24:43 +0100
Received: from AM0PR07MB4177.eurprd07.prod.outlook.com (52.133.59.156) by AM0PR07MB4417.eurprd07.prod.outlook.com (52.133.52.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1122.13; Thu, 6 Sep 2018 14:24:36 +0000
Received: from AM0PR07MB4177.eurprd07.prod.outlook.com ([fe80::6c7c:fd30:f5e4:cd76]) by AM0PR07MB4177.eurprd07.prod.outlook.com ([fe80::6c7c:fd30:f5e4:cd76%5]) with mapi id 15.20.1122.009; Thu, 6 Sep 2018 14:24:36 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
CC: Owen DeLong <owen@delong.com>, Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
Thread-Index: AQHURdlxSz5KqAaJ1E2xLgVHJ4PZXqTjTviA
Date: Thu, 6 Sep 2018 14:24:36 +0000
Message-ID: <D53C2B7A-C67F-4739-9633-60293DE59932@jisc.ac.uk>
References: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com> <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com> <CAKD1Yr3p3mh4OEn2Ai+RZLBGkhusU1Q+5qrjicEM5tjkxe2wiA@mail.gmail.com>
In-Reply-To: <CAKD1Yr3p3mh4OEn2Ai+RZLBGkhusU1Q+5qrjicEM5tjkxe2wiA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.9.1)
x-originating-ip: [2001:610:9d8:8:a8b6:2be9:35d2:4a33]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM0PR07MB4417; 20:8XgkSDha/i8yY/kOgVB+lWWC9DJ1EMD9j1W/Eg0xjvB8/YlB/PyKhkSSg+t1rWQiurFv4nGBfeEefxz1uERuaqbNxFd3X01q2GmI4M6aD43241f3QLK0o2m0DBiNHwpJ+E2axMur/0oRl0BaDxvrpnSZ+Fq+38Kh8Sm/Rz2eUjM=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 0e3a7b3b-34a7-4a9f-3348-08d614047908
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(5600074)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:AM0PR07MB4417; 
x-ms-traffictypediagnostic: AM0PR07MB4417:
x-microsoft-antispam-prvs: <AM0PR07MB4417653FB540AB0D9BE3A02ED6010@AM0PR07MB4417.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231344)(944501410)(52105095)(10201501046)(3002001)(149027)(150027)(6041310)(20161123558120)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123560045)(201708071742011)(7699049)(76991033); SRVR:AM0PR07MB4417; BCL:0; PCL:0; RULEID:; SRVR:AM0PR07MB4417; 
x-forefront-prvs: 0787459938
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(39850400004)(376002)(346002)(366004)(199004)(189003)(102836004)(99286004)(4326008)(46003)(76176011)(7736002)(786003)(8676002)(81156014)(305945005)(11346002)(36756003)(486006)(446003)(2616005)(74482002)(81166006)(256004)(476003)(6246003)(97736004)(8936002)(83716003)(86362001)(5660300001)(14454004)(25786009)(50226002)(72206003)(6116002)(106356001)(57306001)(2906002)(105586002)(53936002)(82746002)(33656002)(2900100001)(5250100002)(186003)(6436002)(478600001)(316002)(68736007)(54906003)(6512007)(6506007)(6486002)(53546011)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB4417; H:AM0PR07MB4177.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
x-microsoft-antispam-message-info: ekNm+dvMQtXw/oHdsBlkIh+F/x1IOjD/GVFQ5HzSWni3MjTOT2GTFiljscArAmnC6Gdzj+qc9X7HZWdoWlHArQ2ezhfHHDMh2FBxsvRgnSDAen+awWCEf7p3aVhX2HH3dAv+e+jkliKG3pCWQVVTLAR5qej3HZuZ/HrJU/BnGKfvqcR/225ljzJXctROk2dzxts7VAXWaV3xnHXN+ZT/3CLQ0DawlXOv2WWIxz6qyNhj0aTEOh6L4u4lHYai647HjGxPkrlEzbMMiaA8EagnwynUi+e3fSj2BAZHVXlxGM9oZxavTD+F6OU6op/XwKF0rygQiJF4Hzm5bNnjsvRdNY54a52vtDG4f0sSFWf4tbE=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <C422FB19CDBC1B40998E2EB71B354BE2@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 0e3a7b3b-34a7-4a9f-3348-08d614047908
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2018 14:24:36.1848 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4417
X-MC-Unique: 0Tby7O8xMsa_UmduhL2C_g-2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/KNqkpqoFagAf0g8SgdwpuqflhT0>
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 14:24:52 -0000

PiBPbiA2IFNlcCAyMDE4LCBhdCAxNDowMSwgTG9yZW56byBDb2xpdHRpIDxsb3JlbnpvPTQwZ29v
Z2xlLmNvbUBkbWFyYy5pZXRmLm9yZz4gd3JvdGU6DQo+IA0KPiBPbiBXZWQsIFNlcCA1LCAyMDE4
IGF0IDExOjA5IFBNIE93ZW4gRGVMb25nIDxvd2VuQGRlbG9uZy5jb20+IHdyb3RlOg0KPiBGdXJ0
aGVyLCBJIGRvbuKAmXQgYmVsaWV2ZSBmb3Igb25lIHNlY29uZCB0aGF0IEFMTCBlbnRlcnByaXNl
cyB3aWxsIHJlcXVpcmUgb3IgdXNlIERIQ1B2Ni4gUGVyaGFwcyBtb3N0LCBidXQgY2VydGFpbmx5
IG5vdCBhbGwuIA0KPiANCj4gKzEuIE91cnMgZG9lc24ndC4NCg0KQW5kIHRoZSByZXF1aXJlbWVu
dC91c2Ugb2YgY29uZmlndXJhdGlvbiBtZXRob2QsIGVzcGVjaWFsbHkgYXQgYSB1bml2ZXJzaXR5
IGNhbXB1cywgbWF5IHZhcnkgYmV0d2VlbiBtYW5hZ2VkIGRlc2t0b3BzIGFuZCBXaUZpL2VkdXJv
YW0gd2hlcmUgQllPRCBpcyB0aGUgbm9ybS4gDQoNClRpbQ0KDQo=


From nobody Thu Sep  6 07:31:16 2018
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 910F8130E6D; Thu,  6 Sep 2018 07:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 Zx5Gy57uDHpU; Thu,  6 Sep 2018 07:31:12 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 A5EAC130E6B; Thu,  6 Sep 2018 07:31:12 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w86EOcwA016853; Thu, 6 Sep 2018 07:31:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=KaE2FNAHCUOp9BDxvfRFgXUDrxBrmhHmhzWyhZP7b14=; b=qccMJo2akpvoUtSe6b1gCtO7lOIAuqKBgCC6KxG20BaxlfE28ugUBV20hDdrEyOsNS5E u6ifNAS6RpsjtagGV7TU429qPKDczQgbPOC6xgCIdEWodZBT8k4sh5kCXEg6uvDdYxIz eDxjlFE7m+Fhsvu3lirO44SdLVTEegCnpHpZHJG0SD2aKGmXT2bYpoF3KsgzX+2oBhHo FTyYkujrCVtHihGD8q/pTGxhPRST1bH0gVpIWG5l/cOjHeiLANXj4LC6sbbtZ4A06ddt mlgdSDoqyJ8fW9FsdZsUUHQ5LMKWBhQZB1t/cjnK9H8bMuc5NQgPbYQed0ixoBUHj6kO SA== 
Received: from nam04-bn3-obe.outbound.protection.outlook.com (mail-bn3nam04lp0117.outbound.protection.outlook.com [216.32.180.117]) by mx0b-00273201.pphosted.com with ESMTP id 2man9ashw9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 06 Sep 2018 07:31:11 -0700
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.1122.10; Thu, 6 Sep 2018 14:31:09 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com ([fe80::990e:3cb2:ad57:cd42]) by CO1PR05MB443.namprd05.prod.outlook.com ([fe80::990e:3cb2:ad57:cd42%18]) with mapi id 15.20.1101.016; Thu, 6 Sep 2018 14:31:09 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "draft-ietf-v6ops-transition-ipv4aas@ietf.org" <draft-ietf-v6ops-transition-ipv4aas@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: IPR: draft-ietf-v6ops-transition-ipv4aas-08
Thread-Index: AdRF7iS3QjybnIjPQnarXiF68fx6iQ==
Date: Thu, 6 Sep 2018 14:31:09 +0000
Message-ID: <CO1PR05MB4433992E2D0CE6ADAB4B07EAE010@CO1PR05MB443.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO1PR05MB441; 6:YpC91jMvMOJnM3mxPhuon7exNAzenAqi9rCTEKDIxSfgh7Dh0NmYo8wMJfA3yFb9PAtpTEWfKJDLOawgjDSUS0cJGTeEwjKrBEpw4+Q96zT+45jpi9jdhQjKvhVpvlhQLXYbFuCeaqzMTFq3HkBWUhmEA45VDXvaF+Fx2LOEN9hCSvlvjwyO2xFwJiYGT1Na8nts6+cWsmLOfMRWWMZeCxZri/WY88c/uSeSaK49VoiNk+YYmE6oVH5k+ZQoX2nUgsUFhHmFEGJQCZfoch6My7GiNBHmNs8/evkHWRCWYKDtxTYMnUq3dI1JzveRM6FkKbGthX2BU9t4TTXF8MlvFnD6cxm8Snxzue6TbV1rx1ylXwgloBfCaYonR/U7fM+gHLYcbUzqFynYo+IHTpK61svuqDacRbu869cGhDxJpmqftXFoZ0aH5+xhbz8HVcdtEURNfxeTN8MIEm5RigWRNA==; 5:lvFbG5ejNG7dBaVuEZ6iZrQgoviwrcQw1uQ5X0Nk08CCSgTUKQC1u+m/K1yRKo5MQ1abJtmU5SQ1K0ujCeEclXiT9kn8i3jQr3KcsfKMMzCGVJhWxNF6my8wzW4s6U1jR9FsCJUTVtOnHMQN8g0kWrOefu04dYDC4aob5mP8sPk=; 7:j14s+PfHtras90FCMpQjMGZXlghS5mesycs0qX4H/HeTOMZMBWA/4NwKrELm2pwi1H4i4rvJggfsE1rf134hrRlJrYsJZ23Ki2Q7Tyg5MZHB3dMRMyszUWIBnVmc1iFRca2MhXWvEPjjAFi5j6puLTUA4UP2tYeU+JBA47YoQ8f+jzzkDAws2THvwa50pgkJRWO4jbLmTA7DxmWobJo0kEr+xCBMkWr3h8w4sle1PBzPRqjA1FG3sVNGTaYV8d3C
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: e6415189-10ad-4166-a6bb-08d61405635d
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(4534165)(4627221)(201703031133081)(201702281549075)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:CO1PR05MB441; 
x-ms-traffictypediagnostic: CO1PR05MB441:
x-microsoft-antispam-prvs: <CO1PR05MB441559BB4A82543DDC1AA5AAE010@CO1PR05MB441.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(3231344)(944501410)(52105095)(93006095)(93001095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(201708071742011)(7699049)(76991033); SRVR:CO1PR05MB441; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB441; 
x-forefront-prvs: 0787459938
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(366004)(39860400002)(136003)(396003)(199004)(189003)(68736007)(186003)(55016002)(2900100001)(6436002)(2501003)(5250100002)(450100002)(53936002)(9686003)(33656002)(478600001)(5660300001)(110136005)(8676002)(6346003)(26005)(7736002)(305945005)(256004)(3846002)(6116002)(74316002)(8936002)(14454004)(102836004)(6506007)(7696005)(105586002)(558084003)(86362001)(99286004)(486006)(66066001)(81166006)(81156014)(97736004)(476003)(316002)(2906002)(25786009)(106356001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB443.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: w95til429r/Agut3MpVr8wMpEjNKsHFwHEqD+v/nUvY2BLfjDHbJOhPDo6GJNY1gR3VkHpkxMUuD4eQwhjlvS+5L/WkSyL4UvtWvNVdVtM+u/G2IJIVTcAv+SH5pS4s4yQpLLklOupiPMdt1ig0AXoNyvjBl12N3jK0g6IxMtUQsAGQEq/8o8OOCYGHon+LlxN2BJesdo0HFD9PixK8jC47roYuzMgV8mqlck1raihB+PozNdCWUTt4dOV8jMPVTP1Wpc33cVZ8AP5TdRTb3R7GH5vPc65XAzXVvPrPbtYLzsemIpQRKr9raV1y1OXX7rbY4BVsbqZLTJGh4BMSeLMcROdzGQnCizy5i8BP7TDs=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: e6415189-10ad-4166-a6bb-08d61405635d
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2018 14:31:09.3040 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB441
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-06_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=724 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809060143
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/FEHkg2MoPUhwy8-6pBPFwBabgxY>
Subject: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-08
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 14:31:15 -0000

Co-authors,

Please send mail to the list stating whether you know of any IPR regarding =
draft-ietf-v6ops-transition-ipv4aas-08.

                                                   Ron


From Hans.Liu@dlinkcorp.com  Thu Sep  6 07:51:46 2018
Return-Path: <Hans.Liu@dlinkcorp.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EFF130E86; Thu,  6 Sep 2018 07:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dlinko365.onmicrosoft.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 IwmtR2d9gpLM; Thu,  6 Sep 2018 07:51:44 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-sg2apc01on0134.outbound.protection.outlook.com [104.47.125.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CAB8126CB6; Thu,  6 Sep 2018 07:51:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dlinko365.onmicrosoft.com; s=selector1-dlinkcorp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RHakgHgkamCveBm6ZVHiTJHlw8lBJ6RFBOWI/Hi4mPU=; b=Vvyi+oTxJc19b+W9bazWDMsl8dJbCZ23xY9WEia2HVoGQIqm7ALAL2bPcmcbbp7aY+gkypqvuJyFDEXJRMF2tXhR0IUo4DqCUzdemSup/sInOKVGvmUaD4KWF39lKd4MQ+OkbicNlMxuCumVyqi7pC/jLGjS1wTaAQRb0kPv6ak=
Received: from HK2PR0201MB1442.apcprd02.prod.outlook.com (10.167.67.24) by HK2PR0201MB2195.apcprd02.prod.outlook.com (10.170.149.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1080.17; Thu, 6 Sep 2018 14:51:40 +0000
Received: from HK2PR0201MB1442.apcprd02.prod.outlook.com ([fe80::9935:3949:e095:bd52]) by HK2PR0201MB1442.apcprd02.prod.outlook.com ([fe80::9935:3949:e095:bd52%4]) with mapi id 15.20.1101.016; Thu, 6 Sep 2018 14:51:40 +0000
From: Hans Liu <Hans.Liu@dlinkcorp.com>
To: Ron Bonica <rbonica@juniper.net>
CC: "draft-ietf-v6ops-transition-ipv4aas@ietf.org" <draft-ietf-v6ops-transition-ipv4aas@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: IPR: draft-ietf-v6ops-transition-ipv4aas-08
Thread-Index: AdRF7iS3QjybnIjPQnarXiF68fx6iQAAvayA
Date: Thu, 6 Sep 2018 14:51:40 +0000
Message-ID: <59CAA0A9-992A-4EEB-B131-4E4B1E5F4EA9@dlinkcorp.com>
References: <CO1PR05MB4433992E2D0CE6ADAB4B07EAE010@CO1PR05MB443.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4433992E2D0CE6ADAB4B07EAE010@CO1PR05MB443.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hans.Liu@dlinkcorp.com; 
x-originating-ip: [2001:b011:200b:1eea:7197:5987:735a:a97d]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HK2PR0201MB2195; 20:gK9IIZ8klWwqolINMgYEXtVcO1ikHR3khQD2GrHfiG4PxUfWg7CI/EUGwFi84RGg85hcxsnRUXmqY9F1IOHGg0RqQH3IId1G96chZNXkXxXQGp4TID7TzdmZBj8jHAmM74Ai9WjUB8wbUplL30Vzxn7RF5GoXlq253gl8SN+iJs=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 4e97052a-5bb1-4df9-e10c-08d614084114
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:HK2PR0201MB2195; 
x-ms-traffictypediagnostic: HK2PR0201MB2195:
x-microsoft-antispam-prvs: <HK2PR0201MB2195271E1B4F9228E4BAB10395010@HK2PR0201MB2195.apcprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(138986009662008);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231311)(944501410)(52105095)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699016); SRVR:HK2PR0201MB2195; BCL:0; PCL:0; RULEID:; SRVR:HK2PR0201MB2195; 
x-forefront-prvs: 0787459938
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39850400004)(136003)(376002)(396003)(366004)(346002)(199004)(189003)(36756003)(99286004)(6486002)(6246003)(1941001)(86362001)(82746002)(8936002)(6436002)(6116002)(105586002)(83716003)(558084003)(76176011)(2906002)(68736007)(4326008)(5250100002)(11346002)(106356001)(6512007)(236005)(478600001)(316002)(53546011)(6506007)(46003)(54896002)(25786009)(2900100001)(5660300001)(229853002)(8676002)(53936002)(6916009)(33656002)(186003)(81156014)(102836004)(72206003)(476003)(256004)(2616005)(81166006)(14454004)(486006)(54906003)(7736002)(446003)(97736004); DIR:OUT; SFP:1102; SCL:1; SRVR:HK2PR0201MB2195; H:HK2PR0201MB1442.apcprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: dlinkcorp.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 4D9a+RuLI8Yg0QaijdIcHvKn9SxjeS7kREKIpz38PVDUjgXxw32D6mvjMVhLNTwwcO68xkvWp9Of9pjr++fdmsNF0KPjYWGtVqAGwdNfl6H+mL/O14Rdu12ee0mPAfgcjUIsWNHMf34CQc4uSQnumm8OM1fRyvCJgfnt3tY9DOu0IarRGLzPo4fCTf1h1nbjAQQ0rIxgdnOHWMko9Z2Vg36fCZdBYlFQ9kGJAlUrC9g2cXve2NXHKgu1HtiChrmXzG0ZWINFnx2Dg3F1UwVf2XKr0ClUdpqVHjZk5th4NfLuapDYv7fbPnhcK9p+7zwSrEl+86luvquAfpLraCefeIgwf2q+eRJ5+vxRV1VrHJ4=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_59CAA0A9992A4EEBB1314E4B1E5F4EA9dlinkcorpcom_"
MIME-Version: 1.0
X-OriginatorOrg: dlinkcorp.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4e97052a-5bb1-4df9-e10c-08d614084114
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2018 14:51:40.2314 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8135e33d-36db-4906-af5e-6a7df298ed96
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2PR0201MB2195
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/M0lsKQq9KKJHl14x_xIRMY-VbO8>
Subject: Re: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-08
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 14:58:17 -0000

--_000_59CAA0A9992A4EEBB1314E4B1E5F4EA9dlinkcorpcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm not aware of any IPR against this draft.

Best regards,
Hans

On Sep 6, 2018, at 10:31 PM, Ron Bonica <rbonica@juniper.net<mailto:rbonica=
@juniper.net>> wrote:

Co-authors,

Please send mail to the list stating whether you know of any IPR regarding =
draft-ietf-v6ops-transition-ipv4aas-08.

                                                  Ron



--_000_59CAA0A9992A4EEBB1314E4B1E5F4EA9dlinkcorpcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <13F2B9AE33778249BD83243146C5C5AB@apcprd02.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break:=
 after-white-space;" class=3D"">
<span style=3D"color: rgb(34, 34, 34); font-family: Arial, Helvetica, sans-=
serif; font-size: small; font-variant-ligatures: normal; orphans: 2; widows=
: 2; background-color: rgb(255, 255, 255);" class=3D"">I'm not aware of any=
&nbsp;</span><span class=3D"il" style=3D"color: rgb(34, 34, 34); font-famil=
y: Arial, Helvetica, sans-serif; font-size: small; font-variant-ligatures: =
normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);">IPR</=
span><span style=3D"color: rgb(34, 34, 34); font-family: Arial, Helvetica, =
sans-serif; font-size: small; font-variant-ligatures: normal; orphans: 2; w=
idows: 2; background-color: rgb(255, 255, 255);" class=3D"">&nbsp;against
 this draft.</span>
<div class=3D"">
<div class=3D"">
<div style=3D"orphans: 2; widows: 2;" class=3D""><font color=3D"#222222" fa=
ce=3D"Arial, Helvetica, sans-serif" size=3D"2" class=3D""><span style=3D"ca=
ret-color: rgb(34, 34, 34); background-color: rgb(255, 255, 255);" class=3D=
""><br class=3D"">
</span></font></div>
<div style=3D"orphans: 2; widows: 2;" class=3D""><font color=3D"#222222" fa=
ce=3D"Arial, Helvetica, sans-serif" size=3D"2" class=3D""><span style=3D"ca=
ret-color: rgb(34, 34, 34); background-color: rgb(255, 255, 255);" class=3D=
"">Best regards,</span></font></div>
<div style=3D"orphans: 2; widows: 2;" class=3D""><font color=3D"#222222" fa=
ce=3D"Arial, Helvetica, sans-serif" size=3D"2" class=3D""><span style=3D"ca=
ret-color: rgb(34, 34, 34); background-color: rgb(255, 255, 255);" class=3D=
"">Hans</span></font></div>
<div><br class=3D"">
<div class=3D"">On Sep 6, 2018, at 10:31 PM, Ron Bonica &lt;<a href=3D"mail=
to:rbonica@juniper.net" class=3D"">rbonica@juniper.net</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div class=3D"">Co-authors,<br class=3D"">
<br class=3D"">
Please send mail to the list stating whether you know of any IPR regarding =
draft-ietf-v6ops-transition-ipv4aas-08.<br class=3D"">
<br class=3D"">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
Ron<br class=3D"">
<br class=3D"">
</div>
</div>
</div>
<br class=3D"">
</div>
</div>
</body>
</html>

--_000_59CAA0A9992A4EEBB1314E4B1E5F4EA9dlinkcorpcom_--


From nobody Thu Sep  6 09:20:17 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A332D130EB7 for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 09:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level: 
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 9rgLUkubuA2u for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 09:20:12 -0700 (PDT)
Received: from atl4mhob02.registeredsite.com (atl4mhob02.registeredsite.com [209.17.115.40]) (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 AE306130ED6 for <v6ops@ietf.org>; Thu,  6 Sep 2018 09:20:10 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob02.registeredsite.com (8.14.4/8.14.4) with ESMTP id w86GK6JS002284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Thu, 6 Sep 2018 12:20:06 -0400
Received: (qmail 11428 invoked by uid 0); 6 Sep 2018 16:20:06 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 6 Sep 2018 16:20:06 -0000
To: v6ops@ietf.org, draft-ietf-doh-dns-over-https.all@ietf.org, evyncke@cisco.com
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org>
Date: Thu, 6 Sep 2018 12:20:05 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------2826BF1DF13CC1DD5362B823"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UphvexLJi7KxFQdQH4VnSUJUK5U>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 16:20:15 -0000

This is a multi-part message in MIME format.
--------------2826BF1DF13CC1DD5362B823
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit



On 09/05/2018 05:50 PM, Erik Nygren wrote:
> DNSSEC isn't the only threat here.  Clients implementing protocols 
> such as DoH also bypass the DNS64.
> draft-ietf-doh-dns-over-https-14 does say:
>
>    Local policy considerations and similar factors mean different DNS
>    servers may provide different results to the same query, for instance
>    in split DNS configurations [RFC6950].  It logically follows that the
>    server that is queried can influence the end result. Therefore a
>    client's choice of DNS server may affect the responses it gets to its
>    queries.  For example, in the case of DNS64 [RFC6147], the choice
>    could affect whether IPv6/IPv4 translation will work at all.
>
> I'm not sure what the best way to approach this is in this draft.


Yes, I remember reading that in DoH and rolling my eyes. The best 
response is to strengthen the statement in that draft to say, "Hundreds 
of millions of users behind DNS64 will be unable to use DoH, unless IPv6 
resource records are available, bypassing the DNS64 function." And maybe 
to point at this draft.

I note that no OpsDir review has been submitted 
https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/
This is an operational issue.

> For example:
>
> * Acknowledge that DNS64 is a shortish-term hack that only works in 
> constrained environments.     If this is the case, that might argue 
> that this draft should be at most Informational and not BCP?

"Constrained environments" in this case meaning "the IPv4 Internet."
This draft is BCP for domains with DNSSEC. It makes no recommendation 
for DNS64 deployers.
>
> * Commit to DNS64 being a robust part of the architecture and cover 
> topics more broadly than just DNSSEC?   Is there a way to handle the 
> DOH case short of mandating that clients implementing DOH also do 
> bump-in-the-API or client-side DNS64 synthesis or 464xlat?  If this is 
> the case, should there be more firm wording in 
> draft-ietf-doh-dns-over-https-14.  I suspect other conflicts will also 
> appear over time.

I wouldn't call it "robust," but I'd call it "widespread." I support 
your suggestion that the BCP be applied more broadly, although it may 
start to become redundant with BCP177 (rfc6540, "IPv6 Support Required 
for All IPv6-Capable Nodes").

> Is there really value in picking some middle ground between these?
>
> Is there concrete data on how often DNSSEC and DNS64 cause interaction 
> issues and where?  They shouldn't on the recursive resolver itself.  
> How often are clients redoing DNSSEC validation and running into 
> issues here?
>
> A separate pragmatic/cynic question is whether we think this will 
> influence behavior?  I don't have a positive feeling that those who 
> control whether a zone has DNSSEC enabled also have control over 
> whether AAAA records are present for dual-stacked content in the 
> zone.  Those are often separate actors.  Will a recommendation here 
> have any substantive impact, and is there an audience who will be able 
> to take action on this?

I think this problem is largely unnoticed, and needs a recommendation to 
address it. It may be unnoticed because the 15% of domains that use 
DNSSEC [https://stats.labs.apnic.net/dnssec/XA?c=XA&x=1&g=1&r=1&w=7&g=0] 
are more likely to be among the 24% of domains that have IPv6 
[http://www.employees.org/~dwing/aaaa-stats/]  (or the other way around) 
because the operators are early adopters.


Lee

>
>        Erik
>
>   
>
> On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica <rbonica@juniper.net 
> <mailto:rbonica@juniper.net>> wrote:
>
>     Folks,
>
>     Each week between now and IETF 103, we will review and discuss one
>     draft with an eye towards progressing it.
>
>     This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
>
>                                           Fred and Ron
>
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org <mailto:v6ops@ietf.org>
>     https://www.ietf.org/mailman/listinfo/v6ops
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--------------2826BF1DF13CC1DD5362B823
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 09/05/2018 05:50 PM, Erik Nygren
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="ltr">DNSSEC isn't the only threat here.  Clients
        implementing protocols such as DoH also bypass the DNS64.<br>
        draft-ietf-doh-dns-over-https-14 does say:<br>
        <br>
           Local policy considerations and similar factors mean
        different DNS<br>
           servers may provide different results to the same query, for
        instance<br>
           in split DNS configurations [RFC6950].  It logically follows
        that the<br>
           server that is queried can influence the end result. 
        Therefore a<br>
           client's choice of DNS server may affect the responses it
        gets to its<br>
           queries.  For example, in the case of DNS64 [RFC6147], the
        choice<br>
           could affect whether IPv6/IPv4 translation will work at all.<br>
      </div>
    </blockquote>
    <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
      <div dir="ltr"><br>
        I'm not sure what the best way to approach this is in this
        draft. <br>
      </div>
    </blockquote>
    <br>
    <br>
    Yes, I remember reading that in DoH and rolling my eyes. The best
    response is to strengthen the statement in that draft to say,
    "Hundreds of millions of users behind DNS64 will be unable to use
    DoH, unless IPv6 resource records are available, bypassing the DNS64
    function." And maybe to point at this draft.<br>
    <br>
    I note that no OpsDir review has been submitted
    <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/">https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/</a><br>
    This is an operational issue.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
      <div dir="ltr"> For example:<br>
        <br>
        * Acknowledge that DNS64 is a shortish-term hack that only works
        in constrained environments.     If this is the case, that might
        argue that this draft should be at most Informational and not
        BCP? <br>
      </div>
    </blockquote>
    <br>
    "Constrained environments" in this case meaning "the IPv4 Internet."
    <br>
    This draft is BCP for domains with DNSSEC. It makes no
    recommendation for DNS64 deployers.<br>
    <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
      <div dir="ltr"><br>
        * Commit to DNS64 being a robust part of the architecture and
        cover topics more broadly than just DNSSEC?   Is there a way to
        handle the DOH case short of mandating that clients implementing
        DOH also do bump-in-the-API or client-side DNS64 synthesis or
        464xlat?  If this is the case, should there be more firm wording
        in draft-ietf-doh-dns-over-https-14.  I suspect other conflicts
        will also appear over time.<br>
      </div>
    </blockquote>
    <br>
    I wouldn't call it "robust," but I'd call it "widespread." I support
    your suggestion that the BCP be applied more broadly, although it
    may start to become redundant with BCP177 (rfc6540, "IPv6 Support
    Required for All IPv6-Capable Nodes").<br>
    <br>
    <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
      <div dir="ltr">Is there really value in picking some middle ground
        between these?<br>
        <br>
        Is there concrete data on how often DNSSEC and DNS64 cause
        interaction issues and where?  They shouldn't on the recursive
        resolver itself.  How often are clients redoing DNSSEC
        validation and running into issues here?<br>
        <br>
        A separate pragmatic/cynic question is whether we think this
        will influence behavior?  I don't have a positive feeling that
        those who control whether a zone has DNSSEC enabled also have
        control over whether AAAA records are present for dual-stacked
        content in the zone.  Those are often separate actors.  Will a
        recommendation here have any substantive impact, and is there an
        audience who will be able to take action on this?<br>
      </div>
    </blockquote>
    <br>
    I think this problem is largely unnoticed, and needs a
    recommendation to address it. It may be unnoticed because the 15% of
    domains that use DNSSEC
[<a class="moz-txt-link-freetext" href="https://stats.labs.apnic.net/dnssec/XA?c=XA&amp;x=1&amp;g=1&amp;r=1&amp;w=7&amp;g=0">https://stats.labs.apnic.net/dnssec/XA?c=XA&amp;x=1&amp;g=1&amp;r=1&amp;w=7&amp;g=0</a>]
    are more likely to be among the 24% of domains that have IPv6
    [<a class="moz-txt-link-freetext" href="http://www.employees.org/~dwing/aaaa-stats/">http://www.employees.org/~dwing/aaaa-stats/</a>]  (or the other way
    around) because the operators are early adopters. <br>
    <br>
    <br>
    Lee<br>
    <br>
    <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
      <div dir="ltr"><br>
               Erik
        <div dir="ltr"><br>
          <div class="gmail_default"
            style="font-family:tahoma,sans-serif">
            <pre class="gmail-newpage"> 
</pre>
            <pre class="gmail-newpage">
</pre>
          </div>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica &lt;<a
            href="mailto:rbonica@juniper.net" moz-do-not-send="true">rbonica@juniper.net</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<br>
          <br>
          Each week between now and IETF 103, we will review and discuss
          one draft with an eye towards progressing it.<br>
          <br>
          This week, please review and comment on
          draft-byrne-v6ops-dnssecaaaa.<br>
          <br>
                                                Fred and Ron<br>
          <br>
          _______________________________________________<br>
          v6ops mailing list<br>
          <a href="mailto:v6ops@ietf.org" target="_blank"
            moz-do-not-send="true">v6ops@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/v6ops"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------2826BF1DF13CC1DD5362B823--


From nobody Thu Sep  6 13:34:17 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34844130F67 for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 13:34:02 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 0O8J9XYr8TEN for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 13:34:00 -0700 (PDT)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 4DF40130FB5 for <v6ops@ietf.org>; Thu,  6 Sep 2018 13:34:00 -0700 (PDT)
Received: by mail-pf1-x42a.google.com with SMTP id s13-v6so5844589pfi.7 for <v6ops@ietf.org>; Thu, 06 Sep 2018 13:34:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Q8e3WnW+wp99ndjy6yMxsvnKrHZsFtz/qPxFeC2pTPM=; b=ZYo/kBTnjntkW3l5fRUJ2lNdKiHL/klYHnPL70YOwzBA6D4LSDFYCE4Yor8+WOzODA NuGh8CJ/04YtnqwuN8wbxa2VaNy6+3WgusvTsVj/Q4ujsBnnVfxky0e+scuyZDHnKbta lUGPxh5mciK4s8qH17zEwF9XNQO2kDcBo/sRK7lk4c3iN08MeeELutW71XrQJs4Pd0WO elPqwilnlcE9fYGCZgQUxSgJdTYnQ35npiqEz5UwRvDEYF1qz63y/P0cdoioPh/lq3EY b0IKA6cADYMtDO6/yHjuTpdxFWx5zrG1MJ0U68d2dUspAWrj7l4vcM7zXN/cV4kgYpTd mm2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Q8e3WnW+wp99ndjy6yMxsvnKrHZsFtz/qPxFeC2pTPM=; b=UlqERa8pwLXLdFcntbJmoZKUplg39dxrg7NRuMGUrAliZLdcEql4LpZ7fU6hTjbf1a Yp7IDr16HJbT3cJ5ye+FGO+tx+wJ1EBbto5Jgrco2++s7KjoQ9YFVHT2ok+nCdFfXwkH BA9uhqZXMhw5urO1v5H3TvEnWJLVUniZWTWCTe8DZ0wniYkyY6zGakqSYZ1BPWhCBBj1 FIPvDT1MfJWCU8VisvHPkVj8MSqLR1G8X9R/XQHjapwD2ka2GEhZQW/wP5emoas2asUv 52v9D/qqt4sttp54tFmTnoTh6dPweEF+6Ieg0tv/n8eRC95AsfRxr82khQ8BkoytBeht 8tJw==
X-Gm-Message-State: APzg51Btoy0lWgiZUuZg83Bqj6xyZSct62VoPHXgOVCqqx9lT8P9F6lX PlgSr0QtiwN2Kgs7Bhcxt8EO/xlb
X-Google-Smtp-Source: ANB0VdaEai7iP+AcVjgAJuuP3Vn5TLtA3Ll2dgDhry3NlKpwDouCF/dTrQv9uFIlM3ZsdH1yvDmM/A==
X-Received: by 2002:a63:cf52:: with SMTP id b18-v6mr4657475pgj.194.1536266039548;  Thu, 06 Sep 2018 13:33:59 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id 8-v6sm6955082pgu.10.2018.09.06.13.33.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Sep 2018 13:33:58 -0700 (PDT)
To: Tim Chown <Tim.Chown@jisc.ac.uk>, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: Simon Hobson <linux@thehobsons.co.uk>, "v6ops@ietf.org WG" <v6ops@ietf.org>
References: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com> <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com> <CAKD1Yr3p3mh4OEn2Ai+RZLBGkhusU1Q+5qrjicEM5tjkxe2wiA@mail.gmail.com> <D53C2B7A-C67F-4739-9633-60293DE59932@jisc.ac.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d27997af-5e02-521a-fd8c-9e24778782d0@gmail.com>
Date: Fri, 7 Sep 2018 08:33:53 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <D53C2B7A-C67F-4739-9633-60293DE59932@jisc.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/E5r6-jRpdXD9hI2pdp7b8PxEuS8>
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 20:34:02 -0000

On 2018-09-07 02:24, Tim Chown wrote:
>> On 6 Sep 2018, at 14:01, Lorenzo Colitti <lorenzo=3D40google.com@dmarc=
=2Eietf.org> wrote:
>>
>> On Wed, Sep 5, 2018 at 11:09 PM Owen DeLong <owen@delong.com> wrote:
>> Further, I don=E2=80=99t believe for one second that ALL enterprises w=
ill require or use DHCPv6. Perhaps most, but certainly not all.=20
>>
>> +1. Ours doesn't.
>=20
> And the requirement/use of configuration method, especially at a univer=
sity campus, may vary between managed desktops and WiFi/eduroam where BYO=
D is the norm.=20

If you base admission to the wired network on registered MAC addresses, w=
hich
is quite common, there seems to be no particular reason to waste resource=
s
on DHCPv6 even for managed devices.

   Brian


From nobody Thu Sep  6 14:37:50 2018
Return-Path: <prvs=17872dd3ec=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5C5130F29; Thu,  6 Sep 2018 14:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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
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 LaNwove_wsL6; Thu,  6 Sep 2018 14:37:46 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DB09130E94; Thu,  6 Sep 2018 14:37:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1536269862; x=1536874662; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:Mime-version: Content-type; bh=Gl9E4SpavW7lHtB1CCc7H5oLHzlwmdEiaDO1l3Crb4I=; b=c7dDHbMeGqPM4MMhwLy1SSCv+VlZ56uTU+3DedxM6AK84xsfNmIrpOy4qrBfhT 4tGMQ4qIitD0FDlVNfZ281cNUG+quu1gtEX28iUDAcWfNP5ZhMurQgBpgq2IyIWq tEhpxX6vK+KxkcMy8xYg8eK9s7wODgUeSjfl/d8t3nnKM=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 06 Sep 2018 23:37:42 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 06 Sep 2018 23:37:41 +0200
Received: from [192.168.3.11] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005873241.msg; Thu, 06 Sep 2018 23:37:41 +0200
X-MDRemoteIP: 2404:2200:16:0:b42f:8913:bb23:bbed
X-MDHelo: [192.168.3.11]
X-MDArrival-Date: Thu, 06 Sep 2018 23:37:41 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=17872dd3ec=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.0.180812
Date: Fri, 07 Sep 2018 08:37:16 +1100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Hans Liu <Hans.Liu@dlinkcorp.com>, Ron Bonica <rbonica@juniper.net>
CC: "draft-ietf-v6ops-transition-ipv4aas@ietf.org" <draft-ietf-v6ops-transition-ipv4aas@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <03C229FA-94D2-4163-9E7A-5C4B8618DFC6@consulintel.es>
Thread-Topic: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-08
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3619154241_1747920679"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/e5mU7mi6DWPRm_r6c2XD7fB3JKQ>
Subject: Re: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-08
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 21:37:49 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3619154241_1747920679
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: 7bit

Same for me, not aware of any IPR.


Regards,

Jordi

 

 

 

De: v6ops <v6ops-bounces@ietf.org> en nombre de Hans Liu <Hans.Liu@dlinkcorp.com>
Fecha: viernes, 7 de septiembre de 2018, 1:58
Para: Ron Bonica <rbonica@juniper.net>
CC: "draft-ietf-v6ops-transition-ipv4aas@ietf.org" <draft-ietf-v6ops-transition-ipv4aas@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Asunto: Re: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-08

 

I'm not aware of any IPR against this draft. 



Best regards,

Hans

 

On Sep 6, 2018, at 10:31 PM, Ron Bonica <rbonica@juniper.net> wrote:

 

Co-authors,

Please send mail to the list stating whether you know of any IPR regarding draft-ietf-v6ops-transition-ipv4aas-08.

                                                  Ron

 

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



**********************************************
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 confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.


--B_3619154241_1747920679
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta ht=
tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name=
=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.il
	{mso-style-name:il;}
span.EstiloCorreo19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DES link=3Dblue vlink=3Dpurple><div class=3DW=
ordSection1><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-la=
nguage:EN-US'>Same for me, not aware of any IPR.<o:p></o:p></span></p><div>=
<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt;color:bla=
ck'><br></span><span lang=3DES-TRAD style=3D'font-size:10.5pt;color:black'>=
Regards,<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:1=
2.0pt'><span lang=3DES-TRAD style=3D'font-size:10.5pt;color:black;mso-farea=
st-language:EN-US'>Jordi<o:p></o:p></span></p><p class=3DMsoNormal style=3D=
'margin-bottom:12.0pt'><span lang=3DES-TRAD style=3D'font-size:10.5pt;color=
:black;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p></div><p cla=
ss=3DMsoNormal><span lang=3DES-TRAD style=3D'mso-fareast-language:EN-US'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DES-TRAD style=
=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div style=3D'b=
order:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p cla=
ss=3DMsoNormal style=3D'margin-left:35.4pt'><b><span style=3D'font-size:12.=
0pt;color:black'>De: </span></b><span style=3D'font-size:12.0pt;color:black=
'>v6ops &lt;v6ops-bounces@ietf.org&gt; en nombre de Hans Liu &lt;Hans.Liu@d=
linkcorp.com&gt;<br><b>Fecha: </b>viernes, 7 de septiembre de 2018, 1:58<br=
><b>Para: </b>Ron Bonica &lt;rbonica@juniper.net&gt;<br><b>CC: </b>&quot;dr=
aft-ietf-v6ops-transition-ipv4aas@ietf.org&quot; &lt;draft-ietf-v6ops-trans=
ition-ipv4aas@ietf.org&gt;, &quot;v6ops@ietf.org&quot; &lt;v6ops@ietf.org&g=
t;<br><b>Asunto: </b>Re: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-0=
8<o:p></o:p></span></p></div><div><p class=3DMsoNormal style=3D'margin-left=
:35.4pt'><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal style=3D'margin-le=
ft:35.4pt'><span style=3D'font-size:12.0pt;font-family:"Arial",sans-serif;c=
olor:#222222;background:white'>I'm not aware of any&nbsp;<span class=3Dil>I=
PR</span>&nbsp;against this draft.</span> <o:p></o:p></p><div><div><div><p =
class=3DMsoNormal style=3D'margin-left:35.4pt'><span style=3D'font-size:10.=
0pt;font-family:"Arial",sans-serif;color:#222222;background:white'><br><br>=
</span><o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:=
35.4pt'><span style=3D'font-size:10.0pt;font-family:"Arial",sans-serif;colo=
r:#222222;background:white'>Best regards,</span><o:p></o:p></p></div><div><=
p class=3DMsoNormal style=3D'margin-left:35.4pt'><span style=3D'font-size:1=
0.0pt;font-family:"Arial",sans-serif;color:#222222;background:white'>Hans</=
span><o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:35=
.4pt'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal style=3D'margin-left:3=
5.4pt'>On Sep 6, 2018, at 10:31 PM, Ron Bonica &lt;<a href=3D"mailto:rbonic=
a@juniper.net">rbonica@juniper.net</a>&gt; wrote:<o:p></o:p></p></div><p cl=
ass=3DMsoNormal style=3D'margin-left:35.4pt'><o:p>&nbsp;</o:p></p><div><div=
><p class=3DMsoNormal style=3D'mso-margin-top-alt:0cm;margin-right:0cm;marg=
in-bottom:12.0pt;margin-left:35.4pt'>Co-authors,<br><br>Please send mail to=
 the list stating whether you know of any IPR regarding draft-ietf-v6ops-tr=
ansition-ipv4aas-08.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;Ron<o:p></o:p></p></div></div></div><p class=3D=
MsoNormal style=3D'margin-left:35.4pt'><o:p>&nbsp;</o:p></p></div></div><p =
class=3DMsoNormal style=3D'margin-left:35.4pt'>____________________________=
___________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/=
mailman/listinfo/v6ops <o:p></o:p></p></div><br>***************************=
*******************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.consulintel.es<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.<br>
<br>
</body></html>

--B_3619154241_1747920679--


From nobody Thu Sep  6 15:25:39 2018
Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D70A7130F4F for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 15:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 YhH1ZpY5Vu-1 for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 15:25:34 -0700 (PDT)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 E3C44130F4A for <v6ops@ietf.org>; Thu,  6 Sep 2018 15:25:33 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 6A7AD1E6 for <v6ops@ietf.org>; Thu,  6 Sep 2018 22:25:33 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 84OgjQsQedIi for <v6ops@ietf.org>; Thu,  6 Sep 2018 17:25:33 -0500 (CDT)
Received: from mail-ua1-f69.google.com (mail-ua1-f69.google.com [209.85.222.69]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 2C4471C3 for <v6ops@ietf.org>; Thu,  6 Sep 2018 17:25:32 -0500 (CDT)
Received: by mail-ua1-f69.google.com with SMTP id n10-v6so5433929uao.1 for <v6ops@ietf.org>; Thu, 06 Sep 2018 15:25:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tPndw6jPrEq2e4EIhVRNkqv1IRBCLrgW3JblhDb/7b4=; b=ockD5TDfepUlNqXZxX97Sh1OWymveyoQHueYlmGwTbxFnTHsozuQVVQysqoRhWNsnQ einT/wsCLtQ5pW+h9hg2m4ExOhDIHH8Lg5zRPYCNJy+tA0hEYecfqkFAA4OGfT+7jKSy cSDLP+jQngzP7C0SNeGVCnBtIImuLlpA97UkXxvRNyYPwr9O5CqeEJSZHoppdvGTTNAc 3XJ4hPU0xtK1r4OV5b3G9TEIJFk6fGqPe6Fu4pfbidApTMM+Vp63y5lO2fmSTtimcv/x kqO00OCzvaa4V4ckTsYOzf/IOhiWUS+s51Oeqh26X+F+okxRBnvTfizPwzk4uZDpb7br xbDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tPndw6jPrEq2e4EIhVRNkqv1IRBCLrgW3JblhDb/7b4=; b=ZFNlqiK+74uUBjFf1FjI2qqNHmJGgMGLwvn5NdrlqWmIOkww5ul2Pu91PGXhHM1PGs 84mb51qeMID/b6QCILf+wug7ZodlUDE8jDP39FsWv5BTIs/YPpt8r17D4WJ+GLF63jcK f4SEUrE1mTb/xEZmHrJu+IldjZamOoUnnqRwHK/OeQ0yRcB1hmkw6hrIfzAo0sMUsjXC WRxTX5n+vit+7Ec2HCBKtoldqraZoToayHIoNHhjREMEEa7l9ZNZMZR52pdgHQ4Apliv B9oVhEoYKMzgAxgSeVmbmIDcvKIXMbgKmWMUqn86fqRdqZ6fcJSn1SC+wCtU/p54G2p1 9fzg==
X-Gm-Message-State: APzg51DbRbihe6eZ3v1CX0nf+nsm77Tb+iNR+vY6bmIN9PlNP2jpLVcN sC/i2E2b+TTqOqyYqkVD49PlkXG3Wp/R1Y1ma2CWWPqOCAVTOHmy3gJMir2E3KzuoTthqhj7m3C eXeW4Ac2tIYvKila6CHD6kShlGw==
X-Received: by 2002:a1f:88cd:: with SMTP id k196-v6mr1737940vkd.84.1536272730560;  Thu, 06 Sep 2018 15:25:30 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdaVj8gR+tigdyepbdPGSRig+kNEwRZH1haIjwjveI5HCNDwhxnvYTA45Bn9MaZitQ5Qkw71zCXVulW/ZmI502A=
X-Received: by 2002:a1f:88cd:: with SMTP id k196-v6mr1737933vkd.84.1536272730096;  Thu, 06 Sep 2018 15:25:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a67:6042:0:0:0:0:0 with HTTP; Thu, 6 Sep 2018 15:25:29 -0700 (PDT)
In-Reply-To: <d27997af-5e02-521a-fd8c-9e24778782d0@gmail.com>
References: <9142206A0C5BF24CB22755C8EC422E459CB4C5DB@AZ-US1EXMB03.global.avaya.com> <8DB1AF29-8BBA-4BB1-A039-CCF806B326D2@delong.com> <CAKD1Yr3p3mh4OEn2Ai+RZLBGkhusU1Q+5qrjicEM5tjkxe2wiA@mail.gmail.com> <D53C2B7A-C67F-4739-9633-60293DE59932@jisc.ac.uk> <d27997af-5e02-521a-fd8c-9e24778782d0@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 6 Sep 2018 17:25:29 -0500
Message-ID: <CAN-Dau0rx9UFpqTuqyrANu+6yyhuNy90s09QUvk=819fDdBT4Q@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>,  Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Simon Hobson <linux@thehobsons.co.uk>,  "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005b1dd805753b5ee5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/EVu--rwm0drGXUNPK2ZwfQbvzis>
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6rtr-reqs-04: Enabling DHCPv6 in the enterprise networks by default, if DHCPv6 is supported on the router
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 22:25:37 -0000

--0000000000005b1dd805753b5ee5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 6, 2018 at 3:33 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 2018-09-07 02:24, Tim Chown wrote:
> >> On 6 Sep 2018, at 14:01, Lorenzo Colitti <lorenzo=3D40google.com@dmarc=
.
> ietf.org> wrote:
> >>
> >> On Wed, Sep 5, 2018 at 11:09 PM Owen DeLong <owen@delong.com> wrote:
> >> Further, I don=E2=80=99t believe for one second that ALL enterprises w=
ill
> require or use DHCPv6. Perhaps most, but certainly not all.
> >>
> >> +1. Ours doesn't.
> >
> > And the requirement/use of configuration method, especially at a
> university campus, may vary between managed desktops and WiFi/eduroam whe=
re
> BYOD is the norm.
>
> If you base admission to the wired network on registered MAC addresses,
> which
> is quite common, there seems to be no particular reason to waste resource=
s
> on DHCPv6 even for managed devices.
>

Well not entirely true. It is common to base admission on registered MAC
addresses. However, if you also want a strong binding between MAC address
and IP address to be enforced with SAVI then DHCPv4 or v6 is still useful.
If you use SLAAC you really only have a First-Come-First-Serve(FCFS)
binding methodology SAVI. FCFS will work in a lot of cases but it is not as
strong of a binding as DHCP.

We have a broad set of tools for a broad set of environments. Some tools
are appropriate in some environments and other tools are not. IPv6 needs to
work in every situation, from wide-open wifi, as in free love wifi, to a
nuclear control room and most networks are someplace in between those two.

--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--0000000000005b1dd805753b5ee5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font-size:small;text-decora=
tion-style:initial;text-decoration-color:initial"><br></div><div class=3D"g=
mail_extra"><div class=3D"gmail_quote">On Thu, Sep 6, 2018 at 3:33 PM, Bria=
n E Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gma=
il.com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">On 2018-09-07 02:24, =
Tim Chown wrote:<br>
&gt;&gt; On 6 Sep 2018, at 14:01, Lorenzo Colitti &lt;lorenzo=3D<a href=3D"=
mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.<wbr>ietf.org</a>&gt=
; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Wed, Sep 5, 2018 at 11:09 PM Owen DeLong &lt;<a href=3D"mailto:=
owen@delong.com">owen@delong.com</a>&gt; wrote:<br>
&gt;&gt; Further, I don=E2=80=99t believe for one second that ALL enterpris=
es will require or use DHCPv6. Perhaps most, but certainly not all. <br>
&gt;&gt;<br>
&gt;&gt; +1. Ours doesn&#39;t.<br>
&gt; <br>
&gt; And the requirement/use of configuration method, especially at a unive=
rsity campus, may vary between managed desktops and WiFi/eduroam where BYOD=
 is the norm. <br>
<br>
If you base admission to the wired network on registered MAC addresses, whi=
ch<br>
is quite common, there seems to be no particular reason to waste resources<=
br>
on DHCPv6 even for managed devices.<br></blockquote><div><br></div><div>Wel=
l not entirely true. It is common to base admission on registered MAC addre=
sses. However, if you also want a strong binding between MAC address and IP=
 address to be enforced with SAVI then DHCPv4 or v6 is still useful. If you=
 use SLAAC you really only have a First-Come-First-Serve(FCFS) binding meth=
odology SAVI. FCFS will work in a lot of cases but it is not as strong of a=
 binding as DHCP.=C2=A0</div><div><br></div><div>We have a broad set of too=
ls for a broad set of environments. Some tools are appropriate in some envi=
ronments and other tools are not. IPv6 needs to work in every situation, fr=
om wide-open wifi, as in free love wifi, to a nuclear control room and most=
 networks are someplace in between those two.</div><div><br></div></div>-- =
<br><div class=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D=
"_blank">Email:farmer@umn.edu</a><br>Networking &amp; Telecommunication Ser=
vices<br>Office of Information Technology<br>University of Minnesota=C2=A0=
=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626=
-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
</div></div></div>

--0000000000005b1dd805753b5ee5--


From nobody Thu Sep  6 16:09:45 2018
Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F05C130DEB for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 16:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 96msE1V8-wZQ for <v6ops@ietfa.amsl.com>; Thu,  6 Sep 2018 16:09:41 -0700 (PDT)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (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 35123130EC7 for <v6ops@ietf.org>; Thu,  6 Sep 2018 16:09:41 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id DF4EE105F for <v6ops@ietf.org>; Thu,  6 Sep 2018 23:09:39 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cnJUYtbhQ3Nl for <v6ops@ietf.org>; Thu,  6 Sep 2018 18:09:39 -0500 (CDT)
Received: from mail-ua1-f69.google.com (mail-ua1-f69.google.com [209.85.222.69]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id A13B3104D for <v6ops@ietf.org>; Thu,  6 Sep 2018 18:09:39 -0500 (CDT)
Received: by mail-ua1-f69.google.com with SMTP id s24-v6so5450320uac.16 for <v6ops@ietf.org>; Thu, 06 Sep 2018 16:09:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YwXNzShG56K0uPeNFke/eZXIvtaJz6bjzfTjxgamQkk=; b=SIK5m4W7fKlEdSYkSFlORzWV+x61kPlLUJbATUuAM9NXXzq54rpXWMAHnblNuFK231 gfc/zFT715zTz45UmwHxzwE2ac+MaRDPuZR+DcXM6p5peOJpDBu+5SVqeOsw123OMgB3 JIudONgvx1JgZFoLCOk9TGDEHJcugbqristYmQlFN7/GDpI64AU1Wr0rbqe4acwWOX6q 5VAbb52b8ANx/5YFmG0gOwcKtZ+fe6aUFp6CyMmwTUWyi6EbVsmPskZvHtIDdnSMZFhE +5+JeudantaIVpy1bgZohatbLj2ORb/K7pTKho367TgTOb9WhczTOPL/E6+NciFTuRDM /+Ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YwXNzShG56K0uPeNFke/eZXIvtaJz6bjzfTjxgamQkk=; b=ghrZ4LrDVNdCYQparIVWygqKPE0bUOHzxvoz+W1OrqGnl9RiUs9mmKUucDVoIjzwOs GrXTS8z7E9z8Zz+ClgEFzTypg3cRa11FZpt7wQOp/CfVYavo9lAClxSi3wDdYFKG6nkb hNheYzTjqys8B0l7tnMJQleL/lx1HLAh40h2jaE/Pe5QzKhpMc5RdJOXfkprOP34ZCRj ozTu6BjwmjpJZw3Ns9o+MIAwMHJrbz6CFzZ6Rnh1R4u+viFdpiSU77+SVcoRk3FPOcOq Xkr6MAI7fRrz5YQfwSoIIUzOrno6HU5I+haxy7SyFdJ7InYrX8PQek5IFkT8ZL2avLZa kcXQ==
X-Gm-Message-State: APzg51BO8ceFjkvI/SvS6uBOU+3zYeCf1GqiRCV7XnLP4MHrMhWu5LQb sMe6RcK+DIGnlJPlSqoot9PsWWUU/CjOzt/J7SV7Q4kDZdVG5uAy2NEBgygMNiRTsq/lMzbuShu 6U/Zga9zJtbW+BDGUiM7Ff4GU/A==
X-Received: by 2002:ab0:5339:: with SMTP id x54-v6mr1773521uax.187.1536275378593;  Thu, 06 Sep 2018 16:09:38 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdZekw3TOSii0BnVSpEYevG6yAXikW5zRSLz08J6vD5ccV3NWItps3m6j5mzUZvWR5hBkEUd7hye7TQDVPjnNDk=
X-Received: by 2002:ab0:5339:: with SMTP id x54-v6mr1773516uax.187.1536275378219;  Thu, 06 Sep 2018 16:09:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a67:6042:0:0:0:0:0 with HTTP; Thu, 6 Sep 2018 16:09:37 -0700 (PDT)
In-Reply-To: <CAKD1Yr0TzX_KUh_h71JJZwKSS_QknDsmVOqeCFmAZoW0Lz3OkQ@mail.gmail.com>
References: <CAAObRXLe35KoONVsSO_oU+SRhMzMrKRE_SU-QNf2pGHYKpUrxA@mail.gmail.com> <2018082709132233449033@chinatelecom.cn> <CAKD1Yr3PFKC06vwALL9Pjyd8Ji-RnqPR-HMvLA6CS6cyDadzVw@mail.gmail.com> <CAAObRXJx-8cPYuU-5gSMCvoOX-m29Q5BZg1-GANXBV-2Zmjv0A@mail.gmail.com> <CAKD1Yr24fXHsRTwFErNGc+RYzXDfHFpF6zG5QFjfjS+xx5-9Mg@mail.gmail.com> <CAAObRXK3jx_FXi-Rt5W3iSkOrf8zmc2z0NC1hUoET=AMFj2sig@mail.gmail.com> <CAAedzxouJUY1-R2NQH8sMDA0vrkOSznOWUaykBtdMy5a5Cup4g@mail.gmail.com> <34329770-1e00-be97-8443-79448be367cb@gmail.com> <201808271339136864338@chinatelecom.cn> <CAD6AjGReSzm0GHwFO74KL8R0F5Ahwd6c0s3bn2PtCyDTo-MPCw@mail.gmail.com> <CAAedzxrDjTO=BSsBGdgbaDRmhCUuB6frtV_oRE-+vNu5tsA5+Q@mail.gmail.com> <48B470F2-3F62-4D3F-90ED-C80A752AB61F@isc.org> <CAAedzxqfmODSBbnzSEg0hH+W+ovoDXcgmUjo+XUySiZFrxVcUg@mail.gmail.com> <D02DED65-CFDB-4ABE-A2C1-AA75440F19A8@isc.org> <7BC525AA-90F2-4477-BF1A-FB1FC80B8AF5@cisco.com> <c3df5aa5-4070-d16f-9c0d-684adb5f40e8@asgard.org> <7B6307F1-19C8-4D80-A32A-973E0F3CA4F7@cisco.com> <CAKD1Yr0TzX_KUh_h71JJZwKSS_QknDsmVOqeCFmAZoW0Lz3OkQ@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 6 Sep 2018 18:09:37 -0500
Message-ID: <CAN-Dau2APTqFePrHC_QQ+Gqfwx3EUgBdBG_hrBzLJuCkRekmzw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: rajiva=40cisco.com@dmarc.ietf.org, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000032448d05753bfca1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/HASbuVSnHl0JKO-Wf189Tl9NR7A>
Subject: Re: [v6ops] How my Android phone got assigned with IPv6 address via 4G LTE?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 23:09:44 -0000

--00000000000032448d05753bfca1
Content-Type: text/plain; charset="UTF-8"

On Thu, Sep 6, 2018 at 5:27 AM, Lorenzo Colitti <
lorenzo=40google.com@dmarc.ietf.org> wrote:

> On Thu, Sep 6, 2018 at 4:53 AM Rajiv Asati (rajiva) <rajiva=
> 40cisco.com@dmarc.ietf.org> wrote:
>
>> BTW, section 2.3.2 https://tools.ietf.org/html/
>> draft-ietf-dnsop-isp-ip6rdns-05#section-2.3.2 reminded me of the
>> solution described here for tracking MAC-IP address coupling in
>> environments such as those of enterprises etc.
>>
>>
>>
>> https://tools.ietf.org/html/draft-asati-dhc-ipv6-
>> autoconfig-address-tracking
>>
>
> I wonder if it's time to revive that draft? It would seem to be the
> easiest solution to support address tracking in existing architectures
> built around DHCP, and could facilitate enterprise networks transitioning
> from IPv4 to IPv6.
>

I've always thought this is an interesting idea, however, I think it needs
to be done for both IPv6 and IPv4.  IPv4 can have statically configured
hosts as well.

Also, I'm not sure it should be part of DHCPv6 or DHCPv4 protocols though,
maybe it should be its own protocol. The trust model between the routers
and a server for this function is quite different than the trust model for
host learning their configuration. It probably makes sense to have a common
database with DHCP, especially DHCPv4 since this is the only practical way
to automatically configure IPv4 hosts. If you have a common database with
DHCPv4, then the same thing with DHCPv6 makes some sense too. So I can see
implementing this protocol in DHCP servers, but maybe it shouldn't be part
of the DHCP protocol v4 or v6.

I understand why DHCPv4 and DHCPv6 are different and I mostly agree with
the reasons. Nevertheless, when a naive network admin looks to implement
IPv6 they think, oh, I can use DHCPv6 and it will work the same as DHCPv4,
and it is a bit of a bait-and-switch when they learn it doesn't work that
way. This DHCPv6 bait-and-switch is a big hindrance to IPv6 adoption
especially for enterprises with operational workflows built around the way
DHCPv4 works.

So, if we add a capability like this it needs to be operationally similar
for both IPv6 and IPv4.

Thanks.



-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

--00000000000032448d05753bfca1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Thu, Sep 6, 2018 at 5:27 AM, Lorenzo Colitti <span =
dir=3D"ltr">&lt;<a href=3D"mailto:lorenzo=3D40google.com@dmarc.ietf.org" ta=
rget=3D"_blank">lorenzo=3D40google.com@dmarc.ietf.org</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On Thu, Sep 6, 201=
8 at 4:53 AM Rajiv Asati (rajiva) &lt;rajiva=3D<a href=3D"mailto:40cisco.co=
m@dmarc.ietf.org" target=3D"_blank">40cisco.com@dmarc.<wbr>ietf.org</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-3037907662634201436gmail-m_-3491792704977201122WordS=
ection1">
<p class=3D"MsoNormal">BTW, section 2.3.2 <a href=3D"https://tools.ietf.org=
/html/draft-ietf-dnsop-isp-ip6rdns-05#section-2.3.2" target=3D"_blank">
https://tools.ietf.org/html/<wbr>draft-ietf-dnsop-isp-ip6rdns-<wbr>05#secti=
on-2.3.2</a> reminded me of the solution described here for tracking MAC-IP=
 address coupling in environments such as those of enterprises etc.<u></u><=
u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><a href=3D"https://tools.ietf.org/html/draft-asati-d=
hc-ipv6-autoconfig-address-tracking" target=3D"_blank">https://tools.ietf.o=
rg/html/<wbr>draft-asati-dhc-ipv6-<wbr>autoconfig-address-tracking</a></p><=
/div></div></blockquote><div><br></div><div>I wonder if it&#39;s time to re=
vive that draft? It would seem to be the easiest solution to support addres=
s tracking in existing architectures built around DHCP, and could facilitat=
e enterprise networks transitioning from IPv4 to IPv6.</div></div></div></d=
iv></blockquote><div><br></div><div>I&#39;ve always thought this is an inte=
resting idea, however, I think it needs to be done for both IPv6 and IPv4.=
=C2=A0 IPv4 can have statically configured hosts as well.=C2=A0</div><div><=
br></div><div>Also, I&#39;m not sure it should be part of DHCPv6 or DHCPv4 =
protocols though, maybe it should be its own protocol. The trust model betw=
een the routers and a server for this function is quite different than the =
trust model for host learning their configuration. It probably makes sense =
to have a common database with DHCP, especially DHCPv4 since this is the on=
ly practical way to automatically configure IPv4 hosts. If you have a commo=
n database with DHCPv4, then the same thing with DHCPv6 makes some sense to=
o. So I can see implementing this protocol in DHCP servers, but maybe it sh=
ouldn&#39;t be part of the DHCP protocol v4 or v6.</div><div><br></div><div=
>I understand why DHCPv4 and DHCPv6 are different and I mostly agree with t=
he reasons. Nevertheless, when a naive network admin looks to implement IPv=
6 they think, oh, I can use DHCPv6 and it will work the same as DHCPv4, and=
 it is a bit of a bait-and-switch when they learn it doesn&#39;t work that =
way. This DHCPv6 bait-and-switch is a big hindrance to IPv6 adoption especi=
ally for enterprises with operational workflows built around the way DHCPv4=
 works.=C2=A0=C2=A0</div><div><br></div><div>So, if we add a capability lik=
e this it needs to be operationally similar for both IPv6 and IPv4.</div><d=
iv><br></div><div>Thanks.</div><div>=C2=A0<br></div></div><br clear=3D"all"=
><div><br></div>-- <br><div class=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@u=
mn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; Tele=
communication Services<br>Office of Information Technology<br>University of=
 Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: 612=
-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D </div>
</div></div></div>

--00000000000032448d05753bfca1--


From nobody Thu Sep  6 16:23:12 2018
Return-Path: <kawashimam@vx.jp.nec.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A05D130F59; Thu,  6 Sep 2018 16:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Uu8g6-lA_vR7; Thu,  6 Sep 2018 16:23:06 -0700 (PDT)
Received: from tyo162.gate.nec.co.jp (tyo162.gate.nec.co.jp [114.179.232.162]) (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 17CB3130F21; Thu,  6 Sep 2018 16:23:05 -0700 (PDT)
Received: from mailgate02.nec.co.jp ([114.179.233.122]) by tyo162.gate.nec.co.jp (8.15.1/8.15.1) with ESMTPS id w86NMs0l022004 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 7 Sep 2018 08:22:54 +0900
Received: from mailsv01.nec.co.jp (mailgate-v.nec.co.jp [10.204.236.94]) by mailgate02.nec.co.jp (8.15.1/8.15.1) with ESMTP id w86NMsVi006682; Fri, 7 Sep 2018 08:22:54 +0900
Received: from mail02.kamome.nec.co.jp (mail02.kamome.nec.co.jp [10.25.43.5]) by mailsv01.nec.co.jp (8.15.1/8.15.1) with ESMTP id w86NMrwQ004247;  Fri, 7 Sep 2018 08:22:54 +0900
Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.150] [10.38.151.150]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-3426182; Fri, 7 Sep 2018 08:22:29 +0900
Received: from BPXM24GP.gisp.nec.co.jp ([10.38.151.216]) by BPXC22GP.gisp.nec.co.jp ([10.38.151.150]) with mapi id 14.03.0319.002; Fri, 7 Sep 2018 08:22:28 +0900
From: Masanobu Kawashima <kawashimam@vx.jp.nec.com>
To: Ron Bonica <rbonica@juniper.net>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, Hans Liu <Hans.Liu@dlinkcorp.com>
CC: "draft-ietf-v6ops-transition-ipv4aas@ietf.org" <draft-ietf-v6ops-transition-ipv4aas@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-08
Thread-Index: AQHURindfv+I0pIKlkqdGy5RQWBj9aTj43Kw
Date: Thu, 6 Sep 2018 23:22:27 +0000
Message-ID: <81A3232BEF82944C8F23DB1CFE276F0F49661FB0@BPXM24GP.gisp.nec.co.jp>
References: <03C229FA-94D2-4163-9E7A-5C4B8618DFC6@consulintel.es>
In-Reply-To: <03C229FA-94D2-4163-9E7A-5C4B8618DFC6@consulintel.es>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.3.141.178]
Content-Type: multipart/alternative; boundary="_000_81A3232BEF82944C8F23DB1CFE276F0F49661FB0BPXM24GPgispnec_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CSaN23QHn0uYKX5PIU1NY6-HXT0>
Subject: Re: [v6ops] IPR: draft-ietf-v6ops-transition-ipv4aas-08
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 23:23:10 -0000

--_000_81A3232BEF82944C8F23DB1CFE276F0F49661FB0BPXM24GPgispnec_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpPbiB0aGUgc2FtZSBwYWdlLiBJ4oCZbSBub3QgYXdhcmUgb2YgYW55IElQUi4NCg0KUmVnYXJk
cywNCk1hc2Fub2J1DQoNCj09PT09PT09PT09PT09PT09PT09PT09PQ0KIE5FQyBQbGF0Zm9ybXMs
IEx0ZC4NCiBLQVdBU0hJTUEgTWFzYW5vYnUNCiBrYXdhc2hpbWFtQHZ4LmpwLm5lYy5jb20NCiBo
dHRwczovL3d3dy5uZWNwbGF0Zm9ybXMuY28uanAvZW4vDQo9PT09PT09PT09PT09PT09PT09PT09
PT0NCg0KDQpGcm9tOiBKT1JESSBQQUxFVCBNQVJUSU5FWiA8am9yZGkucGFsZXRAY29uc3VsaW50
ZWwuZXM+DQpTZW50OiBGcmlkYXksIFNlcHRlbWJlciA3LCAyMDE4IDY6MzcgQU0NClRvOiBIYW5z
IExpdSA8SGFucy5MaXVAZGxpbmtjb3JwLmNvbT47IFJvbiBCb25pY2EgPHJib25pY2FAanVuaXBl
ci5uZXQ+DQpDYzogZHJhZnQtaWV0Zi12Nm9wcy10cmFuc2l0aW9uLWlwdjRhYXNAaWV0Zi5vcmc7
IHY2b3BzQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3Y2b3BzXSBJUFI6IGRyYWZ0LWlldGYtdjZv
cHMtdHJhbnNpdGlvbi1pcHY0YWFzLTA4DQoNClNhbWUgZm9yIG1lLCBub3QgYXdhcmUgb2YgYW55
IElQUi4NCg0KUmVnYXJkcywNCkpvcmRpDQoNCg0KDQpEZTogdjZvcHMgPHY2b3BzLWJvdW5jZXNA
aWV0Zi5vcmc8bWFpbHRvOnY2b3BzLWJvdW5jZXNAaWV0Zi5vcmc+PiBlbiBub21icmUgZGUgSGFu
cyBMaXUgPEhhbnMuTGl1QGRsaW5rY29ycC5jb208bWFpbHRvOkhhbnMuTGl1QGRsaW5rY29ycC5j
b20+Pg0KRmVjaGE6IHZpZXJuZXMsIDcgZGUgc2VwdGllbWJyZSBkZSAyMDE4LCAxOjU4DQpQYXJh
OiBSb24gQm9uaWNhIDxyYm9uaWNhQGp1bmlwZXIubmV0PG1haWx0bzpyYm9uaWNhQGp1bmlwZXIu
bmV0Pj4NCkNDOiAiZHJhZnQtaWV0Zi12Nm9wcy10cmFuc2l0aW9uLWlwdjRhYXNAaWV0Zi5vcmc8
bWFpbHRvOmRyYWZ0LWlldGYtdjZvcHMtdHJhbnNpdGlvbi1pcHY0YWFzQGlldGYub3JnPiIgPGRy
YWZ0LWlldGYtdjZvcHMtdHJhbnNpdGlvbi1pcHY0YWFzQGlldGYub3JnPG1haWx0bzpkcmFmdC1p
ZXRmLXY2b3BzLXRyYW5zaXRpb24taXB2NGFhc0BpZXRmLm9yZz4+LCAidjZvcHNAaWV0Zi5vcmc8
bWFpbHRvOnY2b3BzQGlldGYub3JnPiIgPHY2b3BzQGlldGYub3JnPG1haWx0bzp2Nm9wc0BpZXRm
Lm9yZz4+DQpBc3VudG86IFJlOiBbdjZvcHNdIElQUjogZHJhZnQtaWV0Zi12Nm9wcy10cmFuc2l0
aW9uLWlwdjRhYXMtMDgNCg0KSSdtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIGFnYWluc3QgdGhpcyBk
cmFmdC4NCg0KQmVzdCByZWdhcmRzLA0KSGFucw0KDQpPbiBTZXAgNiwgMjAxOCwgYXQgMTA6MzEg
UE0sIFJvbiBCb25pY2EgPHJib25pY2FAanVuaXBlci5uZXQ8bWFpbHRvOnJib25pY2FAanVuaXBl
ci5uZXQ+PiB3cm90ZToNCg0KQ28tYXV0aG9ycywNCg0KUGxlYXNlIHNlbmQgbWFpbCB0byB0aGUg
bGlzdCBzdGF0aW5nIHdoZXRoZXIgeW91IGtub3cgb2YgYW55IElQUiByZWdhcmRpbmcgZHJhZnQt
aWV0Zi12Nm9wcy10cmFuc2l0aW9uLWlwdjRhYXMtMDguDQoNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9uDQoNCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fIHY2b3BzIG1haWxpbmcgbGlzdCB2Nm9wc0BpZXRm
Lm9yZzxtYWlsdG86djZvcHNAaWV0Zi5vcmc+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vdjZvcHMNCg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKg0KSVB2NCBpcyBvdmVyDQpBcmUgeW91IHJlYWR5IGZvciB0aGUgbmV3IEludGVybmV0
ID8NCmh0dHA6Ly93d3cuY29uc3VsaW50ZWwuZXMNClRoZSBJUHY2IENvbXBhbnkNCg0KVGhpcyBl
bGVjdHJvbmljIG1lc3NhZ2UgY29udGFpbnMgaW5mb3JtYXRpb24gd2hpY2ggbWF5IGJlIHByaXZp
bGVnZWQgb3IgY29uZmlkZW50aWFsLiBUaGUgaW5mb3JtYXRpb24gaXMgaW50ZW5kZWQgdG8gYmUg
Zm9yIHRoZSBleGNsdXNpdmUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsKHMpIG5hbWVkIGFib3ZlIGFu
ZCBmdXJ0aGVyIG5vbi1leHBsaWNpbHR5IGF1dGhvcml6ZWQgZGlzY2xvc3VyZSwgY29weWluZywg
ZGlzdHJpYnV0aW9uIG9yIHVzZSBvZiB0aGUgY29udGVudHMgb2YgdGhpcyBpbmZvcm1hdGlvbiwg
ZXZlbiBpZiBwYXJ0aWFsbHksIGluY2x1ZGluZyBhdHRhY2hlZCBmaWxlcywgaXMgc3RyaWN0bHkg
cHJvaGliaXRlZCBhbmQgd2lsbCBiZSBjb25zaWRlcmVkIGEgY3JpbWluYWwgb2ZmZW5zZS4gSWYg
eW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCBiZSBhd2FyZSB0aGF0IGFueSBkaXNj
bG9zdXJlLCBjb3B5aW5nLCBkaXN0cmlidXRpb24gb3IgdXNlIG9mIHRoZSBjb250ZW50cyBvZiB0
aGlzIGluZm9ybWF0aW9uLCBldmVuIGlmIHBhcnRpYWxseSwgaW5jbHVkaW5nIGF0dGFjaGVkIGZp
bGVzLCBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLCB3aWxsIGJlIGNvbnNpZGVyZWQgYSBjcmltaW5h
bCBvZmZlbnNlLCBzbyB5b3UgbXVzdCByZXBseSB0byB0aGUgb3JpZ2luYWwgc2VuZGVyIHRvIGlu
Zm9ybSBhYm91dCB0aGlzIGNvbW11bmljYXRpb24gYW5kIGRlbGV0ZSBpdC4NCg==

--_000_81A3232BEF82944C8F23DB1CFE276F0F49661FB0BPXM24GPgispnec_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDE1IChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQov
KiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiLvvK3vvLMg
5piO5pydIjsNCglwYW5vc2UtMToyIDIgNiA5IDQgMiA1IDggMyA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6Iu+8re+8syDjgrTjgrfjg4Pjgq8iOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDcg
MiA1IDggMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJ
cGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OiLvvK3vvLMg77yw44K044K344OD44KvIjsNCglwYW5vc2UtMToyIDExIDYg
MCA3IDIgNSA4IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQO+8re+8syDjgrTj
grfjg4Pjgq8iOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDcgMiA1IDggMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6IlxA77yt77yzIO+8sOOCtOOCt+ODg+OCryI7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiXEDvvK3vvLMg5piO5pydIjsNCglwYW5vc2UtMToyIDIgNiA5IDQgMiA1
IDggMyA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MG1tOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmgxDQoJe21zby1zdHlsZS1wcmlvcml0eTo5Ow0KCW1zby1zdHlsZS1s
aW5rOiLopovlh7rjgZcgMSBcKOaWh+Wtl1wpIjsNCgltYXJnaW46MG1tOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglwYWdlLWJyZWFrLWFmdGVyOmF2b2lkOw0KCWZvbnQtc2l6ZToxMS4wcHQ7
DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsc2Fucy1zZXJpZjsNCglmb250LXdlaWdodDpub3JtYWw7
fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
Y29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bh
bi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29Ob1NwYWNpbmcsIGxp
Lk1zb05vU3BhY2luZywgZGl2Lk1zb05vU3BhY2luZw0KCXttc28tc3R5bGUtcHJpb3JpdHk6MTsN
CgltYXJnaW46MG1tOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uMQ0KCXttc28t
c3R5bGUtbmFtZToi6KaL5Ye644GXIDEgXCjmloflrZdcKSI7DQoJbXNvLXN0eWxlLXByaW9yaXR5
Ojk7DQoJbXNvLXN0eWxlLWxpbms6Iuimi+WHuuOBlyAxIjsNCglmb250LWZhbWlseToiVGFob21h
IixzYW5zLXNlcmlmO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1h
bDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRv
Ow0KCW1hcmdpbi1yaWdodDowbW07DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFy
Z2luLWxlZnQ6MG1tOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LHNhbnMtc2VyaWY7fQ0Kc3Bhbi5pbA0KCXttc28tc3R5bGUtbmFtZTppbDt9DQpzcGFuLjIzDQoJ
e21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi4yNA0KCXttc28tc3R5bGUtdHlwZTpwZXJz
b25hbC1yZXBseTsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjsNCgljb2xv
cjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5
Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBw
dCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDMwLjBtbSA3MC44NXB0IDMwLjBtbTt9DQpkaXYu
V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIx
MDI2Ij4NCjx2OnRleHRib3ggaW5zZXQ9IjUuODVwdCwuN3B0LDUuODVwdCwuN3B0IiAvPg0KPC9v
OnNoYXBlZGVmYXVsdHM+PC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkpBIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9Ildv
cmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyxzZXJpZjtjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBS
b21hbiZxdW90OyxzZXJpZjtjb2xvcjojMUY0OTdEIj5PbiB0aGUgc2FtZSBwYWdlLiBJ4oCZbSBu
b3QgYXdhcmUgb2YgYW55IElQUi4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21h
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+UmVnYXJkcywNCjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEIj5NYXNhbm9idQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJ0ZXh0LWFsaWduOmp1c3RpZnk7dGV4dC1qdXN0aWZ5OmludGVyLWlkZW9ncmFwaCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPj09PT09PT09PT09PT09PT09PT09
PT09PQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
InRleHQtYWxpZ246anVzdGlmeTt0ZXh0LWp1c3RpZnk6aW50ZXItaWRlb2dyYXBoIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFo
b21hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7TkVDIFBsYXRmb3Jtcywg
THRkLiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtYWxp
Z246anVzdGlmeTt0ZXh0LWp1c3RpZnk6aW50ZXItaWRlb2dyYXBoIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7S0FXQVNISU1BIE1hc2Fub2J1Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0idGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVzdGlmeTppbnRlci1pZGVvZ3JhcGgiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDtrYXdhc2hpbWFtQHZ4
LmpwLm5lYy5jb20mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmp1c3RpZnk7dGV4
dC1qdXN0aWZ5OmludGVyLWlkZW9ncmFwaCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPiZuYnNwO2h0dHBzOi8vd3d3Lm5lY3BsYXRmb3Jtcy5jby5qcC9lbi8mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmp1c3RpZnk7dGV4dC1qdXN0aWZ5OmludGVyLWlk
ZW9ncmFwaCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQt
ZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPj09PT09
PT09PT09PT09PT09PT09PT09PQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtUaW1l
cyBOZXcgUm9tYW4mcXVvdDssc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssc2VyaWY7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBtbSAwbW0gMG1tIDQuMHB0
Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUx
RTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwbW0gMG1tIDBtbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48Yj48c3BhbiBsYW5nPSJFTi1VUyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVT
Ij4gSk9SREkgUEFMRVQgTUFSVElORVogJmx0O2pvcmRpLnBhbGV0QGNvbnN1bGludGVsLmVzJmd0
Ow0KPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgU2VwdGVtYmVyIDcsIDIwMTggNjozNyBBTTxi
cj4NCjxiPlRvOjwvYj4gSGFucyBMaXUgJmx0O0hhbnMuTGl1QGRsaW5rY29ycC5jb20mZ3Q7OyBS
b24gQm9uaWNhICZsdDtyYm9uaWNhQGp1bmlwZXIubmV0Jmd0Ozxicj4NCjxiPkNjOjwvYj4gZHJh
ZnQtaWV0Zi12Nm9wcy10cmFuc2l0aW9uLWlwdjRhYXNAaWV0Zi5vcmc7IHY2b3BzQGlldGYub3Jn
PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbdjZvcHNdIElQUjogZHJhZnQtaWV0Zi12Nm9wcy10
cmFuc2l0aW9uLWlwdjRhYXMtMDg8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlNhbWUgZm9yIG1lLCBub3QgYXdhcmUg
b2YgYW55IElQUi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJs
YWNrIj48YnI+DQo8L3NwYW4+PHNwYW4gbGFuZz0iRVMtVFJBRCIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Y29sb3I6YmxhY2siPlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJF
Uy1UUkFEIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjpibGFjazttc28tZmFyZWFzdC1s
YW5ndWFnZTpFTi1VUyI+Sm9yZGk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVTLVRSQUQi
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJsYWNrO21zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVTLVRSQUQiIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRVMtVFJBRCIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwbW0gMG1tIDBtbSI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzUuNHB0Ij48Yj48c3Bh
biBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkRlOg0KPC9z
cGFuPjwvYj48c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6Ymxh
Y2siPnY2b3BzICZsdDs8YSBocmVmPSJtYWlsdG86djZvcHMtYm91bmNlc0BpZXRmLm9yZyI+djZv
cHMtYm91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7IGVuIG5vbWJyZSBkZSBIYW5zIExpdSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOkhhbnMuTGl1QGRsaW5rY29ycC5jb20iPkhhbnMuTGl1QGRsaW5rY29ycC5j
b208L2E+Jmd0Ozxicj4NCjxiPkZlY2hhOiA8L2I+dmllcm5lcywgNyBkZSBzZXB0aWVtYnJlIGRl
IDIwMTgsIDE6NTg8YnI+DQo8Yj5QYXJhOiA8L2I+Um9uIEJvbmljYSAmbHQ7PGEgaHJlZj0ibWFp
bHRvOnJib25pY2FAanVuaXBlci5uZXQiPnJib25pY2FAanVuaXBlci5uZXQ8L2E+Jmd0Ozxicj4N
CjxiPkNDOiA8L2I+JnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtdjZvcHMtdHJhbnNp
dGlvbi1pcHY0YWFzQGlldGYub3JnIj5kcmFmdC1pZXRmLXY2b3BzLXRyYW5zaXRpb24taXB2NGFh
c0BpZXRmLm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLXY2b3Bz
LXRyYW5zaXRpb24taXB2NGFhc0BpZXRmLm9yZyI+ZHJhZnQtaWV0Zi12Nm9wcy10cmFuc2l0aW9u
LWlwdjRhYXNAaWV0Zi5vcmc8L2E+Jmd0OywgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOnY2b3BzQGll
dGYub3JnIj52Nm9wc0BpZXRmLm9yZzwvYT4mcXVvdDsNCiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnY2
b3BzQGlldGYub3JnIj52Nm9wc0BpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+QXN1bnRvOiA8L2I+
UmU6IFt2Nm9wc10gSVBSOiBkcmFmdC1pZXRmLXY2b3BzLXRyYW5zaXRpb24taXB2NGFhcy0wODxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tbGVmdDozNS40cHQiPjxzcGFuIGxhbmc9IkVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDozNS40cHQiPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMjIyMjI7YmFj
a2dyb3VuZDp3aGl0ZSI+SSdtIG5vdCBhd2FyZSBvZiBhbnkmbmJzcDs8c3BhbiBjbGFzcz0iaWwi
PklQUjwvc3Bhbj4mbmJzcDthZ2FpbnN0IHRoaXMgZHJhZnQuPC9zcGFuPjxzcGFuIGxhbmc9IkVT
Ij4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6MG1tO21hcmdpbi1yaWdodDow
bW07bWFyZ2luLWJvdHRvbToxMi4wcHQ7bWFyZ2luLWxlZnQ6MzUuNHB0Ij4NCjxzcGFuIGxhbmc9
IkVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzUuNHB0Ij48c3BhbiBsYW5nPSJFUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMjIyMjIyO2JhY2tncm91bmQ6d2hpdGUiPkJlc3QgcmVnYXJkcyw8L3Nw
YW4+PHNwYW4gbGFuZz0iRVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNS40cHQiPjxzcGFuIGxh
bmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMjIyMjI7YmFja2dyb3VuZDp3aGl0ZSI+SGFuczwvc3Bh
bj48c3BhbiBsYW5nPSJFUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM1LjRwdCI+PHNwYW4gbGFu
Zz0iRVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzUuNHB0Ij48c3BhbiBsYW5nPSJFUyI+T24gU2Vw
IDYsIDIwMTgsIGF0IDEwOjMxIFBNLCBSb24gQm9uaWNhICZsdDs8YSBocmVmPSJtYWlsdG86cmJv
bmljYUBqdW5pcGVyLm5ldCI+cmJvbmljYUBqdW5pcGVyLm5ldDwvYT4mZ3Q7IHdyb3RlOjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1sZWZ0OjM1LjRwdCI+PHNwYW4gbGFuZz0iRVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDowbW07bWFyZ2luLXJpZ2h0OjBtbTttYXJnaW4tYm90dG9tOjEyLjBwdDttYXJn
aW4tbGVmdDozNS40cHQiPg0KPHNwYW4gbGFuZz0iRVMiPkNvLWF1dGhvcnMsPGJyPg0KPGJyPg0K
UGxlYXNlIHNlbmQgbWFpbCB0byB0aGUgbGlzdCBzdGF0aW5nIHdoZXRoZXIgeW91IGtub3cgb2Yg
YW55IElQUiByZWdhcmRpbmcgZHJhZnQtaWV0Zi12Nm9wcy10cmFuc2l0aW9uLWlwdjRhYXMtMDgu
PGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Um9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1s
ZWZ0OjM1LjRwdCI+PHNwYW4gbGFuZz0iRVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MzUuNHB0Ij48c3BhbiBsYW5nPSJFUyI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18gdjZvcHMgbWFpbGluZyBsaXN0DQo8YSBocmVmPSJtYWlsdG86djZvcHNA
aWV0Zi5vcmciPnY2b3BzQGlldGYub3JnPC9hPiA8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzIj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vdjZvcHM8L2E+IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxl
PSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O++8re+8syDvvLDjgrTjgrfjg4Pj
gq8mcXVvdDsiPjxicj4NCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKio8YnI+DQpJUHY0IGlzIG92ZXI8YnI+DQpBcmUgeW91IHJlYWR5IGZvciB0aGUgbmV3IElu
dGVybmV0ID88YnI+DQo8YSBocmVmPSJodHRwOi8vd3d3LmNvbnN1bGludGVsLmVzIj5odHRwOi8v
d3d3LmNvbnN1bGludGVsLmVzPC9hPjxicj4NClRoZSBJUHY2IENvbXBhbnk8YnI+DQo8YnI+DQpU
aGlzIGVsZWN0cm9uaWMgbWVzc2FnZSBjb250YWlucyBpbmZvcm1hdGlvbiB3aGljaCBtYXkgYmUg
cHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwuIFRoZSBpbmZvcm1hdGlvbiBpcyBpbnRlbmRlZCB0
byBiZSBmb3IgdGhlIGV4Y2x1c2l2ZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwocykgbmFtZWQgYWJv
dmUgYW5kIGZ1cnRoZXIgbm9uLWV4cGxpY2lsdHkgYXV0aG9yaXplZCBkaXNjbG9zdXJlLCBjb3B5
aW5nLCBkaXN0cmlidXRpb24gb3IgdXNlIG9mDQogdGhlIGNvbnRlbnRzIG9mIHRoaXMgaW5mb3Jt
YXRpb24sIGV2ZW4gaWYgcGFydGlhbGx5LCBpbmNsdWRpbmcgYXR0YWNoZWQgZmlsZXMsIGlzIHN0
cmljdGx5IHByb2hpYml0ZWQgYW5kIHdpbGwgYmUgY29uc2lkZXJlZCBhIGNyaW1pbmFsIG9mZmVu
c2UuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgYmUgYXdhcmUgdGhhdCBh
bnkgZGlzY2xvc3VyZSwgY29weWluZywgZGlzdHJpYnV0aW9uIG9yIHVzZSBvZiB0aGUgY29udGVu
dHMNCiBvZiB0aGlzIGluZm9ybWF0aW9uLCBldmVuIGlmIHBhcnRpYWxseSwgaW5jbHVkaW5nIGF0
dGFjaGVkIGZpbGVzLCBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLCB3aWxsIGJlIGNvbnNpZGVyZWQg
YSBjcmltaW5hbCBvZmZlbnNlLCBzbyB5b3UgbXVzdCByZXBseSB0byB0aGUgb3JpZ2luYWwgc2Vu
ZGVyIHRvIGluZm9ybSBhYm91dCB0aGlzIGNvbW11bmljYXRpb24gYW5kIGRlbGV0ZSBpdC48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_81A3232BEF82944C8F23DB1CFE276F0F49661FB0BPXM24GPgispnec_--


From nobody Thu Sep  6 16:42:19 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C69130F13; Thu,  6 Sep 2018 16:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 u-8CIOBp3Yvh; Thu,  6 Sep 2018 16:42:13 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 B90A612D7F8; Thu,  6 Sep 2018 16:42:13 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 699DA3AB041; Thu,  6 Sep 2018 23:42:13 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 146B4160055; Thu,  6 Sep 2018 23:42:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id EE63716007C; Thu,  6 Sep 2018 23:42:11 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id pOAeZHR2SGEu; Thu,  6 Sep 2018 23:42:11 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 994B7160055; Thu,  6 Sep 2018 23:42:10 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org>
Date: Fri, 7 Sep 2018 09:42:07 +1000
Cc: v6ops@ietf.org, draft-ietf-doh-dns-over-https.all@ietf.org, evyncke@cisco.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_nvg4fV8dsQaKRvaCJMueWSg-TQ>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Sep 2018 23:42:17 -0000

Can we please have some technological leadership in the IETF and
say that DNS64 is technically flawed for a number of reason and
SHOULD NOT be used.  It was a short term hack that really has
out lived its usefulness.  Just because cell phone account software
couldn=E2=80=99t unwrap a IPv4 in IPv6 packet to do accounting was NOT
a good reason to inflict DNS64 long term on the Internet.  Just
because 3GPP was too scared to deploy DS-Lite was NOT a a good
reason to inflict DNS64 long term on the Internet.

You can get all the benefits of DNS64 by putting the mapping in
getaddrinfo() after advising the node what the NAT64 mapping is.

There is NO NEED to do in the mapping in the name server.  DNS64
was presented as a SHORT TERM solution.

* DNS64 does not work with DNSSEC.  Even IANA can=E2=80=99t setup =
IPV4ONLY.ARPA
to make it work correctly with DNS64 as IANA has signed IPV4ONLY.ARPA
and won=E2=80=99t remove the signatures without a RFC and we all know =
how long
that process takes.

* DNS64 does not work with iterative resolvers on nodes.

* DNS64 does not work with external recursive servers.

It has always been a flawed technology that was deployed as a stop-gap.

Stop trying to get the rest of the internet to change because some
sites are continuing to deploy DNS64 which is what this draft does.
That is the tail wagging the dog.

Similarly IPV4ONLY.ARPA as a NAT64 prefix discovery mechanism is
technically flawed even after IANA fixes the DNSSEC issues.

* IPV4ONLY.ARPA does not work with iterative resolvers on nodes.

* IPV4ONLY.ARPA does not work with external recursive servers.

DS-Lite has a mechanism to distribute the mapping information to
every node.

MAP-T and MAP-E have mechanisms to distribute the mapping
information to every node.  The existing NAT64 boxes can be used
with MAP-T.

Mark

> On 7 Sep 2018, at 2:20 am, Lee Howard <lee@asgard.org> wrote:
>=20
>=20
>=20
> On 09/05/2018 05:50 PM, Erik Nygren wrote:
>> DNSSEC isn't the only threat here.  Clients implementing protocols =
such as DoH also bypass the DNS64.
>> draft-ietf-doh-dns-over-https-14 does say:
>>=20
>>    Local policy considerations and similar factors mean different DNS
>>    servers may provide different results to the same query, for =
instance
>>    in split DNS configurations [RFC6950].  It logically follows that =
the
>>    server that is queried can influence the end result.  Therefore a
>>    client's choice of DNS server may affect the responses it gets to =
its
>>    queries.  For example, in the case of DNS64 [RFC6147], the choice
>>    could affect whether IPv6/IPv4 translation will work at all.
>>=20
>> I'm not sure what the best way to approach this is in this draft.=20
>=20
>=20
> Yes, I remember reading that in DoH and rolling my eyes. The best =
response is to strengthen the statement in that draft to say, "Hundreds =
of millions of users behind DNS64 will be unable to use DoH, unless IPv6 =
resource records are available, bypassing the DNS64 function." And maybe =
to point at this draft.
>=20
> I note that no OpsDir review has been submitted =
https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/
> This is an operational issue.
>=20
>> For example:
>>=20
>> * Acknowledge that DNS64 is a shortish-term hack that only works in =
constrained environments.     If this is the case, that might argue that =
this draft should be at most Informational and not BCP?=20
>=20
> "Constrained environments" in this case meaning "the IPv4 Internet."=20=

> This draft is BCP for domains with DNSSEC. It makes no recommendation =
for DNS64 deployers.
>>=20
>> * Commit to DNS64 being a robust part of the architecture and cover =
topics more broadly than just DNSSEC?   Is there a way to handle the DOH =
case short of mandating that clients implementing DOH also do =
bump-in-the-API or client-side DNS64 synthesis or 464xlat?  If this is =
the case, should there be more firm wording in =
draft-ietf-doh-dns-over-https-14.  I suspect other conflicts will also =
appear over time.
>=20
> I wouldn't call it "robust," but I'd call it "widespread." I support =
your suggestion that the BCP be applied more broadly, although it may =
start to become redundant with BCP177 (rfc6540, "IPv6 Support Required =
for All IPv6-Capable Nodes").
>=20
>> Is there really value in picking some middle ground between these?
>>=20
>> Is there concrete data on how often DNSSEC and DNS64 cause =
interaction issues and where?  They shouldn't on the recursive resolver =
itself.  How often are clients redoing DNSSEC validation and running =
into issues here?
>>=20
>> A separate pragmatic/cynic question is whether we think this will =
influence behavior?  I don't have a positive feeling that those who =
control whether a zone has DNSSEC enabled also have control over whether =
AAAA records are present for dual-stacked content in the zone.  Those =
are often separate actors.  Will a recommendation here have any =
substantive impact, and is there an audience who will be able to take =
action on this?
>=20
> I think this problem is largely unnoticed, and needs a recommendation =
to address it. It may be unnoticed because the 15% of domains that use =
DNSSEC [https://stats.labs.apnic.net/dnssec/XA?c=3DXA&x=3D1&g=3D1&r=3D1&w=3D=
7&g=3D0] are more likely to be among the 24% of domains that have IPv6 =
[http://www.employees.org/~dwing/aaaa-stats/]  (or the other way around) =
because the operators are early adopters.=20
>=20
>=20
> Lee
>=20
>>=20
>>        Erik
>>=20
>> =20
>>=20
>>=20
>> On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica <rbonica@juniper.net> =
wrote:
>> Folks,
>>=20
>> Each week between now and IETF 103, we will review and discuss one =
draft with an eye towards progressing it.
>>=20
>> This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
>>=20
>>                                       Fred and Ron
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>>=20
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Thu Sep  6 17:48:24 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3CD9130F84; Thu,  6 Sep 2018 17:48:14 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 deXrVNu0UGDe; Thu,  6 Sep 2018 17:48:11 -0700 (PDT)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 D591912F295; Thu,  6 Sep 2018 17:48:10 -0700 (PDT)
Received: by mail-ed1-x52f.google.com with SMTP id f4-v6so10307837edq.3; Thu, 06 Sep 2018 17:48:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=JhNUwhdsIFoGuyItoE+x53rVUZr/aeVA/31wL9+lotM=; b=AB9iswW+xOEcHbd0epywYHE2E7BimLcxJa1JEDjfRgPi+RGY1E3bFbmJp350qUpALM hD4JSSW8YcKG0F9JN1jMjo1ymESgrCaUp38p+lQ9ejLQpVW6yZ5USztHV/wbxyes/ZTM kkL/pYPQF8yvoMC3wTGrXBwl1alII8Ix6xVBGrEPdH67L4TwXwUXinnk24aUOy4P3NVX CVTDKpnJnQBo1Qech7hOq2Owxrs9KFUQLRE0c+03Sz9HtAa5ENfkJ46BeHO/4yADkj8c qC/ZhB4IrU2qFe0dSSK5RTjs2NU03PgCK44UrIcRapWOPDIdANUKp4gh6s8SYGfb2Q2G aMMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=JhNUwhdsIFoGuyItoE+x53rVUZr/aeVA/31wL9+lotM=; b=LBR/2EpaSJ2C7LGABVZIYAr0iai+evQiKxgU9m/jBE/A02CfMJGi746BhYXvGTvtPU NcdIweZqu3P6qCca5jyyph+d23CJlxkEzVL1VsGh712j8d7q369MDS5l7PBoqGa3JXUK Hu3wVB7KhDMRQwb0ceBNyh8jiV6ivnrxji1nJ9m+sTmYOsOoXo8o7o5bp50oYaNiSsqZ mjifYm8bsMVzcj/AYGice5Wl1+mJbmN8HGAQTZ5Wpp9Ktu82aKn9T+uAhBZ8giPd/nL1 eOabRsZSRxmlhIZ8yrEXnscVZ/bAQXeEvd3hVoSfpwpsslenq5PM06fX0Y0sRzqUaR8z mgyQ==
X-Gm-Message-State: APzg51ApufYiYKgdgZZ1g9myLeygfo5AJosF4yu0t/rZGEvBvMHwK6Bf +iGh0T37UtTEEZzJYwuEDf4=
X-Google-Smtp-Source: ANB0VdZwcxLqbHK9MoCrndarH7vXszVTbqnc4nPRT7fWFtpbtjDadR8U2R7ugZ0vjgKPbg7dXti5mw==
X-Received: by 2002:a50:8d5e:: with SMTP id t30-v6mr6113652edt.256.1536281289423;  Thu, 06 Sep 2018 17:48:09 -0700 (PDT)
Received: from ?IPv6:2601:646:c005:a10:101c:8bcb:f:f4ab? ([2601:646:c005:a10:101c:8bcb:f:f4ab]) by smtp.gmail.com with ESMTPSA id b9-v6sm3917323edk.62.2018.09.06.17.48.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Sep 2018 17:48:08 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <D69D42E5-720E-482B-84CF-9EA4F0863B6E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_934F3071-23C1-4240-93E9-84B381F7B9B3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 6 Sep 2018 17:48:04 -0700
In-Reply-To: <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org>
Cc: Lee Howard <lee@asgard.org>, draft-ietf-doh-dns-over-https.all@ietf.org, v6ops@ietf.org
To: Mark Andrews <marka@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Oa4m15eOIBB2WA_CIwAYdjgZyIA>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 00:48:21 -0000

--Apple-Mail=_934F3071-23C1-4240-93E9-84B381F7B9B3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I think you're looking for =
https://tools.ietf.org/html/draft-pref64folks-6man-ra-pref64. Under =
discussion in 6man.

> On Sep 6, 2018, at 4:42 PM, Mark Andrews <marka@isc.org> wrote:
>=20
> Can we please have some technological leadership in the IETF and
> say that DNS64 is technically flawed for a number of reason and
> SHOULD NOT be used.  It was a short term hack that really has
> out lived its usefulness.  Just because cell phone account software
> couldn=E2=80=99t unwrap a IPv4 in IPv6 packet to do accounting was NOT
> a good reason to inflict DNS64 long term on the Internet.  Just
> because 3GPP was too scared to deploy DS-Lite was NOT a a good
> reason to inflict DNS64 long term on the Internet.
>=20
> You can get all the benefits of DNS64 by putting the mapping in
> getaddrinfo() after advising the node what the NAT64 mapping is.
>=20
> There is NO NEED to do in the mapping in the name server.  DNS64
> was presented as a SHORT TERM solution.
>=20
> * DNS64 does not work with DNSSEC.  Even IANA can=E2=80=99t setup =
IPV4ONLY.ARPA
> to make it work correctly with DNS64 as IANA has signed IPV4ONLY.ARPA
> and won=E2=80=99t remove the signatures without a RFC and we all know =
how long
> that process takes.
>=20
> * DNS64 does not work with iterative resolvers on nodes.
>=20
> * DNS64 does not work with external recursive servers.
>=20
> It has always been a flawed technology that was deployed as a =
stop-gap.
>=20
> Stop trying to get the rest of the internet to change because some
> sites are continuing to deploy DNS64 which is what this draft does.
> That is the tail wagging the dog.
>=20
> Similarly IPV4ONLY.ARPA as a NAT64 prefix discovery mechanism is
> technically flawed even after IANA fixes the DNSSEC issues.
>=20
> * IPV4ONLY.ARPA does not work with iterative resolvers on nodes.
>=20
> * IPV4ONLY.ARPA does not work with external recursive servers.
>=20
> DS-Lite has a mechanism to distribute the mapping information to
> every node.
>=20
> MAP-T and MAP-E have mechanisms to distribute the mapping
> information to every node.  The existing NAT64 boxes can be used
> with MAP-T.
>=20
> Mark
>=20
>> On 7 Sep 2018, at 2:20 am, Lee Howard <lee@asgard.org> wrote:
>>=20
>>=20
>>=20
>> On 09/05/2018 05:50 PM, Erik Nygren wrote:
>>> DNSSEC isn't the only threat here.  Clients implementing protocols =
such as DoH also bypass the DNS64.
>>> draft-ietf-doh-dns-over-https-14 does say:
>>>=20
>>>   Local policy considerations and similar factors mean different DNS
>>>   servers may provide different results to the same query, for =
instance
>>>   in split DNS configurations [RFC6950].  It logically follows that =
the
>>>   server that is queried can influence the end result.  Therefore a
>>>   client's choice of DNS server may affect the responses it gets to =
its
>>>   queries.  For example, in the case of DNS64 [RFC6147], the choice
>>>   could affect whether IPv6/IPv4 translation will work at all.
>>>=20
>>> I'm not sure what the best way to approach this is in this draft.
>>=20
>>=20
>> Yes, I remember reading that in DoH and rolling my eyes. The best =
response is to strengthen the statement in that draft to say, "Hundreds =
of millions of users behind DNS64 will be unable to use DoH, unless IPv6 =
resource records are available, bypassing the DNS64 function." And maybe =
to point at this draft.
>>=20
>> I note that no OpsDir review has been submitted =
https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/
>> This is an operational issue.
>>=20
>>> For example:
>>>=20
>>> * Acknowledge that DNS64 is a shortish-term hack that only works in =
constrained environments.     If this is the case, that might argue that =
this draft should be at most Informational and not BCP?
>>=20
>> "Constrained environments" in this case meaning "the IPv4 Internet."
>> This draft is BCP for domains with DNSSEC. It makes no recommendation =
for DNS64 deployers.
>>>=20
>>> * Commit to DNS64 being a robust part of the architecture and cover =
topics more broadly than just DNSSEC?   Is there a way to handle the DOH =
case short of mandating that clients implementing DOH also do =
bump-in-the-API or client-side DNS64 synthesis or 464xlat?  If this is =
the case, should there be more firm wording in =
draft-ietf-doh-dns-over-https-14.  I suspect other conflicts will also =
appear over time.
>>=20
>> I wouldn't call it "robust," but I'd call it "widespread." I support =
your suggestion that the BCP be applied more broadly, although it may =
start to become redundant with BCP177 (rfc6540, "IPv6 Support Required =
for All IPv6-Capable Nodes").
>>=20
>>> Is there really value in picking some middle ground between these?
>>>=20
>>> Is there concrete data on how often DNSSEC and DNS64 cause =
interaction issues and where?  They shouldn't on the recursive resolver =
itself.  How often are clients redoing DNSSEC validation and running =
into issues here?
>>>=20
>>> A separate pragmatic/cynic question is whether we think this will =
influence behavior?  I don't have a positive feeling that those who =
control whether a zone has DNSSEC enabled also have control over whether =
AAAA records are present for dual-stacked content in the zone.  Those =
are often separate actors.  Will a recommendation here have any =
substantive impact, and is there an audience who will be able to take =
action on this?
>>=20
>> I think this problem is largely unnoticed, and needs a recommendation =
to address it. It may be unnoticed because the 15% of domains that use =
DNSSEC [https://stats.labs.apnic.net/dnssec/XA?c=3DXA&x=3D1&g=3D1&r=3D1&w=3D=
7&g=3D0] are more likely to be among the 24% of domains that have IPv6 =
[http://www.employees.org/~dwing/aaaa-stats/]  (or the other way around) =
because the operators are early adopters.
>>=20
>>=20
>> Lee
>>=20
>>>=20
>>>       Erik
>>>=20
>>>=20
>>>=20
>>>=20
>>> On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica <rbonica@juniper.net> =
wrote:
>>> Folks,
>>>=20
>>> Each week between now and IETF 103, we will review and discuss one =
draft with an eye towards progressing it.
>>>=20
>>> This week, please review and comment on =
draft-byrne-v6ops-dnssecaaaa.
>>>=20
>>>                                      Fred and Ron
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>=20
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>>=20
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

=
--------------------------------------------------------------------------=
------
The fact that there is a highway to hell and a stairway to heaven is an =
interesting comment on projected traffic volume...


--Apple-Mail=_934F3071-23C1-4240-93E9-84B381F7B9B3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluRysQACgkQEhdRnd2G
P+DxiQ/9EaI5gsklXv1U7GIqH8Fb1gfCgDHdViqxXgKWqpDZqr/yrMVwecJ0Kumr
Y8Yng5K47AT2Pig2BF1/NTCnCiTLBAaGFGJH6MjUeV9kMC1QNTu5ozZ5fCQEtySM
yTY5TFWPw1F8NUeeaoqVT+8nS0qIgNswBweVMegrFOKBCMDKE93qBqp/Bzmn37hy
aOhTDiI5z+Xa6viE+p5vssRzsRUPjQ79AUi1gQ7TQO5pZ2BCsTuw489UaAzlM5BZ
K+YhYmRcENKRjGzUo3ySnb3iSNhO/9FohIvNH+aAXQPhvJqoAbTsgOsjnyuh8Ieb
jsjwzFAeD5rOChp0R9TiLibecH3XTKjXpDTfjFuOihBcUMwhf3fab5YaJuRgP3O6
x28vinYaEHZ76LeM8b4oipE11rr7EdK6vSi8nS3myPEAvoEiOaQBI4b3rjgG4Jqg
3X2EYyUiubcHJdXmQTcpEEk85NCLqwnX4sgdtCAOnGq41fPdGp/bcLG5kb4oOO//
8VtDPcKKBDKXhXsdh6aFveEaS4BP6vSRZiseExlgsqyiUAfdSedmVx4A6akYGxhS
noCJTPWViwoLQ0b3OWLuS9T7IwVpXpWFQj9n5QFA7sy38gPo+91LCUZ/e4dwkh0O
2h6w7CYZViJHeeGfsU/O7bVu9sdUWHIEfMQMauUbgJRlCwx8XY0=
=bbIp
-----END PGP SIGNATURE-----

--Apple-Mail=_934F3071-23C1-4240-93E9-84B381F7B9B3--


From nobody Fri Sep  7 06:19:39 2018
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D63DE130DFC for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 06:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level: 
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, 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 zyBKPHKdNTAF for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 06:19:34 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 58ACF130DF6 for <v6ops@ietf.org>; Fri,  7 Sep 2018 06:19:34 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w87DJWYd107362 for <v6ops@ietf.org>; Fri, 7 Sep 2018 15:19:32 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6EFE0203839 for <v6ops@ietf.org>; Fri,  7 Sep 2018 15:19:32 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 655B1202034 for <v6ops@ietf.org>; Fri,  7 Sep 2018 15:19:32 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w87DJWqF026538 for <v6ops@ietf.org>; Fri, 7 Sep 2018 15:19:32 +0200
To: v6ops@ietf.org
References: <CAAObRXLe35KoONVsSO_oU+SRhMzMrKRE_SU-QNf2pGHYKpUrxA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <1ba1193b-f1ca-b51b-ebaa-d0e8312cc363@gmail.com>
Date: Fri, 7 Sep 2018 15:19:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAAObRXLe35KoONVsSO_oU+SRhMzMrKRE_SU-QNf2pGHYKpUrxA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/YJJXntmOwLJoI8GWbGx9XGi9ST0>
Subject: Re: [v6ops] How my Android phone got assigned with IPv6 address via 4G LTE?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 13:19:37 -0000

Le 27/08/2018 à 02:50, Davey Song a écrit :
> Hi folks,
> 
> Recently the IPv6 4G LTE of China moible and China Telecom is working. 
> And I got the address information on my android phone, like :
> 
> China Mobile : 2409:8900:8a10:6dof:4177:9599:de56:7092
> China Telecom: 240e:ff:b10a:54a9:b5f7:5e4c:2f2d:9847

Excellent.  My question is whether when this address is assigned on 
android you can ping6 some IPv6 site (maybe ping6 ipv6.google.com)?

Because there are some cellular operators that do assign IPv6 addresses 
to android and other phones but dont provide IPv6 connectivity to the 
Internet (can not ping6).

> My question is : How these IPv6 addresses are assigned to my pohone and 
> what type of address they are?

That can be answered definitely only by trying.  It's good to know the 
specs too, but better try it to know for sure.

There are three main 'native' ways into which that address could have 
been allocated to your android:
- maybe the android did a DHCPv6 request and the operator responded with
   a DHCPv6 acknowledgment containing the address.
- maybe the layer 2 protocol (IPv6CP - stands for Control Protocol, or
   ppp) negotiated an Interface ID of 64bit length, and then the router
   in the network sent a Router Advertisement, and then the android
   formed an address with the prefix in the RA and the IID negotiated
   earlier.
- maybe the layer 2 protocol negotiated the full IPv6 address rather
   than just the Interface ID (and there was no RA from a
   Router prior to forming an IPv6 address).

Then there are more non-native ways, like 'hacks' that are implemented 
by an application that is specific: it can form an IPv6 address by 
requesting it first with an IPv4 proprietary protocol.

All these I have seen in deployed cellular networks.

You can try it yourself by doing the following:
- contact the phone manufacturer to obtain key to be able to log in root
   in the smartphone.  They are legally obliged to allow you to.  Many
   already do (I know Huawei, SOny and and few others).
- log in the android and learn how to ls, and certainly not rm -rf /.
- then cross-compile a tshark or a tcpdump (it is a packet capture
   tool).
- run the packet dump tool to record which packets circulate (RA, DHCP,
   etc.)
- download the packet dumps to your laptop to see it on nice GUI with
   wireshark.
- identify whether android used pppd, or qmicli or mmicli in order to 
make the connection.  pppd is available for many  modems, qmicli is 
specific to Qualcomm, and mmicli to others.  Other modem manufacturers 
may have other tools.
- use '-v' options to these tools.
- look at the /var/log/messages
- kill all ConnectionManager or NetworkManager.
- there is a certain ability needed to be able to capture before an 
interface is put up, because normally capturing happens while the 
interface is already up.  But when it is already up you already obtained 
the address.
- there is a need to capture more than just IP datagrams, but link-layer 
datagrams.



> They looks no EUI-64 address, without 
> FFFE in the middle of low 64 bits.

Yes, looks so.

Forming 64bit Interface IDs that dont have FF:FE in the middle can 
happens modernly by recent androids (recent linuces, in fact).  Either 
the linux formed such a non-FFFE IID, or that IID was formed by a server 
and delivered to android by the layer2 protocol

> And it can not be done by DHCPv6 
> because I heard Android does not support DHCPv6, right?

Android is an Operating System.  It uses a modified linux kernel.  When 
people say android does not implement DHCPv6 it is because the 
manufacturer of that phone chose to put an Android that has no DHCPv6 
client.  It is however straightforward to put yourself (or your 
operator) a DHCPv6 client on an Android.  We did it numerous times with 
many (5?) DHCPv6 clients.  Android supports them all ok.

Also, this is based on the remark that the manufacturer of that phone 
puts the android and that manufacturer has a hard time to remove the 
SLAAC (a competitor to DHCPv6) from Android: SLAAC is built into the 
linux part of Android.  And Google _and_ Android _and_ phone 
manufacturer dont have enough capacity or will to _remove_ SLAAC from 
linux kernel, because it is not their design.

In that sense: yes, DHCPv6 is _not_ in Android (could easily be added), 
and SLAAC _is_ in Android (could hardly be removed).

> I'm not sure 
> how my LTE provider provisioning IPv6 address.

In the LTE provider's network there is much more private and proprietary 
mechanisms to provision the IPv6 addresses.  What the end user sees is 
only the tip of the iceberg: the RA.

Some of the mechanisms are described in some RFCs that relate to Proxy 
Mobile IP.  I am not saying that's what's used at your operator, but 
these texts approach the most to what's used.

> So The only possbile way 
> is SLAAC+private address？

What you shown above is not a private address.  They both start with 
24-something.  The 'private' addresses in IPv6 are called 'ULA's (for 
Unique Local Addresses) and they start with fd-something or fc-something.

And no, it is not the only possible way to be SLAAC.  I would even say 
that, judged by the excitement, this might be the first time these 
operators give IPv6 to end-users, and I would say it is rather a 
proprietary form of IPv6CP.  But I may be wrong in case these operators 
acquired very recent state-of-the-art hardware and learned from recent 
experience of operators who went with SLAAC.

Alex

> 
> Anyone who can help me out on this question? Or share your experience on 
> how the mobile ISP commonly provison their users. Thanks.

> 
> Best regards,
> Davey
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


From nobody Fri Sep  7 06:53:49 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB85E130E89 for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 06:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 ejQ5RvQpGPOR for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 06:53:34 -0700 (PDT)
Received: from atl4mhob22.registeredsite.com (atl4mhob22.registeredsite.com [209.17.115.116]) (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 B8F89130E64 for <v6ops@ietf.org>; Fri,  7 Sep 2018 06:53:34 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob22.registeredsite.com (8.14.4/8.14.4) with ESMTP id w87DrWds073141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 7 Sep 2018 09:53:32 -0400
Received: (qmail 14879 invoked by uid 0); 7 Sep 2018 13:53:32 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 7 Sep 2018 13:53:32 -0000
To: Mark Andrews <marka@isc.org>
Cc: v6ops@ietf.org, draft-ietf-doh-dns-over-https.all@ietf.org, evyncke@cisco.com
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org>
Date: Fri, 7 Sep 2018 09:53:27 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/VX--KpHAJlsGDMKpaq1PS3QAQGU>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 13:53:48 -0000

On 09/06/2018 07:42 PM, Mark Andrews wrote:
> Can we please have some technological leadership in the IETF and
> say that DNS64 is technically flawed for a number of reason and
> SHOULD NOT be used.

Technological leadership looks to you like telling operators they 
deployed their network wrong, and must change it.
To me, it looks like acknowledging advice from operators on how the 
Internet actually works, and identifying interoperability problems.

Technological leadership to me looks more like warning people about 
interoperability issues and how to avoid them. When that's as easy as 
following previous BCP advice (i.e., rfc6540: deploy IPv6), we are 
remaining entirely consistent.

If you want to deprecate DNS64, and therefore the other transition 
mechanisms that rely on it, that's a different draft. I would not 
support it at this time. If instead you want a draft that warns about 
interoperability problems when deploying DNS64, if it says something 
more than what is already in rfc6147 (DNS64) and this draft, I look 
forward to seeing it.

> It has always been a flawed technology that was deployed as a stop-gap.

That could be said for all transition technologies, and I eagerly await 
the day when they can be discarded.

>
> Stop trying to get the rest of the internet to change because some
> sites are continuing to deploy DNS64 which is what this draft does.
> That is the tail wagging the dog.
I don't think this is "continuing to deploy DNS64" but "continuing to 
deploy DNSSEC when it won't work with existing DNS64."
Most operators I'm talking to are looking at more recent and stateless 
transition technologies. That doesn't get the hundreds of millions of 
folks off of the networks they're on.

In the case of DOH, that is an effort trying to get the Internet to 
change despite known interoperability problems.

Lee


From nobody Fri Sep  7 07:12:52 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82BF1130E1F; Fri,  7 Sep 2018 07:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 0aw886kg0Kgb; Fri,  7 Sep 2018 07:12:48 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91EAC130E44; Fri,  7 Sep 2018 07:12:48 -0700 (PDT)
Received: from astfgl.hanazo.no (unknown [173.38.220.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 20464FECBAC1; Fri,  7 Sep 2018 14:12:18 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 00A3E5500EA; Fri,  7 Sep 2018 16:12:13 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org>
Date: Fri, 7 Sep 2018 16:12:13 +0200
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/DtAsYYqNVbch05mTEMh19Zfpwos>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 14:12:51 -0000

Lee,

So not accepting Mark=E2=80=99s advice is just a trade-off between =
customer support calls and updating implementations to do local address =
synthesizing?
I would certainly make a few phone calls to my ISP if they forced my to =
use their DNS recursive resolvers.

Best regards,
Ole

> On 7 Sep 2018, at 15:53, Lee Howard <lee@asgard.org> wrote:
>=20
>=20
>=20
> On 09/06/2018 07:42 PM, Mark Andrews wrote:
>> Can we please have some technological leadership in the IETF and
>> say that DNS64 is technically flawed for a number of reason and
>> SHOULD NOT be used.
>=20
> Technological leadership looks to you like telling operators they =
deployed their network wrong, and must change it.
> To me, it looks like acknowledging advice from operators on how the =
Internet actually works, and identifying interoperability problems.
>=20
> Technological leadership to me looks more like warning people about =
interoperability issues and how to avoid them. When that's as easy as =
following previous BCP advice (i.e., rfc6540: deploy IPv6), we are =
remaining entirely consistent.
>=20
> If you want to deprecate DNS64, and therefore the other transition =
mechanisms that rely on it, that's a different draft. I would not =
support it at this time. If instead you want a draft that warns about =
interoperability problems when deploying DNS64, if it says something =
more than what is already in rfc6147 (DNS64) and this draft, I look =
forward to seeing it.
>=20
>> It has always been a flawed technology that was deployed as a =
stop-gap.
>=20
> That could be said for all transition technologies, and I eagerly =
await the day when they can be discarded.
>=20
>>=20
>> Stop trying to get the rest of the internet to change because some
>> sites are continuing to deploy DNS64 which is what this draft does.
>> That is the tail wagging the dog.
> I don't think this is "continuing to deploy DNS64" but "continuing to =
deploy DNSSEC when it won't work with existing DNS64."
> Most operators I'm talking to are looking at more recent and stateless =
transition technologies. That doesn't get the hundreds of millions of =
folks off of the networks they're on.
>=20
> In the case of DOH, that is an effort trying to get the Internet to =
change despite known interoperability problems.
>=20
> Lee
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Fri Sep  7 07:15:43 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8DFC128766; Fri,  7 Sep 2018 07:15:40 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 mUEJiO1CYc6F; Fri,  7 Sep 2018 07:15:39 -0700 (PDT)
Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 C5FDF130E10; Fri,  7 Sep 2018 07:15:38 -0700 (PDT)
Received: by mail-yw1-xc31.google.com with SMTP id n21-v6so5438934ywh.5; Fri, 07 Sep 2018 07:15:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=n7Wqlk8zmotwPMGFQeCIJht/klurcn63hrRYpbnG0y8=; b=j/J6rnxCqFfetklo99bDsDbatWXwFE0bHF6BkOsAfvLM6yr5zDuKTDFM+pB6PlQDkn 7VwtZfdKptO6edcNjo+e7du6YNOmpWlA03D19nCuMfURwbMiM32TcIXcCUBG0ojuB42y Cr0p/b5WJBjDzBRPH53nn8+QKwFmWFvZOUaXvp+npHyzlpPVBJDvrz+/B3VTYdf/+vuQ iA6xe6+W0yPgdWXU4NTiRGWeBjSBILkOrV3r4TalsfxYvUuVrY/WBBiAqL0epTVqcaZF oKmN34826+XcpBTrNqClmkK7Ayg3V1rnFPHjBJvyDLNEiG7am2M6z3Za2ndcbKW4hH7r i5lQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=n7Wqlk8zmotwPMGFQeCIJht/klurcn63hrRYpbnG0y8=; b=XTFDmViXZrn1zic4EPJqAHsMaYpxj/47pO/WwJBZUXcLIW5DdP/HyQ1XOay/2sGnen SfZ360HO55CpYrk9c1kx85L0wvqM3+n1rer69k0FPvmcv/8Nb8wYhJ9WPUHlDdxdWiqP 1H0Z3NTriucwGmaxZ7lg8jczzOqKYkl6wxGehSaMJkJTVdKBq9iDaMY00ZWuOrjO7Vkf 4uajO8DRa5Hzf+2he6zd0LfhAM89Oicjpfe+E6PdLEQJntUu+Dob2P9kT0J6qLAvtTMt pvclbDpKw5gwfN/j3S9XHRVdllbSo9DgNV6yfU5mHpO79u4mF+g9dkscv+NeBBbW9cTO e+VQ==
X-Gm-Message-State: APzg51DMUk+q3/S0vYP/5fA86loMfpFJJuFO/XGl/ycKusQ9nrJt8+3e XuLAqgSpLX1XUAJc3WBDdGblO6HwP0iYaO8atfEleg==
X-Google-Smtp-Source: ANB0VdY1GiuxD13GrhP2mwZyr3tSlg5x1LmmJSuf56DtDKYh2XPutQWK93J1/+4brD6Osj0Db+IjSt+SVII3s/Cfwk0=
X-Received: by 2002:a81:59c3:: with SMTP id n186-v6mr4291389ywb.54.1536329737838;  Fri, 07 Sep 2018 07:15:37 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org>
In-Reply-To: <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org>
From: Ca By <cb.list6@gmail.com>
Date: Fri, 7 Sep 2018 07:15:26 -0700
Message-ID: <CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com>
To: Lee Howard <lee@asgard.org>
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000482927057548a478"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9WJ61AvcGnh7J2ta-actZ7u25d8>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 14:15:42 -0000

--000000000000482927057548a478
Content-Type: text/plain; charset="UTF-8"

On Fri, Sep 7, 2018 at 6:54 AM Lee Howard <lee@asgard.org> wrote:

>
>
> On 09/06/2018 07:42 PM, Mark Andrews wrote:
> > Can we please have some technological leadership in the IETF and
> > say that DNS64 is technically flawed for a number of reason and
> > SHOULD NOT be used.
>
> Technological leadership looks to you like telling operators they
> deployed their network wrong, and must change it.
> To me, it looks like acknowledging advice from operators on how the
> Internet actually works, and identifying interoperability problems.
>
> Technological leadership to me looks more like warning people about
> interoperability issues and how to avoid them. When that's as easy as
> following previous BCP advice (i.e., rfc6540: deploy IPv6), we are
> remaining entirely consistent.
>
> If you want to deprecate DNS64, and therefore the other transition
> mechanisms that rely on it, that's a different draft. I would not
> support it at this time. If instead you want a draft that warns about
> interoperability problems when deploying DNS64, if it says something
> more than what is already in rfc6147 (DNS64) and this draft, I look
> forward to seeing it.
>
> > It has always been a flawed technology that was deployed as a stop-gap.
>
> That could be said for all transition technologies, and I eagerly await
> the day when they can be discarded.
>
> >
> > Stop trying to get the rest of the internet to change because some
> > sites are continuing to deploy DNS64 which is what this draft does.
> > That is the tail wagging the dog.
> I don't think this is "continuing to deploy DNS64" but "continuing to
> deploy DNSSEC when it won't work with existing DNS64."
> Most operators I'm talking to are looking at more recent and stateless
> transition technologies. That doesn't get the hundreds of millions of
> folks off of the networks they're on.
>


There is no large scale (1M + subs)  stateless deployment, today, that i am
aware of.  Please correct me. It is 2018.

Meanwhile, ds-lite may be around 10M subs?

And things couched in stateful nat64 are 100s of Millions and growing.
Stateful nat44 10s of billions ?

There is nobody working today, or ever planned to be working, a 3gpp
stateless transition solution. That said, nobody in 3gpp worked a stateful
transition. V6ops simply threaded the needle given that 3gpp does not care
about ipv6.

So, now may be a good time to rebase your expectations and understanding of
the current state and trajectory of the ipv4 internet.

That said, please deploy ipv6, these problems are solved when ipv6 is e2e.



>
> In the case of DOH, that is an effort trying to get the Internet to
> change despite known interoperability problems.
>
> Lee
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--000000000000482927057548a478
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri,=
 Sep 7, 2018 at 6:54 AM Lee Howard &lt;<a href=3D"mailto:lee@asgard.org">le=
e@asgard.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 09/06/2018 07:42 PM, Mark Andrews wrote:<br>
&gt; Can we please have some technological leadership in the IETF and<br>
&gt; say that DNS64 is technically flawed for a number of reason and<br>
&gt; SHOULD NOT be used.<br>
<br>
Technological leadership looks to you like telling operators they <br>
deployed their network wrong, and must change it.<br>
To me, it looks like acknowledging advice from operators on how the <br>
Internet actually works, and identifying interoperability problems.<br>
<br>
Technological leadership to me looks more like warning people about <br>
interoperability issues and how to avoid them. When that&#39;s as easy as <=
br>
following previous BCP advice (i.e., rfc6540: deploy IPv6), we are <br>
remaining entirely consistent.<br>
<br>
If you want to deprecate DNS64, and therefore the other transition <br>
mechanisms that rely on it, that&#39;s a different draft. I would not <br>
support it at this time. If instead you want a draft that warns about <br>
interoperability problems when deploying DNS64, if it says something <br>
more than what is already in rfc6147 (DNS64) and this draft, I look <br>
forward to seeing it.<br>
<br>
&gt; It has always been a flawed technology that was deployed as a stop-gap=
.<br>
<br>
That could be said for all transition technologies, and I eagerly await <br=
>
the day when they can be discarded.<br>
<br>
&gt;<br>
&gt; Stop trying to get the rest of the internet to change because some<br>
&gt; sites are continuing to deploy DNS64 which is what this draft does.<br=
>
&gt; That is the tail wagging the dog.<br>
I don&#39;t think this is &quot;continuing to deploy DNS64&quot; but &quot;=
continuing to <br>
deploy DNSSEC when it won&#39;t work with existing DNS64.&quot;<br>
Most operators I&#39;m talking to are looking at more recent and stateless =
<br>
transition technologies. That doesn&#39;t get the hundreds of millions of <=
br>
folks off of the networks they&#39;re on.<br>
</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">There is no large scale (1M + subs) =C2=A0stateless deployment,=
 today, that i am aware of.=C2=A0 Please correct me. It is 2018. =C2=A0</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">Meanwhile, ds-lite may be a=
round 10M subs?</div><div dir=3D"auto"><br></div><div dir=3D"auto">And thin=
gs couched in stateful nat64 are 100s of Millions and growing.=C2=A0 Statef=
ul nat44 10s of billions ?</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">There is nobody working today, or ever planned to be working, a 3gpp sta=
teless transition solution. That said, nobody in 3gpp worked a stateful tra=
nsition. V6ops simply threaded the needle given that 3gpp does not care abo=
ut ipv6.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">So, now m=
ay be a good time to rebase your expectations and understanding of the curr=
ent state and trajectory of the ipv4 internet.=C2=A0</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">That said, please deploy ipv6, these problems =
are solved when ipv6 is e2e.=C2=A0</div><div dir=3D"auto"><br></div><div di=
r=3D"auto">=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
In the case of DOH, that is an effort trying to get the Internet to <br>
change despite known interoperability problems.<br>
<br>
Lee<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div>

--000000000000482927057548a478--


From nobody Fri Sep  7 08:02:57 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC8E2130DD4 for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 08:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 coy7NyvTuU42 for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 08:02:46 -0700 (PDT)
Received: from atl4mhob11.registeredsite.com (atl4mhob11.registeredsite.com [209.17.115.49]) (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 91169130E11 for <v6ops@ietf.org>; Fri,  7 Sep 2018 08:02:46 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob11.registeredsite.com (8.14.4/8.14.4) with ESMTP id w87F2gNk028141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 7 Sep 2018 11:02:42 -0400
Received: (qmail 16411 invoked by uid 0); 7 Sep 2018 15:02:42 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 7 Sep 2018 15:02:42 -0000
To: Ca By <cb.list6@gmail.com>
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <ef915839-b351-b0f6-9b6a-34a9ad0708be@asgard.org>
Date: Fri, 7 Sep 2018 11:02:41 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------90B8B0F9A16B3F0B814853FB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wgMu0hAGNVcuoPOQrjlFVGUly8o>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 15:02:49 -0000

This is a multi-part message in MIME format.
--------------90B8B0F9A16B3F0B814853FB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit



On 09/07/2018 10:15 AM, Ca By wrote:
>
>
> On Fri, Sep 7, 2018 at 6:54 AM Lee Howard <lee@asgard.org 
> <mailto:lee@asgard.org>> wrote:
>
>
>
>     On 09/06/2018 07:42 PM, Mark Andrews wrote:
>

>
>     > It has always been a flawed technology that was deployed as a
>     stop-gap.
>
>     That could be said for all transition technologies, and I eagerly
>     await
>     the day when they can be discarded.
>
>     >
>     > Stop trying to get the rest of the internet to change because some
>     > sites are continuing to deploy DNS64 which is what this draft does.
>     > That is the tail wagging the dog.
>     I don't think this is "continuing to deploy DNS64" but "continuing to
>     deploy DNSSEC when it won't work with existing DNS64."
>     Most operators I'm talking to are looking at more recent and
>     stateless
>     transition technologies. That doesn't get the hundreds of millions of
>     folks off of the networks they're on.
>
>
>
> There is no large scale (1M + subs)  stateless deployment, today, that 
> i am aware of.  Please correct me. It is 2018.

https://docs.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/edit#gid=0

Reliance Jio, a mobile carrier, has millions, maybe tens of millions 
behind MAP-T.
JPNE has a significant MAP-E, but I can't find a size estimate.
Charter is still in EFT with MAP-T, so not yet 1M.
CERNET told us about their MAP-T/MAP-E switch. 
https://tools.ietf.org/agenda/92/slides/slides-92-v6ops-3.pdf

So, while I agree that stateful transition technologies dwarf stateless, 
my anecdotal impression is that networks who are currently deciding 
between technologies are tending toward the stateless ones. That is not 
an indictment of decisions made by other operators.
>
> Meanwhile, ds-lite may be around 10M subs?
I'd guess a couple tens, not that it matters.

>
> And things couched in stateful nat64 are 100s of Millions and 
> growing.  Stateful nat44 10s of billions ?
>
> There is nobody working today, or ever planned to be working, a 3gpp 
> stateless transition solution. That said, nobody in 3gpp worked a 
> stateful transition. V6ops simply threaded the needle given that 3gpp 
> does not care about ipv6.
>
> So, now may be a good time to rebase your expectations and 
> understanding of the current state and trajectory of the ipv4 internet.
>
> That said, please deploy ipv6, these problems are solved when ipv6 is 
> e2e.

Are we not agreeing?

Lee

--------------90B8B0F9A16B3F0B814853FB
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 09/07/2018 10:15 AM, Ca By wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div><br>
      </div>
      <div><br>
        <div class="gmail_quote">
          <div dir="ltr">On Fri, Sep 7, 2018 at 6:54 AM Lee Howard &lt;<a
              href="mailto:lee@asgard.org" moz-do-not-send="true">lee@asgard.org</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
            <br>
            On 09/06/2018 07:42 PM, Mark Andrews wrote:<br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    <blockquote type="cite"
cite="mid:CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com">
      <div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            &gt; It has always been a flawed technology that was
            deployed as a stop-gap.<br>
            <br>
            That could be said for all transition technologies, and I
            eagerly await <br>
            the day when they can be discarded.<br>
            <br>
            &gt;<br>
            &gt; Stop trying to get the rest of the internet to change
            because some<br>
            &gt; sites are continuing to deploy DNS64 which is what this
            draft does.<br>
            &gt; That is the tail wagging the dog.<br>
            I don't think this is "continuing to deploy DNS64" but
            "continuing to <br>
            deploy DNSSEC when it won't work with existing DNS64."<br>
            Most operators I'm talking to are looking at more recent and
            stateless <br>
            transition technologies. That doesn't get the hundreds of
            millions of <br>
            folks off of the networks they're on.<br>
          </blockquote>
          <div dir="auto"><br>
          </div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">There is no large scale (1M + subs)  stateless
            deployment, today, that i am aware of.  Please correct me.
            It is 2018.  <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
<a class="moz-txt-link-freetext" href="https://docs.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/edit#gid=0">https://docs.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/edit#gid=0</a><br>
    <br>
    Reliance Jio, a mobile carrier, has millions, maybe tens of millions
    behind MAP-T.<br>
    JPNE has a significant MAP-E, but I can't find a size estimate.<br>
    Charter is still in EFT with MAP-T, so not yet 1M.<br>
    CERNET told us about their MAP-T/MAP-E switch.
    <a class="moz-txt-link-freetext" href="https://tools.ietf.org/agenda/92/slides/slides-92-v6ops-3.pdf">https://tools.ietf.org/agenda/92/slides/slides-92-v6ops-3.pdf</a> <br>
    <br>
    So, while I agree that stateful transition technologies dwarf
    stateless, my anecdotal impression is that networks who are
    currently deciding between technologies are tending toward the
    stateless ones. That is not an indictment of decisions made by other
    operators.<br>
    <blockquote type="cite"
cite="mid:CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com">
      <div>
        <div class="gmail_quote">
          <div dir="auto"><br>
          </div>
          <div dir="auto">Meanwhile, ds-lite may be around 10M subs?</div>
        </div>
      </div>
    </blockquote>
    I'd guess a couple tens, not that it matters.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com">
      <div>
        <div class="gmail_quote">
          <div dir="auto"><br>
          </div>
          <div dir="auto">And things couched in stateful nat64 are 100s
            of Millions and growing.  Stateful nat44 10s of billions ?</div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">There is nobody working today, or ever planned
            to be working, a 3gpp stateless transition solution. That
            said, nobody in 3gpp worked a stateful transition. V6ops
            simply threaded the needle given that 3gpp does not care
            about ipv6. </div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">So, now may be a good time to rebase your
            expectations and understanding of the current state and
            trajectory of the ipv4 internet. </div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">That said, please deploy ipv6, these problems
            are solved when ipv6 is e2e. <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Are we not agreeing?<br>
    <br>
    Lee<br>
  </body>
</html>

--------------90B8B0F9A16B3F0B814853FB--


From nobody Fri Sep  7 08:14:16 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C02C8130DD4 for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 08:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 KDf3AFlwN3No for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 08:14:13 -0700 (PDT)
Received: from atl4mhob13.registeredsite.com (atl4mhob13.registeredsite.com [209.17.115.51]) (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 01F4B130D7A for <v6ops@ietf.org>; Fri,  7 Sep 2018 08:14:11 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail02pod6.registeredsite.com [10.30.71.210]) by atl4mhob13.registeredsite.com (8.14.4/8.14.4) with ESMTP id w87FE97S010441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 7 Sep 2018 11:14:10 -0400
Received: (qmail 15504 invoked by uid 0); 7 Sep 2018 15:14:09 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 7 Sep 2018 15:14:09 -0000
To: Ole Troan <otroan@employees.org>
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org>
Date: Fri, 7 Sep 2018 11:14:08 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/qk0Wz8Xn_OLwNabH9L5WdyDSlp8>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 15:14:15 -0000

On 09/07/2018 10:12 AM, Ole Troan wrote:
> Lee,
>
> So not accepting Mark’s advice is just a trade-off between customer support calls and updating implementations to do local address synthesizing?
> I would certainly make a few phone calls to my ISP if they forced my to use their DNS recursive resolvers.

Network operators don't generally have the option of updating 
implementations to do local address synthesizing. That's an OS decision.

Fred pointed to the Pref64 draft, which provides part of Mark's 
suggestion. I don't know whether OS vendors will listen to it, and I 
don't know how many devices would get left behind even if they do 
provide updates.

Good luck with those calls. If my choice as an operator is to lose money 
providing IPv4 or lose money on support calls, I'm going with the method 
that loses the least money. If I can charge for IPv4 addresses (is that 
even possible in mobile networks?) maybe I'll offer that option instead.

We all agree that server operators should deploy IPv6, right? There's no 
doubt that it's Best Current Practice.
One of the reasons it's a Best Current Practice is that if they are 
using DNSSEC, there are interoperability problems with IPv4, 
specifically in some transition mechanisms.

Trying to develop alternative mechanisms and insisting network operators 
deploy those instead is wishful thinking and ignores the deployed 
Internet. The network operators have deployed IPv6: the content 
providers must, too, or risk problems. We can provide operational 
guidance about those potential problems.

Lee


From nobody Fri Sep  7 09:32:14 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2051712F1A2; Fri,  7 Sep 2018 09:32:13 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 8jjg_fBzzizs; Fri,  7 Sep 2018 09:32:11 -0700 (PDT)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 24B97126F72; Fri,  7 Sep 2018 09:32:11 -0700 (PDT)
Received: by mail-yb1-xb30.google.com with SMTP id m123-v6so5676700ybm.0; Fri, 07 Sep 2018 09:32:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=P3tSO14BacfHiJblzAVBOdEhtvkiQNBXBhtoLfyizN8=; b=kymxiR/+hcdljH8kHOFqfjE29WiiQ/ehUtlNAnwlI2n45Lak7XfO+8rcbqwgxM3YOH egoax2ZwX9SqtaPzIgpt1d5cGSFd9k7rCv1t0HxNcL58m8MoCrOsxnzKirSm5M+XNGnE TJ+mcdrPm6GfCyPxHurtAhQqAA/KVLIb/bzsL5w0eTZfFsGqQwG3Mh3al2MqsXsb7aY+ qkczIAgBjQFK4b+YOXbRVgfd4xWv589spAFw1z1KffRpHYbLuLP8PqGspKrziQ562GRG OPaamSzsyY0Mgjbt4JGb59gQX84v+cS010IEu1pAeY5PU5w/IYd069b6LIQ1VNDWRkpn 4K0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=P3tSO14BacfHiJblzAVBOdEhtvkiQNBXBhtoLfyizN8=; b=nZlEwbrXxOAzGp8bn9olhYnvruFD+aF+xdtoM/l6BzxZo+YSVUHAM+99uh1BaAN0OZ BDjUlOpXYNT52XJa54J517XdTqQIiUdb/0DWJ+2c728HEQ0Cjc+H0A2DdIsaZIuycUuZ Awrja/1VyjVwVgxc0PcDZs1eaWPC8qx7d/t25TZsKJugIqrR8gGp3oF7WvjlZ+ouR4DS ecOb+IaVDe2kaeCq0GI/NUA4ZazPFQdKPytJ8ZZjl7JX5wLWHi8OWDlvQ22fcbGJ7eaS JjRBmNLa71Z09QorXFOkrUXZBMgW9OdGTQhjVLKbot4OnO50FW2Tgzu0MI2Hh3xoO1KJ LCXA==
X-Gm-Message-State: APzg51BrIePfqvgg73KdZx1FM0zecIqEufNX2UuLaHUSpVKh+e9K2RDV +Ms6KNH0nGbpWEjwjAKn9PI0qKEJ9WJx4l0lA+g=
X-Google-Smtp-Source: ANB0VdaBM4Jbmft7kMcanVA6+tS63sUCj4hnuGjiH9Nu8QO7xTSlhm9bz+PGZ4lqrYvPoufnzFq9sj7Iz7nJRO009M4=
X-Received: by 2002:a25:6dd4:: with SMTP id i203-v6mr4447695ybc.438.1536337930025;  Fri, 07 Sep 2018 09:32:10 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <CAD6AjGQ=SguFAR=M7rFb_KgCEVJf9L0mie8AzdMC-HgixHbdjw@mail.gmail.com> <ef915839-b351-b0f6-9b6a-34a9ad0708be@asgard.org>
In-Reply-To: <ef915839-b351-b0f6-9b6a-34a9ad0708be@asgard.org>
From: Ca By <cb.list6@gmail.com>
Date: Fri, 7 Sep 2018 09:31:58 -0700
Message-ID: <CAD6AjGTXzS8krtO1YRMSv9Sk-E+WVOnQPvOV=30EUX-uxauboQ@mail.gmail.com>
To: Lee Howard <lee@asgard.org>
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
Content-Type: multipart/alternative; boundary="00000000000092ff0005754a8ce6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ELX3IIOK136mRr6rWLS3plBRCqU>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 16:32:14 -0000

--00000000000092ff0005754a8ce6
Content-Type: text/plain; charset="UTF-8"

https://docs.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/edit#gid=0
>
> Reliance Jio, a mobile carrier, has millions, maybe tens of millions
> behind MAP-T.
>

>From the APNIC blog, Jio is a DOCSIS and Mobile provider. MAP-T is used in
the wireline side along with dual-stack.  But happy to learn specifics from
folks with first hand knowledge.

I would not say millions behind MAP-T without a citation. The blog you
linked to does not pin any particulars or scale or share for various
approaches.


> JPNE has a significant MAP-E, but I can't find a size estimate.
> Charter is still in EFT with MAP-T, so not yet 1M.
> CERNET told us about their MAP-T/MAP-E switch.
> https://tools.ietf.org/agenda/92/slides/slides-92-v6ops-3.pdf
>
> So, while I agree that stateful transition technologies dwarf stateless,
> my anecdotal impression is that networks who are currently deciding between
> technologies are tending toward the stateless ones. That is not an
> indictment of decisions made by other operators.
>
>
> Meanwhile, ds-lite may be around 10M subs?
>
> I'd guess a couple tens, not that it matters.
>
>
> And things couched in stateful nat64 are 100s of Millions and growing.
> Stateful nat44 10s of billions ?
>
> There is nobody working today, or ever planned to be working, a 3gpp
> stateless transition solution. That said, nobody in 3gpp worked a stateful
> transition. V6ops simply threaded the needle given that 3gpp does not care
> about ipv6.
>
> So, now may be a good time to rebase your expectations and understanding
> of the current state and trajectory of the ipv4 internet.
>
> That said, please deploy ipv6, these problems are solved when ipv6 is e2e.
>
>
> Are we not agreeing?
>
>
> Lee
>

--00000000000092ff0005754a8ce6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><div dir=3D"auto"><br></div><br><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF=
">
<a class=3D"m_4263527019810230241moz-txt-link-freetext" href=3D"https://doc=
s.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/ed=
it#gid=3D0" target=3D"_blank">https://docs.google.com/spreadsheets/d/1ksOoW=
OaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/edit#gid=3D0</a><br>
    <br>
    Reliance Jio, a mobile carrier, has millions, maybe tens of millions
    behind MAP-T.</div></blockquote><div dir=3D"auto"><br></div><div dir=3D=
"auto">From the APNIC blog, Jio is a DOCSIS and Mobile provider. MAP-T is u=
sed in the wireline side along with dual-stack.=C2=A0 But happy to learn sp=
ecifics from folks with first hand knowledge.=C2=A0</div><div dir=3D"auto">=
<br></div><div dir=3D"auto">I would not say millions behind MAP-T without a=
 citation. The blog you linked to does not pin any particulars or scale or =
share for various approaches.=C2=A0</div><div dir=3D"auto"><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><br>
    JPNE has a significant MAP-E, but I can&#39;t find a size estimate.<br>
    Charter is still in EFT with MAP-T, so not yet 1M.<br>
    CERNET told us about their MAP-T/MAP-E switch.
    <a class=3D"m_4263527019810230241moz-txt-link-freetext" href=3D"https:/=
/tools.ietf.org/agenda/92/slides/slides-92-v6ops-3.pdf" target=3D"_blank">h=
ttps://tools.ietf.org/agenda/92/slides/slides-92-v6ops-3.pdf</a> <br>
    <br>
    So, while I agree that stateful transition technologies dwarf
    stateless, my anecdotal impression is that networks who are
    currently deciding between technologies are tending toward the
    stateless ones. That is not an indictment of decisions made by other
    operators.<br>
    <blockquote type=3D"cite">
      <div>
        <div class=3D"gmail_quote">
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">Meanwhile, ds-lite may be around 10M subs?</div=
>
        </div>
      </div>
    </blockquote>
    I&#39;d guess a couple tens, not that it matters.<br>
    <br>
    <blockquote type=3D"cite">
      <div>
        <div class=3D"gmail_quote">
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">And things couched in stateful nat64 are 100s
            of Millions and growing.=C2=A0 Stateful nat44 10s of billions ?=
</div>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">There is nobody working today, or ever planned
            to be working, a 3gpp stateless transition solution. That
            said, nobody in 3gpp worked a stateful transition. V6ops
            simply threaded the needle given that 3gpp does not care
            about ipv6.=C2=A0</div>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">So, now may be a good time to rebase your
            expectations and understanding of the current state and
            trajectory of the ipv4 internet.=C2=A0</div>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">That said, please deploy ipv6, these problems
            are solved when ipv6 is e2e. <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Are we not agreeing?</div><div text=3D"#000000" bgcolor=3D"#FFFFFF"><br=
>
    <br>
    Lee<br>
  </div>

</blockquote></div></div>

--00000000000092ff0005754a8ce6--


From nobody Fri Sep  7 09:48:34 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1BA130E62; Fri,  7 Sep 2018 09:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 cMhGOKr7dV2j; Fri,  7 Sep 2018 09:48:20 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66140130E53; Fri,  7 Sep 2018 09:48:20 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 86394FECBBFB; Fri,  7 Sep 2018 16:48:19 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org>
Date: Fri, 7 Sep 2018 18:48:15 +0200
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org>
To: Lee Howard <lee@asgard.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9U96-cK7WWO2mDheoK2fvb__s1A>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 16:48:33 -0000

> On 7 Sep 2018, at 17:14, Lee Howard <lee@asgard.org> wrote:
>=20
> We all agree that server operators should deploy IPv6, right? There's no d=
oubt that it's Best Current Practice.

If you choose a mechanism that depends on a DNS64 in the network,  then depl=
oying IPv6 doesn=E2=80=99t help. The enduser is still stuck with the ISPs re=
cursive resolver.=20

Ole=


From nobody Fri Sep  7 10:15:12 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9BBB130DE4 for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 10:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 twJo5EVtv3xH for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 10:15:09 -0700 (PDT)
Received: from atl4mhob16.registeredsite.com (atl4mhob16.registeredsite.com [209.17.115.109]) (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 6C1761277BB for <v6ops@ietf.org>; Fri,  7 Sep 2018 10:15:09 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob16.registeredsite.com (8.14.4/8.14.4) with ESMTP id w87HF63U000788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 7 Sep 2018 13:15:06 -0400
Received: (qmail 29896 invoked by uid 0); 7 Sep 2018 17:15:06 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 7 Sep 2018 17:15:06 -0000
To: Ole Troan <otroan@employees.org>
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org>
Date: Fri, 7 Sep 2018 13:15:05 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/B_AdxvRDGx_15Xdj2raImEgpmFs>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 17:15:11 -0000

On 09/07/2018 12:48 PM, Ole Troan wrote:
>
>> On 7 Sep 2018, at 17:14, Lee Howard <lee@asgard.org> wrote:
>>
>> We all agree that server operators should deploy IPv6, right? There's no doubt that it's Best Current Practice.
> If you choose a mechanism that depends on a DNS64 in the network,  then deploying IPv6 doesn’t help. The enduser is still stuck with the ISPs recursive resolver.

*chose*

Five or more years ago. The ship has sailed. The decision has been made, 
by multiple network operators, for hundreds of millions of users.

It is too late to un-make that decision.

The decision now is whether to advise other operators on potential 
interoperability issues. "If you deploy DNSSEC, we advise you to deploy 
IPv6 also, to avoid interoperability issues." We don't have an 
alternative that include time travel.

If, as you and Mark argue (I think), we decide not to issue such an 
advisory because we think we can improve DNS64/NAT64/464xlat, then we 
are accepting those interoperability issues until all vendors of network 
devices on those networks have implemented the new option, the operators 
have deployed it, and all vendors of OSes have implemented the new 
option, and have deployed it  (without leaving any devices behind).

IPv4-only DNSSEC deployments will suffer until all of that happens. I 
haven't seen numbers on how bad that is, i.e., how many devices in those 
IPv6+translation networks do their own validation.

DOH deployments will suffer until that happens. Per the DOH draft, "the 
choice [of DNS server] could affect whether IPv6/IPv4 translation will 
work at all." I think that means an IPv4-only server whose A record is 
provided over DOH will be unreachable by the hundreds of millions of 
devices relying on DNS64. That seems like a pretty important 
consideration for someone considering deploying DOH. If deploying IPv6 
means they have no problem, that's advice they might appreciate.


I'm sorry if you don't like using your ISP's resolver. For hundreds of 
millions, they choice is apparently between using their resolver or not 
being able to reach the IPv4 Internet. The way to minimize their pain is 
to reduce the IPv4-only Internet.

Lee



>
> Ole


From nobody Fri Sep  7 11:25:26 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC96130DCE; Fri,  7 Sep 2018 11:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ofnXHKvZSiSG; Fri,  7 Sep 2018 11:25:22 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D923C12008A; Fri,  7 Sep 2018 11:25:22 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id F306DFECBAC1; Fri,  7 Sep 2018 18:25:21 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 1983F553689; Fri,  7 Sep 2018 20:25:19 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org>
Date: Fri, 7 Sep 2018 20:25:18 +0200
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/FgzVEKJlbgLqmp1mZQEceqbNptA>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 18:25:25 -0000

Lee,

>>> We all agree that server operators should deploy IPv6, right? =
There's no doubt that it's Best Current Practice.
>> If you choose a mechanism that depends on a DNS64 in the network,  =
then deploying IPv6 doesn=E2=80=99t help. The enduser is still stuck =
with the ISPs recursive resolver.
>=20
> *chose*
>=20
> Five or more years ago. The ship has sailed. The decision has been =
made, by multiple network operators, for hundreds of millions of users.

Just to be clear:
 MAP-E, MAP-T, LW46, 464XLAT, DS-lite all offer dual stack service to =
the end-user and does not in any way depend on DNS64.

NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.

Are you saying that there are hundreds of millions of users on IPv6 only =
networks with NAT64/DNS64 their only exit to the IPv4 Internet?
Where are these users? Cause I wasn=E2=80=99t aware of any general =
deployments of that to end-users.

Ole




>=20
> It is too late to un-make that decision.
>=20
> The decision now is whether to advise other operators on potential =
interoperability issues. "If you deploy DNSSEC, we advise you to deploy =
IPv6 also, to avoid interoperability issues." We don't have an =
alternative that include time travel.
>=20
> If, as you and Mark argue (I think), we decide not to issue such an =
advisory because we think we can improve DNS64/NAT64/464xlat, then we =
are accepting those interoperability issues until all vendors of network =
devices on those networks have implemented the new option, the operators =
have deployed it, and all vendors of OSes have implemented the new =
option, and have deployed it  (without leaving any devices behind).
>=20
> IPv4-only DNSSEC deployments will suffer until all of that happens. I =
haven't seen numbers on how bad that is, i.e., how many devices in those =
IPv6+translation networks do their own validation.
>=20
> DOH deployments will suffer until that happens. Per the DOH draft, =
"the choice [of DNS server] could affect whether IPv6/IPv4 translation =
will work at all." I think that means an IPv4-only server whose A record =
is provided over DOH will be unreachable by the hundreds of millions of =
devices relying on DNS64. That seems like a pretty important =
consideration for someone considering deploying DOH. If deploying IPv6 =
means they have no problem, that's advice they might appreciate.
>=20
>=20
> I'm sorry if you don't like using your ISP's resolver. For hundreds of =
millions, they choice is apparently between using their resolver or not =
being able to reach the IPv4 Internet. The way to minimize their pain is =
to reduce the IPv4-only Internet.
>=20
> Lee
>=20
>=20
>=20
>>=20
>> Ole
>=20


From nobody Fri Sep  7 11:30:21 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E330F130DE4 for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 11:30:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable 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 xvq-ZzIG8EhB for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 11:30:17 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74409130E57 for <v6ops@ietf.org>; Fri,  7 Sep 2018 11:30:15 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 7F10C438CC for <v6ops@ietf.org>; Fri,  7 Sep 2018 20:30:13 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 70322418E5; Fri,  7 Sep 2018 20:30:13 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 6BFBA921A1; Fri,  7 Sep 2018 20:30:13 +0200 (CEST)
Date: Fri, 7 Sep 2018 20:30:13 +0200
From: Gert Doering <gert@space.net>
To: Ole Troan <otroan@employees.org>
Cc: Lee Howard <lee@asgard.org>, draft-ietf-doh-dns-over-https.all@ietf.org, v6ops@ietf.org
Message-ID: <20180907183013.GA11393@Space.Net>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LkU5IcYqbdqvvZgR52Z-qRfRzD4>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 18:30:19 -0000

Hi,

On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
> 
> Are you saying that there are hundreds of millions of users on IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 Internet?
> Where are these users? Cause I wasn???t aware of any general deployments of that to end-users.

T-Mobile USA...?

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Fri Sep  7 11:57:40 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4ABB12008A for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 11:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 FeeVnb1JDyq5 for <v6ops@ietfa.amsl.com>; Fri,  7 Sep 2018 11:57:37 -0700 (PDT)
Received: from atl4mhob08.registeredsite.com (atl4mhob08.registeredsite.com [209.17.115.46]) (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 26C751252B7 for <v6ops@ietf.org>; Fri,  7 Sep 2018 11:57:35 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail01pod6.registeredsite.com [10.30.71.209]) by atl4mhob08.registeredsite.com (8.14.4/8.14.4) with ESMTP id w87IvXIX020474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 7 Sep 2018 14:57:33 -0400
Received: (qmail 23893 invoked by uid 0); 7 Sep 2018 18:57:33 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 7 Sep 2018 18:57:33 -0000
To: Ole Troan <otroan@employees.org>
Cc: Mark Andrews <marka@isc.org>, draft-ietf-doh-dns-over-https.all@ietf.org,  v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <ee5b07b6-3043-9cd0-9439-b143ba233fbc@asgard.org>
Date: Fri, 7 Sep 2018 14:57:32 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/fU3bqNAsOwuw8Qc3tZVo1Yqi7hU>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 18:57:39 -0000

On 09/07/2018 02:25 PM, Ole Troan wrote:
> Lee,
>
>>>> We all agree that server operators should deploy IPv6, right? There's no doubt that it's Best Current Practice.
>>> If you choose a mechanism that depends on a DNS64 in the network,  then deploying IPv6 doesn’t help. The enduser is still stuck with the ISPs recursive resolver.
>> *chose*
>>
>> Five or more years ago. The ship has sailed. The decision has been made, by multiple network operators, for hundreds of millions of users.
> Just to be clear:
>   MAP-E, MAP-T, LW46, 464XLAT, DS-lite all offer dual stack service to the end-user and does not in any way depend on DNS64.
>
> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>
> Are you saying that there are hundreds of millions of users on IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 Internet?
> Where are these users? Cause I wasn’t aware of any general deployments of that to end-users.

Am I saying it? I'm quoting the draft: "Currently, hundreds of millions 
of host rely on DNS64 for access to the internet. "

Since the draft author said, "I would not say millions behind MAP-T 
without a citation," 
[https://mailarchive.ietf.org/arch/msg/v6ops/ELX3IIOK136mRr6rWLS3plBRCqU], 
perhaps a citation for the "hundreds of millions" is needed in the 
draft. What do you think?

If, indeed, there are hundreds of millions of Internet users dependent 
on DNS64, would you agree that advice along the lines of this draft 
("expect problems if you dont' deploy IPv6") would be useful?

Lee


>
> Ole
>
>
>
>
>> It is too late to un-make that decision.
>>
>> The decision now is whether to advise other operators on potential interoperability issues. "If you deploy DNSSEC, we advise you to deploy IPv6 also, to avoid interoperability issues." We don't have an alternative that include time travel.
>>
>> If, as you and Mark argue (I think), we decide not to issue such an advisory because we think we can improve DNS64/NAT64/464xlat, then we are accepting those interoperability issues until all vendors of network devices on those networks have implemented the new option, the operators have deployed it, and all vendors of OSes have implemented the new option, and have deployed it  (without leaving any devices behind).
>>
>> IPv4-only DNSSEC deployments will suffer until all of that happens. I haven't seen numbers on how bad that is, i.e., how many devices in those IPv6+translation networks do their own validation.
>>
>> DOH deployments will suffer until that happens. Per the DOH draft, "the choice [of DNS server] could affect whether IPv6/IPv4 translation will work at all." I think that means an IPv4-only server whose A record is provided over DOH will be unreachable by the hundreds of millions of devices relying on DNS64. That seems like a pretty important consideration for someone considering deploying DOH. If deploying IPv6 means they have no problem, that's advice they might appreciate.
>>
>>
>> I'm sorry if you don't like using your ISP's resolver. For hundreds of millions, they choice is apparently between using their resolver or not being able to reach the IPv4 Internet. The way to minimize their pain is to reduce the IPv4-only Internet.
>>
>> Lee
>>
>>
>>
>>> Ole


From nobody Fri Sep  7 12:01:33 2018
Return-Path: <kristianmccolm@hotmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5106130E9E; Fri,  7 Sep 2018 12:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.126
X-Spam-Level: 
X-Spam-Status: No, score=-1.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 Jyaj4rLj0gXs; Fri,  7 Sep 2018 12:01:23 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-oln040092000105.outbound.protection.outlook.com [40.92.0.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17507130ED6; Fri,  7 Sep 2018 12:01:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2LEdGWJQw0GYLuxrTgEwS+wBjmUI4U/DzEqiMnm8BHk=; b=HpMhyEHbW/deVJHI+NmPRYg+7nGCgqOZIXozpWQs3zH+YLrJroWbD4jQirmVXIcoAIWM/Rm0/WsbKfPkXouapTPNCXyC9Q9mPrAz+ZwIdNhasFFDCjj6C5IOc7fnWAuwQQA5Apwc+f4qahRp1dFmp/TAF0L1KYFDnevrDCAkU+eGT2TQAnClVWhNXxtXsm/c+KJooeN/see/ckLf9kslLml4gm3WA+zBUgpc/Bqr/svH48roLoMb6jSL0BdiBhMc6BuVUlrjjT3fRxrizK96YrluNtZdY+rTs2NwdM0T3nS48NSK5EDfyZ+M72RccVMBp6oZg611sA7t6qh8fxec/g==
Received: from BN3NAM01FT010.eop-nam01.prod.protection.outlook.com (10.152.66.56) by BN3NAM01HT081.eop-nam01.prod.protection.outlook.com (10.152.67.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.1122.11; Fri, 7 Sep 2018 19:01:06 +0000
Received: from BN6PR04MB0932.namprd04.prod.outlook.com (10.152.66.57) by BN3NAM01FT010.mail.protection.outlook.com (10.152.66.245) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1122.11 via Frontend Transport; Fri, 7 Sep 2018 19:01:06 +0000
Received: from BN6PR04MB0932.namprd04.prod.outlook.com ([fe80::20db:f93:87ea:97a]) by BN6PR04MB0932.namprd04.prod.outlook.com ([fe80::20db:f93:87ea:97a%3]) with mapi id 15.20.1101.016; Fri, 7 Sep 2018 19:01:06 +0000
From: Kristian McColm <kristianmccolm@hotmail.com>
To: Gert Doering <gert@space.net>, Ole Troan <otroan@employees.org>
CC: "draft-ietf-doh-dns-over-https.all@ietf.org" <draft-ietf-doh-dns-over-https.all@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-byrne-v6ops-dnssecaaaa
Thread-Index: AdRFLRaRiSevdVfRR1yuHRNkcg68jgANWhoAACa+XIAAD3AWgAAdu4SAAACnyYAAAimUAAADSXiAAADv6YAAAnPJAAAAK/WAAAELIUA=
Date: Fri, 7 Sep 2018 19:01:06 +0000
Message-ID: <BN6PR04MB09329276E17BEB5D6D3420BDDD000@BN6PR04MB0932.namprd04.prod.outlook.com>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net>
In-Reply-To: <20180907183013.GA11393@Space.Net>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:03A1F3D911BA6819B509C6C1389153EB5903922B7E9F49B72C513EADCDD4EE49; UpperCasedChecksum:8C79E39D765846CCB5F4C2F2923B22C672A9E67C723D7735404DE9006B196423; SizeAsReceived:7873; Count:46
x-tmn: [ooYI1i3oUTmSmfbmZK0vacqf/SlYsczLZSqsN+901DaB5w0LTjoPgCng+SeweZf5]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3NAM01HT081; 6:z5eAL51XyIJ+OYzVFn7JHZRFkmg92BFj549hpcY0DuNwj/+y40noTiyqHUIN2qAjCqZzWRVpjtwAGockWgWMAbdz6YOcBIcc9qYXtvf7oacmceUbSEzaUlIVFKH9EaA53iJh+rDLCdg+zSjJlSm2ipo2eITUzvpAUt8XrcxTGUajKOUITnUpov3+mqy/twquGZzCvHT20L9+YpYoao95Pt8xLDQAAf+FaLMeryMifasppsiwVmReJAgaKTZQWdlXkTuS+thtp1iOAnWuLvL80O/83/2GtkfH0ZhZDcfOXF0apMybxn/1LtXoBpApwcOn1fbt/36UpDAmCwTXth/U6s4e9fNvT8XN+RgzjyK0ePbTJxaEXy6hLZoZb61FirE/OeNIEos1qiRFbaNiLXIG3+pXk/vmgT3nnWYvROJp7VwR6nalw1Ss0Tl8CrhvVQGY+fvh5+71ULgAs+ChP7/liA==; 5:TsduMvSw06Exc1m/ZP9hDkwmtU/aZdr6DOYVmfIki+OqtcCY7kQP1YPVdHU1n1YGeyFB8TUmsvym2GNzdwxOq9qrp4IriEI1nP79QgK6Q+yoP1QHzusdkvuWvXf9fBMlMBekt3yAcpgoXapvva6leWchyWSnwPbZrqXGHCSelKY=; 7:ZkZp+tTWhC3VdaoCJF5zYSb2Bhy1KkOEDjmK+r3NV5lWtVZYkqkDPSNy2/0oKf1OfbitU5GoQPtkld5JvN2nKOO580Z7aNufB/h3fs5lYC/j5zNYN2/gUXfN1wc0RKOU3P6LZpOI5VxotUah8qHq7Qbxvw749+VAJifpk1GeY9pVRu7QmoRTdGp/GDm/D5UZU1JM5xE2aFWyShygGttsIekAxyp0FzHTuXonUSxzRi/58xs3CqkFUF0NfSsrAsQR
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:BN3NAM01HT081; 
x-ms-traffictypediagnostic: BN3NAM01HT081:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:BN3NAM01HT081; BCL:0; PCL:0; RULEID:; SRVR:BN3NAM01HT081; 
x-forefront-prvs: 07880C4932
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(13464003)(189003)(199004)(53546011)(6506007)(33656002)(8676002)(2900100001)(76176011)(7696005)(5660300001)(4326008)(6346003)(56003)(97736004)(229853002)(20460500001)(102836004)(256004)(8936002)(5250100002)(105586002)(106356001)(6246003)(83332001)(93886005)(104016004)(54906003)(99286004)(110136005)(68736007)(73972006)(81156014)(46003)(86362001)(14454004)(966005)(82202002)(74316002)(305945005)(476003)(11346002)(486006)(6306002)(9686003)(55016002)(446003)(6436002)(87572001)(25786009)(15852004); DIR:OUT; SFP:1901; SCL:1; SRVR:BN3NAM01HT081; H:BN6PR04MB0932.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; 
received-spf: None (protection.outlook.com: hotmail.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kristianmccolm@hotmail.com; 
x-microsoft-antispam-message-info: 8MGXVvsNdrNwLGLyDEaWxf85WX8/oiRxyIaVzjGn+NKqeAEbDRJ8WA93XKnaWLD9YgBfD9wNGn11WM5r9jOjN/A+wEVr3wTZGfwwX1dcIr85MCnv2SYEz2O5gAGhPAezsFlMuGm1RvzyvuBsyNw8oNz1aO9f+rPR7HUkgSv7B7QLkp6JnVDht4FTBfwFC7ceJbNKNXNHevKKF+DNib4EuCKUUJscti3vHaEv5Auhtx4=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-Network-Message-Id: 9e8eaa21-06db-4dc2-ca0c-08d614f443f1
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Sep 2018 19:01:06.3373 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3NAM01HT081
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/u2heRSX0JzZSwfQI4OMbgB3aBjY>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 19:01:33 -0000

Rogers Canada..=20
Orange Poland as well I believe..

-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gert Doering
Sent: September 7, 2018 14:30
To: Ole Troan <otroan@employees.org>
Cc: draft-ietf-doh-dns-over-https.all@ietf.org; v6ops@ietf.org
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa

Hi,

On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>=20
> Are you saying that there are hundreds of millions of users on IPv6 only =
networks with NAT64/DNS64 their only exit to the IPv4 Internet?
> Where are these users? Cause I wasn???t aware of any general deployments =
of that to end-users.

T-Mobile USA...?

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Em=
mer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

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


From nobody Fri Sep  7 12:24:19 2018
Return-Path: <adam@nostrum.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA25F129619; Fri,  7 Sep 2018 12:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 eR3tT3SRbTNe; Fri,  7 Sep 2018 12:24:15 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 7DC1212008A; Fri,  7 Sep 2018 12:24:15 -0700 (PDT)
Received: from Svantevit.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w87JO6WV022649 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 7 Sep 2018 14:24:07 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.roach.at
To: Lee Howard <lee@asgard.org>, v6ops@ietf.org, draft-ietf-doh-dns-over-https.all@ietf.org, evyncke@cisco.com, Warren Kumari <warren@kumari.net>, dnsops-chairs@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <d7ae791a-0733-0ebc-5d76-fe3aea93f4a3@nostrum.com>
Date: Fri, 7 Sep 2018 14:24:00 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org>
Content-Type: multipart/alternative; boundary="------------8CC2CBE8270045C2913F5BC7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/g62dBhdIPFPKGmbsU0iYt95G5Cw>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 19:24:18 -0000

This is a multi-part message in MIME format.
--------------8CC2CBE8270045C2913F5BC7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Lee --

What you're describing is an issue that spans *all* Public DNS 
providers, regardless of whether they're DoT, DoH, or classic DNS. I 
believe that any operational advice that addresses the situation needs 
to be written in such a way that it speaks to all three cases, rather 
than being laser-focused on DoH. I don't want to speak for Warren or the 
DNSOPS chairs (copied), but this sounds to me like something that would 
best be resolved by a "Operational Considerations for Public DNS 
Servers" document.

/a

On 9/6/18 11:20 AM, Lee Howard wrote:
>
>
>
> On 09/05/2018 05:50 PM, Erik Nygren wrote:
>> DNSSEC isn't the only threat here.  Clients implementing protocols 
>> such as DoH also bypass the DNS64.
>> draft-ietf-doh-dns-over-https-14 does say:
>>
>>    Local policy considerations and similar factors mean different DNS
>>    servers may provide different results to the same query, for instance
>>    in split DNS configurations [RFC6950].  It logically follows that the
>>    server that is queried can influence the end result. Therefore a
>>    client's choice of DNS server may affect the responses it gets to its
>>    queries.  For example, in the case of DNS64 [RFC6147], the choice
>>    could affect whether IPv6/IPv4 translation will work at all.
>>
>> I'm not sure what the best way to approach this is in this draft.
>
>
> Yes, I remember reading that in DoH and rolling my eyes. The best 
> response is to strengthen the statement in that draft to say, 
> "Hundreds of millions of users behind DNS64 will be unable to use DoH, 
> unless IPv6 resource records are available, bypassing the DNS64 
> function." And maybe to point at this draft.
>
> I note that no OpsDir review has been submitted 
> https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/
> This is an operational issue.
>
>> For example:
>>
>> * Acknowledge that DNS64 is a shortish-term hack that only works in 
>> constrained environments.     If this is the case, that might argue 
>> that this draft should be at most Informational and not BCP?
>
> "Constrained environments" in this case meaning "the IPv4 Internet."
> This draft is BCP for domains with DNSSEC. It makes no recommendation 
> for DNS64 deployers.
>>
>> * Commit to DNS64 being a robust part of the architecture and cover 
>> topics more broadly than just DNSSEC?   Is there a way to handle the 
>> DOH case short of mandating that clients implementing DOH also do 
>> bump-in-the-API or client-side DNS64 synthesis or 464xlat?  If this 
>> is the case, should there be more firm wording in 
>> draft-ietf-doh-dns-over-https-14.  I suspect other conflicts will 
>> also appear over time.
>
> I wouldn't call it "robust," but I'd call it "widespread." I support 
> your suggestion that the BCP be applied more broadly, although it may 
> start to become redundant with BCP177 (rfc6540, "IPv6 Support Required 
> for All IPv6-Capable Nodes").
>
>> Is there really value in picking some middle ground between these?
>>
>> Is there concrete data on how often DNSSEC and DNS64 cause 
>> interaction issues and where?  They shouldn't on the recursive 
>> resolver itself.  How often are clients redoing DNSSEC validation and 
>> running into issues here?
>>
>> A separate pragmatic/cynic question is whether we think this will 
>> influence behavior?  I don't have a positive feeling that those who 
>> control whether a zone has DNSSEC enabled also have control over 
>> whether AAAA records are present for dual-stacked content in the 
>> zone.  Those are often separate actors.  Will a recommendation here 
>> have any substantive impact, and is there an audience who will be 
>> able to take action on this?
>
> I think this problem is largely unnoticed, and needs a recommendation 
> to address it. It may be unnoticed because the 15% of domains that use 
> DNSSEC 
> [https://stats.labs.apnic.net/dnssec/XA?c=XA&x=1&g=1&r=1&w=7&g=0] are 
> more likely to be among the 24% of domains that have IPv6 
> [http://www.employees.org/~dwing/aaaa-stats/] (or the other way 
> around) because the operators are early adopters.
>
>
> Lee
>
>>
>>        Erik
>>
>>   
>>
>> On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica <rbonica@juniper.net 
>> <mailto:rbonica@juniper.net>> wrote:
>>
>>     Folks,
>>
>>     Each week between now and IETF 103, we will review and discuss
>>     one draft with an eye towards progressing it.
>>
>>     This week, please review and comment on draft-byrne-v6ops-dnssecaaaa.
>>
>>                                           Fred and Ron
>>
>>     _______________________________________________
>>     v6ops mailing list
>>     v6ops@ietf.org <mailto:v6ops@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/v6ops
>>
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>


--------------8CC2CBE8270045C2913F5BC7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Lee --</div>
    <div class="moz-cite-prefix"><br>
    </div>
    What you're describing is an issue that spans *all* Public DNS
    providers, regardless of whether they're DoT, DoH, or classic DNS. I
    believe that any operational advice that addresses the situation
    needs to be written in such a way that it speaks to all three cases,
    rather than being laser-focused on DoH. I don't want to speak for
    Warren or the DNSOPS chairs (copied), but this sounds to me like
    something that would best be resolved by a "Operational
    Considerations for Public DNS Servers" document.
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">/a<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 9/6/18 11:20 AM, Lee Howard wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p><br>
      </p>
      <br>
      <div class="moz-cite-prefix">On 09/05/2018 05:50 PM, Erik Nygren
        wrote:<br>
      </div>
      <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
        <meta http-equiv="content-type" content="text/html;
          charset=UTF-8">
        <div dir="ltr">DNSSEC isn't the only threat here.  Clients
          implementing protocols such as DoH also bypass the DNS64.<br>
          draft-ietf-doh-dns-over-https-14 does say:<br>
          <br>
             Local policy considerations and similar factors mean
          different DNS<br>
             servers may provide different results to the same query,
          for instance<br>
             in split DNS configurations [RFC6950].  It logically
          follows that the<br>
             server that is queried can influence the end result. 
          Therefore a<br>
             client's choice of DNS server may affect the responses it
          gets to its<br>
             queries.  For example, in the case of DNS64 [RFC6147], the
          choice<br>
             could affect whether IPv6/IPv4 translation will work at
          all.<br>
        </div>
      </blockquote>
      <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
        <div dir="ltr"><br>
          I'm not sure what the best way to approach this is in this
          draft. <br>
        </div>
      </blockquote>
      <br>
      <br>
      Yes, I remember reading that in DoH and rolling my eyes. The best
      response is to strengthen the statement in that draft to say,
      "Hundreds of millions of users behind DNS64 will be unable to use
      DoH, unless IPv6 resource records are available, bypassing the
      DNS64 function." And maybe to point at this draft.<br>
      <br>
      I note that no OpsDir review has been submitted <a
        class="moz-txt-link-freetext"
        href="https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/"
        moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-doh-dns-over-https/</a><br>
      This is an operational issue.<br>
      <br>
      <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
        <div dir="ltr"> For example:<br>
          <br>
          * Acknowledge that DNS64 is a shortish-term hack that only
          works in constrained environments.     If this is the case,
          that might argue that this draft should be at most
          Informational and not BCP? <br>
        </div>
      </blockquote>
      <br>
      "Constrained environments" in this case meaning "the IPv4
      Internet." <br>
      This draft is BCP for domains with DNSSEC. It makes no
      recommendation for DNS64 deployers.<br>
      <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
        <div dir="ltr"><br>
          * Commit to DNS64 being a robust part of the architecture and
          cover topics more broadly than just DNSSEC?   Is there a way
          to handle the DOH case short of mandating that clients
          implementing DOH also do bump-in-the-API or client-side DNS64
          synthesis or 464xlat?  If this is the case, should there be
          more firm wording in draft-ietf-doh-dns-over-https-14.  I
          suspect other conflicts will also appear over time.<br>
        </div>
      </blockquote>
      <br>
      I wouldn't call it "robust," but I'd call it "widespread." I
      support your suggestion that the BCP be applied more broadly,
      although it may start to become redundant with BCP177 (rfc6540,
      "IPv6 Support Required for All IPv6-Capable Nodes").<br>
      <br>
      <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
        <div dir="ltr">Is there really value in picking some middle
          ground between these?<br>
          <br>
          Is there concrete data on how often DNSSEC and DNS64 cause
          interaction issues and where?  They shouldn't on the recursive
          resolver itself.  How often are clients redoing DNSSEC
          validation and running into issues here?<br>
          <br>
          A separate pragmatic/cynic question is whether we think this
          will influence behavior?  I don't have a positive feeling that
          those who control whether a zone has DNSSEC enabled also have
          control over whether AAAA records are present for dual-stacked
          content in the zone.  Those are often separate actors.  Will a
          recommendation here have any substantive impact, and is there
          an audience who will be able to take action on this?<br>
        </div>
      </blockquote>
      <br>
      I think this problem is largely unnoticed, and needs a
      recommendation to address it. It may be unnoticed because the 15%
      of domains that use DNSSEC
      [<a class="moz-txt-link-freetext"
href="https://stats.labs.apnic.net/dnssec/XA?c=XA&amp;x=1&amp;g=1&amp;r=1&amp;w=7&amp;g=0"
        moz-do-not-send="true">https://stats.labs.apnic.net/dnssec/XA?c=XA&amp;x=1&amp;g=1&amp;r=1&amp;w=7&amp;g=0</a>]
      are more likely to be among the 24% of domains that have IPv6 [<a
        class="moz-txt-link-freetext"
        href="http://www.employees.org/~dwing/aaaa-stats/"
        moz-do-not-send="true">http://www.employees.org/~dwing/aaaa-stats/</a>] 
      (or the other way around) because the operators are early
      adopters. <br>
      <br>
      <br>
      Lee<br>
      <br>
      <blockquote type="cite"
cite="mid:CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com">
        <div dir="ltr"><br>
                 Erik
          <div dir="ltr"><br>
            <div class="gmail_default"
              style="font-family:tahoma,sans-serif">
              <pre class="gmail-newpage"> 
</pre>
            </div>
          </div>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr">On Wed, Sep 5, 2018 at 11:29 AM Ron Bonica &lt;<a
              href="mailto:rbonica@juniper.net" moz-do-not-send="true">rbonica@juniper.net</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0&#xA;
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<br>
            <br>
            Each week between now and IETF 103, we will review and
            discuss one draft with an eye towards progressing it.<br>
            <br>
            This week, please review and comment on
            draft-byrne-v6ops-dnssecaaaa.<br>
            <br>
                                                  Fred and Ron<br>
            <br>
            _______________________________________________<br>
            v6ops mailing list<br>
            <a href="mailto:v6ops@ietf.org" target="_blank"
              moz-do-not-send="true">v6ops@ietf.org</a><br>
            <a href="https://www.ietf.org/mailman/listinfo/v6ops"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
          </blockquote>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org" moz-do-not-send="true">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/v6ops</a>
</pre>
      </blockquote>
      <br>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------8CC2CBE8270045C2913F5BC7--


From nobody Fri Sep  7 12:26:04 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2AC7129619; Fri,  7 Sep 2018 12:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ol5r33P9VLxQ; Fri,  7 Sep 2018 12:26:00 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5C4F12008A; Fri,  7 Sep 2018 12:26:00 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 14187FECBBE3; Fri,  7 Sep 2018 19:26:00 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <BN6PR04MB09329276E17BEB5D6D3420BDDD000@BN6PR04MB0932.namprd04.prod.outlook.com>
Date: Fri, 7 Sep 2018 21:25:57 +0200
Cc: Gert Doering <gert@space.net>, "draft-ietf-doh-dns-over-https.all@ietf.org" <draft-ietf-doh-dns-over-https.all@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D72E18B-8541-410A-BF2B-AB450723411B@employees.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <BN6PR04MB09329276E17BEB5D6D3420BDDD000@BN6PR04MB0932.namprd04.prod.outlook.com>
To: Kristian McColm <kristianmccolm@hotmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/inliO7N8FGdXMfv-kUu6dnVU-R8>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 19:26:03 -0000

> On 7 Sep 2018, at 21:01, Kristian McColm <kristianmccolm@hotmail.com> wrot=
e:
>=20
> Rogers Canada..=20
> Orange Poland as well I believe..

Do you have a detailed service description?
If I recall correctly T-Mobile offers dual stack when tethering, but possibl=
y nat64 for local mobile applications. But note this device is tightly contr=
olled and could of course do address synthesis.=20

Ole


>=20
> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gert Doering
> Sent: September 7, 2018 14:30
> To: Ole Troan <otroan@employees.org>
> Cc: draft-ietf-doh-dns-over-https.all@ietf.org; v6ops@ietf.org
> Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
>=20
> Hi,
>=20
>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>=20
>> Are you saying that there are hundreds of millions of users on IPv6 only n=
etworks with NAT64/DNS64 their only exit to the IPv4 Internet?
>> Where are these users? Cause I wasn???t aware of any general deployments o=
f that to end-users.
>=20
> T-Mobile USA...?
>=20
> Gert Doering
>        -- NetMaster
> --=20
> have you enabled IPv6 on something today...?
>=20
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael E=
mmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Fri Sep  7 12:46:33 2018
Return-Path: <kristianmccolm@hotmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71813130DDA; Fri,  7 Sep 2018 12:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.126
X-Spam-Level: 
X-Spam-Status: No, score=-1.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 57ky3ePrSkWU; Fri,  7 Sep 2018 12:46:29 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-oln040092001072.outbound.protection.outlook.com [40.92.1.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5E1E12008A; Fri,  7 Sep 2018 12:46:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XbEWNhJbD/YiPQ/LyLdBoF5y+3Z74WePnvz3COGQj8A=; b=NDrnKI2Gt+da6KqmJW/i1SQ/LBvYZ4j77pRGcakcdGwh6qBRZ50g7lk7z7/jRkXcrXJL04NCSzdLrAiUoCEsJ3oORh5/IyrRHs62im2IZbs9dNs9f7cGzCpfIaqYGpXrpIeukZsLLlI4SYybi0R9aMYm0o/JHPRzfEv+NxMNPRVj0j0vfHdf3M8soTFADybfRXi4VqXzB6+QRB/I5cO4vU//zaao6JjAW1kzNXkntY+4/6xCWUQKZhspvKnkaIsEA8omJgyryJrvPvu+dTcy7rPj25U2P4p6RMWAlLTBs7XN6CW8r+WqmT9Ax+mj6MInme2JZ/L/jEWPPakXhj+GIw==
Received: from BY2NAM01FT045.eop-nam01.prod.protection.outlook.com (10.152.68.58) by BY2NAM01HT138.eop-nam01.prod.protection.outlook.com (10.152.69.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.1122.11; Fri, 7 Sep 2018 19:46:28 +0000
Received: from BN6PR04MB0932.namprd04.prod.outlook.com (10.152.68.59) by BY2NAM01FT045.mail.protection.outlook.com (10.152.68.206) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1122.11 via Frontend Transport; Fri, 7 Sep 2018 19:46:28 +0000
Received: from BN6PR04MB0932.namprd04.prod.outlook.com ([fe80::20db:f93:87ea:97a]) by BN6PR04MB0932.namprd04.prod.outlook.com ([fe80::20db:f93:87ea:97a%3]) with mapi id 15.20.1101.016; Fri, 7 Sep 2018 19:46:28 +0000
From: Kristian McColm <kristianmccolm@hotmail.com>
To: Ole Troan <otroan@employees.org>, Kristian McColm <kristianmccolm@hotmail.com>
CC: Gert Doering <gert@space.net>, "draft-ietf-doh-dns-over-https.all@ietf.org" <draft-ietf-doh-dns-over-https.all@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-byrne-v6ops-dnssecaaaa
Thread-Index: AdRFLRaRiSevdVfRR1yuHRNkcg68jgANWhoAACa+XIAAD3AWgAAdu4SAAACnyYAAAimUAAADSXiAAADv6YAAAnPJAAAAK/WAAAELIUAAAOcrgAAAeUOA
Date: Fri, 7 Sep 2018 19:46:28 +0000
Message-ID: <BN6PR04MB093265C9F7BA5E45C1D8C287DD000@BN6PR04MB0932.namprd04.prod.outlook.com>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <BN6PR04MB09329276E17BEB5D6D3420BDDD000@BN6PR04MB0932.namprd04.prod.outlook.com> <1D72E18B-8541-410A-BF2B-AB450723411B@employees.org>
In-Reply-To: <1D72E18B-8541-410A-BF2B-AB450723411B@employees.org>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:107949DD05B52BBA14A1C65C7916B633858BCCE1432F27ECC8802338D85A112C; UpperCasedChecksum:A451145A636E518481855BDB5DBFDF40C5F9B6C8309BB816490BF7B8AEA31BE3; SizeAsReceived:8028; Count:46
x-tmn: [uyena3UWK2TFhjZPE2jafjfpjEKLluK2yR3KRHyjVlPLRyforuHtIPg4HR5Xm/P8]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2NAM01HT138; 6:AHGKFVNsT2uBMFMFaOanGc9cx7Fz+1AiG34tfty/fzKqQpqEBJ7EiDFiDc7dl2ANsJMsy+7Th8sEcY9K/4iBqLNd9+khObS/kB1i5XQu98wo+8SWOxZ0JUkR6laSKfqVwkGETw7AAY08T7gHhssXPM+s9/d04J+HEsRtdKcKzQqMXg4Zeuxk1voZGyic6me4FqNa6S+s4DcfvV9biLry9Ou2cm8NItIyx+eK6fwRTVSpIt1TXGkX4/mb2KYr08GnCtSr6kpJosFQjlHQIPJt+vC+cGOhakW4eYVsNZLzZrDJn6MwvXAXRygJ0mNyvSoSey857n4ExcR4FfF3ULrljGypNtaC1yAh/auDyYF++XwdVRWLTWvz0pO7s/6Wk3cfDUanynU7/G3zOvWxcmDFWLudNx2zgRXRKNUsypPcpgMPYlId98Gm90p7M98Ytqtniho2DzxULD+jmVQBgIwqiA==; 5:0PJi1Q3Jq1f35AMIpP+OqeODZyuFIuNgK7P7TdZDwaq6jiTgNn/exURdEP15k4fqxdRVJADZqUuYO4mx8/O9laxWrVc/t7VzuG+WD+QaUCUWEy07m2hOQuw/xkLGYWdOyH6g9ujgELspdRq/HxDsjzbQdebkJ4FU4mYXe9IPn7o=; 7:zjPZWf0jJqvrGJc1Gl3MJ4rGsE2fFsa4VnLwHOadK4hbdsU+9NnqYsLGTbverRh/CnuYxssR++XemfFEvfyEU7aLvy7iYdfKRpa0c4zXtdNLaqk1ApR8PKT6gaMDw3T+n9VGQaeW4bjTQeL0QcP04L1E14fsNDMnwIM6nR1lQI3JN+xfkRqSRNuxquxVDLNOzNxJdPjYAipSVP4A00OQoUKfNB7rbXulBZwFqyJlOBS6Qzot7UPrTpgaclWsiEr8
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-ms-exchange-slblob-mailprops: pt8ZUcDWjMU4xVXKgpSxssrHCFZ0WG1xl+vkTX0ARyyKeC6vmx+nStqjWCcdohuQo9GP0KnpeaDVIjfD83w8g1fiJFBe8kithJlvEaAeUaE1S9zS56Eb4QuspagfWo3K36n8uZWnj6TxKRreQgy5dANdfE5Bkyxe+KfUqE36nwl7vRTI9OdmsB9dGil6kuC1gibC7FvLdFHBmHX2okdVH5poCfEBSTXSKt8iktV3a0bi+LjjVmp+v1pQUxgphDLH/slNvKrsfwOPUAUkxr5SDXYLvYnr4HBLoWghdwmYKBMyUiLQEEbdlVCwpDEmQe1agEnzM+H/a/amW9Fi7S6hEANzp50h2oNCvGFuaxeh77OFkTMA/7elwYKv4zZcFMOo2Ocpt9e2ChC1c/uzE4zyX+TaI10/6PxGFHRhZNF/RuwwODRM22E/o2pkegklqbntZsfNSeKybVCYOmOk/4NaiAOR/5Q3wxtqa+EjP/GVQo7932CUMOvErgiKmqyf4e8BLNfE97n7MMYs25Zl+yoce2gheDrBrRmLteD2d9GS8EfrMHg6DPONLTHP1LkhVfllqrF68O5EiiQRcj+jhnHu4l47cLxkLiEltgVwOsYyk1Sprldtl9WwwVQQYGNzBIGGw81+Pq77TrVY3aowURFvYVqQE+d/Y0MFX0FyovY80Wa4p0/js/gF/o726ztrqqhRwS2CWeqfmL9jC7BpekjOZH2AoIMrs1LWF1pgB1a8jSleOhYLaGcVDP0NYjWukV3yFNoKQI47069vKpgaGuMmgTgfq1BoB/yrBvNRFeydQV1KJIfNSp6sOw3NGaHSk5gCzzPRmA3emxSS60AJwVe34iDOD1Bsq3NIrM2q5rAQXyTPEgs/I4/f28vMlgCYzULkYC8CSKF3PECIj8du4xw8mQ1e1gG2+rL/pVRjAQF3zuKfQwzlPRWJSjAEb0OXjeJD
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(201702181274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:BY2NAM01HT138; 
x-ms-traffictypediagnostic: BY2NAM01HT138:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058);  SRVR:BY2NAM01HT138; BCL:0; PCL:0; RULEID:; SRVR:BY2NAM01HT138; 
x-forefront-prvs: 07880C4932
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(199004)(189003)(13464003)(6246003)(97736004)(39060400002)(9686003)(229853002)(476003)(46003)(20460500001)(73972006)(6436002)(8936002)(256004)(56003)(5660300001)(83332001)(86362001)(74316002)(55016002)(6306002)(99286004)(68736007)(53546011)(8676002)(54906003)(102836004)(966005)(33656002)(82202002)(110136005)(7696005)(2900100001)(486006)(81156014)(76176011)(6506007)(106356001)(105586002)(11346002)(5250100002)(4326008)(446003)(93886005)(305945005)(104016004)(25786009)(6346003)(87572001)(14454004)(15852004); DIR:OUT; SFP:1901; SCL:1; SRVR:BY2NAM01HT138; H:BN6PR04MB0932.namprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; 
received-spf: None (protection.outlook.com: hotmail.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kristianmccolm@hotmail.com; 
x-microsoft-antispam-message-info: YXtqKIqol292w00I7aInV3RsqYLOtRtIYt6RVg6umbgwcOxc/Qvw0WcRIs7aulY42WbQ0rUoyzAdMsOt6KKetIq7xo1GmObIwHgEuEI/JTy3D90QFW7rH5KhWfAPZVDxGqlPpb3/1j+BzfnaMLPMrlT3SpJDMXqU7DG/nvPmOL9HIFmQwHd//dYAGtTbDtg+SHwWFEwQwWDcSgikier6egW59XldAvjILVsrB+9vN4k=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-Network-Message-Id: f13d10ba-1ebb-486e-42de-08d614fa9a63
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Sep 2018 19:46:28.2829 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM01HT138
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/TrLbM_8p_VUlIEEfMcIYU3ezIv0>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 19:46:31 -0000

Not sure how detailed you are looking for. Rogers is IPv6-only with DNS64/N=
AT64 for the main LTE APN and devices Android L and iPhone 6 and newer, but=
 the tethering APN is still dual-stacked.

-----Original Message-----
From: Ole Troan [mailto:otroan@employees.org]=20
Sent: September 7, 2018 15:26
To: Kristian McColm <kristianmccolm@hotmail.com>
Cc: Gert Doering <gert@space.net>; draft-ietf-doh-dns-over-https.all@ietf.o=
rg; v6ops@ietf.org
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa



> On 7 Sep 2018, at 21:01, Kristian McColm <kristianmccolm@hotmail.com> wro=
te:
>=20
> Rogers Canada..=20
> Orange Poland as well I believe..

Do you have a detailed service description?
If I recall correctly T-Mobile offers dual stack when tethering, but possib=
ly nat64 for local mobile applications. But note this device is tightly con=
trolled and could of course do address synthesis.=20

Ole


>=20
> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gert Doering
> Sent: September 7, 2018 14:30
> To: Ole Troan <otroan@employees.org>
> Cc: draft-ietf-doh-dns-over-https.all@ietf.org; v6ops@ietf.org
> Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
>=20
> Hi,
>=20
>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>=20
>> Are you saying that there are hundreds of millions of users on IPv6 only=
 networks with NAT64/DNS64 their only exit to the IPv4 Internet?
>> Where are these users? Cause I wasn???t aware of any general deployments=
 of that to end-users.
>=20
> T-Mobile USA...?
>=20
> Gert Doering
>        -- NetMaster
> --=20
> have you enabled IPv6 on something today...?
>=20
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael =
Emmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Fri Sep  7 12:56:45 2018
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C82D0130E63; Fri,  7 Sep 2018 12:56:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ron Bonica <rbonica@juniper.net>
To: <warren@kumari.net>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.1
Auto-Submitted: auto-generated
Precedence: bulk
Cc: Ron Bonica <rbonica@juniper.net>, v6ops@ietf.org, iesg-secretary@ietf.org,  v6ops-chairs@ietf.org, rbonica@juniper.net
Message-ID: <153635018580.29013.17999792548516683805.idtracker@ietfa.amsl.com>
Date: Fri, 07 Sep 2018 12:56:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/JToVyhthM1Bpj1H-zp9LAEDNWAU>
Subject: [v6ops] Publication has been requested for draft-ietf-v6ops-transition-ipv4aas-08
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 19:56:34 -0000

Ron Bonica has requested publication of draft-ietf-v6ops-transition-ipv4aas-08 as None on behalf of the V6OPS working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/


From nobody Fri Sep  7 13:35:34 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A1C128C65; Fri,  7 Sep 2018 13:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 PYuIyNkuAxI2; Fri,  7 Sep 2018 13:35:31 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27B6612F18C; Fri,  7 Sep 2018 13:35:31 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 61ECDFECBAC2; Fri,  7 Sep 2018 20:35:30 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <BN6PR04MB093265C9F7BA5E45C1D8C287DD000@BN6PR04MB0932.namprd04.prod.outlook.com>
Date: Fri, 7 Sep 2018 22:35:28 +0200
Cc: Gert Doering <gert@space.net>, "draft-ietf-doh-dns-over-https.all@ietf.org" <draft-ietf-doh-dns-over-https.all@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E18B9F5-4A2B-4AB6-97D6-7DB304F70E81@employees.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <BN6PR04MB09329276E17BEB5D6D3420BDDD000@BN6PR04MB0932.namprd04.prod.outlook.com> <1D72E18B-8541-410A-BF2B-AB450723411B@employees.org> <BN6PR04MB093265C9F7BA5E45C1D8C287DD000@BN6PR04MB0932.namprd04.prod.outlook.com>
To: Kristian McColm <kristianmccolm@hotmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/eUdu18I9oF5u0PVVFEj8RoYEA8w>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 20:35:33 -0000

>=20
> Not sure how detailed you are looking for. Rogers is IPv6-only with DNS64/=
NAT64 for the main LTE APN and devices Android L and iPhone 6 and newer, but=
 the tethering APN is still dual-stacked

Right, then we=E2=80=99re talking about a tightly controlled environment whe=
re SPs and handset manufacturers work closely together.
Not particularly difficult to argue that handsets should be able to synthesi=
ze addresses on the host in these cases. So why shouldn=E2=80=99t that be ou=
r recommendation?

Ole


> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]=20
> Sent: September 7, 2018 15:26
> To: Kristian McColm <kristianmccolm@hotmail.com>
> Cc: Gert Doering <gert@space.net>; draft-ietf-doh-dns-over-https.all@ietf.=
org; v6ops@ietf.org
> Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
>=20
>=20
>=20
>> On 7 Sep 2018, at 21:01, Kristian McColm <kristianmccolm@hotmail.com> wro=
te:
>>=20
>> Rogers Canada..=20
>> Orange Poland as well I believe..
>=20
> Do you have a detailed service description?
> If I recall correctly T-Mobile offers dual stack when tethering, but possi=
bly nat64 for local mobile applications. But note this device is tightly con=
trolled and could of course do address synthesis.=20
>=20
> Ole
>=20
>=20
>>=20
>> -----Original Message-----
>> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gert Doering
>> Sent: September 7, 2018 14:30
>> To: Ole Troan <otroan@employees.org>
>> Cc: draft-ietf-doh-dns-over-https.all@ietf.org; v6ops@ietf.org
>> Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
>>=20
>> Hi,
>>=20
>>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>>=20
>>> Are you saying that there are hundreds of millions of users on IPv6 only=
 networks with NAT64/DNS64 their only exit to the IPv4 Internet?
>>> Where are these users? Cause I wasn???t aware of any general deployments=
 of that to end-users.
>>=20
>> T-Mobile USA...?
>>=20
>> Gert Doering
>>       -- NetMaster
>> --=20
>> have you enabled IPv6 on something today...?
>>=20
>> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael E=
mmer
>> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann=

>> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
>> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20


From nobody Fri Sep  7 14:09:59 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2592C130DF7; Fri,  7 Sep 2018 14:09:53 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 9jtpN2QcTptu; Fri,  7 Sep 2018 14:09:51 -0700 (PDT)
Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) (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 2C48A130DDB; Fri,  7 Sep 2018 14:09:51 -0700 (PDT)
Received: by mail-yw1-xc30.google.com with SMTP id n207-v6so5872215ywn.9; Fri, 07 Sep 2018 14:09:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WwrcX/0COAOA8NrLy69sfDvtFaSCUYgUB1jksxd+ugs=; b=mQH4tdRzigokviY2JY5qVVCsSGJOFNgVdhY9fD+3lRt1NL2nXRl8JFdWRGM6kWayhW d6172bPgf850t9KFyhI/s8gm9UbPEBw4rljBwoOlzLnFaxVF7IBdt45APhOlAx2xBZuO +P4uqkswOVgDZKhjc2swO/Yy8mWcHjOSNFwftoK5OEjp1ZuJzMG7IP7pxVhXacE8Cqeg 4UVolKAtVUorpQmYJZOHGYYe8oO3BuwUe3qq8I7via7MtY0RvEJ+RcLY9MX8p55Rqmer CZZR4B48kYjzXBCdT2aucLstFbe8691N0PNs2m/ObFs/9h6pGyFw5wm7Yhd5taGaMrJ4 80Cg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WwrcX/0COAOA8NrLy69sfDvtFaSCUYgUB1jksxd+ugs=; b=rRtGsaAPue8Y0JuldOsAF6hMRAshCgb99j7LH1q00MTtRCzf0yMw/nPS4a/DNcFyCX OABrSZODXiIsKpsU9gAQVoZ6dyM4PEsrtvgfIDlAxWJM2yAt50Arx4xC7uNU3AVKGgyc ABCt5t/nTNGuJUAwSLNL8NQ1YmeVv8Vp0HhWc+YLlBMY4DlV21InbXzSnHLG1Mua5DYL HmTgBaEDdbxL1i2Pc/yUKXx6KuUK7xcovJUCbScFtfw8eX5kxx8XH3UM8d0JbHzeqZT4 L10GN13D1Qsne4m741OJH7utJTrE7fvcuPgaj9fpslaDE0QXobHcRxbJLGM+ncXs95hd 3OOw==
X-Gm-Message-State: APzg51CLtZXdQU5B5N5pUHN+R4TCu61B7u9hqgJnwiWh4kDf5tdHZrX3 7/Fb9kmmwRONcmO8uIRUERi3PZBJOb9KQ7PONBg=
X-Google-Smtp-Source: ANB0VdbrAWci6aSf0kx2xvu2fGRoC5imm69REuTvSNMv8+zDSwVujoXRMJvCIAFgRD64BJb0jWd8xv5pMzKMTZz0Vqg=
X-Received: by 2002:a81:8087:: with SMTP id q129-v6mr5033478ywf.184.1536354590247;  Fri, 07 Sep 2018 14:09:50 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <BN6PR04MB09329276E17BEB5D6D3420BDDD000@BN6PR04MB0932.namprd04.prod.outlook.com> <1D72E18B-8541-410A-BF2B-AB450723411B@employees.org> <BN6PR04MB093265C9F7BA5E45C1D8C287DD000@BN6PR04MB0932.namprd04.prod.outlook.com> <7E18B9F5-4A2B-4AB6-97D6-7DB304F70E81@employees.org>
In-Reply-To: <7E18B9F5-4A2B-4AB6-97D6-7DB304F70E81@employees.org>
From: Ca By <cb.list6@gmail.com>
Date: Fri, 7 Sep 2018 14:09:38 -0700
Message-ID: <CAD6AjGQhrf0sxQ+22sQuBkgPs7UeMhpqSDKcVH7OYx6=xasc3Q@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: Kristian McColm <kristianmccolm@hotmail.com>,  "draft-ietf-doh-dns-over-https.all@ietf.org" <draft-ietf-doh-dns-over-https.all@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000099cf5c05754e6da0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BDha7Gdq_FIVB2TsJQRdb7Ri5P8>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Sep 2018 21:09:57 -0000

--00000000000099cf5c05754e6da0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 7, 2018 at 1:35 PM Ole Troan <otroan@employees.org> wrote:

>
> >
> > Not sure how detailed you are looking for. Rogers is IPv6-only with
> DNS64/NAT64 for the main LTE APN and devices Android L and iPhone 6 and
> newer, but the tethering APN is still dual-stacked
>
> Right, then we=E2=80=99re talking about a tightly controlled environment =
where SPs
> and handset manufacturers work closely together.
> Not particularly difficult to argue that handsets should be able to
> synthesize addresses on the host in these cases. So why shouldn=E2=80=99t=
 that be
> our recommendation?
>

1. They discover the pref64 via rfc 7050 with dns64. There is no dhcp in
3gpp to the ue.  Dns64 must be present.

2.  Many 464xlat networks prefer the use of dns64 to avoid double
translation on the user plane.  This provides simplification and
performance benefits.

3. Nothing about 70+ million subscribers is tightly controlled, please do
not minimize the challenge



> Ole
>
>
> > -----Original Message-----
> > From: Ole Troan [mailto:otroan@employees.org]
> > Sent: September 7, 2018 15:26
> > To: Kristian McColm <kristianmccolm@hotmail.com>
> > Cc: Gert Doering <gert@space.net>;
> draft-ietf-doh-dns-over-https.all@ietf.org; v6ops@ietf.org
> > Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
> >
> >
> >
> >> On 7 Sep 2018, at 21:01, Kristian McColm <kristianmccolm@hotmail.com>
> wrote:
> >>
> >> Rogers Canada..
> >> Orange Poland as well I believe..
> >
> > Do you have a detailed service description?
> > If I recall correctly T-Mobile offers dual stack when tethering, but
> possibly nat64 for local mobile applications. But note this device is
> tightly controlled and could of course do address synthesis.
> >
> > Ole
> >
> >
> >>
> >> -----Original Message-----
> >> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gert Doering
> >> Sent: September 7, 2018 14:30
> >> To: Ole Troan <otroan@employees.org>
> >> Cc: draft-ietf-doh-dns-over-https.all@ietf.org; v6ops@ietf.org
> >> Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
> >>
> >> Hi,
> >>
> >>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
> >>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
> >>>
> >>> Are you saying that there are hundreds of millions of users on IPv6
> only networks with NAT64/DNS64 their only exit to the IPv4 Internet?
> >>> Where are these users? Cause I wasn???t aware of any general
> deployments of that to end-users.
> >>
> >> T-Mobile USA...?
> >>
> >> Gert Doering
> >>       -- NetMaster
> >> --
> >> have you enabled IPv6 on
> <https://maps.google.com/?q=3Dhave+you+enabled+IPv6+on+&entry=3Dgmail&sou=
rce=3Dg>something
> today...?
> >>
> >> SpaceNet AG                      Vorstand: Sebastian v. Bomhard,
> Michael Emmer
> >> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A.
> Grundner-Culemann
> >> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> >> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--00000000000099cf5c05754e6da0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri,=
 Sep 7, 2018 at 1:35 PM Ole Troan &lt;<a href=3D"mailto:otroan@employees.or=
g">otroan@employees.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><br>
&gt; <br>
&gt; Not sure how detailed you are looking for. Rogers is IPv6-only with DN=
S64/NAT64 for the main LTE APN and devices Android L and iPhone 6 and newer=
, but the tethering APN is still dual-stacked<br>
<br>
Right, then we=E2=80=99re talking about a tightly controlled environment wh=
ere SPs and handset manufacturers work closely together.<br>
Not particularly difficult to argue that handsets should be able to synthes=
ize addresses on the host in these cases. So why shouldn=E2=80=99t that be =
our recommendation?<br>
</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">1. They discover=
 the pref64 via rfc 7050 with dns64. There is no dhcp in 3gpp to the ue.=C2=
=A0 Dns64 must be present. =C2=A0</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">2.=C2=A0 Many 464xlat networks prefer the use of dns64 to avoid d=
ouble translation on the user plane.=C2=A0 This provides simplification and=
 performance benefits.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">3. Nothing about 70+ million subscribers is tightly controlled, please=
 do not minimize the challenge</div><div dir=3D"auto"><br></div><div dir=3D=
"auto"><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Ole<br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Ole Troan [mailto:<a href=3D"mailto:otroan@employees.org" target=
=3D"_blank">otroan@employees.org</a>] <br>
&gt; Sent: September 7, 2018 15:26<br>
&gt; To: Kristian McColm &lt;<a href=3D"mailto:kristianmccolm@hotmail.com" =
target=3D"_blank">kristianmccolm@hotmail.com</a>&gt;<br>
&gt; Cc: Gert Doering &lt;<a href=3D"mailto:gert@space.net" target=3D"_blan=
k">gert@space.net</a>&gt;; <a href=3D"mailto:draft-ietf-doh-dns-over-https.=
all@ietf.org" target=3D"_blank">draft-ietf-doh-dns-over-https.all@ietf.org<=
/a>; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a>=
<br>
&gt; Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt;&gt; On 7 Sep 2018, at 21:01, Kristian McColm &lt;<a href=3D"mailto:kri=
stianmccolm@hotmail.com" target=3D"_blank">kristianmccolm@hotmail.com</a>&g=
t; wrote:<br>
&gt;&gt; <br>
&gt;&gt; Rogers Canada.. <br>
&gt;&gt; Orange Poland as well I believe..<br>
&gt; <br>
&gt; Do you have a detailed service description?<br>
&gt; If I recall correctly T-Mobile offers dual stack when tethering, but p=
ossibly nat64 for local mobile applications. But note this device is tightl=
y controlled and could of course do address synthesis. <br>
&gt; <br>
&gt; Ole<br>
&gt; <br>
&gt; <br>
&gt;&gt; <br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: v6ops [mailto:<a href=3D"mailto:v6ops-bounces@ietf.org" targ=
et=3D"_blank">v6ops-bounces@ietf.org</a>] On Behalf Of Gert Doering<br>
&gt;&gt; Sent: September 7, 2018 14:30<br>
&gt;&gt; To: Ole Troan &lt;<a href=3D"mailto:otroan@employees.org" target=
=3D"_blank">otroan@employees.org</a>&gt;<br>
&gt;&gt; Cc: <a href=3D"mailto:draft-ietf-doh-dns-over-https.all@ietf.org" =
target=3D"_blank">draft-ietf-doh-dns-over-https.all@ietf.org</a>; <a href=
=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
&gt;&gt; Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa<br>
&gt;&gt; <br>
&gt;&gt; Hi,<br>
&gt;&gt; <br>
&gt;&gt;&gt; On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:<br>
&gt;&gt;&gt; NAT64 and DNS64 is deployed, and sometimes in chort with 464XL=
AT.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Are you saying that there are hundreds of millions of users on=
 IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 Internet?<=
br>
&gt;&gt;&gt; Where are these users? Cause I wasn???t aware of any general d=
eployments of that to end-users.<br>
&gt;&gt; <br>
&gt;&gt; T-Mobile USA...?<br>
&gt;&gt; <br>
&gt;&gt; Gert Doering<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0-- NetMaster<br>
&gt;&gt; -- <br>
&gt;&gt; <a href=3D"https://maps.google.com/?q=3Dhave+you+enabled+IPv6+on+&=
amp;entry=3Dgmail&amp;source=3Dg">have you enabled IPv6 on </a>something to=
day...?<br>
&gt;&gt; <br>
&gt;&gt; SpaceNet AG=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 Vorstand: Sebastian v. Bomhard, Michael Emmer<br>
&gt;&gt; Joseph-Dollinger-Bogen 14=C2=A0 =C2=A0 =C2=A0 =C2=A0 Aufsichtsrats=
vors.: A. Grundner-Culemann<br>
&gt;&gt; D-80807 Muenchen=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0HRB: 136055 (AG Muenchen)<br>
&gt;&gt; Tel: +49 (0)89/32356-444=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0USt-IdNr=
.: DE813185279<br>
&gt;&gt; <br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; v6ops mailing list<br>
&gt;&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org=
</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"nor=
eferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><=
br>
&gt; <br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div>

--00000000000099cf5c05754e6da0--


From nobody Fri Sep  7 23:23:33 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 303B412D7EA; Fri,  7 Sep 2018 23:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 iRnQ9RTghVuC; Fri,  7 Sep 2018 23:23:30 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 80440128CE4; Fri,  7 Sep 2018 23:23:30 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id E5C4F3AB003; Sat,  8 Sep 2018 06:23:27 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id BCDE6160071; Sat,  8 Sep 2018 06:22:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 6C02A16006D; Sat,  8 Sep 2018 06:22:57 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZU33tyhnV42R; Sat,  8 Sep 2018 06:22:57 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 0D4C8160055; Sat,  8 Sep 2018 06:22:55 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org>
Date: Sat, 8 Sep 2018 16:22:52 +1000
Cc: v6ops@ietf.org, draft-ietf-doh-dns-over-https.all@ietf.org, evyncke@cisco.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A324B33-C05E-4B63-B431-2A091FAC4CF8@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/E6GD8fr1XTzgBuX6De4XuVupEBE>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 08 Sep 2018 06:23:32 -0000

> On 7 Sep 2018, at 11:53 pm, Lee Howard <lee@asgard.org> wrote:
>=20
>=20
>=20
> On 09/06/2018 07:42 PM, Mark Andrews wrote:
>> Can we please have some technological leadership in the IETF and
>> say that DNS64 is technically flawed for a number of reason and
>> SHOULD NOT be used.
>=20
> Technological leadership looks to you like telling operators they =
deployed their network wrong, and must change it.
> To me, it looks like acknowledging advice from operators on how the =
Internet actually works, and identifying interoperability problems.

Yes, they got it WRONG. They just happed to GET AWAY WITH IT because =
they clients
where mainly very limited devices called CELL PHONES that don=E2=80=99t =
*generally* do DNSSEC,
nor do their own iterative DNS resolution, nor use DNS servers other =
than the ones
given to them over 3GPP (directly or indirectly).

Anyone that wants to do those things gets told =E2=80=9Cwe don=E2=80=99t =
support that=E2=80=9D from the
Telcos.

> Technological leadership to me looks more like warning people about =
interoperability issues and how to avoid them. When that's as easy as =
following previous BCP advice (i.e., rfc6540: deploy IPv6), we are =
remaining entirely consistent.

You can=E2=80=99t avoid them with DNS64. The people deploying DNS64 are =
not the ones that
are running IPv4 only sites.

What advice do you give the site deploying DNS64 to make everything =
work?  Deploy
intercepting DNS proxies of which I=E2=80=99ve yet to see one that does =
even a semi-reasonable job.  No, you can=E2=80=99t just direct all the =
DNS queries at a recursive DNS server with DNS64 configured.  That =
doesn=E2=80=99t work for plain DNS let along DNS with DNS64 despite what
the snake oil vendors that off that sort of stuff claim.  I=E2=80=99ve =
had to turn off
full iterative servers too many times to work around the breakage of a =
ISP that
thinks intercepting DNS proxies are a good idea.

> If you want to deprecate DNS64, and therefore the other transition =
mechanisms that rely on it, that's a different draft. I would not =
support it at this time. If instead you want a draft that warns about =
interoperability problems when deploying DNS64, if it says something =
more than what is already in rfc6147 (DNS64) and this draft, I look =
forward to seeing it.
>=20
>> It has always been a flawed technology that was deployed as a =
stop-gap.
>=20
> That could be said for all transition technologies, and I eagerly =
await the day when they can be discarded.

It was deployed as a stop gap for other transition technologies. 3GPP =
said we want
something *NOW*!!!!  We have other transition technologies that have =
don=E2=80=99t have the
drawbacks of DNS64. =20

>> Stop trying to get the rest of the internet to change because some
>> sites are continuing to deploy DNS64 which is what this draft does.
>> That is the tail wagging the dog.
> I don't think this is "continuing to deploy DNS64" but "continuing to =
deploy DNSSEC when it won't work with existing DNS64.=E2=80=9D

It=E2=80=99s not just DNSSEC.  It=E2=80=99s you MUST use our name =
servers as we have deployed DNS64.

> Most operators I'm talking to are looking at more recent and stateless =
transition technologies. That doesn't get the hundreds of millions of =
folks off of the networks they're on.
>=20
> In the case of DOH, that is an effort trying to get the Internet to =
change despite known interoperability problems.

DOH is just a example of what DNS64 breaks.  It is not the only thing.

> Lee

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Fri Sep  7 23:36:16 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8C3512F1A5; Fri,  7 Sep 2018 23:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 B8df9p3rSaMF; Fri,  7 Sep 2018 23:36:12 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 01378126BED; Fri,  7 Sep 2018 23:36:12 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id CCA753AB03B; Sat,  8 Sep 2018 06:36:11 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id B1A7616007F; Sat,  8 Sep 2018 06:36:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 9C6B516007E; Sat,  8 Sep 2018 06:36:11 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id R7lBFe_7zU37; Sat,  8 Sep 2018 06:36:11 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 8269B160080; Sat,  8 Sep 2018 06:36:10 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org>
Date: Sat, 8 Sep 2018 16:36:04 +1000
Cc: Ole Troan <otroan@employees.org>, draft-ietf-doh-dns-over-https.all@ietf.org, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BCCFBAE-D9BB-4EAF-87C5-3295BA937CAF@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3aFxG0pgiU0W8-ye2PGl_FMuMok>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 08 Sep 2018 06:36:14 -0000

> On 8 Sep 2018, at 1:14 am, Lee Howard <lee@asgard.org> wrote:
>=20
> On 09/07/2018 10:12 AM, Ole Troan wrote:
>> Lee,
>>=20
>> So not accepting Mark=E2=80=99s advice is just a trade-off between =
customer support calls and updating implementations to do local address =
synthesizing?
>> I would certainly make a few phone calls to my ISP if they forced my =
to use their DNS recursive resolvers.
>=20
> Network operators don't generally have the option of updating =
implementations to do local address synthesizing. That's an OS decision.

Operators can advertise DS-Lite, MAP-E, and MAP-T simultaneously while =
still doing DNS64.  Customers are not then stuck with DNS64.

> Fred pointed to the Pref64 draft, which provides part of Mark's =
suggestion. I don't know whether OS vendors will listen to it, and I =
don't know how many devices would get left behind even if they do =
provide updates.
>=20
> Good luck with those calls. If my choice as an operator is to lose =
money providing IPv4 or lose money on support calls, I'm going with the =
method that loses the least money. If I can charge for IPv4 addresses =
(is that even possible in mobile networks?) maybe I'll offer that option =
instead.
>=20
> We all agree that server operators should deploy IPv6, right? There's =
no doubt that it's Best Current Practice.
> One of the reasons it's a Best Current Practice is that if they are =
using DNSSEC, there are interoperability problems with IPv4, =
specifically in some transition mechanisms.
>=20
> Trying to develop alternative mechanisms and insisting network =
operators deploy those instead is wishful thinking and ignores the =
deployed Internet. The network operators have deployed IPv6: the content =
providers must, too, or risk problems. We can provide operational =
guidance about those potential problems.

The best operational guidance we can give about DNS64 is make it =
HISTORIC.  It
is a protocol that should not see new deployments.

A lot of this is the IETF=E2=80=99s fault by not saying "Enough is =
enough" when it comes
to IPv4AAS mechanisms soon enough despite the incremental cost of each =
of them
being miniscule.

> Lee
>=20

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Sun Sep  9 18:59:17 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 979FE130E19 for <v6ops@ietfa.amsl.com>; Sun,  9 Sep 2018 18:59:14 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 u6ZNIY0yyI6V for <v6ops@ietfa.amsl.com>; Sun,  9 Sep 2018 18:59:11 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 D9EBD130E18 for <v6ops@ietf.org>; Sun,  9 Sep 2018 18:59:10 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id f17-v6so13364291qkh.4 for <v6ops@ietf.org>; Sun, 09 Sep 2018 18:59:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tPUQccsywPLcMjwNPt5xY5EMSHrx+/MQxjL3ohNaWjM=; b=feWnVNPXxgHZ3siTvMnevdwy56RFjYi10x7GfQHaIp0pNoe/xQA4dXPceBZGxPSSJR UUA8LVf8Gqghh44MG5SPas8y9oddQVxLwO80scoDvvIOkde7p97aedOkmFU90jlAlaGA jiAAz2dCvNS0oJZ5E/BZr4DjhiIIxjcZks1iic4Kj1032fQT1HW1v5U2h83EOnx662tL l/+HG9GII477mhlH+6B4bABDHheZBlO3oCuWEhwOywVQ2PUvoMhv340/FZ7FoqDgPodG IXCCfbKxA8jl5ugNefq6vMyg1aj1evSEcLdWpzSltjE4n7id8cV9QCT+djJV+Dm/5uHw cdzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tPUQccsywPLcMjwNPt5xY5EMSHrx+/MQxjL3ohNaWjM=; b=qhXovYZkIRD/zwd2T7Pn2aWQQkCTYpZuiRHP8x1YktbwvWkOGcbdJZnQ18mtAsU+hq D6DBgGYHxkhhvIJENwdm9VQnWbjAkS5CMFdOazHHK75OtUCl44C7HRE9ppURq91BDlLo Xhhi16ILnjr8pZbrJ6gZbWU5IuF9Ky8gyZMIn5knDq32kWBBWyzl94KdMSOe6rzx4MG2 8lAQrLE0O3vJb/WCwJ3v6me6unU/Fwa4kB+VdG1hdKktp9xJlqf3J2jS2bKhQCmsfcBX LA7f/U5Q3SJ073S8jwJ//T06b7FSrt3tCMerle5C/ZFpt9pjL55ueE2RVZGsRWQynlEe AQNA==
X-Gm-Message-State: APzg51AQohbnt6qeCy6aFsfts3p0TsLLucukvYC6OqiFnmFGK6oy70rm XD53bHDvHDkc+4C9ju3gkhtP0+E7CSDjNBUrY6g=
X-Google-Smtp-Source: ANB0VdbimvF13Pq8rytxtdafdkbwT5uhweAblwmUHui4qFq9A+cnop1stYU9XFODROyUvajGpry7VFYNlwKFC7IywSE=
X-Received: by 2002:a37:12ce:: with SMTP id 75-v6mr13095794qks.319.1536544749914;  Sun, 09 Sep 2018 18:59:09 -0700 (PDT)
MIME-Version: 1.0
References: <CAAObRXLe35KoONVsSO_oU+SRhMzMrKRE_SU-QNf2pGHYKpUrxA@mail.gmail.com> <1ba1193b-f1ca-b51b-ebaa-d0e8312cc363@gmail.com>
In-Reply-To: <1ba1193b-f1ca-b51b-ebaa-d0e8312cc363@gmail.com>
From: Davey Song <songlinjian@gmail.com>
Date: Mon, 10 Sep 2018 09:58:59 +0800
Message-ID: <CAAObRXJPcjbpReLQAMv+QWtYmWmM-vVqKqxb-2XeWM0sZwm3vw@mail.gmail.com>
To: alexandre.petrescu@gmail.com
Cc: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000000ee505757ab440"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0k0cwumt3chMVBe8JkMBI6AQq0Y>
Subject: Re: [v6ops] How my Android phone got assigned with IPv6 address via 4G LTE?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 01:59:14 -0000

--000000000000000ee505757ab440
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Alex, from this thread I filled the gap of IPv6 LTE provisioning in my
mind. Thank you all.

Davey

On Fri, 7 Sep 2018 at 21:20, Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 27/08/2018 =C3=A0 02:50, Davey Song a =C3=A9crit :
> > Hi folks,
> >
> > Recently the IPv6 4G LTE of China moible and China Telecom is working.
> > And I got the address information on my android phone, like :
> >
> > China Mobile : 2409:8900:8a10:6dof:4177:9599:de56:7092
> > China Telecom: 240e:ff:b10a:54a9:b5f7:5e4c:2f2d:9847
>
> Excellent.  My question is whether when this address is assigned on
> android you can ping6 some IPv6 site (maybe ping6 ipv6.google.com)?
>
> Because there are some cellular operators that do assign IPv6 addresses
> to android and other phones but dont provide IPv6 connectivity to the
> Internet (can not ping6).
>
> > My question is : How these IPv6 addresses are assigned to my pohone and
> > what type of address they are?
>
> That can be answered definitely only by trying.  It's good to know the
> specs too, but better try it to know for sure.
>
> There are three main 'native' ways into which that address could have
> been allocated to your android:
> - maybe the android did a DHCPv6 request and the operator responded with
>    a DHCPv6 acknowledgment containing the address.
> - maybe the layer 2 protocol (IPv6CP - stands for Control Protocol, or
>    ppp) negotiated an Interface ID of 64bit length, and then the router
>    in the network sent a Router Advertisement, and then the android
>    formed an address with the prefix in the RA and the IID negotiated
>    earlier.
> - maybe the layer 2 protocol negotiated the full IPv6 address rather
>    than just the Interface ID (and there was no RA from a
>    Router prior to forming an IPv6 address).
>
> Then there are more non-native ways, like 'hacks' that are implemented
> by an application that is specific: it can form an IPv6 address by
> requesting it first with an IPv4 proprietary protocol.
>
> All these I have seen in deployed cellular networks.
>
> You can try it yourself by doing the following:
> - contact the phone manufacturer to obtain key to be able to log in root
>    in the smartphone.  They are legally obliged to allow you to.  Many
>    already do (I know Huawei, SOny and and few others).
> - log in the android and learn how to ls, and certainly not rm -rf /.
> - then cross-compile a tshark or a tcpdump (it is a packet capture
>    tool).
> - run the packet dump tool to record which packets circulate (RA, DHCP,
>    etc.)
> - download the packet dumps to your laptop to see it on nice GUI with
>    wireshark.
> - identify whether android used pppd, or qmicli or mmicli in order to
> make the connection.  pppd is available for many  modems, qmicli is
> specific to Qualcomm, and mmicli to others.  Other modem manufacturers
> may have other tools.
> - use '-v' options to these tools.
> - look at the /var/log/messages
> - kill all ConnectionManager or NetworkManager.
> - there is a certain ability needed to be able to capture before an
> interface is put up, because normally capturing happens while the
> interface is already up.  But when it is already up you already obtained
> the address.
> - there is a need to capture more than just IP datagrams, but link-layer
> datagrams.
>
>
>
> > They looks no EUI-64 address, without
> > FFFE in the middle of low 64 bits.
>
> Yes, looks so.
>
> Forming 64bit Interface IDs that dont have FF:FE in the middle can
> happens modernly by recent androids (recent linuces, in fact).  Either
> the linux formed such a non-FFFE IID, or that IID was formed by a server
> and delivered to android by the layer2 protocol
>
> > And it can not be done by DHCPv6
> > because I heard Android does not support DHCPv6, right?
>
> Android is an Operating System.  It uses a modified linux kernel.  When
> people say android does not implement DHCPv6 it is because the
> manufacturer of that phone chose to put an Android that has no DHCPv6
> client.  It is however straightforward to put yourself (or your
> operator) a DHCPv6 client on an Android.  We did it numerous times with
> many (5?) DHCPv6 clients.  Android supports them all ok.
>
> Also, this is based on the remark that the manufacturer of that phone
> puts the android and that manufacturer has a hard time to remove the
> SLAAC (a competitor to DHCPv6) from Android: SLAAC is built into the
> linux part of Android.  And Google _and_ Android _and_ phone
> manufacturer dont have enough capacity or will to _remove_ SLAAC from
> linux kernel, because it is not their design.
>
> In that sense: yes, DHCPv6 is _not_ in Android (could easily be added),
> and SLAAC _is_ in Android (could hardly be removed).
>
> > I'm not sure
> > how my LTE provider provisioning IPv6 address.
>
> In the LTE provider's network there is much more private and proprietary
> mechanisms to provision the IPv6 addresses.  What the end user sees is
> only the tip of the iceberg: the RA.
>
> Some of the mechanisms are described in some RFCs that relate to Proxy
> Mobile IP.  I am not saying that's what's used at your operator, but
> these texts approach the most to what's used.
>
> > So The only possbile way
> > is SLAAC+private address=EF=BC=9F
>
> What you shown above is not a private address.  They both start with
> 24-something.  The 'private' addresses in IPv6 are called 'ULA's (for
> Unique Local Addresses) and they start with fd-something or fc-something.
>
> And no, it is not the only possible way to be SLAAC.  I would even say
> that, judged by the excitement, this might be the first time these
> operators give IPv6 to end-users, and I would say it is rather a
> proprietary form of IPv6CP.  But I may be wrong in case these operators
> acquired very recent state-of-the-art hardware and learned from recent
> experience of operators who went with SLAAC.
>
> Alex
>
> >
> > Anyone who can help me out on this question? Or share your experience o=
n
> > how the mobile ISP commonly provison their users. Thanks.
>
> >
> > Best regards,
> > Davey
> >
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--000000000000000ee505757ab440
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Alex, from this thread I filled the ga=
p of IPv6 LTE provisioning in my mind. Thank you all.</div><div dir=3D"ltr"=
><br></div><div>Davey</div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr">On Fri, 7 Sep 2018 at 21:20, Alexandre Petrescu &lt;<a href=3D"mailto=
:alexandre.petrescu@gmail.com">alexandre.petrescu@gmail.com</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Le 27/08/2018 =C3=A0 02:50, Davey Song a =C3=A9crit=C2=A0:<br>
&gt; Hi folks,<br>
&gt; <br>
&gt; Recently the IPv6 4G LTE of China moible and China Telecom is working.=
 <br>
&gt; And I got the address information on my android phone, like :<br>
&gt; <br>
&gt; China Mobile : 2409:8900:8a10:6dof:4177:9599:de56:7092<br>
&gt; China Telecom: 240e:ff:b10a:54a9:b5f7:5e4c:2f2d:9847<br>
<br>
Excellent.=C2=A0 My question is whether when this address is assigned on <b=
r>
android you can ping6 some IPv6 site (maybe ping6 <a href=3D"http://ipv6.go=
ogle.com" rel=3D"noreferrer" target=3D"_blank">ipv6.google.com</a>)?<br>
<br>
Because there are some cellular operators that do assign IPv6 addresses <br=
>
to android and other phones but dont provide IPv6 connectivity to the <br>
Internet (can not ping6).<br>
<br>
&gt; My question is : How these IPv6 addresses are assigned to my pohone an=
d <br>
&gt; what type of address they are?<br>
<br>
That can be answered definitely only by trying.=C2=A0 It&#39;s good to know=
 the <br>
specs too, but better try it to know for sure.<br>
<br>
There are three main &#39;native&#39; ways into which that address could ha=
ve <br>
been allocated to your android:<br>
- maybe the android did a DHCPv6 request and the operator responded with<br=
>
=C2=A0 =C2=A0a DHCPv6 acknowledgment containing the address.<br>
- maybe the layer 2 protocol (IPv6CP - stands for Control Protocol, or<br>
=C2=A0 =C2=A0ppp) negotiated an Interface ID of 64bit length, and then the =
router<br>
=C2=A0 =C2=A0in the network sent a Router Advertisement, and then the andro=
id<br>
=C2=A0 =C2=A0formed an address with the prefix in the RA and the IID negoti=
ated<br>
=C2=A0 =C2=A0earlier.<br>
- maybe the layer 2 protocol negotiated the full IPv6 address rather<br>
=C2=A0 =C2=A0than just the Interface ID (and there was no RA from a<br>
=C2=A0 =C2=A0Router prior to forming an IPv6 address).<br>
<br>
Then there are more non-native ways, like &#39;hacks&#39; that are implemen=
ted <br>
by an application that is specific: it can form an IPv6 address by <br>
requesting it first with an IPv4 proprietary protocol.<br>
<br>
All these I have seen in deployed cellular networks.<br>
<br>
You can try it yourself by doing the following:<br>
- contact the phone manufacturer to obtain key to be able to log in root<br=
>
=C2=A0 =C2=A0in the smartphone.=C2=A0 They are legally obliged to allow you=
 to.=C2=A0 Many<br>
=C2=A0 =C2=A0already do (I know Huawei, SOny and and few others).<br>
- log in the android and learn how to ls, and certainly not rm -rf /.<br>
- then cross-compile a tshark or a tcpdump (it is a packet capture<br>
=C2=A0 =C2=A0tool).<br>
- run the packet dump tool to record which packets circulate (RA, DHCP,<br>
=C2=A0 =C2=A0etc.)<br>
- download the packet dumps to your laptop to see it on nice GUI with<br>
=C2=A0 =C2=A0wireshark.<br>
- identify whether android used pppd, or qmicli or mmicli in order to <br>
make the connection.=C2=A0 pppd is available for many=C2=A0 modems, qmicli =
is <br>
specific to Qualcomm, and mmicli to others.=C2=A0 Other modem manufacturers=
 <br>
may have other tools.<br>
- use &#39;-v&#39; options to these tools.<br>
- look at the /var/log/messages<br>
- kill all ConnectionManager or NetworkManager.<br>
- there is a certain ability needed to be able to capture before an <br>
interface is put up, because normally capturing happens while the <br>
interface is already up.=C2=A0 But when it is already up you already obtain=
ed <br>
the address.<br>
- there is a need to capture more than just IP datagrams, but link-layer <b=
r>
datagrams.<br>
<br>
<br>
<br>
&gt; They looks no EUI-64 address, without <br>
&gt; FFFE in the middle of low 64 bits.<br>
<br>
Yes, looks so.<br>
<br>
Forming 64bit Interface IDs that dont have FF:FE in the middle can <br>
happens modernly by recent androids (recent linuces, in fact).=C2=A0 Either=
 <br>
the linux formed such a non-FFFE IID, or that IID was formed by a server <b=
r>
and delivered to android by the layer2 protocol<br>
<br>
&gt; And it can not be done by DHCPv6 <br>
&gt; because I heard Android does not support DHCPv6, right?<br>
<br>
Android is an Operating System.=C2=A0 It uses a modified linux kernel.=C2=
=A0 When <br>
people say android does not implement DHCPv6 it is because the <br>
manufacturer of that phone chose to put an Android that has no DHCPv6 <br>
client.=C2=A0 It is however straightforward to put yourself (or your <br>
operator) a DHCPv6 client on an Android.=C2=A0 We did it numerous times wit=
h <br>
many (5?) DHCPv6 clients.=C2=A0 Android supports them all ok.<br>
<br>
Also, this is based on the remark that the manufacturer of that phone <br>
puts the android and that manufacturer has a hard time to remove the <br>
SLAAC (a competitor to DHCPv6) from Android: SLAAC is built into the <br>
linux part of Android.=C2=A0 And Google _and_ Android _and_ phone <br>
manufacturer dont have enough capacity or will to _remove_ SLAAC from <br>
linux kernel, because it is not their design.<br>
<br>
In that sense: yes, DHCPv6 is _not_ in Android (could easily be added), <br=
>
and SLAAC _is_ in Android (could hardly be removed).<br>
<br>
&gt; I&#39;m not sure <br>
&gt; how my LTE provider provisioning IPv6 address.<br>
<br>
In the LTE provider&#39;s network there is much more private and proprietar=
y <br>
mechanisms to provision the IPv6 addresses.=C2=A0 What the end user sees is=
 <br>
only the tip of the iceberg: the RA.<br>
<br>
Some of the mechanisms are described in some RFCs that relate to Proxy <br>
Mobile IP.=C2=A0 I am not saying that&#39;s what&#39;s used at your operato=
r, but <br>
these texts approach the most to what&#39;s used.<br>
<br>
&gt; So The only possbile way <br>
&gt; is SLAAC+private address=EF=BC=9F<br>
<br>
What you shown above is not a private address.=C2=A0 They both start with <=
br>
24-something.=C2=A0 The &#39;private&#39; addresses in IPv6 are called &#39=
;ULA&#39;s (for <br>
Unique Local Addresses) and they start with fd-something or fc-something.<b=
r>
<br>
And no, it is not the only possible way to be SLAAC.=C2=A0 I would even say=
 <br>
that, judged by the excitement, this might be the first time these <br>
operators give IPv6 to end-users, and I would say it is rather a <br>
proprietary form of IPv6CP.=C2=A0 But I may be wrong in case these operator=
s <br>
acquired very recent state-of-the-art hardware and learned from recent <br>
experience of operators who went with SLAAC.<br>
<br>
Alex<br>
<br>
&gt; <br>
&gt; Anyone who can help me out on this question? Or share your experience =
on <br>
&gt; how the mobile ISP commonly provison their users. Thanks.<br>
<br>
&gt; <br>
&gt; Best regards,<br>
&gt; Davey<br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
&gt; <br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div>

--000000000000000ee505757ab440--


From nobody Mon Sep 10 07:25:14 2018
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C22128CF2 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 07:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 GikhqzuHkKVc for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 07:25:11 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 56E83128C65 for <v6ops@ietf.org>; Mon, 10 Sep 2018 07:25:11 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w8AEOfdn007589 for <v6ops@ietf.org>; Mon, 10 Sep 2018 07:25:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=aqUIFPM1dEBFi/Tiiq1hYIV9R3pASSOEzN4gjV1iyxM=; b=2ATQsN69bNLtupDg4O3JO5mjSBKIZ04y7zm5KMIHr5jLf/lkL9kcUAZvJ7iqmnii6KQU DoBxoOh+stEPOFuvutaFzKGp06P1V89N/iRU6u7j488Kw4RJxOavTv303PqVq3XGHiWj RFZ4ALFmSNmtd4qKUcEcVB5lgo6yf1BvdjgefkVIdN6WHq02luIkdo4Nj3nQGKjfXJS9 M9V6wo+pgcAazsd2MPI2sfy+SpXsnr3zbEW4Y3NKGAEBbmqyCv1W3g9eXxBPMJpDjtV1 tRJNminiQGNOOqEUfz1I9JGbTIOpBOOQ2G5WBgN9BSJ0lbHmmrVkruo6fTFZ1LUhrRyf cA== 
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp0019.outbound.protection.outlook.com [216.32.180.19]) by mx0b-00273201.pphosted.com with ESMTP id 2mdt6r00k6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <v6ops@ietf.org>; Mon, 10 Sep 2018 07:25:10 -0700
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by CO1PR05MB394.namprd05.prod.outlook.com (10.141.75.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.1143.11; Mon, 10 Sep 2018 14:25:08 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com ([fe80::990e:3cb2:ad57:cd42]) by CO1PR05MB443.namprd05.prod.outlook.com ([fe80::990e:3cb2:ad57:cd42%18]) with mapi id 15.20.1101.016; Mon, 10 Sep 2018 14:25:08 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: draft-jaeggli-v6ops-indefensible-nd
Thread-Index: AdRJEhJUITkGHPnURMm4CycU7Aa+VQ==
Date: Mon, 10 Sep 2018 14:25:08 +0000
Message-ID: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO1PR05MB394; 6:HykHDm3QqJp5tR4jW988mp3edHD8dHK+KeLt6V3dQuNh1jy+ZtuDE2MCJmYvWYDAN5pz0IlYiU2deHKPmgY1W7uNUVI+dzIcY2OkYaDgfT9PluAbLO7OO+GmrwqVgWsG1MBexOG0shg6wGLY30kTWjFL9FDSv7+ZLge1FczeCvILm5jCZx1jj3V6IngLyh3txZoNh3BHQYLGwIjLPJmYoXesglZfhvQgjscJDKrQFosZQeECmlYHGVbuhfljV1ldFo5ZuAVa64ykG94OgTRkaUDHkHVUmXKW/odlJApAelUWlpLSs/V0yFF2LYs2W4HN4yk+p5maVUbpXH2Q334+648gNeiMpvMPiHdws5i4CV22T7jQ/y1lzomT7a17oOgj5q4SV9wLQfDpB+2mnuOAh84AGie8ZtepReTcFfH5ntm3rsSW8c6MRZ7Vtcn9AXN7DA9yRy1iGon3UWhtlNWWUg==; 5:xKHUC4o+TT+b4hy6HiCrqQhSK9w06mVI0syfoHApR7NZnp9nhcOU8ag+N5FfZJBe+NjxBfPIBOfjCnVenmjvFAMtzmCJeMJdAWHI6xQHTYxRKvZrvymjDTYwOomolf+tkKYxINQXaOgbD9s/4EC0yZtIDKMGrPTEsBWbEvD/Ac8=; 7:OwtohuUMaUgFRnFIndi2g9YWRK0FFHAUNbE329vZ0032iYSkga4a1lm9YZBE+MXwL+7OT4wkgARxMirUQEZ3BQ31C3QlRrQox8dDG9C7EgaPDY2U3M4hgsxpJznkiarJ8N5hluCc9ukVaWp3A5pauN4KCabyCX2bIOLMPA0aRHVn5A+V/O26q6MIpQHlGAxkVhaiwh1feE1Mvq0L7+gOpYusxehDG/y+4rFhm36XhAhhBgx/qbruphjhGFQiMoq7
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 3004096c-4579-45c6-90cc-08d617293610
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:CO1PR05MB394; 
x-ms-traffictypediagnostic: CO1PR05MB394:
x-microsoft-antispam-prvs: <CO1PR05MB3941EC4BFFD7ECE225682E1AE050@CO1PR05MB394.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(3231311)(944501410)(52105095)(10201501046)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699050); SRVR:CO1PR05MB394; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB394; 
x-forefront-prvs: 07915F544A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(136003)(39860400002)(346002)(366004)(396003)(189003)(199004)(5660300001)(478600001)(99286004)(106356001)(26005)(8676002)(186003)(305945005)(66066001)(74316002)(14454004)(558084003)(7736002)(316002)(8936002)(33656002)(81156014)(81166006)(2351001)(102836004)(7696005)(6506007)(68736007)(2906002)(97736004)(105586002)(6916009)(9686003)(3846002)(6116002)(486006)(53936002)(5640700003)(25786009)(55016002)(6436002)(476003)(5250100002)(2501003)(2900100001)(256004)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB394; H:CO1PR05MB443.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: kx7f9N58y0Se2CEALegOnQc6RVKQ1VCWlsIgKdA/K3gRHnxIZzMg7A2tBan7kHmj9Lbx0ms7z+pj/ZC7QODihKlJdzBXvzW3ilGgRET742N1Roh17E7K6zK3ya9mIifFsRo5uD5ri5WwOHvR6P7LM2BpIC7uQbO8KZGh2GEPmoD5Vqna2pNWYMAQDBoQ9Ar5f1QCcPbD4TTnlYeB7Gx34ef4WgZJrRMEs4VE0IS5C52r5blAVlMUB2e+N6uLUUYiWpk2QQeRUlo7VgaQomCDmi9CLZ8oq9q1stzkMywLDkT0cbw8ZzNETv+2Tpp1VAjBsC5B18s0xHbm5jkHmXnG9+JsZY7SZ7Jwswsil5460ss=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 3004096c-4579-45c6-90cc-08d617293610
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Sep 2018 14:25:08.6407 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB394
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-10_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=425 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809100148
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GSwKte4QSqMBCHtLl1HEowJ0M1k>
Subject: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 14:25:13 -0000

Folks,

Each week between now and IETF 103, we will review and discuss one draft wi=
th an eye towards progressing it.

This week, please review and comment on draft-jaeggli-v6ops-indefensible-nd=
.

                                      Fred and Ron


From nobody Mon Sep 10 11:10:56 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D64BD130FB5; Mon, 10 Sep 2018 11:10:47 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 CvJeIgqtBGZV; Mon, 10 Sep 2018 11:10:46 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 EB636130F91; Mon, 10 Sep 2018 11:10:45 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id v198-v6so24282049oif.9; Mon, 10 Sep 2018 11:10:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Xt7HoS2zVtwcDOXC+u2wjZJC47EF6+Mo1p7GfbtSujE=; b=UfRPpt8YCaDsF3vpI68UGYrKgzUHKGxlQxzQoMW1mQ6qGRpEGY+RiiaV34ZOXm9/re T3FfP4zXFtX/dyZv5ullMVdMVzJRDUEM0SFGtMaS0vjIlsAaDVkb13i7xeOFHG7cVmIL 7iNx2kWvAKliHZmdPQdllDNC69PVtEEMu6cJNaaFqi2yIr3It7zW1ndQHSvegA0N4pUV Hr4Uwbn8jmfcyINdX4Kd9koGRTna4tQyrVMCLAvHqVbBYXIbZyWVK3OU5zF6FcNEyDzA qDpbjBiDpqOzBqH14dj/yiZNW439Be+V4lEKAIDSLImqjI1udIqykIISC/VRin5Hd1LK czrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Xt7HoS2zVtwcDOXC+u2wjZJC47EF6+Mo1p7GfbtSujE=; b=RGEpLJGv/GzMuXilrp7OHnCpBP+4ynP0DnGdkJM3+8LNrz7zMDBCsIOdkbiK9VflbS Gk5Kh7tWnxVqnc9SpEGKz6fPaXTpLv8rzKhPB0IXThRi+SkeAkgEnvTEW/kKpXXXBxsc 0gbYMnyd4QKQgtn1ZNSkw8VcoNLlwIktfamFyFRScmDrT8bT51Q4LK9LivR5gPHfjrLK gOdMBQ/ehcYh9SX/kKDuh/7yxDUj1fLHxgp/aiBC31KrFh+I9dVuZ1oux5UbCskVJoP5 51ScwVtZrwZwSZDhW1PX7YIe54R35xlTn2whQIyXEDeBVTQk3F1JxE4yCi1/ugJg1PNg YHSw==
X-Gm-Message-State: APzg51AukUQzMxtacZG/xYicY35cT7PWGbUiT8LdQBnwPz1h7tBJFdmI kgNX3+xFh0cU3ezkq/Ppp5c=
X-Google-Smtp-Source: ANB0VdYKQsXhQg82BynI59o57E0h2/nZKMJCp9GHsnviZ+yHZH+0VwuYdO6u2y0RNpD2za+9RDxr3A==
X-Received: by 2002:aca:ce85:: with SMTP id e127-v6mr23437265oig.169.1536603045306;  Mon, 10 Sep 2018 11:10:45 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::106d? ([2600:8802:5600:1546::106d]) by smtp.gmail.com with ESMTPSA id f144-v6sm30362645oib.39.2018.09.10.11.10.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Sep 2018 11:10:44 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1FF037D6-1FBD-4BDE-A5A5-1E111FFE9BC4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 10 Sep 2018 11:10:42 -0700
In-Reply-To: <20180907183013.GA11393@Space.Net>
Cc: Ole Troan <otroan@employees.org>, draft-ietf-doh-dns-over-https.all@ietf.org, v6ops@ietf.org
To: Gert Doering <gert@space.net>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-VyGIpsTgk3SLENyM88w9_Gphd8>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 18:10:54 -0000

--Apple-Mail=_1FF037D6-1FBD-4BDE-A5A5-1E111FFE9BC4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Sep 7, 2018, at 11:30 AM, Gert Doering <gert@space.net> wrote:
>=20
> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>=20
>> Are you saying that there are hundreds of millions of users on IPv6 =
only networks with NAT64/DNS64 their only exit to the IPv4 Internet?
>> Where are these users? Cause I wasn???t aware of any general =
deployments of that to end-users.
>=20
> T-Mobile USA...?

Indeed. My telephone has only had an IPv6 address on its LTE interface =
for quite some time now.

=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_1FF037D6-1FBD-4BDE-A5A5-1E111FFE9BC4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluWs6IACgkQEhdRnd2G
P+CflhAAx4Sfg82tTBl1Lg8P19xVrOBbVrZFngcNgvU2DbVoNKIZ3RAOY1woxoPT
RZRZDGYhB+vGQLiz7Ql+OSz+p9Tn3KAgM10FIgP0aBXdwBescu7KNq+18ZLj1WXd
B4d6qPv7MY4nVnWerSmjf+yVhp6rVu1Eue5puXrzeOjPLULD+8iHR+vX7MDTOVsv
uN7Tf1EmnoC9sRf18XCIfeXsIqfFXlkrwi4/NjZQTVLk94PgE/qqG8rCN/TqTrEN
url8Ia+0IzPkk8SR+x/c/4Yjg08dfMKDGZyUsg/zAdQfawQrwNEojH/fAUGOJHcZ
JFgfQeFZwRj9sG/0L6uO5ukOHVojiliuuR1Md66hsLHHtfiE29laVX+BG8GONpE7
1pwPnllaLtZf+eDA0FIV2bJnllyshJ7MiuFuUUnlzHp7PMqFQUn/t99LQo1WRbp3
V4UbNZ8NYXFVKbt2/sg6pt6/qUPlPWmUfqYz83oQKSqKfvVDfn2jugv3C5F9Evg3
+v2Zfv2l9JT57yvn7WDqWLMr/C3cGCpBaf1Oy1thI5QGcd0nSdTYQ492BES1gViJ
mhPDpDIoOgiy/217/ovI140uqxNihSLmSKMMsDnUJ+LNgiUIV4zNwccFZxtu0CrS
v1JmtgIS4MAxHHzhxMmroAFgGh062xGdr7yS6Gkl3S5GUKL8vD0=
=m/na
-----END PGP SIGNATURE-----

--Apple-Mail=_1FF037D6-1FBD-4BDE-A5A5-1E111FFE9BC4--


From nobody Mon Sep 10 12:06:36 2018
Return-Path: <lencse@hit.bme.hu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7E6130F7B for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 12:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 3SEPxOMTL6Ii for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 12:06:32 -0700 (PDT)
Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [IPv6:2001:738:2001:4020::2c]) (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 B0F24130F6F for <v6ops@ietf.org>; Mon, 10 Sep 2018 12:06:31 -0700 (PDT)
Received: from [192.168.1.134] (host-79-121-41-144.kabelnet.hu [79.121.41.144]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id w8AJ6Kvd067232 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <v6ops@ietf.org>; Mon, 10 Sep 2018 21:06:25 +0200 (CEST) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-41-144.kabelnet.hu [79.121.41.144] claimed to be [192.168.1.134]
To: v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com>
From: =?UTF-8?Q?Lencse_G=c3=a1bor?= <lencse@hit.bme.hu>
Message-ID: <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu>
Date: Mon, 10 Sep 2018 21:06:15 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com>
Content-Type: multipart/alternative; boundary="------------0E4F43A892F2D09F2634A334"
X-Virus-Scanned: clamav-milter 0.100.1 at frogstar.hit.bme.hu
X-Virus-Status: Clean
Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.41.144; helo=[192.168.1.134]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; 
X-DCC--Metrics: frogstar.hit.bme.hu; whitelist
X-Scanned-By: MIMEDefang 2.79 on 152.66.248.44
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/qAZ_x8nPyz4DiDK3FBRA8rUKDWY>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 19:06:35 -0000

This is a multi-part message in MIME format.
--------------0E4F43A892F2D09F2634A334
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Dear Fred,

I have just received an e-mail from my head of department with a list of 
topics for our students from a leading Hungarian ISP. One of them is: 
"IPv6-only mobile networks". :-)
As for IPv6 transition technologies to be considered, they mention only 
NAT64, DNS64 and 464XLAT (in this order).

Of course, I do not want to conclude from this single event that they 
would be better than any other IPv6 transition technologies, but I 
believe that it is still worth using them for new deployments.

BTW.: As for the advantages and disadvantages of the different IPv6 
transition technologies for providing IPv4aaS (namely: 464XLAT, DS-Lite, 
lw4o6, MAP-E, MAP-T) we have put together a table for crowd sourcing 
with Lee, Jordi and Richard. Unfortunately, it has not yet been 
finished, because I was too busy in this Summer, but I hope to send the 
link of the google spreadsheet to the v6ops mailing list within a few days.

However, I think that these IPv4aaS technologies may NOT substitute 
NAT64+DNS64 in a communication scenario when an IPv6 only client needs 
to communication with an IPv4 only server. Under an IPv6 only client, I 
mean a client, which does not have an IPv4 address or even IPv4 protocol 
stack. Why should we force anyone to use private IPv4 addresses, who 
does not want to do so?

I think, NAT64+DNS64 is the most appropriate solution for this 
communication scenario and draft-byrne-v6ops-dnssecaaaa is a good 
solution for the conflict of DNS64 and DNSSEC, therefore, I definitely 
support it.

Best regards,

Gábor




9/10/2018 8:10 PM keltezéssel, Fred Baker írta:
>
>> On Sep 7, 2018, at 11:30 AM, Gert Doering <gert@space.net> wrote:
>>
>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>>
>>> Are you saying that there are hundreds of millions of users on IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 Internet?
>>> Where are these users? Cause I wasn???t aware of any general deployments of that to end-users.
>> T-Mobile USA...?
> Indeed. My telephone has only had an IPv6 address on its LTE interface for quite some time now.
>
> --------------------------------------------------------------------------------
> Victorious warriors win first and then go to war,
> Defeated warriors go to war first and then seek to win.
>       Sun Tzu
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--------------0E4F43A892F2D09F2634A334
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear Fred,<br>
    <br>
    I have just received an e-mail from my head of department with a
    list of topics for our students from a leading Hungarian ISP. One of
    them is: "IPv6-only mobile networks". :-)<br>
    As for IPv6 transition technologies to be considered, they mention
    only NAT64, DNS64 and 464XLAT (in this order).<br>
    <br>
    Of course, I do not want to conclude from this single event that
    they would be better than any other IPv6 transition technologies,
    but I believe that it is still worth using them for new deployments.
    <br>
    <br>
    BTW.: As for the advantages and disadvantages of the different IPv6
    transition technologies for providing IPv4aaS (namely: 464XLAT,
    DS-Lite, lw4o6, MAP-E, MAP-T) we have put together a table for crowd
    sourcing with Lee, Jordi and Richard. Unfortunately, it has not yet
    been finished, because I was too busy in this Summer, but I hope to
    send the link of the google spreadsheet to the v6ops mailing list
    within a few days.<br>
    <br>
    However, I think that these IPv4aaS technologies may NOT substitute
    NAT64+DNS64 in a communication scenario when an IPv6 only client
    needs to communication with an IPv4 only server. Under an IPv6 only
    client, I mean a client, which does not have an IPv4 address or even
    IPv4 protocol stack. Why should we force anyone to use private IPv4
    addresses, who does not want to do so?<br>
    <br>
    I think, NAT64+DNS64 is the most appropriate solution for this
    communication scenario and draft-byrne-v6ops-dnssecaaaa is a good
    solution for the conflict of DNS64 and DNSSEC, therefore, I
    definitely support it.<br>
    <br>
    Best regards,<br>
    <br>
    Gábor<br>
    <br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">9/10/2018 8:10 PM keltezéssel, Fred
      Baker írta:<br>
    </div>
    <blockquote
      cite="mid:A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com"
      type="cite">
      <pre wrap="">

</pre>
      <blockquote type="cite">
        <pre wrap="">On Sep 7, 2018, at 11:30 AM, Gert Doering <a class="moz-txt-link-rfc2396E" href="mailto:gert@space.net">&lt;gert@space.net&gt;</a> wrote:

On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.

Are you saying that there are hundreds of millions of users on IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 Internet?
Where are these users? Cause I wasn???t aware of any general deployments of that to end-users.
</pre>
        </blockquote>
        <pre wrap="">
T-Mobile USA...?
</pre>
      </blockquote>
      <pre wrap="">
Indeed. My telephone has only had an IPv6 address on its LTE interface for quite some time now.

--------------------------------------------------------------------------------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu

</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------0E4F43A892F2D09F2634A334--


From nobody Mon Sep 10 13:23:28 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A71130DF6 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 13:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 dedLkERCWwUq for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 13:23:25 -0700 (PDT)
Received: from atl4mhob10.registeredsite.com (atl4mhob10.registeredsite.com [209.17.115.48]) (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 838A3130DDE for <v6ops@ietf.org>; Mon, 10 Sep 2018 13:23:25 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob10.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8AKNMKM010157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Mon, 10 Sep 2018 16:23:22 -0400
Received: (qmail 7598 invoked by uid 0); 10 Sep 2018 20:23:22 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 10 Sep 2018 20:23:22 -0000
To: v6ops@ietf.org
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <41e7e300-e446-0147-2e38-30dab732f074@asgard.org>
Date: Mon, 10 Sep 2018 16:23:21 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Gsa3F4ROjn82ov5UKMfmaj-GBVc>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 20:23:27 -0000

Should there be some mention of SeND (rfc3971), and the several SAVI 
documents? Maybe rc6105 (RA Guard), but that's specific to RA, not ND.

I also know of at least one vendor that allows configuration limiting 
neighbor table cache size, and prioritizing NA timer refresh over new 
discovery.

Operationally, I'd advise logging neighbor table changes, and throwing 
an alert if they exceed some reasonably high threshold. I can't say what 
"reasonable" is; I recently had a home gateway sending 70 RAs per second.

3.4 Firewalls. Is there any scenario where you'd want to allow NDP from 
off-link?  BCP38, don't allow SRC=LLA Link1, DST=GUA Link2, or vice versa.

Theoretically you could limit vulnerability by giving each host a VLAN. 
Or any other L3 segmentation. You could use L2/L3 ACLs to lock down ports.

I'm not sure this document currently provides enough value to advance. 
With the stuff above added in, maybe it consolidates enough advice into 
one place to be useful.

Lee

On 09/10/2018 10:25 AM, Ron Bonica wrote:
> Folks,
>
> Each week between now and IETF 103, we will review and discuss one draft with an eye towards progressing it.
>
> This week, please review and comment on draft-jaeggli-v6ops-indefensible-nd.
>
>                                        Fred and Ron
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Mon Sep 10 13:56:35 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2C9130FA8 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 13:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 A1RcHfcJ_jAy for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 13:56:31 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 EC603130DE1 for <v6ops@ietf.org>; Mon, 10 Sep 2018 13:56:30 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 524993AB03F; Mon, 10 Sep 2018 20:56:30 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id F289616005B; Mon, 10 Sep 2018 20:56:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id BD40B16007D; Mon, 10 Sep 2018 20:56:29 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7njxCDNfskG1; Mon, 10 Sep 2018 20:56:29 +0000 (UTC)
Received: from [172.30.42.88] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 1267316005B; Mon, 10 Sep 2018 20:56:29 +0000 (UTC)
Content-Type: multipart/alternative; boundary=Apple-Mail-4A9C348B-649F-4052-9B5C-D3AA24AD0182
Mime-Version: 1.0 (1.0)
From: Mark Andrews <marka@isc.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu>
Date: Tue, 11 Sep 2018 06:56:26 +1000
Cc: v6ops@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu>
To: =?utf-8?Q?Lencse_G=C3=A1bor?= <lencse@hit.bme.hu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8oR6_t9CdkGRKuTFuenduAyYl7w>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 20:56:33 -0000

--Apple-Mail-4A9C348B-649F-4052-9B5C-D3AA24AD0182
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Well 464XLAT has a IPv4 stack.

You can achieve the same effects as DNS64 in getaddrinfo if you publish the N=
AT64 prefix out side of the DNS.  The problem with DNS64 is that it modifies=
 answers at the wrong place.  Recursive servers really aren=E2=80=99t the co=
rrect place no matter how attractive they seem.=20

Getaddrinfo allows you to get mapped address back. DNS64 is just a different=
 mapped address.


--=20
Mark Andrews

> On 11 Sep 2018, at 05:06, Lencse G=C3=A1bor <lencse@hit.bme.hu> wrote:
>=20
> Dear Fred,
>=20
> I have just received an e-mail from my head of department with a list of t=
opics for our students from a leading Hungarian ISP. One of them is: "IPv6-o=
nly mobile networks". :-)
> As for IPv6 transition technologies to be considered, they mention only NA=
T64, DNS64 and 464XLAT (in this order).
>=20
> Of course, I do not want to conclude from this single event that they woul=
d be better than any other IPv6 transition technologies, but I believe that i=
t is still worth using them for new deployments.=20
>=20
> BTW.: As for the advantages and disadvantages of the different IPv6 transi=
tion technologies for providing IPv4aaS (namely: 464XLAT, DS-Lite, lw4o6, MA=
P-E, MAP-T) we have put together a table for crowd sourcing with Lee, Jordi a=
nd Richard. Unfortunately, it has not yet been finished, because I was too b=
usy in this Summer, but I hope to send the link of the google spreadsheet to=
 the v6ops mailing list within a few days.
>=20
> However, I think that these IPv4aaS technologies may NOT substitute NAT64+=
DNS64 in a communication scenario when an IPv6 only client needs to communic=
ation with an IPv4 only server. Under an IPv6 only client, I mean a client, w=
hich does not have an IPv4 address or even IPv4 protocol stack. Why should w=
e force anyone to use private IPv4 addresses, who does not want to do so?
>=20
> I think, NAT64+DNS64 is the most appropriate solution for this     communi=
cation scenario and draft-byrne-v6ops-dnssecaaaa is a good solution for the c=
onflict of DNS64 and DNSSEC, therefore, I definitely support it.
>=20
> Best regards,
>=20
> G=C3=A1bor
>=20
>=20
>=20
>=20
> 9/10/2018 8:10 PM keltez=C3=A9ssel, Fred Baker =C3=ADrta:
>>>> On Sep 7, 2018, at 11:30 AM, Gert Doering <gert@space.net> wrote:
>>>>=20
>>>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>>>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>>>=20
>>>> Are you saying that there are hundreds of millions of users on IPv6 onl=
y networks with NAT64/DNS64 their only exit to the IPv4 Internet?
>>>> Where are these users? Cause I wasn???t aware of any general deployment=
s of that to end-users.
>>> T-Mobile USA...?
>> Indeed. My telephone has only had an IPv6 address on its LTE interface fo=
r quite some time now.
>>=20
>> -------------------------------------------------------------------------=
-------
>> Victorious warriors win first and then go to war,
>> Defeated warriors go to war first and then seek to win.
>>      Sun Tzu
>>=20
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

--Apple-Mail-4A9C348B-649F-4052-9B5C-D3AA24AD0182
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Well 464XLAT has a IPv4 stack.<div><br></di=
v><div>You can achieve the same effects as DNS64 in getaddrinfo if you publi=
sh the NAT64 prefix out side of the DNS. &nbsp;The problem with DNS64 is tha=
t it modifies answers at the wrong place. &nbsp;Recursive servers really are=
n=E2=80=99t the correct place no matter how attractive they seem.&nbsp;</div=
><div><br></div><div>Getaddrinfo allows you to get mapped address back. DNS6=
4 is just a different mapped address.</div><div><br></div><div><br><div id=3D=
"AppleMailSignature">--&nbsp;<div>Mark Andrews</div></div><div><br>On 11 Sep=
 2018, at 05:06, Lencse G=C3=A1bor &lt;<a href=3D"mailto:lencse@hit.bme.hu">=
lencse@hit.bme.hu</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div=
>
 =20
    <meta content=3D"text/html; charset=3Dwindows-1252" http-equiv=3D"Conten=
t-Type">
 =20
 =20
    Dear Fred,<br>
    <br>
    I have just received an e-mail from my head of department with a
    list of topics for our students from a leading Hungarian ISP. One of
    them is: "IPv6-only mobile networks". :-)<br>
    As for IPv6 transition technologies to be considered, they mention
    only NAT64, DNS64 and 464XLAT (in this order).<br>
    <br>
    Of course, I do not want to conclude from this single event that
    they would be better than any other IPv6 transition technologies,
    but I believe that it is still worth using them for new deployments.
    <br>
    <br>
    BTW.: As for the advantages and disadvantages of the different IPv6
    transition technologies for providing IPv4aaS (namely: 464XLAT,
    DS-Lite, lw4o6, MAP-E, MAP-T) we have put together a table for crowd
    sourcing with Lee, Jordi and Richard. Unfortunately, it has not yet
    been finished, because I was too busy in this Summer, but I hope to
    send the link of the google spreadsheet to the v6ops mailing list
    within a few days.<br>
    <br>
    However, I think that these IPv4aaS technologies may NOT substitute
    NAT64+DNS64 in a communication scenario when an IPv6 only client
    needs to communication with an IPv4 only server. Under an IPv6 only
    client, I mean a client, which does not have an IPv4 address or even
    IPv4 protocol stack. Why should we force anyone to use private IPv4
    addresses, who does not want to do so?<br>
    <br>
    I think, NAT64+DNS64 is the most appropriate solution for this
    communication scenario and draft-byrne-v6ops-dnssecaaaa is a good
    solution for the conflict of DNS64 and DNSSEC, therefore, I
    definitely support it.<br>
    <br>
    Best regards,<br>
    <br>
    G=C3=A1bor<br>
    <br>
    <br>
    <br>
    <br>
    <div class=3D"moz-cite-prefix">9/10/2018 8:10 PM keltez=C3=A9ssel, Fred
      Baker =C3=ADrta:<br>
    </div>
    <blockquote cite=3D"mid:A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com" t=
ype=3D"cite">
      <pre wrap=3D""></pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">On Sep 7, 2018, at 11:30 AM, Gert Doering <a class=3D=
"moz-txt-link-rfc2396E" href=3D"mailto:gert@space.net">&lt;gert@space.net&gt=
;</a> wrote:

On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
</pre>
        <blockquote type=3D"cite">
          <pre wrap=3D"">NAT64 and DNS64 is deployed, and sometimes in chort=
 with 464XLAT.

Are you saying that there are hundreds of millions of users on IPv6 only net=
works with NAT64/DNS64 their only exit to the IPv4 Internet?
Where are these users? Cause I wasn???t aware of any general deployments of t=
hat to end-users.
</pre>
        </blockquote>
        <pre wrap=3D"">T-Mobile USA...?
</pre>
      </blockquote>
      <pre wrap=3D"">Indeed. My telephone has only had an IPv6 address on it=
s LTE interface for quite some time now.

----------------------------------------------------------------------------=
----
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu

</pre>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
v6ops mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:v6ops@ietf.org">v6ops@i=
etf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/list=
info/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>
</pre>
    </blockquote>
    <br>
 =20

</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>v6ops mailing list</span><br><sp=
an><a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mai=
lman/listinfo/v6ops</a></span><br></div></blockquote></div></body></html>=

--Apple-Mail-4A9C348B-649F-4052-9B5C-D3AA24AD0182--


From nobody Mon Sep 10 15:00:07 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8201130FB7 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 15:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 CsLO5ot-MUvY for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 15:00:03 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 BCAE2130FB2 for <v6ops@ietf.org>; Mon, 10 Sep 2018 15:00:03 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 97CE53AB05E; Mon, 10 Sep 2018 22:00:03 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 3887116007F; Mon, 10 Sep 2018 22:00:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 1C09116007E; Mon, 10 Sep 2018 22:00:02 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jaaTazrhbxAr; Mon, 10 Sep 2018 22:00:01 +0000 (UTC)
Received: from beetledviscorg7.home.lan (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 369DC16005B; Mon, 10 Sep 2018 22:00:01 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org>
Date: Tue, 11 Sep 2018 07:59:58 +1000
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org>
To: =?utf-8?Q?Lencse_G=C3=A1bor?= <lencse@hit.bme.hu>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kuiFNYxxmKYvlU1JZ2zPR9vSBsY>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 22:00:06 -0000

Add in a RA and/or DHCP option with

<prefix-len> <prefix-bits> <aclname>

would do.  Where aclname points to a DNS name with a APL record (RFC =
3123) that is
used to exclude AAAA and A records from the processing. If aclname is =
=E2=80=9C.=E2=80=9D then
you don=E2=80=99t lookup the APL RRset.  This move the DNS64 =
configuration from the
recursive server onto the network.  The DNS resolution path for aclname =
needs
to be completely resolvable from a IPv6-only client.

For reference this is the DNS64 configuration syntax for BIND.

        dns64 <netprefix> {
                break-dnssec <boolean>;
                clients { <address_match_element>; ... };
                exclude { <address_match_element>; ... };
                mapped { <address_match_element>; ... };
                recursive-only <boolean>;
                suffix <ipv6_address>;
        }; // may occur multiple times

clients is a no-op.  aclname covers exclude and mapped. recursive-only =
is a no-op.
break-dnssec is a no-op as all this happens after any DNSSEC processing.

Pick a different NAT64 prefix for this option so one can monitor client =
take up
of the use of this method.  Add the prefix advertised using DNS64 to the =
APL record
to prevent DNS64 modified AAAA records being used.

The only thing needed is a getaddrinfo flag to turn this on.  Add the =
flag to
the default set of flags.

Mark

> On 11 Sep 2018, at 6:56 am, Mark Andrews <marka@isc.org> wrote:
>=20
> Well 464XLAT has a IPv4 stack.
>=20
> You can achieve the same effects as DNS64 in getaddrinfo if you =
publish the NAT64 prefix out side of the DNS.  The problem with DNS64 is =
that it modifies answers at the wrong place.  Recursive servers really =
aren=E2=80=99t the correct place no matter how attractive they seem.=20
>=20
> Getaddrinfo allows you to get mapped address back. DNS64 is just a =
different mapped address.
>=20
>=20
> --=20
> Mark Andrews
>=20
> On 11 Sep 2018, at 05:06, Lencse G=C3=A1bor <lencse@hit.bme.hu> wrote:
>=20
>> Dear Fred,
>>=20
>> I have just received an e-mail from my head of department with a list =
of topics for our students from a leading Hungarian ISP. One of them is: =
"IPv6-only mobile networks". :-)
>> As for IPv6 transition technologies to be considered, they mention =
only NAT64, DNS64 and 464XLAT (in this order).
>>=20
>> Of course, I do not want to conclude from this single event that they =
would be better than any other IPv6 transition technologies, but I =
believe that it is still worth using them for new deployments.=20
>>=20
>> BTW.: As for the advantages and disadvantages of the different IPv6 =
transition technologies for providing IPv4aaS (namely: 464XLAT, DS-Lite, =
lw4o6, MAP-E, MAP-T) we have put together a table for crowd sourcing =
with Lee, Jordi and Richard. Unfortunately, it has not yet been =
finished, because I was too busy in this Summer, but I hope to send the =
link of the google spreadsheet to the v6ops mailing list within a few =
days.
>>=20
>> However, I think that these IPv4aaS technologies may NOT substitute =
NAT64+DNS64 in a communication scenario when an IPv6 only client needs =
to communication with an IPv4 only server. Under an IPv6 only client, I =
mean a client, which does not have an IPv4 address or even IPv4 protocol =
stack. Why should we force anyone to use private IPv4 addresses, who =
does not want to do so?
>>=20
>> I think, NAT64+DNS64 is the most appropriate solution for this =
communication scenario and draft-byrne-v6ops-dnssecaaaa is a good =
solution for the conflict of DNS64 and DNSSEC, therefore, I definitely =
support it.
>>=20
>> Best regards,
>>=20
>> G=C3=A1bor
>>=20
>>=20
>>=20
>>=20
>> 9/10/2018 8:10 PM keltez=C3=A9ssel, Fred Baker =C3=ADrta:
>>>> On Sep 7, 2018, at 11:30 AM, Gert Doering <gert@space.net>
>>>>  wrote:
>>>>=20
>>>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>>>>=20
>>>>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>>>>=20
>>>>> Are you saying that there are hundreds of millions of users on =
IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 =
Internet?
>>>>> Where are these users? Cause I wasn???t aware of any general =
deployments of that to end-users.
>>>>>=20
>>>> T-Mobile USA...?
>>>>=20
>>> Indeed. My telephone has only had an IPv6 address on its LTE =
interface for quite some time now.
>>>=20
>>> =
--------------------------------------------------------------------------=
------
>>> Victorious warriors win first and then go to war,
>>> Defeated warriors go to war first and then seek to win.
>>>      Sun Tzu
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>>=20
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Mon Sep 10 16:16:02 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B11E130FF0 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 16:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Level: 
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 0Us80ZY5V5JP for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 16:15:58 -0700 (PDT)
Received: from atl4mhob05.registeredsite.com (atl4mhob05.registeredsite.com [209.17.115.43]) (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 317CB130F8A for <v6ops@ietf.org>; Mon, 10 Sep 2018 16:15:58 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail01pod6.registeredsite.com [10.30.71.209]) by atl4mhob05.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8ANFtkx006577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Mon, 10 Sep 2018 19:15:55 -0400
Received: (qmail 27150 invoked by uid 0); 10 Sep 2018 23:15:55 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 10 Sep 2018 23:15:55 -0000
To: v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org>
Date: Mon, 10 Sep 2018 19:15:54 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3QQr5A4agaka6jy_uqFghnBIWE0>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 23:16:00 -0000

I don't understand why you're working so hard to mark IPv4 work, when 
the clear answer is to deploy IPv6. It's not as if it's a surprise.

But fine, more questions inline. . .


On 09/10/2018 05:59 PM, Mark Andrews wrote:
> Add in a RA and/or DHCP option with
>
> <prefix-len> <prefix-bits> <aclname>
>
> would do.  Where aclname points to a DNS name with a APL record (RFC 3123) that is
> used to exclude AAAA and A records from the processing. If aclname is “.” then
> you don’t lookup the APL RRset.  This move the DNS64 configuration from the
> recursive server onto the network.  The DNS resolution path for aclname needs
> to be completely resolvable from a IPv6-only client.

rfc3123 was new to me. An experiment from 2001; I'd like to hear whether 
name servers other than BIND have implemented APL.

I'm really not following your proposal, so let me try to repeat it: The 
ISP Example provisions, using an as-yet-undescribed RA:
/24 192.0.2.0 example.net

The client then queries the example.net NS for an APL record, which 
provides the IPv6 prefix used for the NAT64 server. When it receives an 
A response, but no AAAA, to a query, it can then forward to the NAT64 
server.

How does an operator know whether to provision (whether RA or DHCPv6) 
the DNS64 nameserver or just a dual-stack resolver?
If a device has the above hack, you don't want it to use the DNS64 
because it'll never get an A record.
If it doesn't have it, it must have DNS64 to reach anything that's 
IPv4-only.


> For reference this is the DNS64 configuration syntax for BIND.
>
>          dns64 <netprefix> {
>                  break-dnssec <boolean>;
>                  clients { <address_match_element>; ... };
>                  exclude { <address_match_element>; ... };
>                  mapped { <address_match_element>; ... };
>                  recursive-only <boolean>;
>                  suffix <ipv6_address>;
>          }; // may occur multiple times
>
> clients is a no-op.  aclname covers exclude and mapped. recursive-only is a no-op.
> break-dnssec is a no-op as all this happens after any DNSSEC processing.

I'm pretty lost. This is saying, "If the DNS query comes from 
<netprefix> then don't do DNS64" i.e., forward the A record and let the 
client sort it out.

>
> Pick a different NAT64 prefix for this option so one can monitor client take up
> of the use of this method.  Add the prefix advertised using DNS64 to the APL record
> to prevent DNS64 modified AAAA records being used.
>
> The only thing needed is a getaddrinfo flag to turn this on.  Add the flag to
> the default set of flags.

A getaddrinfo flag, an RA option, and a DHCPv6 option. This is 
fundamentally a new transition mechanism, using SIIT (as NAT64) again.





At what point do we stop trying to save IPv4-only operators from themselves?

Lee


>
> Mark
>
>> On 11 Sep 2018, at 6:56 am, Mark Andrews <marka@isc.org> wrote:
>>
>> Well 464XLAT has a IPv4 stack.
>>
>> You can achieve the same effects as DNS64 in getaddrinfo if you publish the NAT64 prefix out side of the DNS.  The problem with DNS64 is that it modifies answers at the wrong place.  Recursive servers really aren’t the correct place no matter how attractive they seem.
>>
>> Getaddrinfo allows you to get mapped address back. DNS64 is just a different mapped address.
>>
>>
>> -- 
>> Mark Andrews
>>
>> On 11 Sep 2018, at 05:06, Lencse Gábor <lencse@hit.bme.hu> wrote:
>>
>>> Dear Fred,
>>>
>>> I have just received an e-mail from my head of department with a list of topics for our students from a leading Hungarian ISP. One of them is: "IPv6-only mobile networks". :-)
>>> As for IPv6 transition technologies to be considered, they mention only NAT64, DNS64 and 464XLAT (in this order).
>>>
>>> Of course, I do not want to conclude from this single event that they would be better than any other IPv6 transition technologies, but I believe that it is still worth using them for new deployments.
>>>
>>> BTW.: As for the advantages and disadvantages of the different IPv6 transition technologies for providing IPv4aaS (namely: 464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T) we have put together a table for crowd sourcing with Lee, Jordi and Richard. Unfortunately, it has not yet been finished, because I was too busy in this Summer, but I hope to send the link of the google spreadsheet to the v6ops mailing list within a few days.
>>>
>>> However, I think that these IPv4aaS technologies may NOT substitute NAT64+DNS64 in a communication scenario when an IPv6 only client needs to communication with an IPv4 only server. Under an IPv6 only client, I mean a client, which does not have an IPv4 address or even IPv4 protocol stack. Why should we force anyone to use private IPv4 addresses, who does not want to do so?
>>>
>>> I think, NAT64+DNS64 is the most appropriate solution for this communication scenario and draft-byrne-v6ops-dnssecaaaa is a good solution for the conflict of DNS64 and DNSSEC, therefore, I definitely support it.
>>>
>>> Best regards,
>>>
>>> Gábor
>>>
>>>
>>>
>>>
>>> 9/10/2018 8:10 PM keltezéssel, Fred Baker írta:
>>>>> On Sep 7, 2018, at 11:30 AM, Gert Doering <gert@space.net>
>>>>>   wrote:
>>>>>
>>>>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>>>>>
>>>>>> NAT64 and DNS64 is deployed, and sometimes in chort with 464XLAT.
>>>>>>
>>>>>> Are you saying that there are hundreds of millions of users on IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 Internet?
>>>>>> Where are these users? Cause I wasn???t aware of any general deployments of that to end-users.
>>>>>>
>>>>> T-Mobile USA...?
>>>>>
>>>> Indeed. My telephone has only had an IPv6 address on its LTE interface for quite some time now.
>>>>
>>>> --------------------------------------------------------------------------------
>>>> Victorious warriors win first and then go to war,
>>>> Defeated warriors go to war first and then seek to win.
>>>>       Sun Tzu
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> v6ops mailing list
>>>>
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Mon Sep 10 16:54:01 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2846D130FF7 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 16:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 YH-cHxI9rMyD for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 16:53:56 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 55266130FF2 for <v6ops@ietf.org>; Mon, 10 Sep 2018 16:53:56 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 13E613AB041; Mon, 10 Sep 2018 23:53:56 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id B9B6116005B; Mon, 10 Sep 2018 23:53:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 9BBD816007E; Mon, 10 Sep 2018 23:53:52 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Kg0P4iLajTCB; Mon, 10 Sep 2018 23:53:52 +0000 (UTC)
Received: from beetledviscorg7.home.lan (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id A27D716005B; Mon, 10 Sep 2018 23:53:51 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org>
Date: Tue, 11 Sep 2018 09:53:48 +1000
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7CA035F4-D07C-4FBB-8EE8-7EC58B3EC0EF@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/yEvCe5L6qrblTVxrmTtdy1IYE6s>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 23:53:59 -0000

> On 11 Sep 2018, at 9:15 am, Lee Howard <lee@asgard.org> wrote:
>=20
> I don't understand why you're working so hard to mark IPv4 work, when =
the clear answer is to deploy IPv6. It's not as if it's a surprise.
>=20
> But fine, more questions inline. . .
>=20
>=20
> On 09/10/2018 05:59 PM, Mark Andrews wrote:
>> Add in a RA and/or DHCP option with
>>=20
>> <prefix-len> <prefix-bits> <aclname>
>>=20
>> would do.  Where aclname points to a DNS name with a APL record (RFC =
3123) that is
>> used to exclude AAAA and A records from the processing. If aclname is =
=E2=80=9C.=E2=80=9D then
>> you don=E2=80=99t lookup the APL RRset.  This move the DNS64 =
configuration from the
>> recursive server onto the network.  The DNS resolution path for =
aclname needs
>> to be completely resolvable from a IPv6-only client.
>=20
> rfc3123 was new to me. An experiment from 2001; I'd like to hear =
whether name servers other than BIND have implemented APL.

Every single one as it is supported by UNKNOWN TYPES (RFC 3597) in =
nameservers that do not have type specific code for reading it from the =
master file.  STD13 recursive servers have ALWAYS supported it as they =
are supposed to treat unknown records as opaque blobs. People not =
understanding this in part lead to the myth that it was hard to deploy =
new types.

> I'm really not following your proposal, so let me try to repeat it: =
The ISP Example provisions, using an as-yet-undescribed RA:
> /24 192.0.2.0 example.net


Using the well known prefix as a example:

	96 64:ff9b:: nat64-rules.isp.com

> The client then queries the example.net NS for an APL record, which =
provides the IPv6 prefix used for the NAT64 server. When it receives an =
A response, but no AAAA, to a query, it can then forward to the NAT64 =
server.

It queries for AAAA target.example.com, A target.example.com and APL =
nat64-rules.isp.com.

It then uses those DNS responses along with prefix information from the =
RA/DHCPv6/=E2=80=A6 to construct struct addrinfo answers for getaddrinfo =
to return.

> How does an operator know whether to provision (whether RA or DHCPv6) =
the DNS64 nameserver or just a dual-stack resolver?

How did people decide when to only provision MX records rather than A =
and AAAA records to reach SMTP servers?  They made a judgement call.

I would use RFC 7050 with a ipv4only.arpa zone (not DNS64) and 464XLAT =
as the fallback mechanism for legacy devices and don=E2=80=99t deploy =
DNS64 at all.  That should work for the current crop of cell phones.  It =
should also work for CPE routers as 464XLAT support is effectively =
required for all ISPs deploying DNS64 in wireline scenarios today.

I would expect a CPE devices would be request this information on the =
upstream side and if it sees it, advertise it on the downstream side.  =
Similarly for cell phones when tethering.

> If a device has the above hack, you don't want it to use the DNS64 =
because it'll never get an A record.

DNS64 never stopped A records getting through.  All it does is modify =
some AAAA responses.

> If it doesn't have it, it must have DNS64 to reach anything that's =
IPv4-only.

Mark

>> For reference this is the DNS64 configuration syntax for BIND.
>>=20
>>         dns64 <netprefix> {
>>                 break-dnssec <boolean>;
>>                 clients { <address_match_element>; ... };
>>                 exclude { <address_match_element>; ... };
>>                 mapped { <address_match_element>; ... };
>>                 recursive-only <boolean>;
>>                 suffix <ipv6_address>;
>>         }; // may occur multiple times
>>=20
>> clients is a no-op.  aclname covers exclude and mapped. =
recursive-only is a no-op.
>> break-dnssec is a no-op as all this happens after any DNSSEC =
processing.
>=20
> I'm pretty lost. This is saying, "If the DNS query comes from =
<netprefix> then don't do DNS64" i.e., forward the A record and let the =
client sort it out.
>=20
>>=20
>> Pick a different NAT64 prefix for this option so one can monitor =
client take up
>> of the use of this method.  Add the prefix advertised using DNS64 to =
the APL record
>> to prevent DNS64 modified AAAA records being used.
>>=20
>> The only thing needed is a getaddrinfo flag to turn this on.  Add the =
flag to
>> the default set of flags.
>=20
> A getaddrinfo flag, an RA option, and a DHCPv6 option. This is =
fundamentally a new transition mechanism, using SIIT (as NAT64) again.
>=20
>=20
>=20
>=20
>=20
> At what point do we stop trying to save IPv4-only operators from =
themselves?
>=20
> Lee
>=20
>=20
>>=20
>> Mark
>>=20
>>> On 11 Sep 2018, at 6:56 am, Mark Andrews <marka@isc.org> wrote:
>>>=20
>>> Well 464XLAT has a IPv4 stack.
>>>=20
>>> You can achieve the same effects as DNS64 in getaddrinfo if you =
publish the NAT64 prefix out side of the DNS.  The problem with DNS64 is =
that it modifies answers at the wrong place.  Recursive servers really =
aren=E2=80=99t the correct place no matter how attractive they seem.
>>>=20
>>> Getaddrinfo allows you to get mapped address back. DNS64 is just a =
different mapped address.
>>>=20
>>>=20
>>> --=20
>>> Mark Andrews
>>>=20
>>> On 11 Sep 2018, at 05:06, Lencse G=C3=A1bor <lencse@hit.bme.hu> =
wrote:
>>>=20
>>>> Dear Fred,
>>>>=20
>>>> I have just received an e-mail from my head of department with a =
list of topics for our students from a leading Hungarian ISP. One of =
them is: "IPv6-only mobile networks". :-)
>>>> As for IPv6 transition technologies to be considered, they mention =
only NAT64, DNS64 and 464XLAT (in this order).
>>>>=20
>>>> Of course, I do not want to conclude from this single event that =
they would be better than any other IPv6 transition technologies, but I =
believe that it is still worth using them for new deployments.
>>>>=20
>>>> BTW.: As for the advantages and disadvantages of the different IPv6 =
transition technologies for providing IPv4aaS (namely: 464XLAT, DS-Lite, =
lw4o6, MAP-E, MAP-T) we have put together a table for crowd sourcing =
with Lee, Jordi and Richard. Unfortunately, it has not yet been =
finished, because I was too busy in this Summer, but I hope to send the =
link of the google spreadsheet to the v6ops mailing list within a few =
days.
>>>>=20
>>>> However, I think that these IPv4aaS technologies may NOT substitute =
NAT64+DNS64 in a communication scenario when an IPv6 only client needs =
to communication with an IPv4 only server. Under an IPv6 only client, I =
mean a client, which does not have an IPv4 address or even IPv4 protocol =
stack. Why should we force anyone to use private IPv4 addresses, who =
does not want to do so?
>>>>=20
>>>> I think, NAT64+DNS64 is the most appropriate solution for this =
communication scenario and draft-byrne-v6ops-dnssecaaaa is a good =
solution for the conflict of DNS64 and DNSSEC, therefore, I definitely =
support it.
>>>>=20
>>>> Best regards,
>>>>=20
>>>> G=C3=A1bor
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> 9/10/2018 8:10 PM keltez=C3=A9ssel, Fred Baker =C3=ADrta:
>>>>>> On Sep 7, 2018, at 11:30 AM, Gert Doering <gert@space.net>
>>>>>>  wrote:
>>>>>>=20
>>>>>> On Fri, Sep 07, 2018 at 08:25:18PM +0200, Ole Troan wrote:
>>>>>>=20
>>>>>>> NAT64 and DNS64 is deployed, and sometimes in chort with =
464XLAT.
>>>>>>>=20
>>>>>>> Are you saying that there are hundreds of millions of users on =
IPv6 only networks with NAT64/DNS64 their only exit to the IPv4 =
Internet?
>>>>>>> Where are these users? Cause I wasn???t aware of any general =
deployments of that to end-users.
>>>>>>>=20
>>>>>> T-Mobile USA...?
>>>>>>=20
>>>>> Indeed. My telephone has only had an IPv6 address on its LTE =
interface for quite some time now.
>>>>>=20
>>>>> =
--------------------------------------------------------------------------=
------
>>>>> Victorious warriors win first and then go to war,
>>>>> Defeated warriors go to war first and then seek to win.
>>>>>      Sun Tzu
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> v6ops mailing list
>>>>>=20
>>>>> v6ops@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Mon Sep 10 17:50:40 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B03C8130DFC for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 17:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 pLu7yGK4uzyS for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 17:50:37 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 528A6130DCD for <v6ops@ietf.org>; Mon, 10 Sep 2018 17:50:37 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 0A3063AB040; Tue, 11 Sep 2018 00:50:36 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id EC00416007E; Tue, 11 Sep 2018 00:50:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id DD1A316007D; Tue, 11 Sep 2018 00:50:35 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id F6Mk8Sv2ybfB; Tue, 11 Sep 2018 00:50:35 +0000 (UTC)
Received: from beetledviscorg7.home.lan (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 431AB16005B; Tue, 11 Sep 2018 00:50:35 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org>
Date: Tue, 11 Sep 2018 10:50:32 +1000
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F09B8639-C266-4009-A330-94018688E708@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/nGYwCtG4vNSSz69bm3kVXwLjwVM>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 00:50:39 -0000

> On 11 Sep 2018, at 9:15 am, Lee Howard <lee@asgard.org> wrote:
>=20
> I don't understand why you're working so hard to mark IPv4 work, when =
the clear answer is to deploy IPv6. It's not as if it's a surprise.

Because DNS64 hijacks all use of the DNS and prevents people people =
doing what they currently do with the DNS without a lot of specialised =
knowledge.

I=E2=80=99m trying to give DNS back to the customers.  If they want to =
be able to 1.1.1.1 or 8.8.8.8 as their recursive servers they should be =
able to.  If they want to run their own recursive nameservers they =
should be able to.  If they want to DNSSEC validate answers they get =
from their ISP they should be able to.  DNS64 breaks / makes doing this =
sort of thing extremely difficult.  I can manage it (even if I need to =
install a DNS server to achieve it) but most people can=E2=80=99t.

All the issues we are talking about with DNS64 today where known about =
and hand waved away when DNS64 was being published.  8 years later all =
that hand waving as people deploy beyond the trivial cell phone case is =
coming back to bite.

Mark

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Mon Sep 10 18:26:26 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C18F131088 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 18:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 pEl5fXGuJcvI for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 18:26:13 -0700 (PDT)
Received: from mail-yw1-xc29.google.com (mail-yw1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) (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 DF17E1310A2 for <v6ops@ietf.org>; Mon, 10 Sep 2018 18:26:10 -0700 (PDT)
Received: by mail-yw1-xc29.google.com with SMTP id l189-v6so8596955ywb.10 for <v6ops@ietf.org>; Mon, 10 Sep 2018 18:26:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=l9OVL7GtkplEjCILFzFirBm9CTjs7Uh0Vbd2q+iIpUs=; b=jIZcSSYc64H4Nr4I9iQG/EEs8a+rjZRNdnniW28mBcn7CYvEfRaFoj4BhJJOnXkp7Q KaBxUxYtgqZahY2mXvzF6MkmDGJ18YtSwb5mheFyZhRq634oGgNzs0zeaTGg0bsST8Og zsDGGLpDgWnrRWy9QGbq9SwdCVyUogvxq6X9cnl04OTUvhTpYnXLmO0qhsBtAsHyylaD +WUDJReN4crwXx5HcKe1rLooaOKSaI+8zC1qbNtneiZZDFmGWdMoYqjMLsHE1rlmi/iB ozW1D7d9Dk/lszTnpSxSn1a8QWsZ1p6iDq1Zgfjgzkdz2hTpSnETFMtNE02ibsINL/+D JvYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=l9OVL7GtkplEjCILFzFirBm9CTjs7Uh0Vbd2q+iIpUs=; b=SRXcdlg5ZVzEWyk8tlNiR+tPG+ljp9sXQOWBx+aieAcmfY0EISVkXIIe8nz5YzgDS1 0rkRqT1UQuU3ggffKagK/8g3NOZ37gU+JzODjTekwuR0BseACDjJzWb3Vhy6k+SiyCbS amgby7j0WzejTB73Yb6WvaEb0IjPejSkZIWFjRbLz97wi05cR3aQJDshwzyDZlpe38vm KHJ3mP9sa0o3cE9njGN4vIugKpQ6HzH4CEXiK90ENlVOm+Jv6gautreLr5Y3LAiLP24i 351cPxv3P44O7b+df+F5lnNrnnPaDBHuUYkR2y/nTIjebD2l44ern4rtuNb3rTvAxnX3 stVQ==
X-Gm-Message-State: APzg51BiZL2psMm9U0+1s8dVYWUEYqSW0ruNDOXkWRzNsi776uimpsBg fJ2+HoAwXunKeDV1r/Ctf/EC3yrAvC498CFaifE=
X-Google-Smtp-Source: ANB0VdaxTLI9tmEjrEzJGz02CrXzKFBXD2t7bYdjWEqSyWNWOVA2p4EruRQPmpmvI7ci3CkZ8XhahTCTaTYV9BN4IZY=
X-Received: by 2002:a81:7785:: with SMTP id s127-v6mr11390926ywc.233.1536629170062;  Mon, 10 Sep 2018 18:26:10 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org>
In-Reply-To: <F09B8639-C266-4009-A330-94018688E708@isc.org>
From: Ca By <cb.list6@gmail.com>
Date: Mon, 10 Sep 2018 18:25:58 -0700
Message-ID: <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: Lee Howard <lee@asgard.org>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d54bfe05758e5bcc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tSXfoMUotmUK-z8mi3lfSQJLHTs>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 01:26:25 -0000

--000000000000d54bfe05758e5bcc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 10, 2018 at 5:51 PM Mark Andrews <marka@isc.org> wrote:

>
>
> > On 11 Sep 2018, at 9:15 am, Lee Howard <lee@asgard.org> wrote:
> >
> > I don't understand why you're working so hard to mark IPv4 work, when
> the clear answer is to deploy IPv6. It's not as if it's a surprise.
>
> Because DNS64 hijacks all use of the DNS and prevents people people doing
> what they currently do with the DNS without a lot of specialised knowledg=
e.
>
> I=E2=80=99m trying to give DNS back to the customers.  If they want to be=
 able to
> 1.1.1.1 or 8.8.8.8 as their recursive servers they should be able to.  If
> they want to run their own recursive nameservers they should be able to.
> If they want to DNSSEC validate answers they get from their ISP they shou=
ld
> be able to.  DNS64 breaks / makes doing this sort of thing extremely
> difficult.  I can manage it (even if I need to install a DNS server to
> achieve it) but most people can=E2=80=99t.
>
> All the issues we are talking about with DNS64 today where known about an=
d
> hand waved away when DNS64 was being published.  8 years later all that
> hand waving as people deploy beyond the trivial cell phone case is coming
> back to bite.
>
> Mark


That=E2=80=99s your opinion and your values.

I deployed dns64 6 years ago. Very happy with results. I would deploy
again, 5 out of 5.

http://www.worldipv6launch.org/apps/ipv6week/measurement/images/graphs/T-Mo=
bileUSA.png

My view, and the i-d of referenced for this thread, all the dns64 ills go
away if you deploy ipv6, so please deploy ipv6.

And, dont expect ipv4 to work. IPv4 life support (nat, dns64, map, ...)
breaks ipv4 in various way.

CB


>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--000000000000d54bfe05758e5bcc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon,=
 Sep 10, 2018 at 5:51 PM Mark Andrews &lt;<a href=3D"mailto:marka@isc.org">=
marka@isc.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
&gt; On 11 Sep 2018, at 9:15 am, Lee Howard &lt;<a href=3D"mailto:lee@asgar=
d.org" target=3D"_blank">lee@asgard.org</a>&gt; wrote:<br>
&gt; <br>
&gt; I don&#39;t understand why you&#39;re working so hard to mark IPv4 wor=
k, when the clear answer is to deploy IPv6. It&#39;s not as if it&#39;s a s=
urprise.<br>
<br>
Because DNS64 hijacks all use of the DNS and prevents people people doing w=
hat they currently do with the DNS without a lot of specialised knowledge.<=
br>
<br>
I=E2=80=99m trying to give DNS back to the customers.=C2=A0 If they want to=
 be able to 1.1.1.1 or 8.8.8.8 as their recursive servers they should be ab=
le to.=C2=A0 If they want to run their own recursive nameservers they shoul=
d be able to.=C2=A0 If they want to DNSSEC validate answers they get from t=
heir ISP they should be able to.=C2=A0 DNS64 breaks / makes doing this sort=
 of thing extremely difficult.=C2=A0 I can manage it (even if I need to ins=
tall a DNS server to achieve it) but most people can=E2=80=99t.<br>
<br>
All the issues we are talking about with DNS64 today where known about and =
hand waved away when DNS64 was being published.=C2=A0 8 years later all tha=
t hand waving as people deploy beyond the trivial cell phone case is coming=
 back to bite.<br>
<br>
Mark</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">That=E2=80=
=99s your opinion and your values.=C2=A0</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">I deployed dns64 6 years ago. Very happy with results. I w=
ould deploy again, 5 out of 5.=C2=A0</div><div dir=3D"auto"><br></div><div =
dir=3D"auto"><div><a href=3D"http://www.worldipv6launch.org/apps/ipv6week/m=
easurement/images/graphs/T-MobileUSA.png">http://www.worldipv6launch.org/ap=
ps/ipv6week/measurement/images/graphs/T-MobileUSA.png</a></div><br></div><d=
iv dir=3D"auto">My view, and the i-d of referenced for this thread, all the=
 dns64 ills go away if you deploy ipv6, so please deploy ipv6.=C2=A0</div><=
div dir=3D"auto"><br></div><div dir=3D"auto">And, dont expect ipv4 to work.=
 IPv4 life support (nat, dns64, map, ...) breaks ipv4 in various way.=C2=A0=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">CB</div><div dir=3D"aut=
o"><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><br>
<br>
-- <br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: +61 2 9871 4742=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 INTE=
RNET: <a href=3D"mailto:marka@isc.org" target=3D"_blank">marka@isc.org</a><=
br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div>

--000000000000d54bfe05758e5bcc--


From nobody Mon Sep 10 18:40:13 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AED3713102F for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 18:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 NAx9MhbTFncY for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 18:40:08 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 B7B23130E09 for <v6ops@ietf.org>; Mon, 10 Sep 2018 18:40:08 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 526F43AB040; Tue, 11 Sep 2018 01:40:08 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 27218160045; Tue, 11 Sep 2018 01:40:08 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id F245A16005B; Tue, 11 Sep 2018 01:40:07 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id VHo6weIJ5FpX; Tue, 11 Sep 2018 01:40:07 +0000 (UTC)
Received: from beetledviscorg7.home.lan (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id E814A160045; Tue, 11 Sep 2018 01:40:06 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com>
Date: Tue, 11 Sep 2018 11:40:03 +1000
Cc: Lee Howard <lee@asgard.org>, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD053118-AF5C-4266-9FAF-3291775139C7@isc.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com>
To: Ca By <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/j9HkzjATAzqRSx_eUnfhyrAsag0>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 01:40:11 -0000

> On 11 Sep 2018, at 11:25 am, Ca By <cb.list6@gmail.com> wrote:
>=20
>=20
>=20
> On Mon, Sep 10, 2018 at 5:51 PM Mark Andrews <marka@isc.org> wrote:
>=20
>=20
> > On 11 Sep 2018, at 9:15 am, Lee Howard <lee@asgard.org> wrote:
> >=20
> > I don't understand why you're working so hard to mark IPv4 work, =
when the clear answer is to deploy IPv6. It's not as if it's a surprise.
>=20
> Because DNS64 hijacks all use of the DNS and prevents people people =
doing what they currently do with the DNS without a lot of specialised =
knowledge.
>=20
> I=E2=80=99m trying to give DNS back to the customers.  If they want to =
be able to 1.1.1.1 or 8.8.8.8 as their recursive servers they should be =
able to.  If they want to run their own recursive nameservers they =
should be able to.  If they want to DNSSEC validate answers they get =
from their ISP they should be able to.  DNS64 breaks / makes doing this =
sort of thing extremely difficult.  I can manage it (even if I need to =
install a DNS server to achieve it) but most people can=E2=80=99t.
>=20
> All the issues we are talking about with DNS64 today where known about =
and hand waved away when DNS64 was being published.  8 years later all =
that hand waving as people deploy beyond the trivial cell phone case is =
coming back to bite.
>=20
> Mark
>=20
> That=E2=80=99s your opinion and your values.=20
>=20
> I deployed dns64 6 years ago. Very happy with results. I would deploy =
again, 5 out of 5.=20
>=20
> =
http://www.worldipv6launch.org/apps/ipv6week/measurement/images/graphs/T-M=
obileUSA.png

You deployed to CELL PHONES which has a very RESTRICTED client base.  =
That it mostly =E2=80=9Cworked=E2=80=9D with these very restricted =
clients is not news.  It also does not invalidate all the issues there =
are with DNS64.

> My view, and the i-d of referenced for this thread, all the dns64 ills =
go away if you deploy ipv6, so please deploy ipv6.

Your draft does NOTHING effective to address DNS64 issues.  It won=E2=80=99=
t speed up IPv6 deployment.  It won=E2=80=99t remove the issues clients =
of ISP=E2=80=99s that deploy DNS64 see especially wireline clients.

> And, dont expect ipv4 to work. IPv4 life support (nat, dns64, map, =
...) breaks ipv4 in various way.

I never said it didn=E2=80=99t, but thank you for introducing red =
herring.

> CB
>=20
>=20
>=20
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Mon Sep 10 22:35:01 2018
Return-Path: <lorenzo@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23353130E2D for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 22:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level: 
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 fBegnCIsWOb1 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 22:34:58 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 65ED7127148 for <v6ops@ietf.org>; Mon, 10 Sep 2018 22:34:58 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id p79-v6so32687888itp.3 for <v6ops@ietf.org>; Mon, 10 Sep 2018 22:34:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JjGVgdLbV1isBTEk4nr0eUpG8CfQQ3Aic5/DCq0HwkQ=; b=um/5qVtThckjsyTPX4T4jcM5Z9CIGnfc08gzwbFoed0PtDrlAqS/FHxdXEDGQ5sbgn Tgr99Wj9BDGoTkHoWunu63Er0uLoTWzjD/o9vqFssMlxzujaB9QRDX/LED2+JNEW43mV 9M5izfOWqRhC0vpBY3iG02NlEyMeE2Nd4WHyz6jYyI4GznI5J3ozKektm38QDkE7JfNI T/eTeHYobHD5Rn4SpP57cOL4pHcePQErKYhrMfpHaNqJSwQASgllT9Dxx2sYxGk8IX8k 3oDazjrdXNGmd8KocIn4UBX2Iez17h+NXvThVXILIFtdi635fKTtVZGJrW2LPmHxgOy9 Dbgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JjGVgdLbV1isBTEk4nr0eUpG8CfQQ3Aic5/DCq0HwkQ=; b=P/qTPBai8wBtMcl2/ZqlUlqe5KBBYbJFBU6mnXWpe01SYt23AmymLjS/vwpB2NQwQe mNSMe8x4WuX4vh8xMBj3v5UU+A1SdZBQZLMrvUPhNfQhYHNHoSdTt223bVDQD32SDTH/ VyMexqralqKY9J58MEVzdNH0WR7CvniP3o9zb00kLIPkuZRVzYSyHJj/9+3lPNO54qIB i0kbMy3fLwbTjbvx3KM7YdGonQ0XU9sL8NrLt0ohp/UHp5FfwCTWRteKQf4kEWhZsGeH HmP5VztCMZ0W8w9Ehn1NGl3EXbjDtmLinR3b9qNqRuwvRnMqYWhply3Y0MZkvFbuRgN1 8cMQ==
X-Gm-Message-State: APzg51C0ijeZ4RVb5BWF3BRaZeIlL+veikWYp6eyjTHYMi2QLnysL/pT fmSZffrNCBPG0g2YTq/48Tfj9LrNwO2XqrXbTXSKuV+K++Y=
X-Google-Smtp-Source: ANB0VdbcQl3GbSJf7lf8uT8pe1FR8uDER529lm0+RTI4IEoKUPPbMqTlnQfoFdG0IJ+hiiUwp4UKOKrjHdQ10RD4PbE=
X-Received: by 2002:a24:8282:: with SMTP id t124-v6mr105686itd.57.1536644097285;  Mon, 10 Sep 2018 22:34:57 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 11 Sep 2018 14:34:45 +0900
Message-ID: <CAKD1Yr3ffVL=cdkK4Z+KhO6P7UoyQ=p_PMp2+Vumweh36rvQ8g@mail.gmail.com>
To: Joel Jaeggli <joelja@bogus.com>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Ron Bonica <rbonica@juniper.net>
Content-Type: multipart/alternative; boundary="0000000000009173fb057591d5c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rozTOGYuFIw5KjsyR74QotL98iM>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 05:35:00 -0000

--0000000000009173fb057591d5c4
Content-Type: text/plain; charset="UTF-8"

On Mon, Sep 10, 2018 at 11:25 PM Ron Bonica <rbonica@juniper.net> wrote:

> This week, please review and comment on
> draft-jaeggli-v6ops-indefensible-nd.
>

It seems easy to solve this problem by saying that routers can create
speculative incomplete ND cache entries from DAD probes, and that such
incomplete entries take precedence over incomplete entries due to forwarded
packets. Because all addresses require DAD, this would ensure that any host
that is on the router's link would have ND cache entries for all its
addresses as soon as the host joins the link.

In the presence of non-zero packet loss, this obviously does not increase
the reliability to 100%. However, on most networks it probably lowers the
payoff to such an extent to make the attack not useful in practice.

--0000000000009173fb057591d5c4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Sep 10=
, 2018 at 11:25 PM Ron Bonica &lt;<a href=3D"mailto:rbonica@juniper.net">rb=
onica@juniper.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Th=
is week, please review and comment on draft-jaeggli-v6ops-indefensible-nd.<=
br></blockquote><div><br></div><div>It seems easy to solve this problem by =
saying that routers can create speculative incomplete ND cache entries from=
 DAD probes, and that such incomplete entries take precedence over incomple=
te entries due to forwarded packets. Because all addresses require DAD, thi=
s would ensure that any host that is on the router&#39;s link would have ND=
 cache entries for all its addresses as soon as the host joins the link.</d=
iv><div><br></div><div>In the presence of non-zero packet loss, this obviou=
sly does not increase the reliability to 100%. However, on most networks it=
 probably lowers the payoff to such an extent to make the attack not useful=
 in practice.</div></div></div>

--0000000000009173fb057591d5c4--


From nobody Mon Sep 10 23:15:31 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B50A126DBF for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Nb9ZtTni04LT for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:15:28 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23F49130E34 for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:15:27 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id D47B8FECBB29; Tue, 11 Sep 2018 06:15:26 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com>
Date: Tue, 11 Sep 2018 08:15:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org>
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OCI1fF64dR4S3_rv5V4HiZqyBRE>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 06:15:30 -0000

You might want to include that this problem has been solved with a stateful a=
ddress assignment mechanism like DHCP, possibly combined with SAVI.=20

The ND ARO option would also have solved this.=20

Or you could deploy P2P Ethernet, where there is no address resolution.=20

Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=E2=80=99=
s even less robust in wired networks (blocked ports).=20

Cheers=20
Ole

> On 10 Sep 2018, at 16:25, Ron Bonica <rbonica@juniper.net> wrote:
>=20
> Folks,
>=20
> Each week between now and IETF 103, we will review and discuss one draft w=
ith an eye towards progressing it.
>=20
> This week, please review and comment on draft-jaeggli-v6ops-indefensible-n=
d.
>=20
>                                      Fred and Ron
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Mon Sep 10 23:22:23 2018
Return-Path: <ek@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2543F130E35 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level: 
X-Spam-Status: No, score=-17.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 nykI281theYY for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:22:19 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 56B82126DBF for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:22:19 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id 207-v6so37883wme.5 for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:22:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KX4uufll/dQVhU+CDJrMzL1Vuw70GrhDOBVq9qDYj0U=; b=ouM0SVBxU9ImQ8wf2n7AF1EjDX67k2IRV4itrS0pNhLXWFsgaMoUIWCDVgM7R6CvvV CHnShNCbZkn4IgMnlPpK7oSx8JXK5jbQ0mg5pAc/MdMJM3S7UocArrL8++XyCLH7XfEQ OWqQVc/7hURwALetYWrfOWGF0483PD5e99c8sJjegbywED/mMnzo/IEEQRDzrQ7niaKk d5fnKVWxXayc3vr5sZcYpNC9DS/ccM+eo/1RRqmSZfo+9mE3f9bdY/+WRQMBkqVA8JUR ODQY3rbC7HTvi1CYxV5Z7cWbUbUZYktn3JXIEvxI6g05K121aIsFCb4hJew8oDQjb1x9 oZ5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KX4uufll/dQVhU+CDJrMzL1Vuw70GrhDOBVq9qDYj0U=; b=PFzIDtSfiUDx9fvTQENb/qsXuzTH9ZQWeH7J4WuXqhXqAwhxgCVTXqomm7+e3F7GXa 4HNEM+MLF/5KTqmUBhNjYdLWUcIMgyiDJeWjaw3GjzCq519s+FAIjSYdxu1us4N7JzRq 4CuUAnyNL1IYv1+TftyYgkP+nV4Cm9Q/W1vfYBWdODKEkCpf8ygR633FEUyZ/47uEzRp ySOonKXbjefN6+AHU6s/5RJ/YdeoMwMNaPZhThaLOVTmTixyuchvdZf7OBIAihk7Re1b tfZQqEkQqFAqFPlfIF4XPENjAbfP+3XuWX0jiqJWbBB43KaWGdgPH/IC4hT/ZaYv3yOa VaCg==
X-Gm-Message-State: APzg51B5/nfsbNb+6xCxrIlWpMkx2JsDsaMpJg4kVZs2HgZLLbAvagAn KDeoe0ITZYXgZWePfd76c9jxurK18obeaJxp3xihtA==
X-Google-Smtp-Source: ANB0VdbaGYl5XfCOIbomKTE770x0Jt1VntrfTJ/FtyycNHlZGdQ2sc5z4Pv1m2YEO5jf51qbgjANkuRK2KvuU8jTyTI=
X-Received: by 2002:a1c:e00a:: with SMTP id x10-v6mr241924wmg.58.1536646937455;  Mon, 10 Sep 2018 23:22:17 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org>
In-Reply-To: <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org>
From: Erik Kline <ek@google.com>
Date: Tue, 11 Sep 2018 15:22:05 +0900
Message-ID: <CAAedzxrtOrQrqZw-os45sRA2QT2gT7sE8CiuGxFFEssKx26iyw@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="000000000000e2ec430575927ec6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_iS43JLrE8aXcsZ7ZNFE-3pQHE8>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 06:22:22 -0000

--000000000000e2ec430575927ec6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 11 Sep 2018 at 15:15, Ole Troan <otroan@employees.org> wrote:
>
> You might want to include that this problem has been solved with a statef=
ul address assignment mechanism like DHCP, possibly combined with SAVI.
>
> The ND ARO option would also have solved this.
>
> Or you could deploy P2P Ethernet, where there is no address resolution.
>
> Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=E2=
=80=99s even less robust in wired networks (blocked ports).

But...in such a network NS/NA works?  (alternatively: what does
"blocked" mean here)

> Cheers
> Ole
>
> > On 10 Sep 2018, at 16:25, Ron Bonica <rbonica@juniper.net> wrote:
> >
> > Folks,
> >
> > Each week between now and IETF 103, we will review and discuss one draf=
t with an eye towards progressing it.
> >
> > This week, please review and comment on draft-jaeggli-v6ops-indefensibl=
e-nd.
> >
> >                                      Fred and Ron
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

--000000000000e2ec430575927ec6
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS3wYJKoZIhvcNAQcCoIIS0DCCEswCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBFMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEXDCCA0SgAwIBAgIMPipSifuL4Tx7dmsbMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE4MDcxNTA2MzcxOFoXDTE5MDEx
MTA2MzcxOFowHjEcMBoGCSqGSIb3DQEJAQwNZWtAZ29vZ2xlLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBALkHIP2fSFudoue2xAkNBouFm2EulKm/RKnsxmEw4dSbxQC2Mt72Ga/t
ySyn6PMSAgsyjgP0bKJZf/NHBzDGuSKpY09UgBupEUEejwR4d5vrHk8IJNfIDTQ+Ygv4krlQmkO0
Qh/GB1y4PxtIn0tVfGfB7s3Z7wWyYbN1JrUrxAhKTpvkbJLRF1n/fKgv1nfUYyY9se4cZE3XQbJV
2biA0ATE8hw55TPa9FTv+QuWbAWXlTfsvz8SxdL8cs1HXVzBwi7kpzm2LbLictqUYotBdrCk2JQ9
ZkICHIpunwWnfTfNJ1Vt7MYL8worV+Y0TfBP0Uw1IG8qQ1Fdie3quVfdAoUCAwEAAaOCAWowggFm
MBgGA1UdEQQRMA+BDWVrQGdvb2dsZS5jb20wUAYIKwYBBQUHAQEERDBCMEAGCCsGAQUFBzAChjRo
dHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24uY29tL2NhY2VydC9nc2h2c21pbWVjYTEuY3J0MB0GA1Ud
DgQWBBQw12fRZdlCj/XWgp08Ky/Ct82W7DAfBgNVHSMEGDAWgBTLOBKwx5nAeJKMsyGV5vQmYsDg
PzBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9i
YWxzaWduLmNvbS9yZXBvc2l0b3J5LzA7BgNVHR8ENDAyMDCgLqAshipodHRwOi8vY3JsLmdsb2Jh
bHNpZ24uY29tL2dzaHZzbWltZWNhMS5jcmwwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDANBgkqhkiG9w0BAQsFAAOCAQEAsH2eOQwQDXJ145YZFyjaTxqiVS9t
F3F65BSt739euYxmyoYFAFgBVwRLXBjD0eTRqz6W6O9FC3ZPzsIup/DXZZlPNPitbqGA391usTKN
YHYsBchdjOocgO8gNokf3H4yvjUv6699ncUQXX+d0deUo38jOa4+OujSIQbz+PUicageFuFcraDO
MV5VMHYtn/1Ngkrw4JSaf2nv1WTfUBQyRRorMCPXVJZLEm8K0apTK2RHaxnFvXHJjFPkLLsJSwmQ
RCeC98jyQdFHPQank0x8KmEo+nlu2d0X0n/aLibqG7rRSVKINpvLv6C3j8P4b1t1Fu23J6OYkWUx
Rz/Rs1hfPTGCAl4wggJaAgEBMFwwTDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExIjAgBgNVBAMTGUdsb2JhbFNpZ24gSFYgUy9NSU1FIENBIDECDD4qUon7i+E8e3ZrGzAN
BglghkgBZQMEAgEFAKCB1DAvBgkqhkiG9w0BCQQxIgQgzFHN/cMiT+CuH7c+8XsV6i2m1v3Kh2R+
pJjazlZIyDAwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTgwOTEx
MDYyMjE4WjBpBgkqhkiG9w0BCQ8xXDBaMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMAsGCSqGSIb3DQEBCjALBgkqhkiG9w0BAQcwCwYJYIZIAWUDBAIB
MA0GCSqGSIb3DQEBAQUABIIBAKEsK8LAdVnbirT/ecg2zmKCeCdUKJRegN6lsXf+cioNQTUvbXfi
af1GML19VNzcdG6ZhIAj9r3IWjEtsqr1qB0IkBT/FGzmqlJ0CHgwbAWH4ktAv8uA9I3WvMxcKmMx
twmilV21EKtirOLAu+9uNg4g2cBwRfmyMNeQdzEErNBvLPnk6kWLGpF+PCqSkzK22mIF6l5KJQgv
d//inscLzqk3hdik4VWBLLEcByvCeJKN2PXgdGci9wUOAkHL4UyFC3SKhDL3z79T2DM6ZgWL6qSl
3/esn2SMosMh0/09Nbrerne424MyF4DsrcXDZPAq5pdByBb96bGg3+ksVjcf/FU=
--000000000000e2ec430575927ec6--


From nobody Mon Sep 10 23:34:26 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75021130E35 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Bxt0FNq9eQPI for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:34:21 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 136021277CC for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:34:20 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id A30BFFECBBEB; Tue, 11 Sep 2018 06:34:20 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CAAedzxrtOrQrqZw-os45sRA2QT2gT7sE8CiuGxFFEssKx26iyw@mail.gmail.com>
Date: Tue, 11 Sep 2018 08:34:18 +0200
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD8E7FA1-86F3-4193-ABBF-97AF25CEE565@employees.org>
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org> <CAAedzxrtOrQrqZw-os45sRA2QT2gT7sE8CiuGxFFEssKx26iyw@mail.gmail.com>
To: Erik Kline <ek@google.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GKWrsZlD6shgg3ADA199I95v1t4>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 06:34:24 -0000

Erik,

> On 11 Sep 2018, at 08:22, Erik Kline <ek@google.com> wrote:
>=20
>> On Tue, 11 Sep 2018 at 15:15, Ole Troan <otroan@employees.org> wrote:
>>=20
>> You might want to include that this problem has been solved with a statef=
ul address assignment mechanism like DHCP, possibly combined with SAVI.
>>=20
>> The ND ARO option would also have solved this.
>>=20
>> Or you could deploy P2P Ethernet, where there is no address resolution.
>>=20
>> Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=E2=80=
=99s even less robust in wired networks (blocked ports).
>=20
> But...in such a network NS/NA works?  (alternatively: what does
> "blocked" mean here)

NS/NA has retransmission.=20
Blocked as in 802.1D. Default 30s from link-up until port will switch user t=
raffic.=20

DAD is unreliable for lots of reasons . Didn=E2=80=99t we write a draft on t=
hat?

Ole


>>=20
>>> On 10 Sep 2018, at 16:25, Ron Bonica <rbonica@juniper.net> wrote:
>>>=20
>>> Folks,
>>>=20
>>> Each week between now and IETF 103, we will review and discuss one draft=
 with an eye towards progressing it.
>>>=20
>>> This week, please review and comment on draft-jaeggli-v6ops-indefensible=
-nd.
>>>=20
>>>                                     Fred and Ron
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Mon Sep 10 23:40:13 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7176A130E3C for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 0C2Eck-eAfsb for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:40:10 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFA2B1277CC for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:40:09 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 67A2EFECBB47; Tue, 11 Sep 2018 06:40:09 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com>
Date: Tue, 11 Sep 2018 08:40:06 +0200
Cc: Mark Andrews <marka@isc.org>, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com>
To: Ca By <cb.list6@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/r1hmMO4qXOvqrv1ISCdzhE8_R50>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 06:40:12 -0000

> On 11 Sep 2018, at 03:25, Ca By <cb.list6@gmail.com> wrote:
>=20
> My view, and the i-d of referenced for this thread, all the dns64 ills go a=
way if you deploy ipv6, so please deploy ipv6.=20

If everyone everywhere deployed IPv6, then yes.=20
But until then, this creates problems for IPv6 hosts.=20

Cheers=20
Ole=


From nobody Mon Sep 10 23:47:40 2018
Return-Path: <lorenzo@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85DE3130E39 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level: 
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 wI0uXZ2ZuZeo for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:47:37 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 218F11277CC for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:47:37 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id j81-v6so136280ite.0 for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:47:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dPaEQz7MkJT0hMwAXRl8jjgreHWTIeXEOCGOd4czN38=; b=XndBcIZq1UKTtKvcozzqVJ33x1LKU7MuaWSQxE0EwG488titoGyjHxq0l/XUUxLyKw a3cCHYiHCnAvZsOzOkBO3INhiROAhhMBjzc93zabP0x5zz4w5ae5QcJVTqfhH2YmY481 j24mnvoaGPS4fz+E/vG+TEaCLtrvaP7LEUn1vX7Xj4YDh/tHA3ld2yekubg3nP9xsdWE Vm3QtbyGUgN+8TlPvCnx5eLDtgEDyjK5VTXmBI0aoBRFcf9CsK9Qz55l5ItU8rNYkzV1 31/2As+iYz6xspEOcOAWE65AB0HZaGSEEkoQH2zNyCJGw2r9on/XKSqwuZxH24STGGjZ ENMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dPaEQz7MkJT0hMwAXRl8jjgreHWTIeXEOCGOd4czN38=; b=qIdYyL3QwdYKwGTxMqYCAYuYlXhTckG7m62VP7UQPZK1L8lo1DNhsGleOte3LnAsbn MrnrNIAOnbJsAr+Mp/DmLVngeVdLGIAKVgCOeXgYhmfKez3lRgE4B2rIPSlH8gxamImu bqXzhn7gEEXWZVGfawlJS8+HRYvjnw1K+14cqJXloUMYPvXn+AQkWgyploo4Wuzy4Vwz z0OCPBVqiv7hYckL6GEm3qjyWA81omWaZfGUFyO1j2xAcg+vwtdr86nAHqsquW2GJkWF OkXUrPxufQwFv8ughqjKvT1lqiI6Z1B4jHDcObacL0rEOdLY3JFic2zvo4ZEuTNSw1Ys xw5A==
X-Gm-Message-State: APzg51AtMTmsdQ1HB2+K1vsleQ0scSLZ6RWyMjsRkEMSSdbqY1unjz81 qGVHlZp351IPnwhnTbvAgeo8qr3Q+OhNH+PBXqvYib1a
X-Google-Smtp-Source: ANB0Vdb6UEk0Gr4ZwXsij2MrXis7DwhoYZvk4jioqE7io+aaWuw4jMntgDpBCbIXgFIxhCIe0L9uOB+pqZGLuxJntyQ=
X-Received: by 2002:a02:c4c6:: with SMTP id h6-v6mr21809989jaj.26.1536648456102;  Mon, 10 Sep 2018 23:47:36 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org>
In-Reply-To: <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 11 Sep 2018 15:47:24 +0900
Message-ID: <CAKD1Yr17t0_V4_rCsPSRRf_=Z6y2onoOyVM7OV9Ub3GXbpUKfw@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005f6af7057592d95d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uFV6uva0k4phH5KelPOKryFXPnU>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 06:47:40 -0000

--0000000000005f6af7057592d95d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

You don't need stateful addressing (which has lots of downsides) to solve
this problem. SAVI-FCFS is sufficient.

On Tue, 11 Sep 2018, 15:15 Ole Troan, <otroan@employees.org> wrote:

> You might want to include that this problem has been solved with a
> stateful address assignment mechanism like DHCP, possibly combined with
> SAVI.
>
> The ND ARO option would also have solved this.
>
> Or you could deploy P2P Ethernet, where there is no address resolution.
>
> Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=E2=
=80=99s
> even less robust in wired networks (blocked ports).
>
> Cheers
> Ole
>
> > On 10 Sep 2018, at 16:25, Ron Bonica <rbonica@juniper.net> wrote:
> >
> > Folks,
> >
> > Each week between now and IETF 103, we will review and discuss one draf=
t
> with an eye towards progressing it.
> >
> > This week, please review and comment on
> draft-jaeggli-v6ops-indefensible-nd.
> >
> >                                      Fred and Ron
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--0000000000005f6af7057592d95d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">You don&#39;t need stateful addressing (which has lots of=
 downsides) to solve this problem. SAVI-FCFS is sufficient.</div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr">On Tue, 11 Sep 2018, 15:15 Ole Troan,=
 &lt;<a href=3D"mailto:otroan@employees.org">otroan@employees.org</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">You might want to include tha=
t this problem has been solved with a stateful address assignment mechanism=
 like DHCP, possibly combined with SAVI. <br>
<br>
The ND ARO option would also have solved this. <br>
<br>
Or you could deploy P2P Ethernet, where there is no address resolution. <br=
>
<br>
Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=E2=80=
=99s even less robust in wired networks (blocked ports). <br>
<br>
Cheers <br>
Ole<br>
<br>
&gt; On 10 Sep 2018, at 16:25, Ron Bonica &lt;<a href=3D"mailto:rbonica@jun=
iper.net" target=3D"_blank" rel=3D"noreferrer">rbonica@juniper.net</a>&gt; =
wrote:<br>
&gt; <br>
&gt; Folks,<br>
&gt; <br>
&gt; Each week between now and IETF 103, we will review and discuss one dra=
ft with an eye towards progressing it.<br>
&gt; <br>
&gt; This week, please review and comment on draft-jaeggli-v6ops-indefensib=
le-nd.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Fred and Ron=
<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"noreferrer"=
>v6ops@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"norefer=
rer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6o=
ps</a><br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"noreferrer">v6op=
s@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a=
><br>
</blockquote></div>

--0000000000005f6af7057592d95d--


From nobody Mon Sep 10 23:49:04 2018
Return-Path: <ek@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDB2130E39 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level: 
X-Spam-Status: No, score=-17.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 wDNNbHq5bFzr for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:49:00 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 BA7121277CC for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:48:59 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id 207-v6so101729wme.5 for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:48:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pzESZ93gHexuGe2AQ4f9Fs5ZLlFH4hbSs1uSlqsv230=; b=DWCgLax4uRWGa3YkJKNLAVpjCjxR9WMFwY7z5RXOiRWE5L7/B9KJoSIrz9dEUDFNDP PXKZr6+W552zZcA4K2MhNC7qlYQ+D3roeSG3foqHTQ5ZTYuFdqzYLSnYtN80ZouUo/KL CWDD0UKsCMdgPUhu61UJ6HJRJVOUKIhfViEi6UTG8qwBtAb63kIJKUIhj7tgfVWeYX0+ 35FBySX6mrMPwB+fsBCSLSO8I5SLKvxyUi9bJH/U8cpgQAqG/18yAk36gW/9QbLk1mQ2 /seOpsup/CE7TNA603SgRtALoWQ74PT2kK4/zv54Tmz3ypZgKE8euLN8DCstSocYYsLp ZxTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pzESZ93gHexuGe2AQ4f9Fs5ZLlFH4hbSs1uSlqsv230=; b=DffuDrJ6EQ3pOe5Zhz2eMCTwW7gQ9oFbOQ8HLY7sydRlQSHAxBxrQFBuD8dtDFaobO I7+zcPsSkdpPqTcajOqN8kony1ubdOUVZh+EtW2kkPpvgfUQirqmB0L4nkd7IjP5wAEl RBMM4m6+NMKTOuh0sfqoo/x7Nz1oxPnjUReR3ncDuMpUHGExGaOPOUGgpDDQhsoOcf0i aV91v8UXp5Y/GJBQa8YucneSyLLWvBuWodr7A4TIlubSDT4ZWTu0vX0xe6szVFTS5f0a iizJPqi+uAy8YBeScbj281QNF9E3+pmHarbPXkJIrcULF1jX4PZ9EWs2IZ0Kk61/PBbH D8ig==
X-Gm-Message-State: APzg51C0aysk4MtAlMY8UW+QyJhYZbMfjxJ/XXrHRjfv1oVWpef7f1Wg MkKorR/XnEz10YDUCgubGba967go6g+XYvOcMQFjIA==
X-Google-Smtp-Source: ANB0VdZAfYNg2Y40bxoTb/E3TCzDsvRfVw8GSpI9d2iYr0ZbOqtp4MFgvTSGI9yF+EPUiYLexgbt+v/kJ9O7x7lv1NU=
X-Received: by 2002:a1c:1bca:: with SMTP id b193-v6mr324329wmb.6.1536648537812;  Mon, 10 Sep 2018 23:48:57 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org> <CAAedzxrtOrQrqZw-os45sRA2QT2gT7sE8CiuGxFFEssKx26iyw@mail.gmail.com> <FD8E7FA1-86F3-4193-ABBF-97AF25CEE565@employees.org>
In-Reply-To: <FD8E7FA1-86F3-4193-ABBF-97AF25CEE565@employees.org>
From: Erik Kline <ek@google.com>
Date: Tue, 11 Sep 2018 15:48:45 +0900
Message-ID: <CAAedzxpdWEOn21ci0P5zuU8AgFe99kr_kYkAtFwNE90hREqL-g@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="00000000000047970a057592def8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/G4vIpopLaa49v4w7SNYTfYe8_sk>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 06:49:02 -0000

--00000000000047970a057592def8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 11 Sep 2018 at 15:34, Ole Troan <otroan@employees.org> wrote:
>
> Erik,
>
> > On 11 Sep 2018, at 08:22, Erik Kline <ek@google.com> wrote:
> >
> >> On Tue, 11 Sep 2018 at 15:15, Ole Troan <otroan@employees.org> wrote:
> >>
> >> You might want to include that this problem has been solved with a sta=
teful address assignment mechanism like DHCP, possibly combined with SAVI.
> >>
> >> The ND ARO option would also have solved this.
> >>
> >> Or you could deploy P2P Ethernet, where there is no address resolution=
.
> >>
> >> Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=
=E2=80=99s even less robust in wired networks (blocked ports).
> >
> > But...in such a network NS/NA works?  (alternatively: what does
> > "blocked" mean here)
>
> NS/NA has retransmission.
> Blocked as in 802.1D. Default 30s from link-up until port will switch use=
r traffic.

Do hosts receive RAs during this 30s window?  If not, then the
blocking affects DAD for link-local addresses, but not necessarily for
GUAs.

NOTE: I am most definitely /not/ attempting to argue that DAD is reliable. =
 ;-)

I had a notion about matching forwarding addresses not in cache
against the MLD info associated with the /104 for a given forwarding
destination address.  Seems like routers gathering MLD data might use
that list to prioritize forwarding for destinations not yet in the
neighbor cache.

> DAD is unreliable for lots of reasons . Didn=E2=80=99t we write a draft o=
n that?

https://tools.ietf.org/html/draft-yourtchenko-6man-dad-issues ?

> Ole
>
>
> >>
> >>> On 10 Sep 2018, at 16:25, Ron Bonica <rbonica@juniper.net> wrote:
> >>>
> >>> Folks,
> >>>
> >>> Each week between now and IETF 103, we will review and discuss one dr=
aft with an eye towards progressing it.
> >>>
> >>> This week, please review and comment on draft-jaeggli-v6ops-indefensi=
ble-nd.
> >>>
> >>>                                     Fred and Ron
> >>>
> >>> _______________________________________________
> >>> v6ops mailing list
> >>> v6ops@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/v6ops
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
>

--00000000000047970a057592def8
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS3wYJKoZIhvcNAQcCoIIS0DCCEswCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBFMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEXDCCA0SgAwIBAgIMPipSifuL4Tx7dmsbMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE4MDcxNTA2MzcxOFoXDTE5MDEx
MTA2MzcxOFowHjEcMBoGCSqGSIb3DQEJAQwNZWtAZ29vZ2xlLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBALkHIP2fSFudoue2xAkNBouFm2EulKm/RKnsxmEw4dSbxQC2Mt72Ga/t
ySyn6PMSAgsyjgP0bKJZf/NHBzDGuSKpY09UgBupEUEejwR4d5vrHk8IJNfIDTQ+Ygv4krlQmkO0
Qh/GB1y4PxtIn0tVfGfB7s3Z7wWyYbN1JrUrxAhKTpvkbJLRF1n/fKgv1nfUYyY9se4cZE3XQbJV
2biA0ATE8hw55TPa9FTv+QuWbAWXlTfsvz8SxdL8cs1HXVzBwi7kpzm2LbLictqUYotBdrCk2JQ9
ZkICHIpunwWnfTfNJ1Vt7MYL8worV+Y0TfBP0Uw1IG8qQ1Fdie3quVfdAoUCAwEAAaOCAWowggFm
MBgGA1UdEQQRMA+BDWVrQGdvb2dsZS5jb20wUAYIKwYBBQUHAQEERDBCMEAGCCsGAQUFBzAChjRo
dHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24uY29tL2NhY2VydC9nc2h2c21pbWVjYTEuY3J0MB0GA1Ud
DgQWBBQw12fRZdlCj/XWgp08Ky/Ct82W7DAfBgNVHSMEGDAWgBTLOBKwx5nAeJKMsyGV5vQmYsDg
PzBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9i
YWxzaWduLmNvbS9yZXBvc2l0b3J5LzA7BgNVHR8ENDAyMDCgLqAshipodHRwOi8vY3JsLmdsb2Jh
bHNpZ24uY29tL2dzaHZzbWltZWNhMS5jcmwwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDANBgkqhkiG9w0BAQsFAAOCAQEAsH2eOQwQDXJ145YZFyjaTxqiVS9t
F3F65BSt739euYxmyoYFAFgBVwRLXBjD0eTRqz6W6O9FC3ZPzsIup/DXZZlPNPitbqGA391usTKN
YHYsBchdjOocgO8gNokf3H4yvjUv6699ncUQXX+d0deUo38jOa4+OujSIQbz+PUicageFuFcraDO
MV5VMHYtn/1Ngkrw4JSaf2nv1WTfUBQyRRorMCPXVJZLEm8K0apTK2RHaxnFvXHJjFPkLLsJSwmQ
RCeC98jyQdFHPQank0x8KmEo+nlu2d0X0n/aLibqG7rRSVKINpvLv6C3j8P4b1t1Fu23J6OYkWUx
Rz/Rs1hfPTGCAl4wggJaAgEBMFwwTDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExIjAgBgNVBAMTGUdsb2JhbFNpZ24gSFYgUy9NSU1FIENBIDECDD4qUon7i+E8e3ZrGzAN
BglghkgBZQMEAgEFAKCB1DAvBgkqhkiG9w0BCQQxIgQglUr4P3lhhznAfn99AUr7vpv7eOIsEONA
024B5xzG/u4wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTgwOTEx
MDY0ODU4WjBpBgkqhkiG9w0BCQ8xXDBaMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMAsGCSqGSIb3DQEBCjALBgkqhkiG9w0BAQcwCwYJYIZIAWUDBAIB
MA0GCSqGSIb3DQEBAQUABIIBAEWYNwuP4xyA01wQ5bVJ2Bq5h2sayM/ug5p1ktepjoX3/XJIDnCd
fbAhLOsMLskXGjUbdG3zQStTxxJWvsc/FqQ2enEcJAicEogbeIKT+Cy8ReMpm7FhVkozcCUBp33I
lkQ0TZM6+lwhNxMpsH0ZRJKl4KQ3YHiD7GWK3UowsA7p5pR/02WpUM9AsaxN4J2YLVb04uaXHQVt
BtgCcq80dlP+f1Pc3MBI8Fxrgjvp1sqlrN3Atbe+OkfnLAHrqGjQ8pfcYm6DVvwoVv/KLMtCd8N+
cswDo0c6pHBMDNoMeJo+biJZVl3akkQaIcX/rZrJG/jT+TfrlGSlfGc4ddOF40A=
--00000000000047970a057592def8--


From nobody Mon Sep 10 23:56:20 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2A23130E39 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 tN86K8vmPWL8 for <v6ops@ietfa.amsl.com>; Mon, 10 Sep 2018 23:56:16 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79F241277CC for <v6ops@ietf.org>; Mon, 10 Sep 2018 23:56:16 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 73337FECBB47; Tue, 11 Sep 2018 06:56:15 +0000 (UTC)
Content-Type: multipart/alternative; boundary=Apple-Mail-43D44A7A-170D-4EF6-8CFE-8BD992E80762
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <CAKD1Yr17t0_V4_rCsPSRRf_=Z6y2onoOyVM7OV9Ub3GXbpUKfw@mail.gmail.com>
Date: Tue, 11 Sep 2018 08:56:12 +0200
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <DB0DFDBA-357D-46A0-91B2-7435E1F6D559@employees.org>
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org> <CAKD1Yr17t0_V4_rCsPSRRf_=Z6y2onoOyVM7OV9Ub3GXbpUKfw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3H4T7DAE4ngKhwMYnBaq8OhvGJw>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 06:56:19 -0000

--Apple-Mail-43D44A7A-170D-4EF6-8CFE-8BD992E80762
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



> On 11 Sep 2018, at 08:47, Lorenzo Colitti <lorenzo@google.com> wrote:
>=20
> You don't need stateful addressing (which has lots of downsides) to solve t=
his problem. SAVI-FCFS is sufficient.

SLAAC and SAVI FCFS wouldn=E2=80=99t detect a quiet listening host. And I al=
most managed to not make any comments about the horrible state everywhere la=
yer violating properties of SAVI.

ARO, DHCP or P2P are the only reliable ways of doing this as far as I know.

If you=E2=80=99re happy with, works most of the time, then sure...

Ole

>=20
>> On Tue, 11 Sep 2018, 15:15 Ole Troan, <otroan@employees.org> wrote:
>> You might want to include that this problem has been solved with a statef=
ul address assignment mechanism like DHCP, possibly combined with SAVI.=20
>>=20
>> The ND ARO option would also have solved this.=20
>>=20
>> Or you could deploy P2P Ethernet, where there is no address resolution.=20=

>>=20
>> Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=E2=80=
=99s even less robust in wired networks (blocked ports).=20
>>=20
>> Cheers=20
>> Ole
>>=20
>> > On 10 Sep 2018, at 16:25, Ron Bonica <rbonica@juniper.net> wrote:
>> >=20
>> > Folks,
>> >=20
>> > Each week between now and IETF 103, we will review and discuss one draf=
t with an eye towards progressing it.
>> >=20
>> > This week, please review and comment on draft-jaeggli-v6ops-indefensibl=
e-nd.
>> >=20
>> >                                      Fred and Ron
>> >=20
>> > _______________________________________________
>> > v6ops mailing list
>> > v6ops@ietf.org
>> > https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops

--Apple-Mail-43D44A7A-170D-4EF6-8CFE-8BD992E80762
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div></div><div><br></div><div><br>On 11 Se=
p 2018, at 08:47, Lorenzo Colitti &lt;<a href=3D"mailto:lorenzo@google.com">=
lorenzo@google.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><di=
v><div dir=3D"auto">You don't need stateful addressing (which has lots of do=
wnsides) to solve this problem. SAVI-FCFS is sufficient.</div></div></blockq=
uote><div><br></div><div>SLAAC and SAVI FCFS wouldn=E2=80=99t detect a quiet=
 listening host. And I almost managed to not make any comments about the hor=
rible state everywhere layer violating properties of SAVI.</div><div><br></d=
iv><div>ARO, DHCP or P2P are the only reliable ways of doing this as far as I=
 know.</div><div><br></div><div>If you=E2=80=99re happy with, works most of t=
he time, then sure...</div><div><br></div><div>Ole</div><br><blockquote type=
=3D"cite"><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, 11 Se=
p 2018, 15:15 Ole Troan, &lt;<a href=3D"mailto:otroan@employees.org">otroan@=
employees.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You migh=
t want to include that this problem has been solved with a stateful address a=
ssignment mechanism like DHCP, possibly combined with SAVI. <br>
<br>
The ND ARO option would also have solved this. <br>
<br>
Or you could deploy P2P Ethernet, where there is no address resolution. <br>=

<br>
Depending on DAD for this lie Lorenzo proposed seems ill-advised. It=E2=80=99=
s even less robust in wired networks (blocked ports). <br>
<br>
Cheers <br>
Ole<br>
<br>
&gt; On 10 Sep 2018, at 16:25, Ron Bonica &lt;<a href=3D"mailto:rbonica@juni=
per.net" target=3D"_blank" rel=3D"noreferrer">rbonica@juniper.net</a>&gt; wr=
ote:<br>
&gt; <br>
&gt; Folks,<br>
&gt; <br>
&gt; Each week between now and IETF 103, we will review and discuss one draf=
t with an eye towards progressing it.<br>
&gt; <br>
&gt; This week, please review and comment on draft-jaeggli-v6ops-indefensibl=
e-nd.<br>
&gt; <br>
&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Fred and Ron<br=
>
&gt; <br>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"noreferrer">=
v6ops@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferr=
er noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops=
</a><br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"noreferrer">v6ops=
@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><=
br>
</blockquote></div>
</div></blockquote></body></html>=

--Apple-Mail-43D44A7A-170D-4EF6-8CFE-8BD992E80762--


From nobody Tue Sep 11 00:32:10 2018
Return-Path: <pthubert@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE7C130E65 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 nTche8_b51mt for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:32:05 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97B461294D7 for <v6ops@ietf.org>; Tue, 11 Sep 2018 00:32:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4456; q=dns/txt; s=iport; t=1536651125; x=1537860725; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=/Nyd04DqIzFuQaU38b72Ct/Mvc8RKHF4COmz3qHiZRg=; b=GuSQxXjzLzDC0OQmz2tC6IuZ03JVSfH/lEozdwW7URd1EJ4/QLKo5PIx 0l6I2XS3kKr2rQfULuuwikqGfa/t5V939piIWDvXHNdjF57S6pfukMjp0 BcTP/fO+FwRs7UDOu+YbP8YoyDqwxdHZ5cu3jDRb+LbhmVIaIdk7TxCXE U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C3BgC/bpdb/49dJa1bGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYMkKmV/KINylDKCDYM9lBsDUwsYC4RJAheDaCE4FAECAQE?= =?us-ascii?q?CAQECbRwMhTgBAQEBAgEBASEROgsFCwIBCBgCAiYCAgIlCxUQAQEEDgWDIQG?= =?us-ascii?q?BeQgPpGmBLoQuAT2FGQWBC4gYgUIXgUE/gRInH4JMgxsBAQIBhF8xgiYCnAg?= =?us-ascii?q?JAoY3iUkXgUCEP4hxizqILAIRFIElNCE0gSFwFTsqAYJBgiUXegEEh1qFPm8?= =?us-ascii?q?Bi04HgkQBAQ?=
X-IronPort-AV: E=Sophos;i="5.53,359,1531785600"; d="scan'208";a="170004032"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Sep 2018 07:32:04 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id w8B7W4AJ017569 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 11 Sep 2018 07:32:04 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 11 Sep 2018 02:32:03 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Tue, 11 Sep 2018 02:32:03 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Erik Kline <ek=40google.com@dmarc.ietf.org>
CC: Ole Troan <otroan@employees.org>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-jaeggli-v6ops-indefensible-nd
Thread-Index: AdRJEhJUITkGHPnURMm4CycU7Aa+VQArqikAAAA8DYAAAG06AAAAgTGA//+4SEE=
Date: Tue, 11 Sep 2018 07:32:03 +0000
Message-ID: <069A1C98-208A-44C4-941B-E9B0BCE26796@cisco.com>
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org> <CAAedzxrtOrQrqZw-os45sRA2QT2gT7sE8CiuGxFFEssKx26iyw@mail.gmail.com> <FD8E7FA1-86F3-4193-ABBF-97AF25CEE565@employees.org>, <CAAedzxpdWEOn21ci0P5zuU8AgFe99kr_kYkAtFwNE90hREqL-g@mail.gmail.com>
In-Reply-To: <CAAedzxpdWEOn21ci0P5zuU8AgFe99kr_kYkAtFwNE90hREqL-g@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4YqjTnIAjYItJjgSgAPph3h2_hg>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 07:32:09 -0000

DQpXZSBoYXZlIGdyZWF0bHkgaW1wcm92ZWQgdGhlIEFSTyBhdCA2bG8gYW5kIHRyaWVkIGluIHRo
ZSBwcm9jZXNzIHRvIGFsbGV2aWF0ZSBMb3JlbnpvIOKAmHMgY29uY2VybnMgYWJvdXQgaXQgYmVp
bmcgYW4gdW5kZXNpcmFibGUgd2F5IHRvIHJlbW92ZSBmcmVlZG9tIG9mIGFkZHJlc3MgZm9ybWF0
aW9uLiBXZSBhbHNvIGRpc2N1c3NlZCBCb2LigJlzIGNvbmNlcm5zIG9uIElQdjYgc3RhYmlsaXR5
IGF0IGxlbmd0aCBzbyBob3BlZnVsbHkgd2UgYXJlIHBhc3NlZCB0aGF0IGFzIHdlbGwuDQoNClRo
ZSBuZXcgQVJPIChFQVJPKSBpcyBjbGVhcmx5IGludGVuZGVkIHRvIHByb3RlY3QgdGhlIGFkZHJl
c3Mgb3duZXJzaGlwLiBUaGUgTlAgQUQgZHJhZnQgYXNzb2NpYXRlcyBhIGNyeXB0byB0b2tlbiB0
byB0aGUgcmVnaXN0cmF0aW9uIGJ1dCBkb2VzIG5vdCBjb25zdHJhaW4gdGhlIElJRCBsaWtlIFNF
TkQgZGlkLiANCg0KVGhlIEVBUk8gaXMgYWxyZWFkeSByZWZlcmVuY2VkIGJ5IGEgbnVtYmVyIG9m
IGRyYWZ0cyAoYXQgUk9MTCA2bG8gYW5kIFJJRlQpIGFzIHRoZSBhYnN0cmFjdCB3YXkgZm9yIGEg
aG9zdCB0byBhbm5vdW5jZSBpdHMgYWRkcmVzc2VzIHRvIHNlbGVjdGVkIHJvdXRlcnMgYW5kIGdl
dCBzZXJ2aWNlcyBiYWNrLCBlZyByb3V0aW5nIG9yIE5EIHByb3h5Lg0KDQpSZWdhcmRzLA0KDQpQ
YXNjYWwNCg0KPiBMZSAxMSBzZXB0LiAyMDE4IMOgIDA4OjQ5LCBFcmlrIEtsaW5lIDxlaz00MGdv
b2dsZS5jb21AZG1hcmMuaWV0Zi5vcmc+IGEgw6ljcml0IDoNCj4gDQo+PiBPbiBUdWUsIDExIFNl
cCAyMDE4IGF0IDE1OjM0LCBPbGUgVHJvYW4gPG90cm9hbkBlbXBsb3llZXMub3JnPiB3cm90ZToN
Cj4+IA0KPj4gRXJpaywNCj4+IA0KPj4+PiBPbiAxMSBTZXAgMjAxOCwgYXQgMDg6MjIsIEVyaWsg
S2xpbmUgPGVrQGdvb2dsZS5jb20+IHdyb3RlOg0KPj4+PiANCj4+Pj4gT24gVHVlLCAxMSBTZXAg
MjAxOCBhdCAxNToxNSwgT2xlIFRyb2FuIDxvdHJvYW5AZW1wbG95ZWVzLm9yZz4gd3JvdGU6DQo+
Pj4+IA0KPj4+PiBZb3UgbWlnaHQgd2FudCB0byBpbmNsdWRlIHRoYXQgdGhpcyBwcm9ibGVtIGhh
cyBiZWVuIHNvbHZlZCB3aXRoIGEgc3RhdGVmdWwgYWRkcmVzcyBhc3NpZ25tZW50IG1lY2hhbmlz
bSBsaWtlIERIQ1AsIHBvc3NpYmx5IGNvbWJpbmVkIHdpdGggU0FWSS4NCj4+Pj4gDQo+Pj4+IFRo
ZSBORCBBUk8gb3B0aW9uIHdvdWxkIGFsc28gaGF2ZSBzb2x2ZWQgdGhpcy4NCj4+Pj4gDQo+Pj4+
IE9yIHlvdSBjb3VsZCBkZXBsb3kgUDJQIEV0aGVybmV0LCB3aGVyZSB0aGVyZSBpcyBubyBhZGRy
ZXNzIHJlc29sdXRpb24uLg0KPj4+PiANCj4+Pj4gRGVwZW5kaW5nIG9uIERBRCBmb3IgdGhpcyBs
aWUgTG9yZW56byBwcm9wb3NlZCBzZWVtcyBpbGwtYWR2aXNlZC4gSXTigJlzIGV2ZW4gbGVzcyBy
b2J1c3QgaW4gd2lyZWQgbmV0d29ya3MgKGJsb2NrZWQgcG9ydHMpLg0KPj4+IA0KPj4+IEJ1dC4u
LmluIHN1Y2ggYSBuZXR3b3JrIE5TL05BIHdvcmtzPyAgKGFsdGVybmF0aXZlbHk6IHdoYXQgZG9l
cw0KPj4+ICJibG9ja2VkIiBtZWFuIGhlcmUpDQo+PiANCj4+IE5TL05BIGhhcyByZXRyYW5zbWlz
c2lvbi4NCj4+IEJsb2NrZWQgYXMgaW4gODAyLjFELiBEZWZhdWx0IDMwcyBmcm9tIGxpbmstdXAg
dW50aWwgcG9ydCB3aWxsIHN3aXRjaCB1c2VyIHRyYWZmaWMuDQo+IA0KPiBEbyBob3N0cyByZWNl
aXZlIFJBcyBkdXJpbmcgdGhpcyAzMHMgd2luZG93PyAgSWYgbm90LCB0aGVuIHRoZQ0KPiBibG9j
a2luZyBhZmZlY3RzIERBRCBmb3IgbGluay1sb2NhbCBhZGRyZXNzZXMsIGJ1dCBub3QgbmVjZXNz
YXJpbHkgZm9yDQo+IEdVQXMuDQo+IA0KPiBOT1RFOiBJIGFtIG1vc3QgZGVmaW5pdGVseSAvbm90
LyBhdHRlbXB0aW5nIHRvIGFyZ3VlIHRoYXQgREFEIGlzIHJlbGlhYmxlLiAgOy0pDQo+IA0KPiBJ
IGhhZCBhIG5vdGlvbiBhYm91dCBtYXRjaGluZyBmb3J3YXJkaW5nIGFkZHJlc3NlcyBub3QgaW4g
Y2FjaGUNCj4gYWdhaW5zdCB0aGUgTUxEIGluZm8gYXNzb2NpYXRlZCB3aXRoIHRoZSAvMTA0IGZv
ciBhIGdpdmVuIGZvcndhcmRpbmcNCj4gZGVzdGluYXRpb24gYWRkcmVzcy4gIFNlZW1zIGxpa2Ug
cm91dGVycyBnYXRoZXJpbmcgTUxEIGRhdGEgbWlnaHQgdXNlDQo+IHRoYXQgbGlzdCB0byBwcmlv
cml0aXplIGZvcndhcmRpbmcgZm9yIGRlc3RpbmF0aW9ucyBub3QgeWV0IGluIHRoZQ0KPiBuZWln
aGJvciBjYWNoZS4NCj4gDQo+PiBEQUQgaXMgdW5yZWxpYWJsZSBmb3IgbG90cyBvZiByZWFzb25z
IC4gRGlkbuKAmXQgd2Ugd3JpdGUgYSBkcmFmdCBvbiB0aGF0Pw0KPiANCj4gaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LXlvdXJ0Y2hlbmtvLTZtYW4tZGFkLWlzc3VlcyA/DQo+IA0K
Pj4gT2xlDQo+PiANCj4+IA0KPj4+PiANCj4+Pj4+IE9uIDEwIFNlcCAyMDE4LCBhdCAxNjoyNSwg
Um9uIEJvbmljYSA8cmJvbmljYUBqdW5pcGVyLm5ldD4gd3JvdGU6DQo+Pj4+PiANCj4+Pj4+IEZv
bGtzLA0KPj4+Pj4gDQo+Pj4+PiBFYWNoIHdlZWsgYmV0d2VlbiBub3cgYW5kIElFVEYgMTAzLCB3
ZSB3aWxsIHJldmlldyBhbmQgZGlzY3VzcyBvbmUgZHJhZnQgd2l0aCBhbiBleWUgdG93YXJkcyBw
cm9ncmVzc2luZyBpdC4NCj4+Pj4+IA0KPj4+Pj4gVGhpcyB3ZWVrLCBwbGVhc2UgcmV2aWV3IGFu
ZCBjb21tZW50IG9uIGRyYWZ0LWphZWdnbGktdjZvcHMtaW5kZWZlbnNpYmxlLW5kLg0KPj4+Pj4g
DQo+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEZyZWQgYW5kIFJvbg0K
Pj4+Pj4gDQo+Pj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPj4+Pj4gdjZvcHMgbWFpbGluZyBsaXN0DQo+Pj4+PiB2Nm9wc0BpZXRmLm9yZw0KPj4+
Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcw0KPj4+PiANCj4+
Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4g
djZvcHMgbWFpbGluZyBsaXN0DQo+Pj4+IHY2b3BzQGlldGYub3JnDQo+Pj4+IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjZvcHMNCj4+IA0KPiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB2Nm9wcyBtYWlsaW5nIGxpc3QNCj4g
djZvcHNAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92
Nm9wcw0K


From nobody Tue Sep 11 00:50:31 2018
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47976130E6B for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level: 
X-Spam-Status: No, score=-1.497 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 kbqaUy92aJ_E for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:50:27 -0700 (PDT)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 95494130E65 for <v6ops@ietf.org>; Tue, 11 Sep 2018 00:50:27 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id v198-v6so27692485oif.9 for <v6ops@ietf.org>; Tue, 11 Sep 2018 00:50:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0g/8gQsTqKJzQOrLt7hvFRIsiZamFUb5P7XhXlxpfJs=; b=PCLIuJXe75nf0QGkRfH5aRQhEA9GzNGcfVRkNf5BAJN4KLr6z43PQz/uCpWFzQh81j zQs3GrqbBkgiDwxQ0HLV62Mv7nDYj01H48deDlygsGyu2GcKiLFtrCqrJko1T0aM7X3O hIbemFwtozHL1Ei2I3wOA56JGDAjNbm1UJhDMmLr7JWdiIn8DlF4/xkpzOBEn4dyxY2X F6YpBzKqXiyqVec98g1cVZOBOHiL8VV/c/mYIsFE0k8JSwNAbH8AR3CxTIuDfg4knv8t xoMR8Ty/PnOV40OOANpBmYr/WMDgTzLu3PzU7KXe9gsYT9RimU+oLnRVKNvK4j7y0gLu aPRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0g/8gQsTqKJzQOrLt7hvFRIsiZamFUb5P7XhXlxpfJs=; b=POHVXswb+4E34wd9Y74PYz4qXZeuCVfXGGqc2gq5Q6iSZFIiijhFm9EM/iJqls6bQP lOBD2BckooB9vVtaPZK0dmbJ9gV4/piwUKGV8Y95tPYvtlosFiAweyIJ3Vbp0PdJo6LN FPPTyCNTT5uAkome9NnLcFDhOvdsdKI0pf1FINWD4GxF7Twc72il3BXB2OHIF9NR5Zej fsiWIs36VkFcd/Xl+saAaMUW5yUQHd+rGBpujreurXJiExTn+e40ECiE1To6SXhcZ26x 2GiS2uDAvBrCT6ppS2bdQiHXSBi+MU3iFmDFy+Cr/7iUzsiw8+XkKRmVDlolITltCd9m 4DGg==
X-Gm-Message-State: APzg51B540XNkcNLm2NzLsAoAz8x1bOtqv7Qu8qMoJN2/pGdzzTDP221 hVWMewzkawfYpN0A94F9It2LtRTC4Hif/fcUQEtU3A==
X-Google-Smtp-Source: ANB0VdbzfejG/uB+0QTpfKmQWrRWqPpWoocfqkeIjiSQZ+3NKevZiWuG+YBO9iO5fW6DhzeNvyipujjGa6cIajljEvs=
X-Received: by 2002:aca:3606:: with SMTP id d6-v6mr27443843oia.327.1536652226883;  Tue, 11 Sep 2018 00:50:26 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <CAKD1Yr3ffVL=cdkK4Z+KhO6P7UoyQ=p_PMp2+Vumweh36rvQ8g@mail.gmail.com>
In-Reply-To: <CAKD1Yr3ffVL=cdkK4Z+KhO6P7UoyQ=p_PMp2+Vumweh36rvQ8g@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Tue, 11 Sep 2018 17:50:15 +1000
Message-ID: <CAO42Z2z+zYz_yy8kNCkmqEdGKVUN2CdYkoLyfWBzHOhCUOnxKw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: joel jaeggli <joelja@bogus.com>, v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002074b5057593bac6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ABqE7CHsjJ3CmE4Ct5XxBN035K8>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 07:50:29 -0000

--0000000000002074b5057593bac6
Content-Type: text/plain; charset="UTF-8"

On Tue., 11 Sep. 2018, 15:35 Lorenzo Colitti, <lorenzo=
40google.com@dmarc.ietf.org> wrote:

> On Mon, Sep 10, 2018 at 11:25 PM Ron Bonica <rbonica@juniper.net> wrote:
>
>> This week, please review and comment on
>> draft-jaeggli-v6ops-indefensible-nd.
>>
>
> It seems easy to solve this problem by saying that routers can create
> speculative incomplete ND cache entries from DAD probes, and that such
> incomplete entries take precedence over incomplete entries due to forwarded
> packets. Because all addresses require DAD,
>

Actually, on-link anycast addresses don't, as DAD is specifically disabled
for them. Granted, on-link anycast aren't common.

I've been meaning to forward to Joel this draft by Joel et. al. from
Ericsson for reference that describes using DAD for ND DoS protection.

https://tools.ietf.org/html/draft-halpern-6man-nd-pre-resolve-addr-00

Regards,
Mark.

this would ensure that any host that is on the router's link would have ND
> cache entries for all its addresses as soon as the host joins the link.
>
> In the presence of non-zero packet loss, this obviously does not increase
> the reliability to 100%. However, on most networks it probably lowers the
> payoff to such an extent to make the attack not useful in practice.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--0000000000002074b5057593bac6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">=
On Tue., 11 Sep. 2018, 15:35 Lorenzo Colitti, &lt;lorenzo=3D<a href=3D"mail=
to:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.org</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmai=
l_quote"><div dir=3D"ltr">On Mon, Sep 10, 2018 at 11:25 PM Ron Bonica &lt;<=
a href=3D"mailto:rbonica@juniper.net" target=3D"_blank" rel=3D"noreferrer">=
rbonica@juniper.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
This week, please review and comment on draft-jaeggli-v6ops-indefensible-nd=
.<br></blockquote><div><br></div><div>It seems easy to solve this problem b=
y saying that routers can create speculative incomplete ND cache entries fr=
om DAD probes, and that such incomplete entries take precedence over incomp=
lete entries due to forwarded packets. Because all addresses require DAD, <=
/div></div></div></blockquote></div></div><div dir=3D"auto"><br></div><div =
dir=3D"auto">Actually, on-link anycast addresses don&#39;t, as DAD is speci=
fically disabled for them. Granted, on-link anycast aren&#39;t common.</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">I&#39;ve been meaning to for=
ward to Joel this draft by Joel et. al. from Ericsson for reference that de=
scribes using DAD for ND DoS protection.</div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><a href=3D"https://tools.ietf.org/html/draft-halpern-6man-=
nd-pre-resolve-addr-00">https://tools.ietf.org/html/draft-halpern-6man-nd-p=
re-resolve-addr-00</a><br></div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">Regards,</div><div dir=3D"auto">Mark.</div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"ltr"><div class=3D"gmail_quote"><div>this would ensure that any=
 host that is on the router&#39;s link would have ND cache entries for all =
its addresses as soon as the host joins the link.</div><div><br></div><div>=
In the presence of non-zero packet loss, this obviously does not increase t=
he reliability to 100%. However, on most networks it probably lowers the pa=
yoff to such an extent to make the attack not useful in practice.</div></di=
v></div>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"noreferrer">v6op=
s@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a=
><br>
</blockquote></div></div></div>

--0000000000002074b5057593bac6--


From nobody Tue Sep 11 00:52:46 2018
Return-Path: <lorenzo@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE6C5130E68 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level: 
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 dEqB3SZvmY7Y for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:52:43 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 457C0130E65 for <v6ops@ietf.org>; Tue, 11 Sep 2018 00:52:43 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id h23-v6so281268ita.5 for <v6ops@ietf.org>; Tue, 11 Sep 2018 00:52:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9vpjmif8v01kF+PqExlD6z4FyXFo0hN5CbXO2ZsE5PU=; b=v8WJVY0J2XYljtu7Qs5vourwREwfn+i1Z4ZlsE3d9Ay4nxxPvuDXAPX8QD5LFi/QIh qFXdDP5pDLCLT9IP5KwOVox1eukv6uEg7+0mUVsOhhTalwBW8M60ZKFSP4Ve/FUZK5zm gdZFsxYPY1mpqNNO+f424fNKGDTMeWwpkteVhKUrdkxblAWsXOuSqc10qCewX5T72LXC zuAvJbj6V6Nq3SQ+kuk0ENlU1vNyvVTmQ3GuOsPee+HB2vf7R6qWHist+hIw/11jD5+f m+7tAtMUujBUyz6vttO1rNNOobetXZOlyIwKfONGjFvoFlRnrYraWRhFUnGYpp7SKp76 ypZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9vpjmif8v01kF+PqExlD6z4FyXFo0hN5CbXO2ZsE5PU=; b=NhxUwRZVCwb6KTUJ/KQMv5IpkRHFvl9X225mePi8KRfrQLFIsCUGMGADcX0d7GHx2R G9tmTBH64PnTOaHMxZ7+n/dPt1OfRIhtW9BqNmdifdtLfU/TjcaUPuiBBurvw+i6RdZP B0Qp4tbahdWehjTXLPeI9Vo8697cBP0wPJ2z7r0xF5m7wOTZAE0IG0sJvcOe4la0enYg ldG0R2ToYkwezjLEDiwpYRa8kezme56Lr7LC4v0acSFu+q35xbLZievYYRcXj6XsYt+/ +cqrtaJwbg90qvLdp1OHWD+wH6d+EJyg2UotTTKWhDaHegDGS8Eqf2Z1sKbWBXP5R5Dj Y4tA==
X-Gm-Message-State: APzg51A9z91OYLFpXowCgzZxtMuTPERywxJbLi3Ywknud5znvm7rnydi cQztu0QQKX/y+mXXl9eGqFyAJ2r3BD4FnjFJQIFYmb8rmCWkeg==
X-Google-Smtp-Source: ANB0Vdb1V8fv0MKUgEU1o98SAQX528riDcSLsTczSd2BKWmJP0vnkU4aBWhivjdp++XQFqrD06RC50OCltqSLJ5nuQ4=
X-Received: by 2002:a24:41e9:: with SMTP id b102-v6mr441636itd.19.1536652362113;  Tue, 11 Sep 2018 00:52:42 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org> <CAKD1Yr17t0_V4_rCsPSRRf_=Z6y2onoOyVM7OV9Ub3GXbpUKfw@mail.gmail.com> <DB0DFDBA-357D-46A0-91B2-7435E1F6D559@employees.org>
In-Reply-To: <DB0DFDBA-357D-46A0-91B2-7435E1F6D559@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 11 Sep 2018 16:52:30 +0900
Message-ID: <CAKD1Yr1cBKw1GMktHsGn5T7nxesZwebzedoJ3vD-Cofc7mYv6Q@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000309474057593c253"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rqxGM98ThW_jYr-0ZrCS5OgemYI>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 07:52:45 -0000

--000000000000309474057593c253
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 11, 2018 at 3:56 PM Ole Troan <otroan@employees.org> wrote:

> SLAAC and SAVI FCFS wouldn=E2=80=99t detect a quiet listening host.
>

In the real world, quiet listening hosts don't exist.

   1. Pretty much every OS these days is very chatty.
   2. The IPv6 protocol requires that you announce every IPv6 address using
   DAD.

Perhaps you mean an IP address that does not originate connections?


> And I almost managed to not make any comments about the horrible state
> everywhere layer violating properties of SAVI.
>
ARO, DHCP or P2P are the only reliable ways of doing this as far as I know.
>

If security is what you're after, then DHCPv6 is not secure without SAVI,
either. I'd argue that the whole idea of a network blocking you at L2
because of your L3 address is a layering violation, anyway.

--000000000000309474057593c253
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"lt=
r">On Tue, Sep 11, 2018 at 3:56 PM Ole Troan &lt;<a href=3D"mailto:otroan@e=
mployees.org">otroan@employees.org</a>&gt; wrote:</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"auto"><div>SLAAC and SAVI FCFS wo=
uldn=E2=80=99t detect a quiet listening host.</div></div></blockquote><div>=
<div><br></div><div>In the real world, quiet listening hosts don&#39;t exis=
t.</div><div><ol><li>Pretty much every OS these days is very chatty.</li><l=
i>The IPv6 protocol requires that you announce every IPv6 address using DAD=
.</li></ol><div>Perhaps you mean an IP address that does not originate conn=
ections?</div></div></div><div>=C2=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div dir=3D"auto"><div>And I almost managed to not make a=
ny comments about the horrible state everywhere layer violating properties =
of SAVI.=C2=A0</div></div></blockquote><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"auto"><div>ARO, DHCP or P2P are the only reliable=
 ways of doing this as far as I know.</div></div></blockquote><div><br></di=
v><div>If security is what you&#39;re after, then DHCPv6 is not secure with=
out SAVI, either. I&#39;d argue that the whole idea of a network blocking y=
ou at L2 because of your L3 address is a layering violation, anyway.</div><=
/div></div></div>

--000000000000309474057593c253--


From nobody Tue Sep 11 00:54:37 2018
Return-Path: <lorenzo@google.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC67F130E6B for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level: 
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 d8EoHpj4mto4 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 00:54:32 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 133E8130E65 for <v6ops@ietf.org>; Tue, 11 Sep 2018 00:54:32 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id 139-v6so313321itf.0 for <v6ops@ietf.org>; Tue, 11 Sep 2018 00:54:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eI4zoq0HacpSoNuf5xThHyfc0WQzQr0j1jZDdghIjME=; b=MqafmL6lziPfgBlKowPmTTOiXH6XDazNrtitTHumEioXqhOcaFgVzqhhzWY1dcGl2F 0KuO8f4uAwtfe9r8hWqMLlxb/3A0Rro+us3uRiQURxOaBgzmgl7hIDOdos4jiewtPhJG I9v0XoDWgmSBg3sA4b411T3QPlyYPA9ejFI2sIUDOHcSdFW6+J733173AMnhLjAQDS82 46BR0DqkdmUIpj5kjD7ym6zd6k0hkIW6oG9wlNakdzJV+q7kKQ4TZtc9W5p6pom4cVoa BOu2TAwX637L4am9hSXiuC3Eg/JUOxYMQKJPi44+j/eFoU8ZLBvr4N/Ey3niKSGBcpsT 2Uug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eI4zoq0HacpSoNuf5xThHyfc0WQzQr0j1jZDdghIjME=; b=nFGnw1TCFcRp2+E7WBF0c9YIy59d73jJbrco+qWa/D2cZonQAhS354fT4Wh/PforOy wJZIw1cTIf9S+CfCrlZryKruJR4avY4+R31PKkhirsSWmGSYZesqcT6kVd361iQhTMn9 uwP/n1CUDHsI4rkXDJsWcPn5l+o/Ld9EK6eO6FMHHgI7bQ26Ziq5obF42t0G5Agi1P43 F49nY7vE3eesZwsuT3BeXaPauKJs9fvU203vDQ+EhHvz/mGGehCgEDrUr/aFU/XXd/Ba miWCD+N+XOKkSJR6m1q28l45w615YRi9PZ9PfS9u6g7zA3GehRpiFAohHDFskHM6m0J0 Jpnw==
X-Gm-Message-State: APzg51ANB87eAwCDiIcA/2IoUVNlzG1b6asZpUCRIW9MoiVCAfa6E8Dy b9txhqZY+OcubAb9jm574dIxydoouDlUg3M+rdCRO3J6ngBipg==
X-Google-Smtp-Source: ANB0Vdaet2lu+mKLBX45PQ/ic+r4H8dVCz3280EUDOEWYfCy0U6IbMYvRAYEim5ODwEW86Pu/t96lRXRIjAYSelsX2k=
X-Received: by 2002:a02:1c48:: with SMTP id c69-v6mr22066156jac.65.1536652470950;  Tue, 11 Sep 2018 00:54:30 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org> <CAAedzxrtOrQrqZw-os45sRA2QT2gT7sE8CiuGxFFEssKx26iyw@mail.gmail.com> <FD8E7FA1-86F3-4193-ABBF-97AF25CEE565@employees.org> <CAAedzxpdWEOn21ci0P5zuU8AgFe99kr_kYkAtFwNE90hREqL-g@mail.gmail.com> <069A1C98-208A-44C4-941B-E9B0BCE26796@cisco.com>
In-Reply-To: <069A1C98-208A-44C4-941B-E9B0BCE26796@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 11 Sep 2018 16:54:19 +0900
Message-ID: <CAKD1Yr1v-j7mMkZhQib73=7hxZWJmiU0rYT_naaFPWtJxjuN2A@mail.gmail.com>
To: pthubert=40cisco.com@dmarc.ietf.org
Cc: ek=40google.com@dmarc.ietf.org, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ad4b2b057593c89d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Ah3l6kqRG9DKwyggOU7dCjlvSsA>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 07:54:34 -0000

--000000000000ad4b2b057593c89d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 11, 2018 at 4:32 PM Pascal Thubert (pthubert) <pthubert=3D
40cisco.com@dmarc.ietf.org> wrote:

> We have greatly improved the ARO at 6lo and tried in the process to
> alleviate Lorenzo =E2=80=98s concerns about it being an undesirable way t=
o remove
> freedom of address formation. We also discussed Bob=E2=80=99s concerns on=
 IPv6
> stability at length so hopefully we are passed that as well.
>
> The new ARO (EARO) is clearly intended to protect the address ownership.
> The NP AD draft associates a crypto token to the registration but does no=
t
> constrain the IID like SEND did.
>
> The EARO is already referenced by a number of drafts (at ROLL 6lo and
> RIFT) as the abstract way for a host to announce its addresses to selecte=
d
> routers and get services back, eg routing or ND proxy.
>

I don't see how requiring any form of ARO can respect IPv6 addressing best
practices. RFC 7934 section 8 says: "it is RECOMMENDED that the network
give the host the ability to use new addresses without requiring explicit
requests". An ARO is an explicit request.

--000000000000ad4b2b057593c89d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"lt=
r">On Tue, Sep 11, 2018 at 4:32 PM Pascal Thubert (pthubert) &lt;pthubert=
=3D<a href=3D"mailto:40cisco.com@dmarc.ietf.org">40cisco.com@dmarc.ietf.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
We have greatly improved the ARO at 6lo and tried in the process to allevia=
te Lorenzo =E2=80=98s concerns about it being an undesirable way to remove =
freedom of address formation. We also discussed Bob=E2=80=99s concerns on I=
Pv6 stability at length so hopefully we are passed that as well.<br>
<br>
The new ARO (EARO) is clearly intended to protect the address ownership. Th=
e NP AD draft associates a crypto token to the registration but does not co=
nstrain the IID like SEND did. <br>
<br>
The EARO is already referenced by a number of drafts (at ROLL 6lo and RIFT)=
 as the abstract way for a host to announce its addresses to selected route=
rs and get services back, eg routing or ND proxy.<br></blockquote><div><br>=
</div><div>I don&#39;t see how requiring any form of ARO can respect IPv6 a=
ddressing best practices. RFC 7934 section 8 says: &quot;it is RECOMMENDED =
that the network give the host the ability to use new addresses without req=
uiring explicit requests&quot;. An ARO is an explicit request.</div></div><=
/div></div>

--000000000000ad4b2b057593c89d--


From nobody Tue Sep 11 01:58:47 2018
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 811111310AF for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 01:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level: 
X-Spam-Status: No, score=-1.497 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Y9n3TJujQjxm for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 01:58:44 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 A645C130E4E for <v6ops@ietf.org>; Tue, 11 Sep 2018 01:58:44 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id k12-v6so45688588oiw.8 for <v6ops@ietf.org>; Tue, 11 Sep 2018 01:58:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t5Ws4WxqdKSFegZaJsmVfUi3mqX2DAewG8S2YvXsmRQ=; b=lXLYGEK5ojfahpzQ/dgsP5OEvtorTfH/Em2RIUZ/Fxjp5SF9VPBPpD1lcWqZFa09h0 /T3cwxZ82d+27zHayWcbc4atK/ExQ82pN5+4UyJvIVOgADwn1Iee1Kh05WkU6y6Px72O 6Wk+af3Sw8E65lReigXTtc8r01Ad6QDzwq3XiK4d+hI6MTVSI+DiVRYts6laucwUPncp 0dproB3b9nHt0+0lkcwXFFPYIyBX3IXKBmLk9VwC2rGZi+4+QoOdOBDfg5Nlje8CMuel y1k3XrXGLS3Cj/c/MVvO3u76phtdRI8+px38HcrQZn0DQMch044bcJzvxxCsXkoJl73A 93mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t5Ws4WxqdKSFegZaJsmVfUi3mqX2DAewG8S2YvXsmRQ=; b=Kb2RDd6WHKesTBHISoK8AQC4BFJlSgbRhRCGD0aMUozkCl8QiU3IACogLkUQNueIzc 43RVtmNhjzafiPGlqH3Ppm4riaqXXmIQXeXENTu0cfpqXv8KwyeN+DlKbPRPLZikv4f9 oSshZcfaLgXk9cTVs6JAt8iYjIaGlgHcF5LA6rirYesdydN3LSr4P2Q3WuLQbLgB0pYr 2/Tkf6Ag5GqSCJ30UrP5zjycZ7iaAjlCznHgWDdDXjbV9OcqhjGXzFnM3b/OjxUHvDzW N3Gurzj7FJy2XUjaaPyw2EtVrVZI+Xq6FI39HywLRowq0SgY1J0pLrYqqr3GVG7x3/EK icOQ==
X-Gm-Message-State: APzg51AfUWYsUa9goJHOSwxuDiqYVMBTcUUVsYVSsFMomZs5W5CRwqsX /1bZlGKDzmk5mPnd8nh+4aCc2IpscLmr21BW1eM=
X-Google-Smtp-Source: ANB0VdZPkjAlqvceLYDe5D15aWXwJONQ6br537Ix2u8if5EiyECy2tQLOv0htBVLyyfEeIp3RRZXOtDlWUAnUbMQA00=
X-Received: by 2002:aca:e748:: with SMTP id e69-v6mr26380048oih.263.1536656323559;  Tue, 11 Sep 2018 01:58:43 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB4439DAC0BE86DF0503CEB41AE050@CO1PR05MB443.namprd05.prod.outlook.com> <AA63368D-923E-4890-B518-CA8B119BCD7E@employees.org> <CAAedzxrtOrQrqZw-os45sRA2QT2gT7sE8CiuGxFFEssKx26iyw@mail.gmail.com> <FD8E7FA1-86F3-4193-ABBF-97AF25CEE565@employees.org> <CAAedzxpdWEOn21ci0P5zuU8AgFe99kr_kYkAtFwNE90hREqL-g@mail.gmail.com>
In-Reply-To: <CAAedzxpdWEOn21ci0P5zuU8AgFe99kr_kYkAtFwNE90hREqL-g@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Tue, 11 Sep 2018 18:58:32 +1000
Message-ID: <CAO42Z2xXbeFYaCgidBTsBqPbAz_KSzYMHwRAncqrpTW8_PHaWQ@mail.gmail.com>
To: Erik Kline <ek=40google.com@dmarc.ietf.org>
Cc: Ole Troan <otroan@employees.org>, v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ec547057594ae5e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BDY2ZLpSB6ZozjCURnWsLr3yDYg>
Subject: Re: [v6ops] draft-jaeggli-v6ops-indefensible-nd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 08:58:46 -0000

--0000000000004ec547057594ae5e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue., 11 Sep. 2018, 16:49 Erik Kline, <ek=3D40google.com@dmarc.ietf.org>
wrote:

> On Tue, 11 Sep 2018 at 15:34, Ole Troan <otroan@employees.org> wrote:
> >
> > Erik,
> >
> > > On 11 Sep 2018, at 08:22, Erik Kline <ek@google.com> wrote:
> > >
> > >> On Tue, 11 Sep 2018 at 15:15, Ole Troan <otroan@employees.org> wrote=
:
> > >>
> > >> You might want to include that this problem has been solved with a
> stateful address assignment mechanism like DHCP, possibly combined with
> SAVI.
> > >>
> > >> The ND ARO option would also have solved this.
> > >>
> > >> Or you could deploy P2P Ethernet, where there is no address
> resolution..
> > >>
> > >> Depending on DAD for this lie Lorenzo proposed seems ill-advised.
> It=E2=80=99s even less robust in wired networks (blocked ports).
> > >
> > > But...in such a network NS/NA works?  (alternatively: what does
> > > "blocked" mean here)
> >
> > NS/NA has retransmission.
> > Blocked as in 802.1D. Default 30s from link-up until port will switch
> user traffic.
>
> Do hosts receive RAs during this 30s window?  If not, then the
> blocking affects DAD for link-local addresses, but not necessarily for
> GUAs.
>
> NOTE: I am most definitely /not/ attempting to argue that DAD is
> reliable.  ;-)
>
> I had a notion about matching forwarding addresses not in cache
> against the MLD info associated with the /104 for a given forwarding
> destination address.  Seems like routers gathering MLD data might use
> that list to prioritize forwarding for destinations not yet in the
> neighbor cache.
>

So did I ;-)

https://tools.ietf.org/html/draft-smith-v6ops-mitigate-rtr-dos-mld-slctd-no=
de-02


> > DAD is unreliable for lots of reasons . Didn=E2=80=99t we write a draft=
 on that?
>
> https://tools.ietf.org/html/draft-yourtchenko-6man-dad-issues ?
>
> > Ole
> >
> >
> > >>
> > >>> On 10 Sep 2018, at 16:25, Ron Bonica <rbonica@juniper.net> wrote:
> > >>>
> > >>> Folks,
> > >>>
> > >>> Each week between now and IETF 103, we will review and discuss one
> draft with an eye towards progressing it.
> > >>>
> > >>> This week, please review and comment on
> draft-jaeggli-v6ops-indefensible-nd.
> > >>>
> > >>>                                     Fred and Ron
> > >>>
> > >>> _______________________________________________
> > >>> v6ops mailing list
> > >>> v6ops@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/v6ops
> > >>
> > >> _______________________________________________
> > >> v6ops mailing list
> > >> v6ops@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/v6ops
> >
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--0000000000004ec547057594ae5e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">=
On Tue., 11 Sep. 2018, 16:49 Erik Kline, &lt;ek=3D<a href=3D"mailto:40googl=
e.com@dmarc.ietf.org">40google.com@dmarc.ietf.org</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">On Tue, 11 Sep 2018 at 15:34, Ole Troan &lt;<=
a href=3D"mailto:otroan@employees.org" target=3D"_blank" rel=3D"noreferrer"=
>otroan@employees.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Erik,<br>
&gt;<br>
&gt; &gt; On 11 Sep 2018, at 08:22, Erik Kline &lt;<a href=3D"mailto:ek@goo=
gle.com" target=3D"_blank" rel=3D"noreferrer">ek@google.com</a>&gt; wrote:<=
br>
&gt; &gt;<br>
&gt; &gt;&gt; On Tue, 11 Sep 2018 at 15:15, Ole Troan &lt;<a href=3D"mailto=
:otroan@employees.org" target=3D"_blank" rel=3D"noreferrer">otroan@employee=
s.org</a>&gt; wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; You might want to include that this problem has been solved w=
ith a stateful address assignment mechanism like DHCP, possibly combined wi=
th SAVI.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The ND ARO option would also have solved this.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Or you could deploy P2P Ethernet, where there is no address r=
esolution..<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Depending on DAD for this lie Lorenzo proposed seems ill-advi=
sed. It=E2=80=99s even less robust in wired networks (blocked ports).<br>
&gt; &gt;<br>
&gt; &gt; But...in such a network NS/NA works?=C2=A0 (alternatively: what d=
oes<br>
&gt; &gt; &quot;blocked&quot; mean here)<br>
&gt;<br>
&gt; NS/NA has retransmission.<br>
&gt; Blocked as in 802.1D. Default 30s from link-up until port will switch =
user traffic.<br>
<br>
Do hosts receive RAs during this 30s window?=C2=A0 If not, then the<br>
blocking affects DAD for link-local addresses, but not necessarily for<br>
GUAs.<br>
<br>
NOTE: I am most definitely /not/ attempting to argue that DAD is reliable.=
=C2=A0 ;-)<br>
<br>
I had a notion about matching forwarding addresses not in cache<br>
against the MLD info associated with the /104 for a given forwarding<br>
destination address.=C2=A0 Seems like routers gathering MLD data might use<=
br>
that list to prioritize forwarding for destinations not yet in the<br>
neighbor cache.<br></blockquote></div></div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">So did I ;-)</div><div dir=3D"auto"><br></div><div dir=3D"au=
to"><a href=3D"https://tools.ietf.org/html/draft-smith-v6ops-mitigate-rtr-d=
os-mld-slctd-node-02">https://tools.ietf.org/html/draft-smith-v6ops-mitigat=
e-rtr-dos-mld-slctd-node-02</a><br></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt; DAD is unreliable for lots of reasons . Didn=E2=80=99t we write a draf=
t on that?<br>
<br>
<a href=3D"https://tools.ietf.org/html/draft-yourtchenko-6man-dad-issues" r=
el=3D"noreferrer noreferrer" target=3D"_blank">https://tools.ietf.org/html/=
draft-yourtchenko-6man-dad-issues</a> ?<br>
<br>
&gt; Ole<br>
&gt;<br>
&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; On 10 Sep 2018, at 16:25, Ron Bonica &lt;<a href=3D"mailt=
o:rbonica@juniper.net" target=3D"_blank" rel=3D"noreferrer">rbonica@juniper=
.net</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Folks,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Each week between now and IETF 103, we will review and di=
scuss one draft with an eye towards progressing it.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; This week, please review and comment on draft-jaeggli-v6o=
ps-indefensible-nd.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0Fred and Ron<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt; v6ops mailing list<br>
&gt; &gt;&gt;&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=
=3D"noreferrer">v6ops@ietf.org</a><br>
&gt; &gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" r=
el=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/listinfo/v6ops</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; v6ops mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"no=
referrer">v6ops@ietf.org</a><br>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=
=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/v6ops</a><br>
&gt;<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank" rel=3D"noreferrer">v6op=
s@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a=
><br>
</blockquote></div></div></div>

--0000000000004ec547057594ae5e--


From nobody Tue Sep 11 05:20:36 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 803DA130E8B for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 05:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Ro7SlNDMXgHf for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 05:20:31 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 0BDA7130E08 for <v6ops@ietf.org>; Tue, 11 Sep 2018 05:20:31 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id o17-v6so9237563yba.2 for <v6ops@ietf.org>; Tue, 11 Sep 2018 05:20:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/R42/mFyV2Zvr1NiNhi0NwpTz0mt1GVzS9IJ4h4LufE=; b=tqBelqv46s90jjaZXT9Q8k0LJpObM56EyC6j20mDASKd2EsFJR+3LvDL+FecM2Y7jm 257y8p/qSHS1fuTwSW96W3hhxLngoL0750SrYFHk8cGqVCF8oNLfqXlM22auEarIzgpa eGQkdwn1+HCyWHaDo+0G/LP9GD+Y+WwRlBqBYM8Op3sMoO7rXlMznmnSGtkQZzepiYEJ krfmc13I9d7MF2fmLoI57SvGsPSjru8SW1/W9Bh412dkzUaka/35IW//G9RAjeYVTLg3 /OGJOseM+d+CYX0aNSHtq7UbHzxOO1lBGKmPgpTkK4cHyoGkGIsgejrLsbP33xZY/2sR whVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/R42/mFyV2Zvr1NiNhi0NwpTz0mt1GVzS9IJ4h4LufE=; b=Q9VykG0ECeDfIGAU/I/sWMD3Ns9aeKJt0lmYQ4IWRpUC4xBc5ewe0TI+st5UzigOQJ fkZ6VBWooiv6pM9jKmNO1ceoDhuY8mtC63lRO+7MP5n4roHayeNYEkSRPXb+DYNJQHJE KLcpsHbD8slNbApF0eMNWRTICAkZWUUN4ctkkmnPqk5WOMgecJvqIDNdqtiljXyHQCJ4 Be4UAl7VNMhSVex8PQPZyi/ns+E8RjRsEWBPXbrdO+fU4NsIgaZyw9aC7c/6nelsMPdg I/RHRpAorrHIGn1S7rwUd+28pvpswqakwhsMtZ/Yc6rEAT1T8B1N8d5Ku2kzIQNYbjxr tGHw==
X-Gm-Message-State: APzg51CaUNWvBLLKJFp2teKITUW9wjs6VfvJMSkyagp5H4EA3EQNCGWI U99+9UkUYsZ9o7fVMoVe/peIHFCEIKpAJYtrbqA=
X-Google-Smtp-Source: ANB0VdaAkoDCMyCxPoXBGAU0GynoNSgJGmD83qIg35F6blCDB6xwKWZqdJzMg+O3nSBGIQNRzwjsPCTuSh/UPqmsxJ0=
X-Received: by 2002:a25:6285:: with SMTP id w127-v6mr12149703ybb.97.1536668430163;  Tue, 11 Sep 2018 05:20:30 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com> <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org>
In-Reply-To: <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org>
From: Ca By <cb.list6@gmail.com>
Date: Tue, 11 Sep 2018 05:20:19 -0700
Message-ID: <CAD6AjGRgVXCnQcZQ0xHiieNxbkWpzCAc0hsJOSk=V8-sz9yA_Q@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: Mark Andrews <marka@isc.org>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000eae37e0575977f44"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/bUbHF8ruSD3fW_T-ghNxrF8Entc>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 12:20:34 -0000

--000000000000eae37e0575977f44
Content-Type: text/plain; charset="UTF-8"

On Mon, Sep 10, 2018 at 11:40 PM Ole Troan <otroan@employees.org> wrote:

>
>
> > On 11 Sep 2018, at 03:25, Ca By <cb.list6@gmail.com> wrote:
> >
> > My view, and the i-d of referenced for this thread, all the dns64 ills
> go away if you deploy ipv6, so please deploy ipv6.
>
> If everyone everywhere deployed IPv6, then yes.
> But until then, this creates problems for IPv6 hosts.
>

The queation in this i-d is who carries the burden? This i-d assigns the
burden to the person trying to do dnssec, not the person doing ipv6-only
with dns64.  This i-d says the optional activity of deploying dnssec, to
work best, also includes the cost of having that resouce identified in the
resource record to have ipv6. The person deploying dnssec is clearly smart,
well healed, and is well positioned to do ipv6 on their described end points

cheers,
CB


> Cheers
> Ole
>

--000000000000eae37e0575977f44
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon,=
 Sep 10, 2018 at 11:40 PM Ole Troan &lt;<a href=3D"mailto:otroan@employees.=
org">otroan@employees.org</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><br>
<br>
&gt; On 11 Sep 2018, at 03:25, Ca By &lt;<a href=3D"mailto:cb.list6@gmail.c=
om" target=3D"_blank">cb.list6@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; My view, and the i-d of referenced for this thread, all the dns64 ills=
 go away if you deploy ipv6, so please deploy ipv6. <br>
<br>
If everyone everywhere deployed IPv6, then yes. <br>
But until then, this creates problems for IPv6 hosts. <br>
</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">The queation in =
this i-d is who carries the burden? This i-d assigns the burden to the pers=
on trying to do dnssec, not the person doing ipv6-only with dns64.=C2=A0 Th=
is i-d says the optional activity of deploying dnssec, to work best, also i=
ncludes the cost of having that resouce identified in the resource record t=
o have ipv6. The person deploying dnssec is clearly smart, well healed, and=
 is well positioned to do ipv6 on their described end points</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">cheers,</div><div dir=3D"auto">CB</di=
v><div dir=3D"auto"><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Cheers <br>
Ole<br>
</blockquote></div></div>

--000000000000eae37e0575977f44--


From nobody Tue Sep 11 06:31:50 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA4C12F1A2 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 06:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 ExSGGbv6JOUt for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 06:31:46 -0700 (PDT)
Received: from atl4mhob17.registeredsite.com (atl4mhob17.registeredsite.com [209.17.115.110]) (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 AFF1F130E7F for <v6ops@ietf.org>; Tue, 11 Sep 2018 06:31:46 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail02pod6.registeredsite.com [10.30.71.210]) by atl4mhob17.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8BDVhZF030823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Tue, 11 Sep 2018 09:31:43 -0400
Received: (qmail 26723 invoked by uid 0); 11 Sep 2018 13:31:43 -0000
X-TCPREMOTEIP: 68.100.71.215
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.1.135?) (lee@asgard.org@68.100.71.215) by 0 with ESMTPA; 11 Sep 2018 13:31:43 -0000
To: v6ops@ietf.org
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com> <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <3aba0d06-3225-7630-036e-8bb405bcb4b5@asgard.org>
Date: Tue, 11 Sep 2018 09:31:42 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/fXRhvX7JIvKPOGkKQosNYanyfUg>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 13:31:48 -0000

On 09/11/2018 02:40 AM, Ole Troan wrote:
>
>> On 11 Sep 2018, at 03:25, Ca By <cb.list6@gmail.com> wrote:
>>
>> My view, and the i-d of referenced for this thread, all the dns64 ills go away if you deploy ipv6, so please deploy ipv6.
> If everyone everywhere deployed IPv6, then yes.
> But until then, this creates problems for IPv6 hosts.

Or you could say, "This creates problems for DNSSEC hosts."
Or DOH hosts.

Is this more a DNS/server side problem or a DNS64/network side problem?
In my world view, which I admit is strongly biased in this case, 
everyone MUST eventually run IPv6, and everyone SHOULD run DNSSEC. IPv6 
and DNSSEC are perfectly interoperable, it's only the transition 
mechanism state where there's a problem.

Does anyone on v6ops disagree that best practice is for server operators 
to deploy IPv6? If not, is there anything wrong with the statement in 
this draft?

Publishing this draft does not prevent us from making other updates that 
would make it less of a problem. Even if we resolve the interoperability 
problem (in a few years), it will still be best practice to deploy IPv6.

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


From nobody Tue Sep 11 06:51:04 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6E2130DF5 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 06:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Nkm2wxdt-NPQ for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 06:51:00 -0700 (PDT)
Received: from mail-yw1-xc33.google.com (mail-yw1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) (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 2F588130DD8 for <v6ops@ietf.org>; Tue, 11 Sep 2018 06:51:00 -0700 (PDT)
Received: by mail-yw1-xc33.google.com with SMTP id q129-v6so9211110ywg.8 for <v6ops@ietf.org>; Tue, 11 Sep 2018 06:51:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FnWoUMLZhLmJIktwjouwK6NoN6QUuLEkX+Cde5KGqXc=; b=qNChtM6urrthol3+9enwM9AiySQpPOIvbV4cvr6iCXh9re3+ePZm/ObLjK/DsU7JoR eAltoiE88Fnm0UcnSIjek7uIVia8O513ZGwd8pzsURPTjV8Py9MQcAYMbB37ExYBza41 TB/mcSyBysWbSKFVDGHBABoB1oFJXojJ92jQDwq2GdK7ZkD0EHlWAVcEMN9EOG5YvdxT Lh6LCEQdNEM61DYHlCW6RJj8hl92ly5AHwS5kj7qmVY+VLkTX1hcbkAb26HbY1CHySKo II5HfS+YkwKyc2LKnkqe7J1u/tdRzBgzVEvSwTspvzJqJRyBYtuHE06vVBdskhVhL25h sYuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FnWoUMLZhLmJIktwjouwK6NoN6QUuLEkX+Cde5KGqXc=; b=NX1mwHdutwIG+D0Myja5eD0gDfclVzWjgfRls8N/QyzL+0PI5XN/vXgpy7SerkF5fV uNPpFKl8Y87zbFzrsvUNxV+W3VYS1COg4pK1dr7wiuEKjeMDKIdwyxWTPBfIONb50xYl JkEnizH8e+7FXux4bGg0cjMp/r3LlWkxMCs1AjD/eoP8aKvwShHdxfvdZuoE6X51cSTQ eKdh0YvdGK26N9hSmFB6pzvtwn/cQp/R2YNFomRxxfeH6xuEr6ys7LV2Kn705yzZSfYB WR0zR2xySDSDX8GXE8aT1Dj6IDlYPbcrzxMM9vuhroa/oSL5qXbNNpPugwf5DBXriUhg 4E8w==
X-Gm-Message-State: APzg51AfQ0MmK91WJ0KdR0JWNiDgVXITxwCBA3dHDMbDRtH7LV1FZAQs 6ZtgKSsweEyW3aSkFX6uVWX899vfDKY3c0wJVb8=
X-Google-Smtp-Source: ANB0VdYcJJ1MG0BBkXHWtPfuKml7vymAFpHFwPyanCBd/DFNFRrwB8qt5lUVTUraEA1ss7V7zRMl31Kd5yVU0TZGUlI=
X-Received: by 2002:a81:59c3:: with SMTP id n186-v6mr12945124ywb.54.1536673859283;  Tue, 11 Sep 2018 06:50:59 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com> <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org> <3aba0d06-3225-7630-036e-8bb405bcb4b5@asgard.org>
In-Reply-To: <3aba0d06-3225-7630-036e-8bb405bcb4b5@asgard.org>
From: Ca By <cb.list6@gmail.com>
Date: Tue, 11 Sep 2018 06:50:48 -0700
Message-ID: <CAD6AjGQFuz_cg4Bnv3uCU624cJWijCdtLM+00UBho5zL=W_9dw@mail.gmail.com>
To: Lee Howard <lee@asgard.org>
Cc: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="00000000000084afef057598c379"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MReSJX15htXc4hCKrzT-FMoaMk0>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 13:51:02 -0000

--00000000000084afef057598c379
Content-Type: text/plain; charset="UTF-8"

On Tue, Sep 11, 2018 at 6:32 AM Lee Howard <lee@asgard.org> wrote:

>
>
> On 09/11/2018 02:40 AM, Ole Troan wrote:
> >
> >> On 11 Sep 2018, at 03:25, Ca By <cb.list6@gmail.com> wrote:
> >>
> >> My view, and the i-d of referenced for this thread, all the dns64 ills
> go away if you deploy ipv6, so please deploy ipv6.
> > If everyone everywhere deployed IPv6, then yes.
> > But until then, this creates problems for IPv6 hosts.
>
> Or you could say, "This creates problems for DNSSEC hosts."
> Or DOH hosts.
>
> Is this more a DNS/server side problem or a DNS64/network side problem?
> In my world view, which I admit is strongly biased in this case,
> everyone MUST eventually run IPv6, and everyone SHOULD run DNSSEC. IPv6
> and DNSSEC are perfectly interoperable, it's only the transition
> mechanism state where there's a problem.
>
> Does anyone on v6ops disagree that best practice is for server operators
> to deploy IPv6? If not, is there anything wrong with the statement in
> this draft?
>

One could say this i-d is simply a personal invitation to dnssec deployers
to the rfc6540 party, which already states ipv6 is not optional.

Here is an example use case of the i-d

Dnssec-Person: my stuff does not validate on your network, fix it by
burning down your infrastructure that has delivered material improvement to
the global ipv6 deployment and overall health , scale, and security of the
internet!

Dns64 operator: your resources do not have ipv6, please comply with rfc6540
and move us all forward. My host have v6, dns64 will not be used for your
v6 records.

DP- 6540 does not apply to me

DO- well, i-d-byrne is real specific about this issue.  Your CDN / cloud /
ISP / OS  likely will let you enable it for free. Let me google it for you
....

DP - Ok! I did it!  Now i need to write blog about how great i am at ipv6

Crisis averted. Internet goals achieved.

CB


> Publishing this draft does not prevent us from making other updates that
> would make it less of a problem. Even if we resolve the interoperability
> problem (in a few years), it will still be best practice to deploy IPv6.
>
> Lee
> >
> > Cheers
> > Ole
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--00000000000084afef057598c379
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue,=
 Sep 11, 2018 at 6:32 AM Lee Howard &lt;<a href=3D"mailto:lee@asgard.org">l=
ee@asgard.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 09/11/2018 02:40 AM, Ole Troan wrote:<br>
&gt;<br>
&gt;&gt; On 11 Sep 2018, at 03:25, Ca By &lt;<a href=3D"mailto:cb.list6@gma=
il.com" target=3D"_blank">cb.list6@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; My view, and the i-d of referenced for this thread, all the dns64 =
ills go away if you deploy ipv6, so please deploy ipv6.<br>
&gt; If everyone everywhere deployed IPv6, then yes.<br>
&gt; But until then, this creates problems for IPv6 hosts.<br>
<br>
Or you could say, &quot;This creates problems for DNSSEC hosts.&quot;<br>
Or DOH hosts.<br>
<br>
Is this more a DNS/server side problem or a DNS64/network side problem?<br>
In my world view, which I admit is strongly biased in this case, <br>
everyone MUST eventually run IPv6, and everyone SHOULD run DNSSEC. IPv6 <br=
>
and DNSSEC are perfectly interoperable, it&#39;s only the transition <br>
mechanism state where there&#39;s a problem.<br>
<br>
Does anyone on v6ops disagree that best practice is for server operators <b=
r>
to deploy IPv6? If not, is there anything wrong with the statement in <br>
this draft?<br>
</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">One could say th=
is i-d is simply a personal invitation to dnssec deployers to the rfc<span =
style=3D"font-size:1em">6540 party, which already states ipv6 is not option=
al.</span></div><div dir=3D"auto"><span style=3D"font-size:1em"><br></span>=
</div><div dir=3D"auto"><span style=3D"font-size:1em">Here is an example us=
e case of the i-d</span></div><div dir=3D"auto"><span style=3D"font-size:1e=
m"><br></span></div><div dir=3D"auto"><span style=3D"font-size:1em">Dnssec-=
Person: my stuff does not validate on your network, fix it by burning down =
your infrastructure that has delivered material improvement to the global i=
pv6 deployment and overall health , scale, and security of the internet!</s=
pan></div><div dir=3D"auto"><span style=3D"font-size:1em"><br></span></div>=
<div dir=3D"auto"><span style=3D"font-size:1em">Dns64 operator: your resour=
ces do not have ipv6, please comply with rfc</span><span style=3D"font-size=
:1em">6540 and move us all forward. My host have v6, dns64 will not be used=
 for your v6 records.=C2=A0</span></div><div dir=3D"auto"><span style=3D"fo=
nt-size:1em"><br></span></div><div dir=3D"auto"><span style=3D"font-size:1e=
m">DP-=C2=A0</span><span style=3D"font-size:1em">6540 does not apply to me<=
/span></div><div dir=3D"auto"><span style=3D"font-size:1em"><br></span></di=
v><div dir=3D"auto"><span style=3D"-webkit-tap-highlight-color: rgba(26, 26=
, 26, 0.301961); -webkit-text-size-adjust: auto;">DO- well, i-d-byrne is re=
al specific about this issue.=C2=A0 Your CDN / cloud / ISP / OS =C2=A0likel=
y will let you enable it for free. Let me google it for you ....</span></di=
v><div dir=3D"auto"><span style=3D"-webkit-tap-highlight-color: rgba(26, 26=
, 26, 0.301961); -webkit-text-size-adjust: auto;"><br></span></div><div dir=
=3D"auto"><span style=3D"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.30=
1961); -webkit-text-size-adjust: auto;">DP - Ok! I did it!=C2=A0 Now i need=
 to write blog about how great i am at ipv6=C2=A0</span></div><div dir=3D"a=
uto"><span style=3D"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.301961)=
; -webkit-text-size-adjust: auto;"><br></span></div><div dir=3D"auto"><span=
 style=3D"-webkit-tap-highlight-color: rgba(26, 26, 26, 0.301961); -webkit-=
text-size-adjust: auto;">Crisis averted. Internet goals achieved.=C2=A0</sp=
an></div><div dir=3D"auto"><span style=3D"font-size:1em"><br></span></div><=
div dir=3D"auto"><span style=3D"font-size:1em">CB</span></div><div dir=3D"a=
uto"><span style=3D"font-size:1em"><br></span></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><br>
Publishing this draft does not prevent us from making other updates that <b=
r>
would make it less of a problem. Even if we resolve the interoperability <b=
r>
problem (in a few years), it will still be best practice to deploy IPv6.<br=
>
<br>
Lee<br>
&gt;<br>
&gt; Cheers<br>
&gt; Ole<br>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div>

--00000000000084afef057598c379--


From nobody Tue Sep 11 14:51:28 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFFC8130EFE for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 14:51:26 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 IwMjPKLG6_oB for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 14:51:25 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 16941130DF6 for <v6ops@ietf.org>; Tue, 11 Sep 2018 14:51:25 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id 13-v6so50366774ois.1 for <v6ops@ietf.org>; Tue, 11 Sep 2018 14:51:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=8w0+z1OTp2rIeeYWU3Mcz2S0wtA/XT+1eSvv/GqwyJM=; b=M56YJttu1VXkAafwwfTiWxlMDcglylvsb/N0lvt7bEnl/a9DBxdVwgeGEpxA9D6l2q TCctXD4eQ1VRsllwLQjsfQ7hhOqWVfv27nh2NyQ/YNzlk00nca3Ox2cGHQGyTsnkkz8j FWfZDJdbb5i2wlQJx7cuZ1u76kDwR8vHDLaoHwTbHyJxUQ7y9WEhxPUeU3KR1fPkcKVc 6Qu7zS36a1zTjDWIRpOATECp+LFHpWXpRupD/hCQEx1ZaukOb45jTgxjXEzLZKUCeSsL sXZeZVSRd8kq3Lvq40vJxGRSfH0OmmUJTsH34dnDqSQ2McWZbHQcIR5pwTvGuLdzwcyT GHAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=8w0+z1OTp2rIeeYWU3Mcz2S0wtA/XT+1eSvv/GqwyJM=; b=YXmmKrchZHzmyH8r7QeaocI+07CW9FIMtTCe4JqJZvebjQjRCW+/gSeecE1R2s/qhO JCF2TTUvzRQS3RWJW5TAfM8wV5uCxCDJTfcltSP/pKDkb+Jj1K51pdW+XBQQfvaaMf1d WUrl4o6AhgEhs25LhQR4tBoADJYjC3nZVDLnCazJy+Tmz4zSBMUpgaTXs7deMlpFekHi zfKCcmBirLDZ1Wz1wQuJxqfvLiPUqTsVjGXROo0JHg70lciNgU2k3KuaVxlKXpJybumM tfTioQbBK3zcGz1gCSfwVDM/dLt9Ud++NYIyREHRpXCMbAlFuFuOtELkaZ18u/RBEcTP uGSQ==
X-Gm-Message-State: APzg51Cg4NJz822pVihCZtOMF9ztjIBMT4ORz7FVg6UYN2RnEvOZS9ev 4Elu1rtkEoIWZGcmgo4IwrU=
X-Google-Smtp-Source: ANB0VdYfbZmylA8GtBNoURLp6BSlk30cDEH5XVOhPeAssl+tPmlyr0O4osDi0qSwdg4Neipwtst1eQ==
X-Received: by 2002:aca:171a:: with SMTP id j26-v6mr8824665oii.277.1536702684428;  Tue, 11 Sep 2018 14:51:24 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1070? ([2600:8802:5600:1546::1070]) by smtp.gmail.com with ESMTPSA id m11-v6sm19728086oif.27.2018.09.11.14.51.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Sep 2018 14:51:23 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <04941AA7-A08F-4B63-8606-005FC5E90531@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_076EF02D-0D2B-42E4-AAED-D50926B6976B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 11 Sep 2018 14:51:21 -0700
In-Reply-To: <CAD6AjGQFuz_cg4Bnv3uCU624cJWijCdtLM+00UBho5zL=W_9dw@mail.gmail.com>
Cc: Lee Howard <lee@asgard.org>, v6ops@ietf.org
To: Ca By <cb.list6@gmail.com>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com> <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org> <3aba0d06-3225-7630-036e-8bb405bcb4b5@asgard.org> <CAD6AjGQFuz_cg4Bnv3uCU624cJWijCdtLM+00UBho5zL=W_9dw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/k5HnkOGUhJsV4sOph5CvHJ4voBM>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 21:51:27 -0000

--Apple-Mail=_076EF02D-0D2B-42E4-AAED-D50926B6976B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Sep 11, 2018, at 6:50 AM, Ca By <cb.list6@gmail.com> wrote:
>=20
> One could say this i-d is simply a personal invitation to dnssec =
deployers to the rfc6540 party, which already states ipv6 is not =
optional.

Sort of. RFC 6540 says that the industry wants "ubiquitous [ipv6] =
hardware and software support" in the products that it deploys. What =
you're saying (which I'm quite OK with) is different: you want =
ubiquitous service support using that hardware and software. I wonder =
(this is a question) whether if RFC 6540 was something we needed, =
whether the service counterpart to it is needed as an RFC as well.

=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_076EF02D-0D2B-42E4-AAED-D50926B6976B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluYONkACgkQEhdRnd2G
P+ADpxAAsWowoHNp0UutC98sQ5+BDChS+yNJNdZ2zPkyjYw+C6LzRFJmO052jeKG
To7F8wPG3Qz8b4d2Z2xm3Me+l5cUsOWWoFKt+fXCVf2bK0cvs5uEeGwemsWN0sKb
BOY25lxrJWWC0M4cR4YUMwuFgy0bIqrCDNy+35iIzCc9LfrGzmHY89LkxnW7z7Wa
o9S3BJrGpqvrSdRPGd9ajm5Jrr2zP0NApm0kcoIvtDhN6fWxEdYDiHZ/M6bJz47w
WZciHv9PjEjPyLoUkQuJdFoxYvts5Omgm5dh+nCWcVw1M1uL55LTWIUVR+K7yRQx
FlmruqLItm9rsqpA7mmD99+mksSdyC7tLRKBKi19aphi1nUHLwLSwAQ3+hgP3sxR
7vxLGUKpRVkWgYMEdUE/KGE9jKhG5CA1OQ/eokh/aJqeqTMIz9VCijOLKlKJIZHN
rgNHG6T0pfkBuq7sCno4X79sQSV6q13XTAbCKIkEUnJeuGej7CADgP/HoK7NeRrs
1qcTnbrV/pVTrJ/JKxH0dI2cjr/4XmELq1T3YzuLm+RwATMV6Ay97LswS13Vlrvk
7ueR29nzvY6gSiGJC3rFdy9R6HIKt8rn5v2i/e09LDbLQ7PjSZbTHG6LRcx4+4Bh
owPIYsWN9kZrKrE3635VvlzN/ZvlLCYDO/hXG/1NW9ISvjsZdkM=
=Efhf
-----END PGP SIGNATURE-----

--Apple-Mail=_076EF02D-0D2B-42E4-AAED-D50926B6976B--


From nobody Tue Sep 11 14:58:30 2018
Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F62A130F3E for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 14:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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=umn.edu
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 ErG1fwa0jnIC for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 14:58:27 -0700 (PDT)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 D4A37130F3C for <v6ops@ietf.org>; Tue, 11 Sep 2018 14:58:27 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 4866FFC5 for <v6ops@ietf.org>; Tue, 11 Sep 2018 21:58:27 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCl27iiMGUOo for <v6ops@ietf.org>; Tue, 11 Sep 2018 16:58:27 -0500 (CDT)
Received: from mail-vk0-f69.google.com (mail-vk0-f69.google.com [209.85.213.69]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 14B5CD76 for <v6ops@ietf.org>; Tue, 11 Sep 2018 16:58:26 -0500 (CDT)
Received: by mail-vk0-f69.google.com with SMTP id s204-v6so765922vke.23 for <v6ops@ietf.org>; Tue, 11 Sep 2018 14:58:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VGVv4MWDgQOXAcHC/wTdchYjtsfXSkgK3I3o6oUzMGg=; b=HDRLepUOWmjMZGU3iEC40ZBBGMuY3wrsrilAy4viQLCMsS4A7vhXjMKRyDM0p3iLfd hr7SbjPuDlHVlKVFysZhTSHgLWSdKuaUt0Jv0XoFsrHJmgMl3YkuloPR0TlXo9TZbcUx agoTfEt/BPb1qqWt3np9zs2viw5lK2MGmgYWzcMxqiC6oFAkG/qiVZjm0PkzRI3Zn2In /Eyje2KdqbsOlDKYHJpyMaDo4OP7u09Nt8KmMcxz/YrnQvABZaZqYxzjAD3KwEFH1yPW aPelRlAIRt625OVjNwrQ8z1m8utbgoKqRp4UDmpWwL48NxZtHAdbVxnk0qYH8lM6lYtX 1H2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VGVv4MWDgQOXAcHC/wTdchYjtsfXSkgK3I3o6oUzMGg=; b=YQbF02teCUQibz0vVFU5IstBohcu529HKxLDDapIVKoblAxQGCqo06UgrfomPiWtII Vjq2AdSsZrtwiY3CrbrMf/aeaSLIqDoKSHaFAkXD+DHExVAPjZQLNXMCnwwGSvFtpoJr A4nMXaYQEdqDun5Ni359q22lX2K18PyKK9/o0f2AtsmrV+W26Q0OZ7v8tiujPOw98CsN XGZEnn7LmfmZBa8xRyDU+ibBpp+IVcNxadLLZpud6WYrqSu+BkP2oH0ecLxWhXUZmcNQ QrAIWuIXhZrfkpJaMyQrYWAEFdDbW6OFLN/ucTFqACUMiBgo1afGxSsHBG/b667y615K GIhw==
X-Gm-Message-State: APzg51APl04uHqMSxfjfAkhA4wnRMGvbbxahOnubSRviQkVNHZzOgybk rXhoGkCjd72fG8B4gXId4CH8hJFazgSeJqpwjA8zw+SViNw+6Q8lrFmCn9s/FVkbzQk5tYzueOv sV6FGOrQvo+GMh+hWsy3xfCRETw==
X-Received: by 2002:a9f:3d1a:: with SMTP id l26-v6mr10131608uai.29.1536703106134;  Tue, 11 Sep 2018 14:58:26 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdY3ivHUlaO3NxgRC86G16oykYBiBgv5P+80QTYKEzRcnu9o3rKmRnVy0I1WG95IuQPUVXzC6anx3MQhD6+yV1U=
X-Received: by 2002:a9f:3d1a:: with SMTP id l26-v6mr10131604uai.29.1536703105872;  Tue, 11 Sep 2018 14:58:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a67:6042:0:0:0:0:0 with HTTP; Tue, 11 Sep 2018 14:58:24 -0700 (PDT)
In-Reply-To: <04941AA7-A08F-4B63-8606-005FC5E90531@gmail.com>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com> <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org> <3aba0d06-3225-7630-036e-8bb405bcb4b5@asgard.org> <CAD6AjGQFuz_cg4Bnv3uCU624cJWijCdtLM+00UBho5zL=W_9dw@mail.gmail.com> <04941AA7-A08F-4B63-8606-005FC5E90531@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Tue, 11 Sep 2018 16:58:24 -0500
Message-ID: <CAN-Dau1k9jocPLJ2ysuV-CBQ2Z=Hs-z_0W+OAcfJe5f-uq-weA@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Ca By <cb.list6@gmail.com>, V6 Ops List <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c04b5c05759f927b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Kft5jA4wJ4yqqHLy5qMzvZafTr4>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 21:58:30 -0000

--000000000000c04b5c05759f927b
Content-Type: text/plain; charset="UTF-8"

On Tue, Sep 11, 2018 at 4:51 PM, Fred Baker <fredbaker.ietf@gmail.com>
wrote:

>
>
> > On Sep 11, 2018, at 6:50 AM, Ca By <cb.list6@gmail.com> wrote:
> >
> > One could say this i-d is simply a personal invitation to dnssec
> deployers to the rfc6540 party, which already states ipv6 is not optional.
>
> Sort of. RFC 6540 says that the industry wants "ubiquitous [ipv6] hardware
> and software support" in the products that it deploys. What you're saying
> (which I'm quite OK with) is different: you want ubiquitous service support
> using that hardware and software. I wonder (this is a question) whether if
> RFC 6540 was something we needed, whether the service counterpart to it is
> needed as an RFC as well.
>

I have been thinking maybe this should update RFC6540, making it one BCP.
I'm not sure they really need to be distinct entities.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

--000000000000c04b5c05759f927b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Sep 11, 2018 at 4:51 PM, Fred Baker <span dir=3D"l=
tr">&lt;<a href=3D"mailto:fredbaker.ietf@gmail.com" target=3D"_blank">fredb=
aker.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><br>
<br>
&gt; On Sep 11, 2018, at 6:50 AM, Ca By &lt;<a href=3D"mailto:cb.list6@gmai=
l.com">cb.list6@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; One could say this i-d is simply a personal invitation to dnssec deplo=
yers to the rfc6540 party, which already states ipv6 is not optional.<br>
<br>
Sort of. RFC 6540 says that the industry wants &quot;ubiquitous [ipv6] hard=
ware and software support&quot; in the products that it deploys. What you&#=
39;re saying (which I&#39;m quite OK with) is different: you want ubiquitou=
s service support using that hardware and software. I wonder (this is a que=
stion) whether if RFC 6540 was something we needed, whether the service cou=
nterpart to it is needed as an RFC as well.<br></blockquote><div><br></div>=
<div><div>I have been thinking maybe this should update RFC6540, making it =
one BCP. I&#39;m not sure they really need to be distinct entities.=C2=A0 =
=C2=A0</div></div></div><div><br></div>-- <br><div class=3D"gmail_signature=
">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Da=
vid Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D=
"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><=
br>Networking &amp; Telecommunication Services<br>Office of Information Tec=
hnology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-30=
29=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
</div></div></div>

--000000000000c04b5c05759f927b--


From nobody Tue Sep 11 15:40:50 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A82F130F56 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 15:40:48 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 WZmETCaCy1eS for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 15:40:46 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 94870130EF7 for <v6ops@ietf.org>; Tue, 11 Sep 2018 15:40:46 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id x197-v6so50474438oix.5 for <v6ops@ietf.org>; Tue, 11 Sep 2018 15:40:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=8l6zQG6zuZPyxqq+1j8xYH8wYACG4G7tpzNxSxHrNos=; b=GMzUbxcgDbmC/m/0vtdTHMhDYRvb4N1IWfxV3ccL7mrOqPBrAt3xm1Dp7/HkLyQITJ bwTTk98hIcMBbJOdvWNHLejR/QA2vFGNYeg/dlOXiDNzsWEpgjq6ZISj6bvCuT3tUXvA lyWeVF7tRpIL8wZlc6c6qHSdUlkSMpZgL0tKRVkNXLnzE7JtZFP562X0wyPUY1eS3LcD d3mha0vrB63jVv09zfO3L5X2ydlQ8dddm7REOFdRXynKy9VA7fzCYY2IwA1XYnpWJ5At +ubFlwtdSSgiS4f5d2+wCk1dbaFfJMVxnMIB5Di8rgrnM2Wy7wli+MmZNOOv/TtfyM74 RL1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=8l6zQG6zuZPyxqq+1j8xYH8wYACG4G7tpzNxSxHrNos=; b=bITAVzIp3Sk+SNM9CVbxaUN9wTrx5fqM2wJ+gbRImA/Xp+AL8fvH4KnYc34H9wp3iw DpmQMGDHUaVP1Cp+6NKc9Ot1SS2vu9CZYL/qAPiT+9kIyv6P48xnL2fir64Xi0Aib+H1 anHKK+cYW+L1JAWWpBlF07PNPgmyN8+CdbQx2fBMzwJe19FKxM/OjD9lm72IxnDquer+ Fe+IAAGhb7WIjIQbxZw/xjY1x9xdz7I6gsJ/JXx5vDxntcgXNpDlA4F7hRyp5PhVKdVw +TppLXM/+pqSnjhLH0yqOSDEqwsRvFg69kTHGDcsCfIjGrJchpbq6rcysQvf7wgOP0C0 GnrQ==
X-Gm-Message-State: APzg51AcnmD3tJ7h/mx+pBz/ug8eKLs3DzmKNqqxtHQ7k6xiJHJuNdUA dreno+o2OiUzuBvHmy65cbGtc3ly
X-Google-Smtp-Source: ANB0VdZwEYun8NjsX+iKZ5k3LU+s2e3yePloy4mv8IoUmQpWgGXpKqUP3Xi/Hu0jiI41NDai0q2Z+A==
X-Received: by 2002:aca:c34b:: with SMTP id t72-v6mr31289398oif.338.1536705646007;  Tue, 11 Sep 2018 15:40:46 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1070? ([2600:8802:5600:1546::1070]) by smtp.gmail.com with ESMTPSA id i132-v6sm30226137oif.20.2018.09.11.15.40.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Sep 2018 15:40:45 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <40DBEF25-78C7-49FE-B13B-592CAA16C167@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_64CA8F20-D0C1-454B-9E4F-E5EAF3AC7726"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 11 Sep 2018 15:40:43 -0700
In-Reply-To: <CAN-Dau1k9jocPLJ2ysuV-CBQ2Z=Hs-z_0W+OAcfJe5f-uq-weA@mail.gmail.com>
Cc: Ca By <cb.list6@gmail.com>, V6 Ops List <v6ops@ietf.org>
To: David Farmer <farmer@umn.edu>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com> <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org> <3aba0d06-3225-7630-036e-8bb405bcb4b5@asgard.org> <CAD6AjGQFuz_cg4Bnv3uCU624cJWijCdtLM+00UBho5zL=W_9dw@mail.gmail.com> <04941AA7-A08F-4B63-8606-005FC5E90531@gmail.com> <CAN-Dau1k9jocPLJ2ysuV-CBQ2Z=Hs-z_0W+OAcfJe5f-uq-weA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8BOthGy53RE6mWcm-8QlmlXyCtA>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 22:40:48 -0000

--Apple-Mail=_64CA8F20-D0C1-454B-9E4F-E5EAF3AC7726
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Sep 11, 2018, at 2:58 PM, David Farmer <farmer@umn.edu> wrote:
>=20
>=20
> On Tue, Sep 11, 2018 at 4:51 PM, Fred Baker <fredbaker.ietf@gmail.com> =
wrote:
>=20
>=20
> > On Sep 11, 2018, at 6:50 AM, Ca By <cb.list6@gmail.com> wrote:
> >
> > One could say this i-d is simply a personal invitation to dnssec =
deployers to the rfc6540 party, which already states ipv6 is not =
optional.
>=20
> Sort of. RFC 6540 says that the industry wants "ubiquitous [ipv6] =
hardware and software support" in the products that it deploys. What =
you're saying (which I'm quite OK with) is different: you want =
ubiquitous service support using that hardware and software. I wonder =
(this is a question) whether if RFC 6540 was something we needed, =
whether the service counterpart to it is needed as an RFC as well.
>=20
> I have been thinking maybe this should update RFC6540, making it one =
BCP. I'm not sure they really need to be distinct entities.

But by implication, you think there is value in saying this?


> --
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> David Farmer               Email:farmer@umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=
--------------------------------------------------------------------------=
------
The fact that there is a highway to hell and a stairway to heaven is an =
interesting comment on projected traffic volume...


--Apple-Mail=_64CA8F20-D0C1-454B-9E4F-E5EAF3AC7726
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluYRGsACgkQEhdRnd2G
P+DB2hAAuZ6Fc8TM7/QfP8BJpUztpfgoNCyEoYkpBvjtbAKNmI3fGtCMUARAIu9n
e5RwFJ93w/26PKW2jZcfLyyH/oB8+Hkejua96vikZCvcKgY/GxN+nPi6bEw/7iim
YFraRfQZDPaYEUAEvNyRbnCo94KjGEhD70Rwfyis5cEMrFoRCLXwxyspitjTmYxg
D9KO0z4V/2kfi0utL0//fdEH7go+GSlsLTZ5tBFJkP4kRQ6jiIYoaOIzFpz3vmQD
4fpW/rOXT5QlRf7w2DfsyiaLhW417uELFah7zWLqGoWgmV/BDbfP7ZuTa2+0VPwO
teBdsPxUZVWF8AoRlaaH5IKUoAynN4C35XYAw6HoX8y7ybz3W5DQ/owE0xJmLn5i
On5UDUFoPdvISbzfrKM1RI64fvGC1anPK7wg23Dn+chmqFjUKJe/XeYE3jYUGuNl
4Kc+0tOUNN3L26yyd3HvkVQAPDlkpuy5K4UP00dWa20RtfqB9XI6yly3lTHnLA53
RFe2DNivdw4taeBVae7eqUz45livGGGwP6WuWhnbLPyaW4NkteehB5NUZGuq/dEj
KLebqXr66ApQ4SjcBHu1nBtOGkD7TUmWpYpo+a5zD93EzNRJssnJtcZ09ZVkD+KJ
xsmsBhIo3+z9lcK/uvnwwkxcwqOqg8uAq+HfJrzDcUvVEVlOnUY=
=6oQO
-----END PGP SIGNATURE-----

--Apple-Mail=_64CA8F20-D0C1-454B-9E4F-E5EAF3AC7726--


From nobody Tue Sep 11 20:13:58 2018
Return-Path: <paul@nohats.ca>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E39130DF0 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 20:13:56 -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=nohats.ca
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 x59971MMSp70 for <v6ops@ietfa.amsl.com>; Tue, 11 Sep 2018 20:13:54 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 0817B130DC1 for <v6ops@ietf.org>; Tue, 11 Sep 2018 20:13:54 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4296Ll1SBxz1mD; Wed, 12 Sep 2018 05:13:51 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1536722031; bh=h0Dbhd+lT6p4jUlm8oNkPXsEcHxd47qoF8/dGBEoVbs=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=DJaMIACp/q83pdNcJRFebv875I/lGbNvxHtt/PXf6iNmLgq361fzpD233aNLLMbFM 9RBwvygtFeDEr38tlBykkIbAlGZqf/XIm4VYcKyEy7cVuhsiKdyK5TsalvwQikNn+q uXkujIvBydDYCv+NHTy36em1WYiyPRzUIHaYx42s=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id PK6pPBYlyz01; Wed, 12 Sep 2018 05:13:49 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 12 Sep 2018 05:13:48 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 1B4999E1; Tue, 11 Sep 2018 23:13:47 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 1B4999E1
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 1383B4027A94; Tue, 11 Sep 2018 23:13:47 -0400 (EDT)
Date: Tue, 11 Sep 2018 23:13:47 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Dan York <york@isoc.org>
cc: DNSSEC Coordination <dnssec-coord@elists.isoc.org>, v6ops@ietf.org
In-Reply-To: <A132DE26-0BFB-4E6D-9D61-AEBBD12922A5@isoc.org>
Message-ID: <alpine.LRH.2.21.1809112302140.15408@bofh.nohats.ca>
References: <A132DE26-0BFB-4E6D-9D61-AEBBD12922A5@isoc.org>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Uc9y450dAdfO9qrb8SuEhLlkRP4>
Subject: Re: [v6ops] [dnssec-coord] Comments? draft-byrne-v6ops-dnssecaaaa - DNSSEC Resource Record Should Include AAAA
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 12 Sep 2018 03:13:57 -0000

On Wed, 12 Sep 2018, Dan York wrote:

> A friend just clued me in to this draft over in v6OPS from Cameron Byrne at T-Mobile USA:
> 
> https://tools.ietf.org/html/draft-byrne-v6ops-dnssecaaaa-00
> If I understand this correctly, basically what he is saying is “everything signed with DNSSEC should have
> an IPv6 address”, right?

Yes and kind of badly phrased. It assumes DNS is only for A and AAAA
records :P It should really say "All names with an A record should also
have a AAAA record" (instead of talking about "DNSSEC signed resources")

But the intent is good and I agree with the document's BCP statement.

Although deploying IPv6 and DNSSEC "in tandem" as stated would be a
restriction too many. Instead it is better to state "deploy AAAA along
all A before deploying DNSSEC". I don't think anyone will roll out DNSSEC
and IPv6 "in tandem".

The draft is also missing another obvious exception. Clients should
really run a validating resolver themselves (with a forwarder over IPv6)
and implement DNS64 natively. Then the client can accept insecure
synthesized AAAA records safely.

Paul


From nobody Wed Sep 12 11:18:19 2018
Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53FD1128C65 for <v6ops@ietfa.amsl.com>; Wed, 12 Sep 2018 11:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 WW0qrxv6Yax4 for <v6ops@ietfa.amsl.com>; Wed, 12 Sep 2018 11:18:16 -0700 (PDT)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (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 C2B79126CB6 for <v6ops@ietf.org>; Wed, 12 Sep 2018 11:18:16 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id 7E35AD88 for <v6ops@ietf.org>; Wed, 12 Sep 2018 18:18:15 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oeNxYyiHLcnK for <v6ops@ietf.org>; Wed, 12 Sep 2018 13:18:15 -0500 (CDT)
Received: from mail-vk1-f200.google.com (mail-vk1-f200.google.com [209.85.221.200]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 476E4E93 for <v6ops@ietf.org>; Wed, 12 Sep 2018 13:18:15 -0500 (CDT)
Received: by mail-vk1-f200.google.com with SMTP id l5-v6so183235vkd.12 for <v6ops@ietf.org>; Wed, 12 Sep 2018 11:18:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=I1A6KxeXReU2XtK8MJmRYzciY0P2FHBzl7ONEG85JnM=; b=U5ccS2rhbUsUGhzolfiEtqHT+YIWS6LHIdRzDC/No1h1wpSrJttBOfwzPhjiaJu+68 HyWhuqEIpFpk/+EJ0cXmUz1n5SrQ+7BJnLKBw94d+pybvjCGwJ3q5NwLIRh94SmEtxke ORJ3qhO0gi9qN3HU2arAdv1BF25xiykRmL80XdGB7l7q6JA6MhAxg2uTD7vYageKO9fI C7sbFQJ/8hR87Otz5LkgTff+Hqt7OMlDeD+j/LBWgoiKv5KF4S2gcuYb8DoMuxhW8SP3 FQGtjXezjYlZQFb0fWISeGJr2G6eOqjgRhGOrq3vtD5+pd2MTtCpTSdzCluk9tlPXGJr /udg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=I1A6KxeXReU2XtK8MJmRYzciY0P2FHBzl7ONEG85JnM=; b=EMktBfr+56Al1UGSXlkhz9wPUW9WMu0Z7vpItAqpYfGuqIP9Wvx+BKQp5Dj85zB2pK fL6Eork3EujYvP+MDxYQcV0eOVV4YhdksIUiI7d47M2Lu+lA1XAXfZ6HFeHklVVwlqsg 4EaEIX5x5hC9GBEh20wq7zt5G0siWSQ5PSZ0e1kV9fMZEed+Y7qigY9ca/0fSNVKBMta wIz7AYTeY/hpiDEkxBLiHRBxj1bicWdZKfR2LSIE6FgIRtTuXgh9HGVABWL5O39iYiBk nEY+f/9QbiBQEK1F7Kpfbt7BK3JZQDaTvMqHDk8ESj+D9NP6OxkZVzAoqwS5x2M7BR6V ypog==
X-Gm-Message-State: APzg51Ck7vZSpy4Ylk4wIl2E1tSg2eQq/uwzxl9b9LHpcC7VeYOVGobN +3DtFiCv3ECStW5dtw1tgsFF5Fbe/mf6MMHLjYqTYpF31SSpK5UK1o2owZNjHnKt9tT/fTPExo9 Zu9E3Ctpn0O8Mf92GuTD2rFalwA==
X-Received: by 2002:a1f:2008:: with SMTP id g8-v6mr452882vkg.63.1536776294106;  Wed, 12 Sep 2018 11:18:14 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdbTlRVMr5KmxEn4f764yfX1UHtFrhf528tKqeAwl1Qx+OfkV0yQMQlk4TrrcBPglpIQF51AVK3onaa2hnrI168=
X-Received: by 2002:a1f:2008:: with SMTP id g8-v6mr452869vkg.63.1536776293641;  Wed, 12 Sep 2018 11:18:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a67:6042:0:0:0:0:0 with HTTP; Wed, 12 Sep 2018 11:18:12 -0700 (PDT)
In-Reply-To: <40DBEF25-78C7-49FE-B13B-592CAA16C167@gmail.com>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com> <1B3050D6-52EF-460D-AF5C-D168C440A127@employees.org> <3aba0d06-3225-7630-036e-8bb405bcb4b5@asgard.org> <CAD6AjGQFuz_cg4Bnv3uCU624cJWijCdtLM+00UBho5zL=W_9dw@mail.gmail.com> <04941AA7-A08F-4B63-8606-005FC5E90531@gmail.com> <CAN-Dau1k9jocPLJ2ysuV-CBQ2Z=Hs-z_0W+OAcfJe5f-uq-weA@mail.gmail.com> <40DBEF25-78C7-49FE-B13B-592CAA16C167@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Wed, 12 Sep 2018 13:18:12 -0500
Message-ID: <CAN-Dau08b4FjvXukNwCoUCqGKSee8HgWHpENwyA9yvi2JYw7bQ@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Ca By <cb.list6@gmail.com>, V6 Ops List <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000151c0a0575b09d40"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/2CiVk_4niXFyooAYJGoLen4ytZ4>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 12 Sep 2018 18:18:18 -0000

--000000000000151c0a0575b09d40
Content-Type: text/plain; charset="UTF-8"

On Tue, Sep 11, 2018 at 5:40 PM, Fred Baker <fredbaker.ietf@gmail.com>
wrote:

>
>
> > On Sep 11, 2018, at 2:58 PM, David Farmer <farmer@umn.edu> wrote:
> >
> >
> > On Tue, Sep 11, 2018 at 4:51 PM, Fred Baker <fredbaker.ietf@gmail.com>
> wrote:
> >
> >
> > > On Sep 11, 2018, at 6:50 AM, Ca By <cb.list6@gmail.com> wrote:
> > >
> > > One could say this i-d is simply a personal invitation to dnssec
> deployers to the rfc6540 party, which already states ipv6 is not optional.
> >
> > Sort of. RFC 6540 says that the industry wants "ubiquitous [ipv6]
> hardware and software support" in the products that it deploys. What you're
> saying (which I'm quite OK with) is different: you want ubiquitous service
> support using that hardware and software. I wonder (this is a question)
> whether if RFC 6540 was something we needed, whether the service
> counterpart to it is needed as an RFC as well.
> >
> > I have been thinking maybe this should update RFC6540, making it one
> BCP. I'm not sure they really need to be distinct entities.
>
> But by implication, you think there is value in saying this?
>

Yes, I said I supported the draft and the suggestions Lee made earlier,
that hasn't changed.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

--000000000000151c0a0575b09d40
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Tue, Sep 11, 2018 at 5:40 PM, Fred Baker <span dir=3D"ltr">&lt;<a href=
=3D"mailto:fredbaker.ietf@gmail.com" target=3D"_blank">fredbaker.ietf@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
&gt; On Sep 11, 2018, at 2:58 PM, David Farmer &lt;<a href=3D"mailto:farmer=
@umn.edu">farmer@umn.edu</a>&gt; wrote:<br>
&gt; <br>
&gt; <br>
&gt; On Tue, Sep 11, 2018 at 4:51 PM, Fred Baker &lt;<a href=3D"mailto:fred=
baker.ietf@gmail.com">fredbaker.ietf@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; <br>
&gt; &gt; On Sep 11, 2018, at 6:50 AM, Ca By &lt;<a href=3D"mailto:cb.list6=
@gmail.com">cb.list6@gmail.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; One could say this i-d is simply a personal invitation to dnssec =
deployers to the rfc6540 party, which already states ipv6 is not optional.<=
br>
&gt; <br>
&gt; Sort of. RFC 6540 says that the industry wants &quot;ubiquitous [ipv6]=
 hardware and software support&quot; in the products that it deploys. What =
you&#39;re saying (which I&#39;m quite OK with) is different: you want ubiq=
uitous service support using that hardware and software. I wonder (this is =
a question) whether if RFC 6540 was something we needed, whether the servic=
e counterpart to it is needed as an RFC as well.<br>
&gt; <br>
&gt; I have been thinking maybe this should update RFC6540, making it one B=
CP. I&#39;m not sure they really need to be distinct entities.<br>
<br>
But by implication, you think there is value in saying this?<br></blockquot=
e><div><br></div><div><span style=3D"font-size:small;background-color:rgb(2=
55,255,255);text-decoration-style:initial;text-decoration-color:initial;flo=
at:none;display:inline">Yes, I said I supported the draft and the suggestio=
ns Lee made earlier, that hasn&#39;t changed.</span><br></div></div><div><b=
r></div>-- <br><div class=3D"gmail_signature" data-smartmail=3D"gmail_signa=
ture">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=
=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</=
a><br>Networking &amp; Telecommunication Services<br>Office of Information =
Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave S=
E=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3=
029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
</div></div>

--000000000000151c0a0575b09d40--


From nobody Thu Sep 13 14:29:55 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5048A130E7D; Thu, 13 Sep 2018 14:29:47 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 KndBHaL9dEKB; Thu, 13 Sep 2018 14:29:45 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 071F7130E7C; Thu, 13 Sep 2018 14:29:45 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id r69-v6so10908921oie.3; Thu, 13 Sep 2018 14:29:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=a5/UsJRTe1olkuhZ+G2CZWt/k84ynhvcNTOKokuVWLY=; b=Pflfejm+Sgm5hdbAgWafTtou0ZetpB+qurHBtcJn1QZOo2dG7DngJDwJqK+Gnv85MO Lq/1aKQHZMb7vUQKVbV0LjXiHkGuVZP+YYZ/AZyfcxkaE+zjJDuQmcGF3BobyX3FEznG bWy08NctVkVPvby2NdydqqNiggVxm7GJHn42A6SvKTwteEOUwTPrUExpgwNiUpcUo0Sa TihFVfxmI4h6FwWWr9cLO3csjmjAT2XYN1nzVRsnrwxYMIyAS3lpzz/Be51aVtsBlsCQ u7Cy8zuhQDt9PFY5Ncjw3ZOlw5JJvPBR0fAMBdEJgnQtF4K87nGqusDDl6MBo5OhU8WA vnlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=a5/UsJRTe1olkuhZ+G2CZWt/k84ynhvcNTOKokuVWLY=; b=dSmUPQXrn9yOqUMMaPgVGa8oriG4gySUCu/OQ36a2N4iWkkxoSHOEMah6ia9YHEWpC DeaPCIqjUX96/aDbJ2q6Anb6l/XDIYBZY67dNQ5drmrFTgSAn8UQgOE+hYlZ3fsbESY+ ZHWI13m8J/DXn7ItQVTcQ7WYVBh5bAfmFqmq3i63eAwlvocFxRp1vQcN5mI2/252MZ05 FMAHO3fNX90DGl5CuLb9MRI9gZmPmneL2Ty3hKd0DzhL9qKF7BY7+p0ZbLthk8eVwXDu TMFmXtxEmiVhTAL/qqTFYaivfusQOwYTixrMGS7zRy2qYvJ4dR8pNTOUIil5WP97Tipv hW/A==
X-Gm-Message-State: APzg51CBAppyHZ7yS+XE13HTfZUnWVsUdCx92VpU21aeRgZ9WO9ywymG qhNUl3STQ2LMMM4bT0XIwNF/W8Cc
X-Google-Smtp-Source: ANB0VdaiNTtUxws8mjceO3aMqvVFtw4DRZX9cruaOdruFdJ0fI6zWtwKZ4o36OQwGCAWr3WsJid+fg==
X-Received: by 2002:aca:f105:: with SMTP id p5-v6mr8065060oih.342.1536874184269;  Thu, 13 Sep 2018 14:29:44 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1073? ([2600:8802:5600:1546::1073]) by smtp.gmail.com with ESMTPSA id q12-v6sm942364otd.41.2018.09.13.14.29.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Sep 2018 14:29:43 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_9ACC1D7F-9565-4A26-89BF-7150FB92DCE1"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 13 Sep 2018 14:29:41 -0700
In-Reply-To: <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi>
Cc: 6man WG <ipv6@ietf.org>, V6 Ops List <v6ops@ietf.org>
To: Markku Savela <msa@moth.iki.fi>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/YurFA9dZHSWEQFLo6hhfqnkE2bA>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Sep 2018 21:29:47 -0000

--Apple-Mail=_9ACC1D7F-9565-4A26-89BF-7150FB92DCE1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Speaking strictly for myself, all one of me. However, I'm copying v6ops =
in case someone operational will dispute my viewpoint or support it.

I would expect that if an ISP is offering only IPv6 to the CPE, the CPE =
might well implement both an IPv6 router and a 464XLAT CLAT for IPv4 =
within the LAN. The ISP will never know whether there is actual IPv4 in =
the home/SOHO/Enterprise, other than that the PLAT it presumably =
implements will see traffic. If it's doing CGN, MAP-E, or MAP-T, it is =
implementing the overlay, will be aware of it, and will be paying for =
it; the 464XLAT model means that it doesn't have to think about it (or =
pay for it) beyond the PLAT and its prefix. I'm hearing rumblings from =
various operators to the effect that IPv4 is becoming operationally =
expensive - one that has been in the news recently was Aussie Broadband, =
but they are in no sense the only source of such rumblings.

=46rom my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 is =
the best case currently on the table. If 6man agrees, I would suggest =
using draft-pref64folks-6man-ra-pref64 at PS to deprecate (make =
historic/NOT RECOMMENDED) RFCs 6147 and 7050. In that, there would be =
value in a plugfest, perhaps at IETF 103 or 104 during the Hackathon, to =
let various implementors demonstrate draft-ietf-v6ops-transition-ipv4aas =
using 464XLAT+draft-pref64folks-6man-ra-pref64 and state their roll-out =
plans.

I find myself thinking about =
https://www.youtube.com/watch?v=3D_y36fG2Oba0. Yes, I think a day =
something like that is coming. First they ignore you; then they laugh at =
you, ...

> On Sep 12, 2018, at 2:31 AM, Markku Savela <msa@moth.iki.fi> wrote:
>=20
> On 12/09/18 12:08, Ole Troan wrote:
>>>> If there is a DHCPv4 response, then the host SHOULD NOT shut down =
IPv4
>>>> operations. The RA flag is incorrectly configured.  Barbara
>>> I don't agree.  If all the RAs have ipv6-only set, and there is =
still DHCPv4,
>>> I'd conclude that the IPv4 is fake.
>> Agree. =46rom my perspective the whole point of this flag is to =
signal configuration information to hosts.
>> A compliant host receiving this flag, should disable all IPv4 =
processing on the relevant interface.
>=20
> And if I have a home/site network
>=20
> - connected to ISP offering IPv6 only,
>=20
> - and internally using additional IPv4 addresses via local DHCP server =
(or via another ISP connection offering IPv4) to support locally IPv4 =
only legacy devices (printers, etc.).
>=20
> As home/small site user (*), I may not have ANY control on RA's sent =
by the first ISP. If they were to set this ipv6-only flag and, if this =
would disable my IPv4 addressing, I would be a bit pissed off...
>=20
> (*) though, if ISP provided "home router" is configurable, and the =
ipv6-only flag in RA would be controllable by home user. Then maybe =
acceptable...
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_9ACC1D7F-9565-4A26-89BF-7150FB92DCE1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlua1sUACgkQEhdRnd2G
P+BDhQ/+LtYy9DQUuzZwJ5+mLemwABJwAQIYeYNBL0P85tA+UwKc4RQJ55kftohb
WXUvY8GhgvUS4YiFyAfE8cR6+MpHxdgdywLHdp0afFETFWuPlYgvHuoVVkWVHpyY
wqROEvLeLhqD7lvo7xmHvZ/XHx3+sBTN5iRUOvanTjIUsc52FdKsuQPt+/bCJOFX
/zTU1mlC7aIfzZFB+de8D4IKR/oTBGOgtxusWvC8U0K+XjJJtv+beWH5CnTa7CRx
4tFuT/wNipfpDNrxBIlu/EB+R6BMi7VFGyazhbBeLTTkozlyLVzkP3zGXXD6Wx2q
kRY0Jr9asFGkldq4UhbU5VrPvtAVT/XbakUnSgaMfHb60k4TH4iC6DTanka6y1Co
eyX5bHMFErZg9nR2GymnFr4x6oWcmkjgxCZvWrXtNXgbc0rceQjeewNikanL3SUW
sR7O2dwpOW6NuVv5qNKe7FqHzUDdPAKFZaMrX8qakdhuSczyFmB06OfW6MoYjqFm
TYwUOzR/XnfI7OrD8B8gkwBWhZA4kEdbLTDNb5SaabnIjMDyqZ5C0JyxFb/sTbC2
pNJQ3ZHXEdO2ZIIivF7GHDUfLNNmRKGwIXxbP8v4G4ZaYHgyZyZGItR6hmFvf6uP
X8obmcoyCTEPB0sXir+2eI4FRYVJjRbZ+ETdxRKdTUBeuw63jMk=
=3GH7
-----END PGP SIGNATURE-----

--Apple-Mail=_9ACC1D7F-9565-4A26-89BF-7150FB92DCE1--


From nobody Thu Sep 13 14:52:48 2018
Return-Path: <session-request@ietf.org>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 34380130E05; Thu, 13 Sep 2018 14:52:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: warren@kumari.net, v6ops@ietf.org, v6ops-chairs@ietf.org, fredbaker.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com>
Date: Thu, 13 Sep 2018 14:52:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8TRU2yArSx8Dll-mFiyb1zgq3mE>
Subject: [v6ops] v6ops - New Meeting Session Request for IETF 103
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Sep 2018 21:52:45 -0000

A new meeting session request has just been submitted by Fred Baker, a Chair of the v6ops working group.


---------------------------------------------------------
Working Group Name: IPv6 Operations
Area Name: Operations and Management Area
Session Requester: Fred Baker

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 70
Conflicts to Avoid: 
 First Priority: rtgwg mboned ipsecme dnsop grow intarea 6man  ippm
 Second Priority: suit tsvwg opsec idr  
 Third Priority:   6lo bess bier ccamp    ipwave  l2sm lsr lsvr mpls netmod nvo3  opsawg  quic  sfc teas


People who must be present:
  Fred Baker
  Ron Bonica
  Warren &quot;Ace&quot; Kumari

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Thu Sep 13 15:30:23 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A68E3130E78 for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 15:30:21 -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, FREEMAIL_FROM=0.001, 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 1u-EljUuYcz8 for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 15:30:20 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 01D79130DC5 for <v6ops@ietf.org>; Thu, 13 Sep 2018 15:30:19 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id i10-v6so2800124oth.0 for <v6ops@ietf.org>; Thu, 13 Sep 2018 15:30:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc:reply-to:message-id :references:to; bh=QzJC4e7Qg3FARoJ9Hf9SvxZpFBKxMdtY7KNFU7M7V0A=; b=QTdTGBVlPeeJ7+BV2AziAf3DoYWFxvT77b4vAxi3gtb4DieZfjckC1efZFSii9Gik9 sCfaoN11Lf0k4v1aQyB33QQwi1TTpxRO9IpltPNhoJk8MDueWkhTKVydRz8NaYE2qQOJ yPF2wR7LwOMEMuV8X7Gn8zYiETXpFsvISQ5aAnx5ShSlIqExj+TLiN9gYekXouUpRvOV 1iyDD0gESpn7c3YLOIUn5cbo8ojCapQgCbbt8w+e7n8JNEkxlcBT8jIxu8dyQSVvUgZn V8bbNidPBgwuTB29D5O8Q1KnvQOAiihffZhdv1H6dXahfa+tKmgAHio80220NxmCaSFp uhQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :reply-to:message-id:references:to; bh=QzJC4e7Qg3FARoJ9Hf9SvxZpFBKxMdtY7KNFU7M7V0A=; b=Iqh5WUa5PATmpbA/LeYPGz/nMjKAL4wid7k5z0BejkfBTE5wW1d8YJkplrkAiKwtrU ORvekwoqAW+s+MlU+2ULMD4UNbaF9lqsbLDQsRUEnLI82XZSs2DxsK7r5Ey319am5Rfm 9KhVLQuHnZrqsvxZkwMBkpR0puEvK3xZAfwv0la3kZTnbOsjjV9OFDD7TDaYydfDbEkj qBW3i4ZtYmx8cHuGsJ3o5WNBegOCzwjjQ9T/jcliKIuUkDKTbGRZFSMg6sXjIkFSHAHu mk1l0kUy/ZAdbylj0s3hJg0lvwRI1tzUfpy4uMPD4Kao7+Gr0FxWWKkKeGXE7AlkaFxo f7xQ==
X-Gm-Message-State: APzg51B8fX07+ic6qjtMJoQzDBHRUqNJ2kjzlupUdFvVP+CH9JYbIJx2 mg2jjMMfUJuq5fXDnj/Zzl7Zh8e3
X-Google-Smtp-Source: ANB0VdZDVViA/d3RuZIk0lERyjnTEHjrUoRl7H7CNeFwUN+RP8rk97UBg7m9c/DmCBZLAG4352NiHA==
X-Received: by 2002:a9d:2055:: with SMTP id n79-v6mr2474455ota.379.1536877818183;  Thu, 13 Sep 2018 15:30:18 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1073? ([2600:8802:5600:1546::1073]) by smtp.gmail.com with ESMTPSA id q124-v6sm2471756oif.8.2018.09.13.15.30.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Sep 2018 15:30:17 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_C4C94C2D-DCEF-48FA-BFDE-4BDCA92DCB71"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com>
Date: Thu, 13 Sep 2018 15:30:15 -0700
Cc: Warren Kumari <warren@kumari.net>, Ron Bonica <ron@bonica.org>
Reply-To: V6Ops Chairs <v6ops-chairs@ietf.org>
Message-Id: <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
References: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com>
To: V6 Ops List <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jruyYPKqkrqIOF5Q_7u_znl0Hyc>
Subject: [v6ops] IETF 103 meeting planning
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Sep 2018 22:30:22 -0000

--Apple-Mail=_C4C94C2D-DCEF-48FA-BFDE-4BDCA92DCB71
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

FYI, I have requested one meeting for v6ops in November, as follows. =
Most important might be the clash list; I derived that in part from =
history and in part from the list of working groups our authors also =
have work in. I freely admit I may have misprioritized a potential =
conflict. If you have any heartburn in this, please let Ron and I know =
to correct it.

One thing that is happening, experimentally, is reducing the meeting =
days from Monday-Friday to Monday-Thursday, and apparently no longer =
having 2.5 hour morning meetings (such slots were not presented to me as =
option). In the past few meetings, we have had a too-packed meeting (in =
London) and time on our hands (in Montreal). Given the current set of =
drafts, I expect to have a presentation from CERNET on their IPv6-only =
experience (which has been ongoing for 10+ years, with IVI/SIIT between =
their IPv6-only network and their IPv4-only network), an discussion of =
an updated version of draft-ietf-v6ops-nat64-deployment, and a =
discussion of an updated version of draft-byrne-v6ops-dnssecaaaa. We'll =
see what else shakes out between now and November...

Let me pose a question that I think I know the answer to, but per our =
procedures I need to formally ask. We had several comments during the =
discussion of draft-byrne-v6ops-dnssecaaaa to the effect that it should =
be BCP. To accomplish that, I think it should be a working group draft =
(e.g., we agree to collaborate to make it happen). Do we agree to ask =
Cameron to resubmit as draft-ietf-v6ops-dnssecaaaa and target BCP =
status?

While I'm commenting and asking questions, let me ask one more. On =
several occasions in the past, I have asked the working group to focus =
on a particular draft and comment on it, with mixed results. Between =
IETF 101 and 102, and again since IETF 102, we have weekly asked the =
working group to look at a given draft and comment. That has seemed, to =
Ron and I, to have worked reasonably well - we have gotten comments on =
drafts without the noise level that we have seen in the past, and have =
gotten some pretty clear direction on what should happen with various =
drafts. One side-effect, not altogether unintended, has been to need =
less meeting time f2f. We talk about the IETF doing much of its work on =
mailing lists, but v6ops has had difficulty doing that in the past. I'd =
like to believe that maybe we have a formula that helps this work =
better.

What is your opinion of the weekly "let's take a look at X"? Is it =
helpful to you? Is it a practice you would like to see continue?

On Sep 13, 2018, at 2:52 PM, IETF Meeting Session Request Tool =
<session-request@ietf.org> wrote:
> A new meeting session request has just been submitted by Fred Baker, a =
Chair of the v6ops working group.
>=20
> ---------------------------------------------------------
> Working Group Name: IPv6 Operations
> Area Name: Operations and Management Area
> Session Requester: Fred Baker
>=20
> Number of Sessions: 1
> Length of Session(s):  2 Hours
> Number of Attendees: 70
> Conflicts to Avoid:
> First Priority: rtgwg mboned ipsecme dnsop grow intarea 6man  ippm
> Second Priority: suit tsvwg opsec idr
> Third Priority: 6lo bess bier ccamp ipwave l2sm lsr lsvr mpls netmod =
nvo3 opsawg quic sfc teas
>=20
>=20
> People who must be present:
>  Fred Baker
>  Ron Bonica
>  Warren &quot;Ace&quot; Kumari
>=20
> Resources Requested:
>=20
> Special Requests:
>=20
> ---------------------------------------------------------
>=20

=
--------------------------------------------------------------------------=
------
The fact that there is a highway to hell and a stairway to heaven is an =
interesting comment on projected traffic volume...


--Apple-Mail=_C4C94C2D-DCEF-48FA-BFDE-4BDCA92DCB71
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlua5PcACgkQEhdRnd2G
P+BA1g//RUxwGwiakGzzD3IuxyWAqODTgCBWc/XwwdXRaIfcYTQYSe3dNrKGYHYh
gwmFjFdrnaFY0TEt6jdg4OIl/rMDBpsRbD2hz3tNhmgpUaaaQAqAc+aVLNxGgc0Y
PwOjsODMo0ni8AKQYDZ25jeBnlB8I7ttMmDMpwX/s59Id+FBBsZ+vET6spHx/7NG
YK/3wxdsrK0QPVpxVf9sQx/VwiB79XLov/YRC2TQyZ5UOzHdFeyYyTsyCXqjsoAf
P9EWzkBXksvHKRDnJ81qN8WPTFYofG1xRcUkrG6WlvzZSr+L//z5lh35ezWRNao1
ITj1KdgXCbsnClfizXbx2kOc48lNVTbfsh3pcSe634kftHEAOQ/pJ4PeGsQuRz7O
N8pIdZk3UmAcnTv7YRhNwgsFHcJqZLo8leIEclpa0C8X407KIURs3A5Xp/qGcUtc
n1ys51QE4ZY4Afu9aqqXU0q4FLffE4oabqZZfA37uegLJvjk7V2GjmTA1WrCzemN
XP+LqGpZcdzEn9kc5WuRriu4o3S1kz0wG3pefOvpoDhojgqOdLwzK89E8Dq794NI
JHJ5v81dcUTSQNHCDNg2kvZl8pLjHOdaxUhg558q7kNcB7HZwLvfHZZgNMZ+PZPY
egBwYrMmxZMjHbqH5BaY91IwWkULOKvvHY8JY0w+BwFHR9IDNLc=
=PVDb
-----END PGP SIGNATURE-----

--Apple-Mail=_C4C94C2D-DCEF-48FA-BFDE-4BDCA92DCB71--


From nobody Thu Sep 13 16:46:10 2018
Return-Path: <prvs=1794e86a39=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B764212008A for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 16:46:08 -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
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 1IoT64gAURWM for <v6ops@ietfa.amsl.com>; Thu, 13 Sep 2018 16:46:06 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AF2A129C6B for <v6ops@ietf.org>; Thu, 13 Sep 2018 16:46:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1536882363; x=1537487163; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=abHWRWJj m24enmace4m0GMv2msUUFCkLoLRuSzhFSg8=; b=gPmk0GveFFpWln8VB+JjAxrA x4/KFSaG2O7Sh+tvfEM0UclxH4J1cOc3T2NSvLZ4hrOXFZYRK7AnxYBaVzmPXAFT 3uB/dkRhPWtPZxZWOlHVQuRrceBeN6olF9yfAhR6k90kSziW10rKZKrzynSCt0FC 0i7N4blQ7PdFat/UluA=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Fri, 14 Sep 2018 01:46:03 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 14 Sep 2018 01:46:03 +0200
Received: from [172.16.188.4] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005878758.msg for <v6ops@ietf.org>; Fri, 14 Sep 2018 01:46:01 +0200
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [172.16.188.4]
X-MDArrival-Date: Fri, 14 Sep 2018 01:46:01 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1794e86a39=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Fri, 14 Sep 2018 10:45:43 +1100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <36F6603F-D589-4EE1-99F2-15E05E591EC2@consulintel.es>
Thread-Topic: [v6ops] IETF 103 meeting planning
References: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com> <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
In-Reply-To: <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/NDwvFn3j-uJ0HTCTQrwlojJv_3k>
Subject: Re: [v6ops] IETF 103 meeting planning
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Sep 2018 23:46:09 -0000

Hi Fred, all,

I agree that it will be good to adopt draft-byrne-v6ops-dnssecaaaa as a BCP=
/WG item.

Regarding the one week per draft. I think is good, but I also think that fr=
om time to time, if a document is not getting inputs, it may be because peo=
ple is busy with their own daily work, and the option is to repeat that aft=
er a few weeks. A kind of rolling list among the different documents.

We had several documents that got no inputs at a given moment, and when we =
tried again after some weeks, they got comments.

Regards,
Jordi
=20
=20

=EF=BB=BF-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Fred Baker <fredbaker.ietf@=
gmail.com>
Responder a: V6Ops Chairs <v6ops-chairs@ietf.org>
Fecha: viernes, 14 de septiembre de 2018, 9:31
Para: V6 Ops List <v6ops@ietf.org>
CC: Ron Bonica <ron@bonica.org>
Asunto: [v6ops] IETF 103 meeting planning

    FYI, I have requested one meeting for v6ops in November, as follows. Mo=
st important might be the clash list; I derived that in part from history a=
nd in part from the list of working groups our authors also have work in. I=
 freely admit I may have misprioritized a potential conflict. If you have a=
ny heartburn in this, please let Ron and I know to correct it.
   =20
    One thing that is happening, experimentally, is reducing the meeting da=
ys from Monday-Friday to Monday-Thursday, and apparently no longer having 2=
.5 hour morning meetings (such slots were not presented to me as option). I=
n the past few meetings, we have had a too-packed meeting (in London) and t=
ime on our hands (in Montreal). Given the current set of drafts, I expect t=
o have a presentation from CERNET on their IPv6-only experience (which has =
been ongoing for 10+ years, with IVI/SIIT between their IPv6-only network a=
nd their IPv4-only network), an discussion of an updated version of draft-i=
etf-v6ops-nat64-deployment, and a discussion of an updated version of draft=
-byrne-v6ops-dnssecaaaa. We'll see what else shakes out between now and Nov=
ember...
   =20
    Let me pose a question that I think I know the answer to, but per our p=
rocedures I need to formally ask. We had several comments during the discus=
sion of draft-byrne-v6ops-dnssecaaaa to the effect that it should be BCP. T=
o accomplish that, I think it should be a working group draft (e.g., we agr=
ee to collaborate to make it happen). Do we agree to ask Cameron to resubmi=
t as draft-ietf-v6ops-dnssecaaaa and target BCP status?
   =20
    While I'm commenting and asking questions, let me ask one more. On seve=
ral occasions in the past, I have asked the working group to focus on a par=
ticular draft and comment on it, with mixed results. Between IETF 101 and 1=
02, and again since IETF 102, we have weekly asked the working group to loo=
k at a given draft and comment. That has seemed, to Ron and I, to have work=
ed reasonably well - we have gotten comments on drafts without the noise le=
vel that we have seen in the past, and have gotten some pretty clear direct=
ion on what should happen with various drafts. One side-effect, not altoget=
her unintended, has been to need less meeting time f2f. We talk about the I=
ETF doing much of its work on mailing lists, but v6ops has had difficulty d=
oing that in the past. I'd like to believe that maybe we have a formula tha=
t helps this work better.
   =20
    What is your opinion of the weekly "let's take a look at X"? Is it help=
ful to you? Is it a practice you would like to see continue?
   =20
    On Sep 13, 2018, at 2:52 PM, IETF Meeting Session Request Tool <session=
-request@ietf.org> wrote:
    > A new meeting session request has just been submitted by Fred Baker, =
a Chair of the v6ops working group.
    >=20
    > ---------------------------------------------------------
    > Working Group Name: IPv6 Operations
    > Area Name: Operations and Management Area
    > Session Requester: Fred Baker
    >=20
    > Number of Sessions: 1
    > Length of Session(s):  2 Hours
    > Number of Attendees: 70
    > Conflicts to Avoid:
    > First Priority: rtgwg mboned ipsecme dnsop grow intarea 6man  ippm
    > Second Priority: suit tsvwg opsec idr
    > Third Priority: 6lo bess bier ccamp ipwave l2sm lsr lsvr mpls netmod =
nvo3 opsawg quic sfc teas
    >=20
    >=20
    > People who must be present:
    >  Fred Baker
    >  Ron Bonica
    >  Warren &quot;Ace&quot; Kumari
    >=20
    > Resources Requested:
    >=20
    > Special Requests:
    >=20
    > ---------------------------------------------------------
    >=20
   =20
    -----------------------------------------------------------------------=
---------
    The fact that there is a highway to hell and a stairway to heaven is an=
 interesting comment on projected traffic volume...
   =20
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Thu Sep 13 16:53:19 2018
Return-Path: <prvs=1794e86a39=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA6D12008A; Thu, 13 Sep 2018 16:53:18 -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
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 4PR9KQ0B_VNI; Thu, 13 Sep 2018 16:53:15 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCBDF129C6B; Thu, 13 Sep 2018 16:53:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1536882793; x=1537487593; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=wgYrHKXFF2w4/6Wp6ehbbc8R4+ZmO/0yuZBJ6D9JJiI=; b=wgv6h0G5RtkOR vv7bqbvaNUAHW1Kg4IBuTzMTevYEFRr2BiiCbMIdIOUgKBWDfmiPWZhx4WJHj8Qs j9OvDpudYv9Mh/dolAaIpNrx+rSCUtxQufTNsZ93aHpHzEKU3HjW+hM9MRaEnu74 GrYHCEvU2hZgYTs6KfRwByo2/nXDhs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Fri, 14 Sep 2018 01:53:13 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 14 Sep 2018 01:53:12 +0200
Received: from [172.16.188.4] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005878760.msg; Fri, 14 Sep 2018 01:53:11 +0200
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [172.16.188.4]
X-MDArrival-Date: Fri, 14 Sep 2018 01:53:11 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1794e86a39=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Fri, 14 Sep 2018 10:52:53 +1100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Fred Baker <fredbaker.ietf@gmail.com>, Markku Savela <msa@moth.iki.fi>
CC: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Message-ID: <A37699C4-9A10-4DFC-A20B-29018B1C99C8@consulintel.es>
Thread-Topic: [v6ops] ipv6only-flag-02 security
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com>
In-Reply-To: <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Bn3zDGr2Iy2EKEkeyJ1VyuYdDcc>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Sep 2018 23:53:18 -0000

I fully agree with this point of view.

Regards,
Jordi
=20
=20

=EF=BB=BF-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Fred Baker <fredbaker.ietf@=
gmail.com>
Fecha: viernes, 14 de septiembre de 2018, 8:31
Para: Markku Savela <msa@moth.iki.fi>
CC: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Asunto: Re: [v6ops] ipv6only-flag-02 security

    Speaking strictly for myself, all one of me. However, I'm copying v6ops=
 in case someone operational will dispute my viewpoint or support it.
   =20
    I would expect that if an ISP is offering only IPv6 to the CPE, the CPE=
 might well implement both an IPv6 router and a 464XLAT CLAT for IPv4 withi=
n the LAN. The ISP will never know whether there is actual IPv4 in the home=
/SOHO/Enterprise, other than that the PLAT it presumably implements will se=
e traffic. If it's doing CGN, MAP-E, or MAP-T, it is implementing the overl=
ay, will be aware of it, and will be paying for it; the 464XLAT model means=
 that it doesn't have to think about it (or pay for it) beyond the PLAT and=
 its prefix. I'm hearing rumblings from various operators to the effect tha=
t IPv4 is becoming operationally expensive - one that has been in the news =
recently was Aussie Broadband, but they are in no sense the only source of =
such rumblings.
   =20
    From my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 is t=
he best case currently on the table. If 6man agrees, I would suggest using =
draft-pref64folks-6man-ra-pref64 at PS to deprecate (make historic/NOT RECO=
MMENDED) RFCs 6147 and 7050. In that, there would be value in a plugfest, p=
erhaps at IETF 103 or 104 during the Hackathon, to let various implementors=
 demonstrate draft-ietf-v6ops-transition-ipv4aas using 464XLAT+draft-pref64=
folks-6man-ra-pref64 and state their roll-out plans.
   =20
    I find myself thinking about https://www.youtube.com/watch?v=3D_y36fG2O=
ba0. Yes, I think a day something like that is coming. First they ignore yo=
u; then they laugh at you, ...
   =20
    > On Sep 12, 2018, at 2:31 AM, Markku Savela <msa@moth.iki.fi> wrote:
    >=20
    > On 12/09/18 12:08, Ole Troan wrote:
    >>>> If there is a DHCPv4 response, then the host SHOULD NOT shut down =
IPv4
    >>>> operations. The RA flag is incorrectly configured.  Barbara
    >>> I don't agree.  If all the RAs have ipv6-only set, and there is sti=
ll DHCPv4,
    >>> I'd conclude that the IPv4 is fake.
    >> Agree. From my perspective the whole point of this flag is to signal=
 configuration information to hosts.
    >> A compliant host receiving this flag, should disable all IPv4 proces=
sing on the relevant interface.
    >=20
    > And if I have a home/site network
    >=20
    > - connected to ISP offering IPv6 only,
    >=20
    > - and internally using additional IPv4 addresses via local DHCP serve=
r (or via another ISP connection offering IPv4) to support locally IPv4 onl=
y legacy devices (printers, etc.).
    >=20
    > As home/small site user (*), I may not have ANY control on RA's sent =
by the first ISP. If they were to set this ipv6-only flag and, if this woul=
d disable my IPv4 addressing, I would be a bit pissed off...
    >=20
    > (*) though, if ISP provided "home router" is configurable, and the ip=
v6-only flag in RA would be controllable by home user. Then maybe acceptabl=
e...
    >=20
    >=20
    > --------------------------------------------------------------------
    > IETF IPv6 working group mailing list
    > ipv6@ietf.org
    > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    > --------------------------------------------------------------------
   =20
    -----------------------------------------------------------------------=
---------
    Victorious warriors win first and then go to war,
    Defeated warriors go to war first and then seek to win.
         Sun Tzu
   =20
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Fri Sep 14 04:10:47 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC0FD130E12; Fri, 14 Sep 2018 04:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 codbVimoGHA8; Fri, 14 Sep 2018 04:10:42 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDFB0126DBF; Fri, 14 Sep 2018 04:10:42 -0700 (PDT)
Received: from astfgl.hanazo.no (unknown [173.38.220.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 292CCFECBB47; Fri, 14 Sep 2018 11:10:41 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id D86CF5ABCB5; Fri, 14 Sep 2018 13:10:38 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com>
Date: Fri, 14 Sep 2018 13:10:38 +0200
Cc: Markku Savela <msa@moth.iki.fi>, V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/zXH7n0K5pQedA_93ap-Z9z4LRSA>
Subject: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 11:10:45 -0000

Fred,

Did you post this on the wrong thread? I am not sure how this relates to =
the ip6only-flag draft.
Changed subject.

> Speaking strictly for myself, all one of me. However, I'm copying =
v6ops in case someone operational will dispute my viewpoint or support =
it.
>=20
> I would expect that if an ISP is offering only IPv6 to the CPE, the =
CPE might well implement both an IPv6 router and a 464XLAT CLAT for IPv4 =
within the LAN. The ISP will never know whether there is actual IPv4 in =
the home/SOHO/Enterprise, other than that the PLAT it presumably =
implements will see traffic. If it's doing CGN, MAP-E, or MAP-T, it is =
implementing the overlay, will be aware of it, and will be paying for =
it; the 464XLAT model means that it doesn't have to think about it (or =
pay for it) beyond the PLAT and its prefix. I'm hearing rumblings from =
various operators to the effect that IPv4 is becoming operationally =
expensive - one that has been in the news recently was Aussie Broadband, =
but they are in no sense the only source of such rumblings.

Speaking as one of the editors of the MAP series documents, that=E2=80=99s=
 a misrepresentation.
PLAT =3D stateful NAT64 has similar costs and scaling properties as a =
CGN. That is, significantly worse than stateless solutions.

> =46rom my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 =
is the best case currently on the table. If 6man agrees, I would suggest =
using draft-pref64folks-6man-ra-pref64 at PS to deprecate (make =
historic/NOT RECOMMENDED) RFCs 6147 and 7050. In that, there would be =
value in a plugfest, perhaps at IETF 103 or 104 during the Hackathon, to =
let various implementors demonstrate draft-ietf-v6ops-transition-ipv4aas =
using 464XLAT+draft-pref64folks-6man-ra-pref64 and state their roll-out =
plans.

I don=E2=80=99t know if 6man has a particular view on provisioining of a =
NAT64 prefixes. Nor do I know if we should.

If you mentioned the ipv6only-flag draft in the context 464XLAT. 464XLAT =
offers a native dual-stack service, and that=E2=80=99s not what the =
ipv6only-flag draft is about.
That=E2=80=99s about true IPv6 only links, where there is no IPv4 =
packets on the link.

Ole=


From nobody Fri Sep 14 04:42:06 2018
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FBA2130E35; Fri, 14 Sep 2018 04:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level: 
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, 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 fe0ZbGkKhhY2; Fri, 14 Sep 2018 04:42:02 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 2CD36126DBF; Fri, 14 Sep 2018 04:42:02 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8EBfv65031215; Fri, 14 Sep 2018 13:41:57 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BC32F2059E3; Fri, 14 Sep 2018 13:41:57 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A7A33203195; Fri, 14 Sep 2018 13:41:57 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8EBfu6E019520; Fri, 14 Sep 2018 13:41:57 +0200
To: Ole Troan <otroan@employees.org>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, Markku Savela <msa@moth.iki.fi>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <4fcbfcea-2419-fa3a-4e27-33dd4c62e435@gmail.com>
Date: Fri, 14 Sep 2018 13:41:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/x87i59Ch-DWV9P84dkRl_7wtu9g>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 11:42:05 -0000

Le 14/09/2018 à 13:10, Ole Troan a écrit :
> Fred,
> 
> Did you post this on the wrong thread? I am not sure how this relates to the ip6only-flag draft.
> Changed subject.
> 
>> Speaking strictly for myself, all one of me. However, I'm copying v6ops in case someone operational will dispute my viewpoint or support it.
>>
>> I would expect that if an ISP is offering only IPv6 to the CPE, the CPE might well implement both an IPv6 router and a 464XLAT CLAT for IPv4 within the LAN. The ISP will never know whether there is actual IPv4 in the home/SOHO/Enterprise, other than that the PLAT it presumably implements will see traffic. If it's doing CGN, MAP-E, or MAP-T, it is implementing the overlay, will be aware of it, and will be paying for it; the 464XLAT model means that it doesn't have to think about it (or pay for it) beyond the PLAT and its prefix. I'm hearing rumblings from various operators to the effect that IPv4 is becoming operationally expensive - one that has been in the news recently was Aussie Broadband, but they are in no sense the only source of such rumblings.
> 
> Speaking as one of the editors of the MAP series documents, that’s a misrepresentation.
> PLAT = stateful NAT64 has similar costs and scaling properties as a CGN. That is, significantly worse than stateless solutions.
> 
>>  From my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 is the best case currently on the table. If 6man agrees, I would suggest using draft-pref64folks-6man-ra-pref64 at PS to deprecate (make historic/NOT RECOMMENDED) RFCs 6147 and 7050. In that, there would be value in a plugfest, perhaps at IETF 103 or 104 during the Hackathon, to let various implementors demonstrate draft-ietf-v6ops-transition-ipv4aas using 464XLAT+draft-pref64folks-6man-ra-pref64 and state their roll-out plans.
> 
> I don’t know if 6man has a particular view on provisioining of a NAT64 prefixes. Nor do I know if we should.
> 
> If you mentioned the ipv6only-flag draft in the context 464XLAT. 464XLAT offers a native dual-stack service, and that’s not what the ipv6only-flag draft is about.
> That’s about true IPv6 only links, where there is no IPv4 packets on the link.

On 4G links of smartphones using CLAT and PDP type IPv6 (no IPv4 PDP 
type) there are no IPv4 packets.

I understand CLAT has to do with 464xlat.

So I suppose there is relevance of ipv6-only flag and 464xlat.

I may be wrong though.

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


From nobody Fri Sep 14 06:00:45 2018
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D904130ED8; Fri, 14 Sep 2018 06:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 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, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 5sxYuBhWbB5j; Fri, 14 Sep 2018 06:00:36 -0700 (PDT)
Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (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 B428F130E3D; Fri, 14 Sep 2018 06:00:36 -0700 (PDT)
Received: by mail-yw1-xc2c.google.com with SMTP id y134-v6so2573839ywg.1; Fri, 14 Sep 2018 06:00:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yyQVAh1Se6jXvP1AA4Z1wsdYHLHX6ZfY2xbRp44Olak=; b=QeOsvqblw5kJBsUvglgydphJ1BsyNCK/Wls08U2nPODFghJe0/MOpewVZkVYSiFePP 6qO4+inS1wYIxVGNcJpMPbGPNVFSCxIDxCbW1Oib4iwQ0GmfWn/atflMxctaqK+v7CNI gqAxCCLjyVgeBN6qLanMCjl8fcxlPTln26mLnX2YG8gFxp+vv40wDaixABvSegQi/mYZ FM7whuToUJF4HQl31HHd7d7sOVI8Adz6xTGfEugxwqOYLN/h5mUORlZYSmhPIAt1Sc7m jp1FCB1xq0QKIkNXx1k0Lx+ufNy4bnqI0h/ToFxg6S9adWF1eeY29Uvc1U1spjwm6iXa AAmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yyQVAh1Se6jXvP1AA4Z1wsdYHLHX6ZfY2xbRp44Olak=; b=MJ/2bPXrt9AW2qTjlZJLwtdR+lGn/6DNHZ2EJdHHNkOtnZPWJcQ6RtVJFc0m/hDczs ktd2SDrWxdCm6iXATCctufD9aPDQNuoqVouv2joX1Yl5SS4xQD7LRFxbqzkVsNN7wwrK h9NEX/yEm6LrlLd+tg7aIwLYn7GFB7WbCiDwtVhR6kU2iuRsBh+SVR4VmI/nG5TaHDpP 0qzPwe1I8px3L/Ph2Dl5GSDSZqUe7V7MsxmiMgLef175ysLH3HsDQau4/UiN9nxN2xyW ijNiraUbJLJTnJY3nsLGi18JzPDG8UrZk32IIGm3hU8Mz4nhXNte1Gkc2snncDy2dTVl uAjg==
X-Gm-Message-State: APzg51CyxQx/gQX9vEz6S/lnrOynavwgtZDiHyy4CdFdL3yfCg0K7wbQ hrD0CkPoUIS1eJPxZNqOVhDh73mCfQpac5E3oi0f7A==
X-Google-Smtp-Source: ANB0VdZTJ/RX34Yu1Y0ErArkjRJX8hze9L4zcc0dCcIqCCljCTSosNwyh6w1HHxX+QpI9xlZEjZGMcpNQrA1gycFQzI=
X-Received: by 2002:a0d:c505:: with SMTP id h5-v6mr5416511ywd.477.1536930035817;  Fri, 14 Sep 2018 06:00:35 -0700 (PDT)
MIME-Version: 1.0
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
In-Reply-To: <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
From: Ca By <cb.list6@gmail.com>
Date: Fri, 14 Sep 2018 06:00:24 -0700
Message-ID: <CAD6AjGRehCH0fxJ5PQ-iqRWmUFNEP8VKx1d=huKOnaujixxOFA@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: 6man WG <ipv6@ietf.org>, Fred Baker <fredbaker.ietf@gmail.com>,  Markku Savela <msa@moth.iki.fi>, V6 Ops List <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d45fca0575d468bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/QdJQASpwkCKQfSq9YDxYTjbEiE8>
Subject: [v6ops] =?utf-8?q?Market_Rate_Cost_of_IPv4_life_support=E2=80=94?= =?utf-8?q?_was_Re=3A__NAT64_prefix_configuration?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 13:00:45 -0000

--000000000000d45fca0575d468bf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 14, 2018 at 4:11 AM Ole Troan <mblings.

>
> Speaking as one of the editors of the MAP series documents, that=E2=80=99=
s a
> misrepresentation.
> PLAT =3D stateful NAT64 has similar costs and scaling properties as a CGN=
.
> That is, significantly worse than stateless solutions.
>

Citation?  I don=E2=80=99t believe it is true, but would like to see your m=
arket
rate analysis (not the stateless religion axiom).

In my own case, coming from nat44, we simply turned on nat64 on the same
box, added ipv6 to the user, and load has gone down on that combined
nat44/64 box due to most traffic going ipv6 e2e.   In this way, nat64 has
lowerd my load / bill with no new capex. That is my specific case.

That said, i have only seen MAP BR be spec=E2=80=99d to deployed on million=
 dollar
cards in million dollar routers.  Also, map comes with a less efficient
static v4 allocation model and complex dhcpv6 deployment.  Both MAP and
NAT64 come as freeware, but that is less interesting than a commercial
solution a general telco could deploy, unless you have a freeware
deployment case study.


>
>

--000000000000d45fca0575d468bf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri,=
 Sep 14, 2018 at 4:11 AM Ole Troan &lt;mblings.</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<br>
Speaking as one of the editors of the MAP series documents, that=E2=80=99s =
a misrepresentation.<br>
PLAT =3D stateful NAT64 has similar costs and scaling properties as a CGN. =
That is, significantly worse than stateless solutions.<br>
</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">Citation?=C2=A0 =
I don=E2=80=99t believe it is true, but would like to see your market rate =
analysis (not the stateless religion axiom).=C2=A0</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">In my own case, coming from nat44, we simply tur=
ned on nat64 on the same box, added ipv6 to the user, and load has gone dow=
n on that combined nat44/64 box due to most traffic going ipv6 e2e. =C2=A0 =
In this way, nat64 has lowerd my load / bill with no new capex. That is my =
specific case.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Tha=
t said, i have only seen MAP BR be spec=E2=80=99d to deployed on million do=
llar cards in million dollar routers.=C2=A0 Also, map comes with a less eff=
icient static v4 allocation model and complex dhcpv6 deployment.=C2=A0 Both=
 MAP and NAT64 come as freeware, but that is less interesting than a commer=
cial solution a general telco could deploy, unless you have a freeware depl=
oyment case study.=C2=A0</div><div dir=3D"auto"><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><br><br>
</blockquote></div></div>

--000000000000d45fca0575d468bf--


From nobody Fri Sep 14 07:17:06 2018
Return-Path: <ianfarrer@gmx.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF7D1277BB; Fri, 14 Sep 2018 07:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 GQEHuiWyDKbi; Fri, 14 Sep 2018 07:16:56 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 A69ED12785F; Fri, 14 Sep 2018 07:16:55 -0700 (PDT)
Received: from [192.168.2.228] ([80.159.240.8]) by mail.gmx.com (mrgmx001 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MQ2Wx-1fvbxx1TRT-005FQ8; Fri, 14 Sep 2018 16:16:50 +0200
From: ianfarrer@gmx.com
Message-Id: <F0EDD5BE-5ECF-4A2C-9999-4AED25CE0739@gmx.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_873CAC1F-2D28-4BBA-BB7A-54608E3FB027"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 14 Sep 2018 16:16:48 +0200
In-Reply-To: <CAD6AjGRehCH0fxJ5PQ-iqRWmUFNEP8VKx1d=huKOnaujixxOFA@mail.gmail.com>
Cc: Ole Troan <otroan@employees.org>, V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
To: Ca By <cb.list6@gmail.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <CAD6AjGRehCH0fxJ5PQ-iqRWmUFNEP8VKx1d=huKOnaujixxOFA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Provags-ID: V03:K1:hewbFQGPBqOce//xmHQleDLbNUUP0lmAiPTzGs9ZRpwZ0FHHP8U 6ERD00+PVInFCWtd52aXgtQQqYMDPQOYDuGpZaSt1OrtM1S3QbrCYSRE+S/2BJQZESxy9Qp uN+xV/yVvBjrA+BoZPfwwilSA0fTXjPrgcP1SJDPl0O9cOzNiqEcZlXZF4Os2DHCDEEKf0u dR96Kod5+D4uAdzt2483A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:p3EHsIXqS68=:Zo22tcy2vme7Ii7M4L0kal kzyFih+w3DY9/cu/t2qhRueuQXNWybAcBvp0C7VxoB24/UnJouS5HKpcAt/ROLlTtgcIsro1+ WOBtD1Dd9KzwqWASo/8tZyen7Q0ZB/3iipr5AKOJr+imCYD2AzLt8sLOelK7rWhxalrg0TyVx /azgipkJj9su1mud3Fwa2KzqwkutwAwA/Mh9OGog6fYW+rm3OpZbGdc1HZnn/YRCrg5Phx2nI veVy7y8aLbxXLEAjhlUchu1KYBUqu2oGdU5Cg0AlCRy44/JF8/Cybr0joDfy6SgR/ycXfs0LN svdq7TxJc/OE1q9PmDD1iH0OcqCYqcoD00NxJpqqY7JVk3wWpNWrIf1Wdn8gnPmznF6kuSbSC k7bbWrfQEDSCbh2QMv2sXPDFlbZ6o5gNzUXsWppCEMqWRIR73CO47awB8Aderspz8UzhiSzxr a5VnVImSQx9CS4Xq/1RyDkHMqqGjLijtiEEtpxtife3W2wSS03KyM7yTnqPXJ0mhvz1alnNkO kYAwjk3aGPb49BsJk0MdmhpkKIHR8RHGh5Yvt/9wMTVx8F3jrqR0CU8LzJ10zmAwPjMTEqoPX OURdSbY2O8ZqvUbmgHk0mpBte0Yc4cAwRt5k8UUWfiCwvctYoVOeIB4XoHahsQJ3t9h1h6nc/ WI/SVW5wfm5PqI1Q64PJfo2Z4/FHORa8c19HC7Oytpe1rMpi4MYyPi9ABNPD8UJrE/xy4OR1O pwEg+7ZyQM8Ote4nVxKYDiUlkS9oK801P9dXqaVS+uO08RjWeuyQBerTvS1YeFFuwXc2Crq8S gPyy0vo6EGcdx4iRIKBazjyNfInPm/mk4RaRNprGRNxtfEwzxw=
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/V4GvCdD5_BFFFTG_YVHXrKhDXoc>
Subject: Re: [v6ops]  =?utf-8?q?Market_Rate_Cost_of_IPv4_life_support=E2=80=94?= =?utf-8?q?_was_Re=3A__NAT64_prefix_configuration?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 14:16:58 -0000

--Apple-Mail=_873CAC1F-2D28-4BBA-BB7A-54608E3FB027
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

H Cameron,

>=20
> Speaking as one of the editors of the MAP series documents, that=E2=80=99=
s a misrepresentation.
> PLAT =3D stateful NAT64 has similar costs and scaling properties as a =
CGN. That is, significantly worse than stateless solutions.
>=20
> Citation?  I don=E2=80=99t believe it is true, but would like to see =
your market rate analysis (not the stateless religion axiom).=20

We (DT) currently have customer deployments of both FOSS and commercial =
implementations of lw4o6 AFTRs in production. Compared to a stateful =
NAT44/64 based solution (where none was currently deployed), the =
business case was pretty simple to make.

Cheers,
Ian



--Apple-Mail=_873CAC1F-2D28-4BBA-BB7A-54608E3FB027
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">H =
Cameron,<div class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class=3D"">
Speaking as one of the editors of the MAP series documents, that=E2=80=99s=
 a misrepresentation.<br class=3D"">
PLAT =3D stateful NAT64 has similar costs and scaling properties as a =
CGN. That is, significantly worse than stateless solutions.<br class=3D"">=

</blockquote><div dir=3D"auto" class=3D""><br class=3D""></div><div =
dir=3D"auto" class=3D"">Citation?&nbsp; I don=E2=80=99t believe it is =
true, but would like to see your market rate analysis (not the stateless =
religion axiom).&nbsp;</div></div></div></div></blockquote><div><br =
class=3D""></div><div>We (DT) currently have customer deployments of =
both FOSS and commercial implementations of lw4o6 AFTRs in production. =
Compared to a stateful NAT44/64 based solution (where none was currently =
deployed), the business case was pretty simple to make.</div><div><br =
class=3D""></div><div>Cheers,</div><div>Ian</div><br class=3D""></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_873CAC1F-2D28-4BBA-BB7A-54608E3FB027--


From nobody Fri Sep 14 09:11:05 2018
Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1FA130F27 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 09:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 PKKIM-pAUpMf for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 09:10:49 -0700 (PDT)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 49E8F130DED for <v6ops@ietf.org>; Fri, 14 Sep 2018 09:10:49 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id C38131113 for <v6ops@ietf.org>; Fri, 14 Sep 2018 16:10:48 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RvMCHF4F_wBm for <v6ops@ietf.org>; Fri, 14 Sep 2018 11:10:48 -0500 (CDT)
Received: from mail-vk1-f199.google.com (mail-vk1-f199.google.com [209.85.221.199]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 81F59DF2 for <v6ops@ietf.org>; Fri, 14 Sep 2018 11:10:47 -0500 (CDT)
Received: by mail-vk1-f199.google.com with SMTP id o62-v6so1540856vko.1 for <v6ops@ietf.org>; Fri, 14 Sep 2018 09:10:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=A1J4gxFFoRivd6/cXj5NF++BP36h4kfG9BEyS9ed5RY=; b=T7o6ZNKaZ0FYGSSjGx/liG2gek4pPshNr+3IAHk3TL914U20D2POzc67okoUcI/UjW acHjM4IdAFetqyjlDYk88yItgarvNZgEltQp65Aplf4sNsYCsdeonLAeQtovkl3KtZyc LUD/zu0PLdZOXDBxaBbFCfBayQQzAdbdUsubdRaimtKkNER0okKY9wcqLZvPnM5WGtfx AL7XwZIsrvcRyMtH83PnI72iko4XfrwmbIeOIyWheEdwdCkxSo5B0Bj4TNs8W7ink4GB oRNRaG69hyO2AxhNiOsPWO3ez2ngtahFVeVKM5JzTukycBZmRqnuPbZGbTHWOtr8NR64 Ugtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=A1J4gxFFoRivd6/cXj5NF++BP36h4kfG9BEyS9ed5RY=; b=SKH9KhAp2931jTGrfh7FEzdE1YGlFyRQDA2vlg/uGKohD+JQWThGj8CVm01NEruCCC jGUdtnC2UgPND+hzLexoXejQQL2eWLP0OAAShYPsoCVePLSll8cfiXl45U3BrrwJIK/1 PAhth8+TXS+vD/bq/7EMViixNvWysSpshoBjvC/5l9Cw3508Tg2RiSEQBrTjKyynw1nD y06Tj5Q5dWAorVwemhUwymK6DBD41BXtUNCYo0hRbtgYoNRkd6COEHvOxJUX9aJRqdLq cVabUR9J9DVvf/3w0wB2nN+k1NNN6X8zLWAl+z86jmTzr2vdyj379OSL4So0ikrql87V riGw==
X-Gm-Message-State: APzg51AmsUfT0hZh9oJDs3bwunLFjXbzzXm6WG3L3dPridjocW+iHR/l jcx/J+tj2LImoB3oHevaNhWKRo5dx3lqXT8OMPC7ZFVNC7A+NLHgx5e+0AhKXSwSEbTc4rEFoMF SlgdWYxUYrEExa5VEx5GqvIaJQw==
X-Received: by 2002:ab0:7414:: with SMTP id r20-v6mr4559389uap.167.1536941446063;  Fri, 14 Sep 2018 09:10:46 -0700 (PDT)
X-Google-Smtp-Source: ANB0Vdb014KDrPvIxJ0XYp5PTWJcbPxnvb61RQKKOsdu0X/vabFyMsI1vkSG4x7UbrfVkBCEEEfpDzUsWVE43W5wBxU=
X-Received: by 2002:ab0:7414:: with SMTP id r20-v6mr4559367uap.167.1536941445454;  Fri, 14 Sep 2018 09:10:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a67:6042:0:0:0:0:0 with HTTP; Fri, 14 Sep 2018 09:10:44 -0700 (PDT)
In-Reply-To: <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com>
References: <CO1PR05MB443E35E7AC7D4B8EF0CE463AE020@CO1PR05MB443.namprd05.prod.outlook.com> <CAKC-DJgdV1aT-Av1U0Tryre-s2NGEk-vnMNRwmD2wvQ82SAnnw@mail.gmail.com> <b91a7d46-071e-0b13-fec7-efb343af60d9@asgard.org> <2B49040E-8928-4200-B03E-E473AB38CFEF@isc.org> <fe617a8b-4cb7-b559-c60e-3618103e3bcc@asgard.org> <7830409B-8A77-43F7-9982-816BE505FC4B@employees.org> <aef8903c-d923-482d-41ed-3545cb0c4610@asgard.org> <44E105F4-BEEB-4876-95E7-664B47E1DB62@employees.org> <993f76ea-683b-a039-5eab-aa9a26a43071@asgard.org> <122B01D4-A5CF-4089-ACB0-E9CBAA5E57E9@employees.org> <20180907183013.GA11393@Space.Net> <A5E7DC2E-41E6-467B-B1F9-309F22F1AE7F@gmail.com> <3175f16c-9eda-2194-4a98-5777c0a18b43@hit.bme.hu> <EC85456F-DAE6-4CE4-B4BB-B28F34FF0DD0@isc.org> <EC11349B-28B5-44C5-91D4-05619FBEEA1B@isc.org> <b5968e7f-ca4e-4288-170c-308e2bb0426a@asgard.org> <F09B8639-C266-4009-A330-94018688E708@isc.org> <CAD6AjGT+xT5FQvC5dZX57Zz37NNDy5-5g0zbpkGPCk2xZTkwvA@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Fri, 14 Sep 2018 11:10:44 -0500
Message-ID: <CAN-Dau33gdQ3RdLN3hhpYM3A-RgGLE4fS=t+2XNhkkByCw8FPA@mail.gmail.com>
To: Ca By <cb.list6@gmail.com>
Cc: Mark Andrews <marka@isc.org>, V6 Ops List <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e5b5cb0575d71041"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LBikpeNCP6PQAvrDVDaurvE2_24>
Subject: Re: [v6ops] draft-byrne-v6ops-dnssecaaaa
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 16:11:04 -0000

--000000000000e5b5cb0575d71041
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 10, 2018 at 8:25 PM, Ca By <cb.list6@gmail.com> wrote:

>
>
> On Mon, Sep 10, 2018 at 5:51 PM Mark Andrews <marka@isc.org> wrote:
>
>>
>>
>> > On 11 Sep 2018, at 9:15 am, Lee Howard <lee@asgard.org> wrote:
>> >
>> > I don't understand why you're working so hard to mark IPv4 work, when
>> the clear answer is to deploy IPv6. It's not as if it's a surprise.
>>
>> Because DNS64 hijacks all use of the DNS and prevents people people doin=
g
>> what they currently do with the DNS without a lot of specialised knowled=
ge.
>>
>> I=E2=80=99m trying to give DNS back to the customers.  If they want to b=
e able to
>> 1.1.1.1 or 8.8.8.8 as their recursive servers they should be able to.  I=
f
>> they want to run their own recursive nameservers they should be able to.
>> If they want to DNSSEC validate answers they get from their ISP they sho=
uld
>> be able to.  DNS64 breaks / makes doing this sort of thing extremely
>> difficult.  I can manage it (even if I need to install a DNS server to
>> achieve it) but most people can=E2=80=99t.
>>
>> All the issues we are talking about with DNS64 today where known about
>> and hand waved away when DNS64 was being published.  8 years later all t=
hat
>> hand waving as people deploy beyond the trivial cell phone case is comin=
g
>> back to bite.
>>
>> Mark
>
>
> That=E2=80=99s your opinion and your values.
>
> I deployed dns64 6 years ago. Very happy with results. I would deploy
> again, 5 out of 5.
>
> http://www.worldipv6launch.org/apps/ipv6week/measurement/ima
> ges/graphs/T-MobileUSA.png
>
> My view, and the i-d of referenced for this thread, all the dns64 ills go
> away if you deploy ipv6, so please deploy ipv6.
>
> And, dont expect ipv4 to work. IPv4 life support (nat, dns64, map, ...)
> breaks ipv4 in various way.
>
> CB
>

I would make a slightly stronger statement, deploying IPv6, especially on
the content side, makes the DNS64 irrelevant.

I support this draft. I also support the work on
draft-pref64folks-6man-ra-pref64. Further, once it is generally available
and supported in hosts, it wouldn't take too much to convince me to support
deprecating DNS64 and both RFCs 6147 and 7050.

DNS64 clearly has issues and I would prefer a solution like
draft-pref64folks-6man-ra-pref64. But that doesn't mean DNS64 hasn't served
a purpose. Like it or not, as a solution, it is at least partially
responsible for much of the IPv6 deployment we have today especially in the
mobile and cellular realm. Do I wish we would have done something like
draft-pref64folks-6man-ra-pref64 instead of DNS64? Yes, but that is water
under the bridge.

Thanks

--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--000000000000e5b5cb0575d71041
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div class=3D"gmail_extra"><br></div></div><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote">On Mon, Sep 10, 2018 at 8:=
25 PM, Ca By <span dir=3D"ltr">&lt;<a href=3D"mailto:cb.list6@gmail.com" ta=
rget=3D"_blank">cb.list6@gmail.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div><br></div><div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr">On Mon, Sep 10, 2018 at 5:51 PM Mark Andrews &l=
t;<a href=3D"mailto:marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
&gt; On 11 Sep 2018, at 9:15 am, Lee Howard &lt;<a href=3D"mailto:lee@asgar=
d.org" target=3D"_blank">lee@asgard.org</a>&gt; wrote:<br>
&gt; <br>
&gt; I don&#39;t understand why you&#39;re working so hard to mark IPv4 wor=
k, when the clear answer is to deploy IPv6. It&#39;s not as if it&#39;s a s=
urprise.<br>
<br>
Because DNS64 hijacks all use of the DNS and prevents people people doing w=
hat they currently do with the DNS without a lot of specialised knowledge.<=
br>
<br>
I=E2=80=99m trying to give DNS back to the customers.=C2=A0 If they want to=
 be able to 1.1.1.1 or 8.8.8.8 as their recursive servers they should be ab=
le to.=C2=A0 If they want to run their own recursive nameservers they shoul=
d be able to.=C2=A0 If they want to DNSSEC validate answers they get from t=
heir ISP they should be able to.=C2=A0 DNS64 breaks / makes doing this sort=
 of thing extremely difficult.=C2=A0 I can manage it (even if I need to ins=
tall a DNS server to achieve it) but most people can=E2=80=99t.<br>
<br>
All the issues we are talking about with DNS64 today where known about and =
hand waved away when DNS64 was being published.=C2=A0 8 years later all tha=
t hand waving as people deploy beyond the trivial cell phone case is coming=
 back to bite.<br>
<br>
Mark</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">That=E2=80=
=99s your opinion and your values.=C2=A0</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">I deployed dns64 6 years ago. Very happy with results. I w=
ould deploy again, 5 out of 5.=C2=A0</div><div dir=3D"auto"><br></div><div =
dir=3D"auto"><div><a href=3D"http://www.worldipv6launch.org/apps/ipv6week/m=
easurement/images/graphs/T-MobileUSA.png" target=3D"_blank">http://www.worl=
dipv6launch.org<wbr>/apps/ipv6week/measurement/ima<wbr>ges/graphs/T-MobileU=
SA.png</a></div><br></div><div dir=3D"auto">My view, and the i-d of referen=
ced for this thread, all the dns64 ills go away if you deploy ipv6, so plea=
se deploy ipv6.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">An=
d, dont expect ipv4 to work. IPv4 life support (nat, dns64, map, ...) break=
s ipv4 in various way.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">CB</div></div></div></blockquote><br></div><div class=3D"gmail_quote">=
<div class=3D"gmail_quote">I would make a slightly stronger statement, depl=
oying IPv6, especially on the content side, makes the DNS64 irrelevant.=C2=
=A0=C2=A0</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quo=
te">I support this draft. I also support the work on draft-pref64folks-6man=
-ra-pref64. Further, once it is generally available and supported in hosts,=
 it wouldn&#39;t take too much to convince me to support deprecating DNS64 =
and both RFCs 6147 and 7050.=C2=A0</div><div class=3D"gmail_quote"><br></di=
v><div class=3D"gmail_quote">DNS64 clearly has issues and I would prefer a =
solution like draft-pref64folks-6man-ra-pref64. But that doesn&#39;t mean D=
NS64 hasn&#39;t served a purpose. Like it or not, as a solution, it is at l=
east partially responsible for much of the IPv6 deployment we have today es=
pecially in the mobile and cellular realm. Do I wish we would have done som=
ething like draft-pref64folks-6man-ra-pref64 instead of DNS64? Yes, but tha=
t is water under the bridge.</div><div class=3D"gmail_quote"><br></div><div=
 class=3D"gmail_quote">Thanks</div><div><br></div></div>-- <br><div class=
=3D"gmail-m_8157726402515616166gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@u=
mn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; Tele=
communication Services<br>Office of Information Technology<br>University of=
 Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: 612=
-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D</div>
</div></div></div></div></div></div>

--000000000000e5b5cb0575d71041--


From nobody Fri Sep 14 09:41:02 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB1F130E1E for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 09:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 1i0ffmKCEqVs for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 09:40:58 -0700 (PDT)
Received: from atl4mhob18.registeredsite.com (atl4mhob18.registeredsite.com [209.17.115.111]) (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 8027712F1A2 for <v6ops@ietf.org>; Fri, 14 Sep 2018 09:40:58 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail02pod6.registeredsite.com [10.30.71.210]) by atl4mhob18.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8EGeuOH009434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 14 Sep 2018 12:40:56 -0400
Received: (qmail 22006 invoked by uid 0); 14 Sep 2018 16:40:56 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 14 Sep 2018 16:40:56 -0000
To: v6ops@ietf.org
References: <153687556514.29625.12933889270084668897.idtracker@ietfa.amsl.com> <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <1a3d1d14-dcf3-35ca-ca6d-b1f9977d0b11@asgard.org>
Date: Fri, 14 Sep 2018 12:40:55 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <7CEF9C90-C47A-4711-8384-B1C579965ED7@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/aINmV6dbg07OEmLBSYAtKzyoXTA>
Subject: Re: [v6ops] IETF 103 meeting planning
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 16:41:00 -0000

On 09/13/2018 06:30 PM, Fred Baker wrote:
> FYI, I have requested one meeting for v6ops in November, as follows. Most important might be the clash list; I derived that in part from history and in part from the list of working groups our authors also have work in. I freely admit I may have misprioritized a potential conflict. If you have any heartburn in this, please let Ron and I know to correct it.
>
> One thing that is happening, experimentally, is reducing the meeting days from Monday-Friday to Monday-Thursday, and apparently no longer having 2.5 hour morning meetings (such slots were not presented to me as option). In the past few meetings, we have had a too-packed meeting (in London) and time on our hands (in Montreal). Given the current set of drafts, I expect to have a presentation from CERNET on their IPv6-only experience (which has been ongoing for 10+ years, with IVI/SIIT between their IPv6-only network and their IPv4-only network), an discussion of an updated version of draft-ietf-v6ops-nat64-deployment, and a discussion of an updated version of draft-byrne-v6ops-dnssecaaaa. We'll see what else shakes out between now and November...
>
> Let me pose a question that I think I know the answer to, but per our procedures I need to formally ask. We had several comments during the discussion of draft-byrne-v6ops-dnssecaaaa to the effect that it should be BCP. To accomplish that, I think it should be a working group draft (e.g., we agree to collaborate to make it happen). Do we agree to ask Cameron to resubmit as draft-ietf-v6ops-dnssecaaaa and target BCP status?
I support WG adoption.
>
> While I'm commenting and asking questions, let me ask one more. On several occasions in the past, I have asked the working group to focus on a particular draft and comment on it, with mixed results. Between IETF 101 and 102, and again since IETF 102, we have weekly asked the working group to look at a given draft and comment. That has seemed, to Ron and I, to have worked reasonably well - we have gotten comments on drafts without the noise level that we have seen in the past, and have gotten some pretty clear direction on what should happen with various drafts. One side-effect, not altogether unintended, has been to need less meeting time f2f. We talk about the IETF doing much of its work on mailing lists, but v6ops has had difficulty doing that in the past. I'd like to believe that maybe we have a formula that helps this work better.
>
> What is your opinion of the weekly "let's take a look at X"? Is it helpful to you? Is it a practice you would like to see continue?
It's been great. I get notification that there's a draft I might want to 
read, and I read it and comment. I can handle one draft a week.

Lee


From nobody Fri Sep 14 09:53:15 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD1ED130DFB for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 09:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Level: 
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 Es5V5sHrgchl for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 09:52:58 -0700 (PDT)
Received: from atl4mhob07.registeredsite.com (atl4mhob07.registeredsite.com [209.17.115.45]) (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 C2E1012F1A5 for <v6ops@ietf.org>; Fri, 14 Sep 2018 09:52:57 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail02pod6.registeredsite.com [10.30.71.210]) by atl4mhob07.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8EGqusu020703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 14 Sep 2018 12:52:56 -0400
Received: (qmail 6257 invoked by uid 0); 14 Sep 2018 16:52:55 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 14 Sep 2018 16:52:55 -0000
To: v6ops@ietf.org
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org>
Date: Fri, 14 Sep 2018 12:52:54 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/IZXNBGSVL4vOu5JoT9S9zQRVhA8>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 16:53:13 -0000

On 09/14/2018 07:10 AM, Ole Troan wrote:
> Fred,
>
> Did you post this on the wrong thread? I am not sure how this relates to the ip6only-flag draft.
> Changed subject.
>
>> Speaking strictly for myself, all one of me. However, I'm copying v6ops in case someone operational will dispute my viewpoint or support it.
>>
>> I would expect that if an ISP is offering only IPv6 to the CPE, the CPE might well implement both an IPv6 router and a 464XLAT CLAT for IPv4 within the LAN. The ISP will never know whether there is actual IPv4 in the home/SOHO/Enterprise, other than that the PLAT it presumably implements will see traffic. If it's doing CGN, MAP-E, or MAP-T, it is implementing the overlay, will be aware of it, and will be paying for it; the 464XLAT model means that it doesn't have to think about it (or pay for it) beyond the PLAT and its prefix. I'm hearing rumblings from various operators to the effect that IPv4 is becoming operationally expensive - one that has been in the news recently was Aussie Broadband, but they are in no sense the only source of such rumblings.
> Speaking as one of the editors of the MAP series documents, that’s a misrepresentation.
> PLAT = stateful NAT64 has similar costs and scaling properties as a CGN. That is, significantly worse than stateless solutions.

I asked a vendor for performance numbers on NAT44, NAT64, and MAP, and 
their stateful solutions were faster. "We've had more time to tune and 
optimize."

>
>>  From my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 is the best case currently on the table. If 6man agrees, I would suggest using draft-pref64folks-6man-ra-pref64 at PS to deprecate (make historic/NOT RECOMMENDED) RFCs 6147 and 7050. In that, there would be value in a plugfest, perhaps at IETF 103 or 104 during the Hackathon, to let various implementors demonstrate draft-ietf-v6ops-transition-ipv4aas using 464XLAT+draft-pref64folks-6man-ra-pref64 and state their roll-out plans.
> I don’t know if 6man has a particular view on provisioining of a NAT64 prefixes. Nor do I know if we should.
>
> If you mentioned the ipv6only-flag draft in the context 464XLAT. 464XLAT offers a native dual-stack service, and that’s not what the ipv6only-flag draft is about.
> That’s about true IPv6 only links, where there is no IPv4 packets on the link.

The statement "464XLAT offers a native dual-stack service" is the 
complete opposite to my understanding of "native." What do you mean?

There are lots of ways IPv6-only links can carry IPv4 packets, and those 
ways comprise the set "transition technologies."


Lee


From nobody Fri Sep 14 10:37:35 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68DBD130E03 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 10:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 Vx9no8oDbXL5 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 10:37:31 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D72A130DCB for <v6ops@ietf.org>; Fri, 14 Sep 2018 10:37:31 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 892B9FECBB93; Fri, 14 Sep 2018 17:37:28 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org>
Date: Fri, 14 Sep 2018 19:37:19 +0200
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org>
To: Lee Howard <lee@asgard.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_4O-z7GpN_bS_P6pNU7sWdJt5iE>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 17:37:34 -0000

On 14 Sep 2018, at 18:52, Lee Howard <lee@asgard.org> wrote:

>> If you mentioned the ipv6only-flag draft in the context 464XLAT. 464XLAT o=
ffers a native dual-stack service, and that=E2=80=99s not what the ipv6only-=
flag draft is about.
>> That=E2=80=99s about true IPv6 only links, where there is no IPv4 packets=
 on the link.
>=20
> The statement "464XLAT offers a native dual-stack service" is the complete=
 opposite to my understanding of "native." What do you mean?

You are not trolling me?
All the IPv4aaS mechanisms have as their purpose to offer IPv4 service to ho=
sts. In 464xlat, as the others they hosts on links behind one of these devic=
es get native IPv4. IPv4 Ethernet 0x800. In the typical 464xlat case, triple=
 NATted, but indistinguishable from any other IPv4 service. If that was carr=
ied over MPLS, Ethernet or PPP upstream.=20

Ole





From nobody Fri Sep 14 11:44:32 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741BA130DC4 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 11:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 SNbBhI_Nhfwg for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 11:44:29 -0700 (PDT)
Received: from atl4mhob23.registeredsite.com (atl4mhob23.registeredsite.com [209.17.115.117]) (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 B6402128CFD for <v6ops@ietf.org>; Fri, 14 Sep 2018 11:44:29 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail01pod6.registeredsite.com [10.30.71.209]) by atl4mhob23.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8EIiQ1i013153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 14 Sep 2018 14:44:27 -0400
Received: (qmail 16369 invoked by uid 0); 14 Sep 2018 18:44:26 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 14 Sep 2018 18:44:26 -0000
To: Ole Troan <otroan@employees.org>
Cc: v6ops@ietf.org
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org>
Date: Fri, 14 Sep 2018 14:44:25 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/eHUrkilylLjaZbGR12oITN62rDw>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 18:44:32 -0000

On 09/14/2018 01:37 PM, Ole Troan wrote:
>
> On 14 Sep 2018, at 18:52, Lee Howard <lee@asgard.org> wrote:
>
>>> If you mentioned the ipv6only-flag draft in the context 464XLAT. 464XLAT offers a native dual-stack service, and that’s not what the ipv6only-flag draft is about.
>>> That’s about true IPv6 only links, where there is no IPv4 packets on the link.
>> The statement "464XLAT offers a native dual-stack service" is the complete opposite to my understanding of "native." What do you mean?
> You are not trolling me?
> All the IPv4aaS mechanisms have as their purpose to offer IPv4 service to hosts. In 464xlat, as the others they hosts on links behind one of these devices get native IPv4. IPv4 Ethernet 0x800. In the typical 464xlat case, triple NATted, but indistinguishable from any other IPv4 service. If that was carried over MPLS, Ethernet or PPP upstream.

If I'm trolling, I swear it's unintentional.
A mobile handset with CLAT built in is a host that only has native IPv6, 
and is doing IPv4 in translation only, right? That host couldn't be 
considered "native dual-stack," could it? Even the bump that provides 
IPv4 to the application is faking it: it's not providing native IPv4, 
it's providing translated IPv4.

Then there's the much rarer case of CLAT in a home gateway (I'd love to 
find one that work well!).  Maybe you could say they have native IPv4 
access to hosts on the LAN, maybe even throughout the house, but they 
don't have native IPv4 Internet access, do they?

If your ISP provisioned your home with IPv6+464xlat and called it 
"native dual-stack," would you be satisfied with their representation of 
their service?

All of that was about the definition of "native."  In the original 
context, I agree that a device offering CLAT, such as a home gateway or 
mobile hotspot offering CLAT, should not use the ipv6only-flag. Maybe we 
need an "ipv4-sorta" flag? (okay, now I'm trolling)

Lee

>
> Ole
>
>
>
>


From nobody Fri Sep 14 12:17:15 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3A0130E48 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 12:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 mauK-0CoUnuI for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 12:17:10 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB996130E3B for <v6ops@ietf.org>; Fri, 14 Sep 2018 12:17:10 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id B14A6FECBC69; Fri, 14 Sep 2018 19:17:09 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 8A1BE5B1ABB; Fri, 14 Sep 2018 21:17:07 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org>
Date: Fri, 14 Sep 2018 21:17:07 +0200
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C63DD8E5-0DBA-41C2-8694-EA07000C9406@employees.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org> <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6W7RXOwY0HncxF707XaYS3PWQzA>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 19:17:14 -0000

Lee,

>>>> If you mentioned the ipv6only-flag draft in the context 464XLAT. =
464XLAT offers a native dual-stack service, and that=E2=80=99s not what =
the ipv6only-flag draft is about.
>>>> That=E2=80=99s about true IPv6 only links, where there is no IPv4 =
packets on the link.
>>> The statement "464XLAT offers a native dual-stack service" is the =
complete opposite to my understanding of "native." What do you mean?
>> You are not trolling me?
>> All the IPv4aaS mechanisms have as their purpose to offer IPv4 =
service to hosts. In 464xlat, as the others they hosts on links behind =
one of these devices get native IPv4. IPv4 Ethernet 0x800. In the =
typical 464xlat case, triple NATted, but indistinguishable from any =
other IPv4 service. If that was carried over MPLS, Ethernet or PPP =
upstream.
>=20
> If I'm trolling, I swear it's unintentional.

Good. ;-)

> A mobile handset with CLAT built in is a host that only has native =
IPv6, and is doing IPv4 in translation only, right? That host couldn't =
be considered "native dual-stack," could it? Even the bump that provides =
IPv4 to the application is faking it: it's not providing native IPv4, =
it's providing translated IPv4.

The host has an IPv4 enabled interface, and an IPv4 only application on =
that host sends IPv4 packets that appear just like they were sent =
(barring the =E2=80=9Cnormal IPv4 NAT=E2=80=9D to the destination.
By =E2=80=9Cnative dual-stack=E2=80=9D, I would consier both protocols =
delivered on =E2=80=9Cequal=E2=80=9D terms, that=E2=80=99s not quite the =
case when the application runs on the CLAT as in this case. It=E2=80=99s =
certainly not an IPv6 only host.

> Then there's the much rarer case of CLAT in a home gateway (I'd love =
to find one that work well!).  Maybe you could say they have native IPv4 =
access to hosts on the LAN, maybe even throughout the house, but they =
don't have native IPv4 Internet access, do they?

This was the case I was mainly thinking about, and since this happens =
for all tethering cases I doubt it=E2=80=99s rare.
Anyway those hosts are certainly =E2=80=9Cnative dual stack=E2=80=9D, if =
you are lucky enough that the CLAT also gives you IPv6.
On that link you could put an unchanged IPv4 host from the 80s, and it =
would still work, right?

> If your ISP provisioned your home with IPv6+464xlat and called it =
"native dual-stack," would you be satisfied with their representation of =
their service?

Yes. There is nothing distinguishing the resulting IPv4 service from =
LW46, MAP-E/T or 464XLAT from IPv4 delivered if the upstream access was =
Ethernet, PPP or HDLC. Or more typically some sort of L2TP tunnelling.
>=20
> All of that was about the definition of "native."  In the original =
context, I agree that a device offering CLAT, such as a home gateway or =
mobile hotspot offering CLAT, should not use the ipv6only-flag. Maybe we =
need an "ipv4-sorta" flag? (okay, now I'm trolling)

Native is from the perspective you are sitting.
A good measure I believe is if you can take an unchanged IPv4 host and =
connect it to the link, if that works, then you have native IPv4. =
Regardless of how the network delivers those packets in the network. If =
you disagree with that, then you couldn=E2=80=99t even fit header =
compression into the Internet architure.

The IPv6 only flag could have been applied on the CLAT up-link. Now, in =
the mobile network case, there is already support for that in the =
link-layer.

Cheers,
Ole=


From nobody Fri Sep 14 12:45:05 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE8D130E6B; Fri, 14 Sep 2018 12:44:57 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 o4ht49ixMFlM; Fri, 14 Sep 2018 12:44:54 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::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 764F0130E3A; Fri, 14 Sep 2018 12:44:54 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id b15-v6so13836302oib.10; Fri, 14 Sep 2018 12:44:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kwczqSRZun2u2WnwQPayOTwj1WPUk+pg3zEsy64V8tw=; b=ec1JfZ95DOPEbkbWh5L79cWJLLf3hT9o/F8lzNkJet/Fc6IN5z0Q4z7QaflhWUDQ7X uu+G+WkDL02aWS/dH+DAkna5N6jxqtTkt9CjUVSN+JD76/+X5oF1JSPht5MWEISKkfcJ sO2El+bgkUr30TBvlzkhlKaSY5ev6N9exCZPFdMrPn4DcEoi+zd4c3p+jyco1rZJJq03 m2jvEwm15mzDeJaiQ5S22yhQAq6Fz9c1Meq6W1u79w+N/2P//T1L3uhM3KNaDlDH6eQ3 V5HH8Ec/nlLTg0yXiy8rDwTS1lzH2dpfH59n112IHaKyx98EWvkFPLDVNNv0Z1Hc0N0H FR+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kwczqSRZun2u2WnwQPayOTwj1WPUk+pg3zEsy64V8tw=; b=qdYK1mnGMjSIRHx9i+/k2Jj3nRBDcvIhvgkhyztH9V6Af7eamfm5EZqcD40lQ9rfHr AcL3WDlpuRwFM6+caeFdVcChhElaYR3Mdin6AVD8qrHkL73Vivji0I2N6jsKURNcmfa4 FJpLtgzG2ao1KMpxBMlsGwsGSXLSbXh5vh2Bq7vMJ+9IIUV1dF4XJ0AGE9jLrGQPflou Skb0E1cczAmVXLxofylmHsCoV5jxZ0fMoFSy1sTTNyb5x8D3AulXoSOqe4lPt0A5WPdG q4k/rvMT8tOUU1k5NkhGQbhxO++iJwm8OJA+DQNt2e5zZK3DnIM4kj5oz7r3EdrxoVB/ EdBQ==
X-Gm-Message-State: APzg51D4XnuH52J9Fw/daMGdsA5NVYeNO/eT3WXSfP4sjl0HYxJ+8aTQ cwfFD/OkJPkHiJvwRDwQpcY=
X-Google-Smtp-Source: ANB0VdZ7T3SO3A13AGnLbmCUPK5QUpQ7kYxl/da1un4dbJCwHkGZo0mpBVhTe5AY5UlwNctAsOu6rg==
X-Received: by 2002:a54:4017:: with SMTP id x23-v6mr10013659oie.25.1536954293690;  Fri, 14 Sep 2018 12:44:53 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1073? ([2600:8802:5600:1546::1073]) by smtp.gmail.com with ESMTPSA id 207-v6sm7360720oie.14.2018.09.14.12.44.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Sep 2018 12:44:52 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <55866B92-DF5B-4E17-89A8-8B0B409AC23D@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_303BD5F0-E9BA-455B-9860-3FF4A1756A45"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 14 Sep 2018 12:44:41 -0700
In-Reply-To: <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
Cc: Markku Savela <msa@moth.iki.fi>, V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
To: Ole Troan <otroan@employees.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/B7LM7I9RjLsW9XbbOuXhyYkNWIc>
Subject: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 19:44:57 -0000

--Apple-Mail=_303BD5F0-E9BA-455B-9860-3FF4A1756A45
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Sep 14, 2018, at 4:10 AM, Ole Troan <otroan@employees.org> wrote:
>=20
> Fred,
>=20
> Did you post this on the wrong thread? I am not sure how this relates =
to the ip6only-flag draft.

Well, it was in the context of a comment raised on that thread. But yes, =
after I sent it, I realized I should have changed the subject.

> Changed subject.
>=20
>> Speaking strictly for myself, all one of me. However, I'm copying =
v6ops in case someone operational will dispute my viewpoint or support =
it.
>>=20
>> I would expect that if an ISP is offering only IPv6 to the CPE, the =
CPE might well implement both an IPv6 router and a 464XLAT CLAT for IPv4 =
within the LAN. The ISP will never know whether there is actual IPv4 in =
the home/SOHO/Enterprise, other than that the PLAT it presumably =
implements will see traffic. If it's doing CGN, MAP-E, or MAP-T, it is =
implementing the overlay, will be aware of it, and will be paying for =
it; the 464XLAT model means that it doesn't have to think about it (or =
pay for it) beyond the PLAT and its prefix. I'm hearing rumblings from =
various operators to the effect that IPv4 is becoming operationally =
expensive - one that has been in the news recently was Aussie Broadband, =
but they are in no sense the only source of such rumblings.
>=20
> Speaking as one of the editors of the MAP series documents, that=E2=80=99=
s a misrepresentation.
> PLAT =3D stateful NAT64 has similar costs and scaling properties as a =
CGN. That is, significantly worse than stateless solutions.

Agreed. But a stateless solution has the operator purchasing IPv4 =
address space and using it end to end for the IPv4 component. If the =
objective is to no longer need to purchase or manage IPv4 address space =
(Aussie Broadband's presentation at AUSNOG a couple of weeks ago being =
but one example of such a viewpoint), a solution that requires them to =
purchase and manage IPv4 in the ISP network fails the requirement.

>> =46rom my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 =
is the best case currently on the table. If 6man agrees, I would suggest =
using draft-pref64folks-6man-ra-pref64 at PS to deprecate (make =
historic/NOT RECOMMENDED) RFCs 6147 and 7050. In that, there would be =
value in a plugfest, perhaps at IETF 103 or 104 during the Hackathon, to =
let various implementors demonstrate draft-ietf-v6ops-transition-ipv4aas =
using 464XLAT+draft-pref64folks-6man-ra-pref64 and state their roll-out =
plans.


--Apple-Mail=_303BD5F0-E9BA-455B-9860-3FF4A1756A45
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlucD6wACgkQEhdRnd2G
P+A1hw/+L2yHvmg1089sCUw2V55t+/8tqm3pcZ8y91FitCEEaMrIgRdtFGVigcMh
m0pz2BMZe0+fKqjTx6DfPoauqEgoCWQ19TB2ng5nngZb5Sce3jr3k82gVH7aNo3Y
n6CURTPMxElH+2fxLR4O2qviHQSHe0aM0Hzjfftq85jCk6r29Ws2oMQ+VfjdWJoU
w05bvq55Mz8M2HargrtLlT2vjw5auIkVMIdwfxS7cgXWlTYMBl4Ri7xvi+AqH6mV
L11i2rZb+MIe8RI74JD87XkqkyU4W0VA6rPb9rDkB3VoGB+Fa88QJLg1K58qYL9k
MLDAoFQMfeb/9ANAnD2MqC6VAgT71/K2f0t0DhI0OOd89OHhpH5PmvTrKMS6YpP/
2N8DZFslQlBz5ZK1bH6f4dLbec+C2IKSe1vtlaPG0mZoBf1wuMBYGUB3bLaKZLB6
+2GFigN7MoLDuysuFgt7ntfC2Y10WA7ONNe6oKR8HIKvogHXD+Yw/Uri6lJaCkPS
i7vQJpdbaw6cg+SyvE0u+EJR2YGYFGG6l1/8fDX9tqGmsN6ShBZBvIdY47E4NdpN
gaT8nKq9vUR6PiznoTHdi5pcAsU3WC1qJsqGoUGD2rxsNzBNKbjkrmhhqAkG9CVA
+fDh0ghslssqXxZqBmsyrw/StNj6zJwvcABWrDRlVD3m7K6PBqo=
=4KlS
-----END PGP SIGNATURE-----

--Apple-Mail=_303BD5F0-E9BA-455B-9860-3FF4A1756A45--


From nobody Fri Sep 14 12:56:06 2018
Return-Path: <lencse@hit.bme.hu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9352130EE0 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 12:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 hKRpc8SiXuvK for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 12:55:57 -0700 (PDT)
Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [IPv6:2001:738:2001:4020::2c]) (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 7DD12130EF9 for <v6ops@ietf.org>; Fri, 14 Sep 2018 12:55:57 -0700 (PDT)
Received: from [192.168.1.134] (host-79-121-41-151.kabelnet.hu [79.121.41.151]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id w8EJtliS060393 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <v6ops@ietf.org>; Fri, 14 Sep 2018 21:55:53 +0200 (CEST) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-41-151.kabelnet.hu [79.121.41.151] claimed to be [192.168.1.134]
To: v6ops@ietf.org
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org> <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org> <C63DD8E5-0DBA-41C2-8694-EA07000C9406@employees.org>
From: =?UTF-8?Q?Lencse_G=c3=a1bor?= <lencse@hit.bme.hu>
Message-ID: <742a00c7-c712-8b10-39bb-4b4ca0e61c9f@hit.bme.hu>
Date: Fri, 14 Sep 2018 21:55:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <C63DD8E5-0DBA-41C2-8694-EA07000C9406@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.100.1 at frogstar.hit.bme.hu
X-Virus-Status: Clean
Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.41.151; helo=[192.168.1.134]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; 
X-DCC--Metrics: frogstar.hit.bme.hu; whitelist
X-Scanned-By: MIMEDefang 2.79 on 152.66.248.44
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jtpqu0V5SY9I3iC3MevOFW_9TWM>
Subject: [v6ops] native IPv4 vs. native IPv6 -- Re: NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 19:56:05 -0000

Dear Ole,

I wonder how would you define native IPv6.

So far, I have been teaching to my students that if they use different 
IPv6 transition technologies, which carry their IPv6 packets over IPv4 
(like 6to4, teredo, 6rd, tunnel broker, etc.), then it is not native IPv6.

Best regards,

Gábor

9/14/2018 9:17 PM keltezéssel, Ole Troan írta:
> Lee,
>
>>>>> If you mentioned the ipv6only-flag draft in the context 464XLAT. 464XLAT offers a native dual-stack service, and that’s not what the ipv6only-flag draft is about.
>>>>> That’s about true IPv6 only links, where there is no IPv4 packets on the link.
>>>> The statement "464XLAT offers a native dual-stack service" is the complete opposite to my understanding of "native." What do you mean?
>>> You are not trolling me?
>>> All the IPv4aaS mechanisms have as their purpose to offer IPv4 service to hosts. In 464xlat, as the others they hosts on links behind one of these devices get native IPv4. IPv4 Ethernet 0x800. In the typical 464xlat case, triple NATted, but indistinguishable from any other IPv4 service. If that was carried over MPLS, Ethernet or PPP upstream.
>> If I'm trolling, I swear it's unintentional.
> Good. ;-)
>
>> A mobile handset with CLAT built in is a host that only has native IPv6, and is doing IPv4 in translation only, right? That host couldn't be considered "native dual-stack," could it? Even the bump that provides IPv4 to the application is faking it: it's not providing native IPv4, it's providing translated IPv4.
> The host has an IPv4 enabled interface, and an IPv4 only application on that host sends IPv4 packets that appear just like they were sent (barring the “normal IPv4 NAT” to the destination.
> By “native dual-stack”, I would consier both protocols delivered on “equal” terms, that’s not quite the case when the application runs on the CLAT as in this case. It’s certainly not an IPv6 only host.
>
>> Then there's the much rarer case of CLAT in a home gateway (I'd love to find one that work well!).  Maybe you could say they have native IPv4 access to hosts on the LAN, maybe even throughout the house, but they don't have native IPv4 Internet access, do they?
> This was the case I was mainly thinking about, and since this happens for all tethering cases I doubt it’s rare.
> Anyway those hosts are certainly “native dual stack”, if you are lucky enough that the CLAT also gives you IPv6.
> On that link you could put an unchanged IPv4 host from the 80s, and it would still work, right?
>
>> If your ISP provisioned your home with IPv6+464xlat and called it "native dual-stack," would you be satisfied with their representation of their service?
> Yes. There is nothing distinguishing the resulting IPv4 service from LW46, MAP-E/T or 464XLAT from IPv4 delivered if the upstream access was Ethernet, PPP or HDLC. Or more typically some sort of L2TP tunnelling.
>> All of that was about the definition of "native."  In the original context, I agree that a device offering CLAT, such as a home gateway or mobile hotspot offering CLAT, should not use the ipv6only-flag. Maybe we need an "ipv4-sorta" flag? (okay, now I'm trolling)
> Native is from the perspective you are sitting.
> A good measure I believe is if you can take an unchanged IPv4 host and connect it to the link, if that works, then you have native IPv4. Regardless of how the network delivers those packets in the network. If you disagree with that, then you couldn’t even fit header compression into the Internet architure.
>
> The IPv6 only flag could have been applied on the CLAT up-link. Now, in the mobile network case, there is already support for that in the link-layer.
>
> Cheers,
> Ole
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>


From nobody Fri Sep 14 12:59:34 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9864130E90 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 12:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 IiJK52lqe6DD for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 12:59:23 -0700 (PDT)
Received: from atl4mhob17.registeredsite.com (atl4mhob17.registeredsite.com [209.17.115.110]) (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 D9B36130E51 for <v6ops@ietf.org>; Fri, 14 Sep 2018 12:59:17 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail02pod6.registeredsite.com [10.30.71.210]) by atl4mhob17.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8EJxFXa032967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 14 Sep 2018 15:59:16 -0400
Received: (qmail 13790 invoked by uid 0); 14 Sep 2018 19:59:15 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 14 Sep 2018 19:59:15 -0000
To: Ole Troan <otroan@employees.org>
Cc: v6ops@ietf.org
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org> <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org> <C63DD8E5-0DBA-41C2-8694-EA07000C9406@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <57a841ea-fc01-16c6-a485-8d6e084be897@asgard.org>
Date: Fri, 14 Sep 2018 15:59:15 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <C63DD8E5-0DBA-41C2-8694-EA07000C9406@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dDXdFUbNexRuP8LF7eBIseE8_T4>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 19:59:25 -0000

On 09/14/2018 03:17 PM, Ole Troan wrote:
>
>> A mobile handset with CLAT built in is a host that only has native IPv6, and is doing IPv4 in translation only, right? That host couldn't be considered "native dual-stack," could it? Even the bump that provides IPv4 to the application is faking it: it's not providing native IPv4, it's providing translated IPv4.
> The host has an IPv4 enabled interface, and an IPv4 only application on that host sends IPv4 packets that appear just like they were sent (barring the “normal IPv4 NAT” to the destination.
> By “native dual-stack”, I would consier both protocols delivered on “equal” terms, that’s not quite the case when the application runs on the CLAT as in this case. It’s certainly not an IPv6 only host.
Okay, so if they're not quite equal, it's not native, but it's arguably 
dual-stack.
Why, oh why, didn't we get consensus to work on Jordi's vocabulary draft?

>
>> Then there's the much rarer case of CLAT in a home gateway (I'd love to find one that work well!).  Maybe you could say they have native IPv4 access to hosts on the LAN, maybe even throughout the house, but they don't have native IPv4 Internet access, do they?
> This was the case I was mainly thinking about, and since this happens for all tethering cases I doubt it’s rare.
> Anyway those hosts are certainly “native dual stack”, if you are lucky enough that the CLAT also gives you IPv6.
> On that link you could put an unchanged IPv4 host from the 80s, and it would still work, right?

Last I heard, it doesn't happen for tethering cases, because the 
tetherers were unable to allocate IPv6 addresses. I guess you'd argue 
that the clients behind the handset/AP were single-stack IPv4.
Maybe that's been updated.
And maybe I'm putting too fine a point on it, but are they being 
"delivered on 'equal' terms" if one is in translation?

Let me back up to pre-history:
Before I had IPv6 to my house, I had native IPv4 to my home, but 
translated (i.e., not native) IPv4 to the hosts in my home.
Natives speak the language. They don't require translation.

>
>> If your ISP provisioned your home with IPv6+464xlat and called it "native dual-stack," would you be satisfied with their representation of their service?
> Yes. There is nothing distinguishing the resulting IPv4 service from LW46, MAP-E/T or 464XLAT from IPv4 delivered if the upstream access was Ethernet, PPP or HDLC. Or more typically some sort of L2TP tunnelling.

I'm not so sure. Layer 2 protocols never (for fairly high values of 
"never") touch any of the upper layer header fields. Some 
implementations of various transition technologies (including some 
NAT44) alter some header fields. I'm thinking of source port numbers or 
DF bits. In a native deployment, that would never happen.
>> All of that was about the definition of "native."  In the original context, I agree that a device offering CLAT, such as a home gateway or mobile hotspot offering CLAT, should not use the ipv6only-flag. Maybe we need an "ipv4-sorta" flag? (okay, now I'm trolling)
> Native is from the perspective you are sitting.

I do agree with that, and is what I proposed for the terminology draft. 
You might have an IPv4-only application on a native-IPv6+v4-translated 
host on an IPv6-only link that is part of an IPv6-only+IPv4aaS network.
> A good measure I believe is if you can take an unchanged IPv4 host and connect it to the link, if that works, then you have native IPv4. Regardless of how the network delivers those packets in the network. If you disagree with that, then you couldn’t even fit header compression into the Internet architure.
What is the antecedent of "you" in the clause "you have native IPv4"? I 
agree that the host is provisioned with native IPv4, but I don't agree 
that it has native IPv4 Internet connectivity.

So I go back again, to the early days of deployment. We used to ask, 
"You have IPv6, but is it *native* IPv6?" I guess the only alternatives 
then were 6rd, 6to4, 6in4, Teredo, and every other version of tunneling. 
"Native IPv6" meant you had IPv6 end to end.

Is that not what we mean anymore?  Or is it a question of tunneling vs. 
translation? It would feel very strange to say that MAP-E is native IPv4 
and MAP-T is not.

>
> The IPv6 only flag could have been applied on the CLAT up-link. Now, in the mobile network case, there is already support for that in the link-layer.

Yes, as far as I understand from others on this list and 6man, that is 
the case.

Lee


>
> Cheers,
> Ole


From nobody Fri Sep 14 13:30:56 2018
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC16130EEE for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 13:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 g3b6nLmE5sml for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 13:30:40 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39FEF130E43 for <v6ops@ietf.org>; Fri, 14 Sep 2018 13:30:40 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from simons-macbookpro.thehobsons.co.uk (Simons-MacBookPro.thehobsons.co.uk [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 1212B1BC37 for <v6ops@ietf.org>; Fri, 14 Sep 2018 20:30:33 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <742a00c7-c712-8b10-39bb-4b4ca0e61c9f@hit.bme.hu>
Date: Fri, 14 Sep 2018 21:30:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <397255ED-0627-426A-8EC2-44549E369E98@thehobsons.co.uk>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org> <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org> <C63DD8E5-0DBA-41C2-8694-EA07000C9406@employees.org> <742a00c7-c712-8b10-39bb-4b4ca0e61c9f@hit.bme.hu>
To: "v6ops@ietf.org list" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PeorBlF7Rtrx3hsrWoNUZAcSE0c>
Subject: Re: [v6ops] native IPv4 vs. native IPv6 -- Re: NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 20:30:54 -0000

Lencse G=C3=A1bor <lencse@hit.bme.hu> wrote:

> I wonder how would you define native IPv6.
>=20
> So far, I have been teaching to my students that if they use different =
IPv6 transition technologies, which carry their IPv6 packets over IPv4 =
(like 6to4, teredo, 6rd, tunnel broker, etc.), then it is not native =
IPv6.

I would suggest, as previously said in reference to native IPv4, it =
depends on what chair you are sitting in. Take my setup which (when I =
sort out the wiring after a house move) uses a GNU/Linux VM as a router =
doing PPPoE to my ISP for IPv4 and a tunnel to HE's TunnelBroker service =
for IPv6 :

If your seat is the router VM, then on the "outside" I don't have native =
IPv6 - it arrives via a tunnel. On the "inside" I am running native IPv6 =
as in "fire an IPv6 packet out of the ethernet port and it arrives at =
another host".
It could be argued that the external IPv4 service is not native either =
since external IPv4 traffic is tunnelled in a PPP connection.

For other devices on my LAN, it's native IPv6 (and IPv4) - they just =
fire out IP packets over the ethernet wire and they get routed.

So I'd use the definition also previously mentioned. If the device =
simply fires packets out of an ethernet (or wireless, or 4G, or ...) =
interface without any translation* or encapsulation beyond simply =
wrapping in a transport layer (eg PPP) then it's "native" - regardless =
of whether the packets get tunnelled in some manner upstream. But if the =
application or local host protocol stacks have to do some mangling (eg =
NAT46) then it's not native.

Analogy: We're all familiar with the Plain Old Telephone Service (POTS) =
where we have a socket on the wall, plug in an analogue phone, and get =
dial tone. We don't really care that in the exchange the signal gets =
digitised - it appears to us as an analogue service.
Now lets go VoIP ... Your provider sends you a terminal adapter with a =
POTS socket on it - and as far as your phone is concerned it's still a =
native POTS service even though the voice is now encapsulated in IP =
packets, but from the PoV of the adapter it's IP on the "outside". But =
if you get a VoIP phone, then it's not a native POTS service from the =
PoV of the phone as the phone is now talking IP packets.


From nobody Fri Sep 14 13:55:51 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87820130E00 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 13:55:49 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 j1RXA4Je0cUg for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 13:55:47 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 AC2E8130DCA for <v6ops@ietf.org>; Fri, 14 Sep 2018 13:55:47 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id p84-v6so14027744oic.4 for <v6ops@ietf.org>; Fri, 14 Sep 2018 13:55:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=cdvhhpigf0t6MX7DSsj6SfvcbC+1ZswrPdiSsLjoIFk=; b=OSyZKgD0zLqaHP8yAImZsXHt9YrSHKygcJe9rJJaNo12jg85FcLNVaFV+6iOT47OOp FjCj1GDW6l2XnRUO9egPAEEtRPMvL+bvWLFINhjTV61/ivdN0+NyNpdcvr6RWIFpR1wg kE5ZTRJbjxwIi8AIkStSsux0oRw3nWD5tN1ggW2Uk6wSQD2ALjycO/I4kbeqj+rvrc6a 4a4vdnQVYbq/vBRs/hcRyWTUHVV6ojgGx64LO9DqmNPAt45G706XhF9L/V/HIcTgOIXr Z95EHFQivIQK66zPX+DFu2mJifXf24Om9BrbcPNEYJ9LwROVZaKSghnY2bw/3kD16UqF 2SrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=cdvhhpigf0t6MX7DSsj6SfvcbC+1ZswrPdiSsLjoIFk=; b=eKVw4fdHChu+lLf3qECV9F4AwynJrnT9PxXXFqCg4nkQCQjmzGul2k3yP1L/LfqV6H KPRq93v1+MGLn1Hw1JN3gZcEFDKdlCesVK1fUQp1vgxNDMUZ+EjbQB25iJ8IV1GxR+bu hynRDuyF7pdmG/iucR2k8ZNhRFNyAEMhRKcmuuvSIVWfTevbUTa6KKwV9mnzI+qmrQJf nN3dJMX5A1inMc7bWYgpkOontNhN0EtEJZqZkchQEjQRAu2/GC8/qOjvvKaUquyBpzzW MwML0CqDec6rkZtTSvkwL5wehImF81JfEAUxG0ivvM2XYcGSG33j4fMGkfAxiJAy+q3J YcRg==
X-Gm-Message-State: APzg51B9Rd2OWmiQHvdcBx8oW845Pbre9uIOXvAdkjFDwptos9g/wjwg 5n3FAYgsS4hecij3aRHoFe0=
X-Google-Smtp-Source: ANB0VdYnWgrJQXi0uoyRwNOL+utYAw0rZsfk4S7H/mBG86M2AKmn9vxWefOgnQ/HEVqd3imk5h2FyQ==
X-Received: by 2002:aca:4f44:: with SMTP id d65-v6mr11272189oib.224.1536958547081;  Fri, 14 Sep 2018 13:55:47 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1073? ([2600:8802:5600:1546::1073]) by smtp.gmail.com with ESMTPSA id t3-v6sm4150241oie.52.2018.09.14.13.55.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Sep 2018 13:55:46 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <C9FA1716-B304-41CC-8FFF-7C245EB7E6B2@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_3653C7FE-F503-4973-87C1-A93ACD6B74A8"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 14 Sep 2018 13:55:44 -0700
In-Reply-To: <57a841ea-fc01-16c6-a485-8d6e084be897@asgard.org>
Cc: Ole Troan <otroan@employees.org>, v6ops@ietf.org
To: Lee Howard <Lee@asgard.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org> <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org> <C63DD8E5-0DBA-41C2-8694-EA07000C9406@employees.org> <57a841ea-fc01-16c6-a485-8d6e084be897@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/w-fRcOguEaOBuRqzUMachZaHTkM>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 20:55:49 -0000

--Apple-Mail=_3653C7FE-F503-4973-87C1-A93ACD6B74A8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Sep 14, 2018, at 12:59 PM, Lee Howard <Lee@asgard.org> wrote:
>=20
> And maybe I'm putting too fine a point on it, but are they being =
"delivered on 'equal' terms" if one is in translation?

Said without hats...

I'm sorry, IPv4 and IPv6 are not equals. If they were, there would be no =
argument for preferring one over the other. IPv6 gives you an end-to-end =
architecture, while IPv4 gives you a NAT-NAT architecture, with the =
issues raised in RFC 1993.

=
--------------------------------------------------------------------------=
------
The fact that there is a highway to hell and a stairway to heaven is an =
interesting comment on projected traffic volume...


--Apple-Mail=_3653C7FE-F503-4973-87C1-A93ACD6B74A8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlucIFAACgkQEhdRnd2G
P+BPjxAAvx69kpZlQeweTeqXXAHawHP2r7eIFkbsTHMMWAlQ2+o/52qAxYyhoSs9
mXlgJFF64AVPLoSzHywB+Z1iPciVqqDnw3L3KZf6z7Txw5TQ98vstyVLRTRy8TEG
yO8Pz2gpA6NjWxxmYRHV0SQNGuNSkux9tGv2d/pTuvhiWb81rDeo+dN2l/5mXanw
Ubh0YfKwfdiCpMPlK24S0g8dJ2ECjunrfQKIpNXz2DLR/y7xxvAeldNovRb91QO5
seZwzP1zdogMpZ/E5gaVj7POdGHgrbWkza8j+tpKK9tPzKj14DkaU0NicE1GwqRj
WLe4O7otZ0UvxqevjdaK3O42YtuTE0U6rms8l7kekNIwbVCoImLgtdzxYXGKRsaZ
wru+ADo5VP59AYioLp7UopHt0PSCMS1DBFGuXfioTGvOHJ5eh0QRa6Ek5thEgEh1
c0kA3qHzlUjf6FldvE1D8JBg6me8XOU9AlxM5R+zoH2/zMQEhnLLKgIA7FGEJTJA
JynxO8d3TrLWggKki97YdGaV5zbM1CdiE5eSOj9NUYZwWA5WRpeMpRzxwpT9Aytd
gqrRkEQZhpADxE/J04t7PzQCXP8d8PQEeM26tTiB4tv4La3T+/jAB+n8DUd3gFh0
emIJ8Uqn5f+Vh0BKXnz7r6lVXIz0fB+pQFZnd89eyP90v70Mp1g=
=g46B
-----END PGP SIGNATURE-----

--Apple-Mail=_3653C7FE-F503-4973-87C1-A93ACD6B74A8--


From nobody Fri Sep 14 14:17:57 2018
Return-Path: <prvs=1795d2080d=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18C59128C65; Fri, 14 Sep 2018 14:17:55 -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
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 Brlg0DUbEKuV; Fri, 14 Sep 2018 14:17:53 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30257126CB6; Fri, 14 Sep 2018 14:17:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1536959870; x=1537564670; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=Ao/9NH0pR4kvy8wW8tl+JHgRumr/VCxR7pv21cdLVI8=; b=Dg0iOw1Ha65S6 MmI6ph60WzEqmOf3e3gaVJx0GB7FY1LUjnkm/o/0++rZrJywyPuQIERP3npO60A4 jP/U2+tkvryDaTryyh20sgkLCq9jxgkTZ1W8lVroe3Xd5ZnhIgPWD343/kzTxs1Z qGozmd0tksw5HkDqDChzDnQpOoKth0=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Fri, 14 Sep 2018 23:17:50 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 14 Sep 2018 23:17:50 +0200
Received: from [172.16.188.4] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005879498.msg; Fri, 14 Sep 2018 23:17:49 +0200
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [172.16.188.4]
X-MDArrival-Date: Fri, 14 Sep 2018 23:17:49 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1795d2080d=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Sat, 15 Sep 2018 08:17:32 +1100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Ole Troan <otroan@employees.org>, Fred Baker <fredbaker.ietf@gmail.com>
CC: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Message-ID: <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es>
Thread-Topic: NAT64 prefix configuration (was: Re: [v6ops] ipv6only-flag-02 security)
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
In-Reply-To: <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/IjBQRqYOf23yJUXqkp_YHXPNzx0>
Subject: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 21:17:55 -0000

Hi Ole,

I don't think you can compare CGN with NAT64.

NAT64 is doing a much better and dynamic (on demand) usage of the port of t=
he IPv4 address pool. So, it scales much more than CGN. As a consequence, a=
n ISP need much less IPv4 addresses for the same number of customers with N=
AT64 than CGN, and you don't have many of the problems that CGN poses becau=
se the restrictions in the number of ports.

Regards,
Jordi
=20
=20

=EF=BB=BF-----Mensaje original-----
De: ipv6 <ipv6-bounces@ietf.org> en nombre de Ole Troan <otroan@employees.o=
rg>
Fecha: viernes, 14 de septiembre de 2018, 22:13
Para: Fred Baker <fredbaker.ietf@gmail.com>
CC: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Asunto: NAT64 prefix configuration (was: Re: [v6ops] ipv6only-flag-02 secur=
ity)

    Fred,
   =20
    Did you post this on the wrong thread? I am not sure how this relates t=
o the ip6only-flag draft.
    Changed subject.
   =20
    > Speaking strictly for myself, all one of me. However, I'm copying v6o=
ps in case someone operational will dispute my viewpoint or support it.
    >=20
    > I would expect that if an ISP is offering only IPv6 to the CPE, the C=
PE might well implement both an IPv6 router and a 464XLAT CLAT for IPv4 wit=
hin the LAN. The ISP will never know whether there is actual IPv4 in the ho=
me/SOHO/Enterprise, other than that the PLAT it presumably implements will =
see traffic. If it's doing CGN, MAP-E, or MAP-T, it is implementing the ove=
rlay, will be aware of it, and will be paying for it; the 464XLAT model mea=
ns that it doesn't have to think about it (or pay for it) beyond the PLAT a=
nd its prefix. I'm hearing rumblings from various operators to the effect t=
hat IPv4 is becoming operationally expensive - one that has been in the new=
s recently was Aussie Broadband, but they are in no sense the only source o=
f such rumblings.
   =20
    Speaking as one of the editors of the MAP series documents, that=E2=80=
=99s a misrepresentation.
    PLAT =3D stateful NAT64 has similar costs and scaling properties as a C=
GN. That is, significantly worse than stateless solutions.
   =20
    > From my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 is=
 the best case currently on the table. If 6man agrees, I would suggest usin=
g draft-pref64folks-6man-ra-pref64 at PS to deprecate (make historic/NOT RE=
COMMENDED) RFCs 6147 and 7050. In that, there would be value in a plugfest,=
 perhaps at IETF 103 or 104 during the Hackathon, to let various implemento=
rs demonstrate draft-ietf-v6ops-transition-ipv4aas using 464XLAT+draft-pref=
64folks-6man-ra-pref64 and state their roll-out plans.
   =20
    I don=E2=80=99t know if 6man has a particular view on provisioining of =
a NAT64 prefixes. Nor do I know if we should.
   =20
    If you mentioned the ipv6only-flag draft in the context 464XLAT. 464XLA=
T offers a native dual-stack service, and that=E2=80=99s not what the ipv6o=
nly-flag draft is about.
    That=E2=80=99s about true IPv6 only links, where there is no IPv4 packe=
ts on the link.
   =20
    Ole
    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    ipv6@ietf.org
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Fri Sep 14 15:07:47 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83ACE130E8D; Fri, 14 Sep 2018 15:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 ObKBSomSeQJ0; Fri, 14 Sep 2018 15:07:36 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 B91FE130E43; Fri, 14 Sep 2018 15:07:36 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 4CE5E3AB004; Fri, 14 Sep 2018 22:07:36 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 35F9A160046; Fri, 14 Sep 2018 22:07:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id EDF3316005C; Fri, 14 Sep 2018 22:07:35 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dDoxAGLWTu6L; Fri, 14 Sep 2018 22:07:35 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id AB308160046; Fri, 14 Sep 2018 22:07:34 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es>
Date: Sat, 15 Sep 2018 08:07:32 +1000
Cc: Ole Troan <otroan@employees.org>, Fred Baker <fredbaker.ietf@gmail.com>, V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <69A473AC-E52E-48E3-B31C-15C7E17C607F@isc.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Fv83NfJ0aIhziXefjGdzd_P-_lM>
Subject: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 22:07:39 -0000

> On 15 Sep 2018, at 7:17 am, JORDI PALET MARTINEZ =
<jordi.palet=3D40consulintel.es@dmarc.ietf.org> wrote:
>=20
> Hi Ole,
>=20
> I don't think you can compare CGN with NAT64.
>=20
> NAT64 is doing a much better and dynamic (on demand) usage of the port =
of the IPv4 address pool. So, it scales much more than CGN. As a =
consequence, an ISP need much less IPv4 addresses for the same number of =
customers with NAT64 than CGN, and you don't have many of the problems =
that CGN poses because the restrictions in the number of ports.
>=20
> Regards,
> Jordi

There is nothing architecturally different between CGN and NAT64 w.r.t. =
IPv4 port allocation.  NAT64 may have less traffic going though it as we =
know there is a IPv6 service.  For CGN we don=E2=80=99t know if there is =
a IPv6 service to offload traffic or not.

		IPv6 + NAT64 vs IPv6 + CGN vs CGN

Both destination address selection rules and DNS64 (if in use) push =
traffic towards IPv6
if there is a choice in transports.  Even if you don=E2=80=99t have =
native IPv6 you can still move traffic off the CGN using 6rd where the =
BR is stateless.

	    IPv6 + NAT64 vs IPv6 + CGN vs CGN vs CGN + 6rd

Mark
--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Fri Sep 14 16:03:11 2018
Return-Path: <prvs=1795d2080d=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A971292F1; Fri, 14 Sep 2018 16:03:10 -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
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 YUf-i3rb9t0v; Fri, 14 Sep 2018 16:03:08 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C84F12872C; Fri, 14 Sep 2018 16:03:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1536966185; x=1537570985; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=/8sDHy544QLsftZd0IoHwUeyLta50hLgTqEcvThgp+w=; b=IIECUI2EdTMw8 KcpZHpKeb1QRRRMlUfNNAFOn1uOOUuy+32ZXPGj/yonI1Yt6JAfetS+fgvwvtcl0 t+U//6anOm+ixW8B3FAQZbi8O9WkbGUSR8D6LkYEsu5xQvWsWfEMHPoVS7bOZPhB Bh5iDQgQqbxGB3szLxQBKAnVqqfOhk=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sat, 15 Sep 2018 01:03:05 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 15 Sep 2018 01:03:05 +0200
Received: from [172.16.188.4] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005879564.msg; Sat, 15 Sep 2018 01:03:04 +0200
X-MDRemoteIP: 202.22.157.240
X-MDHelo: [172.16.188.4]
X-MDArrival-Date: Sat, 15 Sep 2018 01:03:04 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1795d2080d=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Sat, 15 Sep 2018 09:13:33 +1100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Mark Andrews <marka@isc.org>, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
CC: 6man WG <ipv6@ietf.org>, V6 Ops List <v6ops@ietf.org>
Message-ID: <86710663-6F7A-4A6E-8F46-C62D46DD0DDB@consulintel.es>
Thread-Topic: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es> <69A473AC-E52E-48E3-B31C-15C7E17C607F@isc.org>
In-Reply-To: <69A473AC-E52E-48E3-B31C-15C7E17C607F@isc.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/o1W4e4mSFr9juiHMBHBqKOrOHkA>
Subject: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 23:03:10 -0000

Hi Mark,

It may depend on the specific CGN implementation protocol, but in CGN you p=
re-allocate a given number of ports per user.

Is not relevant if that user actually uses all those ports or needs more. T=
hey aren't available for other users and each user has a specific limit on =
the number of ports.

In NAT64, the ports get allocated on the fly as needed for each user. So I =
think it is clear that it is much more efficient.

Regars,
Jordi
=20
=20

=EF=BB=BF-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Mark Andrews <marka@isc.org=
>
Fecha: s=C3=A1bado, 15 de septiembre de 2018, 9:09
Para: JORDI PALET MARTINEZ <jordi.palet=3D40consulintel.es@dmarc.ietf.org>
CC: 6man WG <ipv6@ietf.org>, V6 Ops List <v6ops@ietf.org>
Asunto: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 s=
ecurity)

   =20
   =20
    > On 15 Sep 2018, at 7:17 am, JORDI PALET MARTINEZ <jordi.palet=3D40con=
sulintel.es@dmarc.ietf.org> wrote:
    >=20
    > Hi Ole,
    >=20
    > I don't think you can compare CGN with NAT64.
    >=20
    > NAT64 is doing a much better and dynamic (on demand) usage of the por=
t of the IPv4 address pool. So, it scales much more than CGN. As a conseque=
nce, an ISP need much less IPv4 addresses for the same number of customers =
with NAT64 than CGN, and you don't have many of the problems that CGN poses=
 because the restrictions in the number of ports.
    >=20
    > Regards,
    > Jordi
   =20
    There is nothing architecturally different between CGN and NAT64 w.r.t.=
 IPv4 port allocation.  NAT64 may have less traffic going though it as we k=
now there is a IPv6 service.  For CGN we don=E2=80=99t know if there is a I=
Pv6 service to offload traffic or not.
   =20
    		IPv6 + NAT64 vs IPv6 + CGN vs CGN
   =20
    Both destination address selection rules and DNS64 (if in use) push tra=
ffic towards IPv6
    if there is a choice in transports.  Even if you don=E2=80=99t have nat=
ive IPv6 you can still move traffic off the CGN using 6rd where the BR is s=
tateless.
   =20
    	    IPv6 + NAT64 vs IPv6 + CGN vs CGN vs CGN + 6rd
   =20
    Mark
    --=20
    Mark Andrews, ISC
    1 Seymour St., Dundas Valley, NSW 2117, Australia
    PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
   =20
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Fri Sep 14 16:21:43 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2863130EDF; Fri, 14 Sep 2018 16:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=unavailable 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 oh6lARNiOSOz; Fri, 14 Sep 2018 16:21:21 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 42E80130E97; Fri, 14 Sep 2018 16:21:21 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 270C13AB001; Fri, 14 Sep 2018 23:21:21 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D305616005C; Fri, 14 Sep 2018 23:21:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id C0675160066; Fri, 14 Sep 2018 23:21:19 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id MQkMdTvqeqSS; Fri, 14 Sep 2018 23:21:19 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id BE20E16005C; Fri, 14 Sep 2018 23:21:18 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <86710663-6F7A-4A6E-8F46-C62D46DD0DDB@consulintel.es>
Date: Sat, 15 Sep 2018 09:21:16 +1000
Cc: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, 6man WG <ipv6@ietf.org>, V6 Ops List <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4F32082-3437-401A-B848-3392B261C42C@isc.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es> <69A473AC-E52E-48E3-B31C-15C7E17C607F@isc.org> <86710663-6F7A-4A6E-8F46-C62D46DD0DDB@consulintel.es>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lWUJpVgjU6PR0RapqzbNEltcgSE>
Subject: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2018 23:21:36 -0000

> On 15 Sep 2018, at 8:13 am, JORDI PALET MARTINEZ =
<jordi.palet@consulintel.es> wrote:
>=20
> Hi Mark,
>=20
> It may depend on the specific CGN implementation protocol, but in CGN =
you pre-allocate a given number of ports per user.

It=E2=80=99s definitely implementation specific.  You can do the same =
thing with a NAT64 box (IPv6 prefix to IPv4 <address,port-range>).  =
It=E2=80=99s all about logging trade offs.  There is nothing in the two =
technologies requiring it or prohibiting it.  In many cases those =
logging trade offs are driven by legislative requirements to be able to =
trace back to specific customers for traffic that is years old.

> Is not relevant if that user actually uses all those ports or needs =
more. They aren't available for other users and each user has a specific =
limit on the number of ports.
>=20
> In NAT64, the ports get allocated on the fly as needed for each user. =
So I think it is clear that it is much more efficient.
>=20
> Regars,
> Jordi
--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Fri Sep 14 22:19:45 2018
Return-Path: <rajiva@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE0D4130E09 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 22:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 4j8VWbQ3yH3R for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 22:19:40 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A422D130DF5 for <v6ops@ietf.org>; Fri, 14 Sep 2018 22:19:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12723; q=dns/txt; s=iport; t=1536988780; x=1538198380; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5ex2bnrFHbqrSqYpcAvfJ4NeXlCp0ZBf6xo5zTTjal4=; b=gkM2iyf+YqBQka3gcjH0Q6oKbN75Yw3YvdP/9/jvs8KMGJTJZKOBsc/h k3sQjntcHYFn1ldrwEkFymqpkfkeVLoynA/v0B02klwXm5r71VF1fufD1 rErGdWuXoyvVH5UBBSv99FgCQS8V9qMlFzeb6E4EAEyjPhEZv8ztg2ZyL c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A2AAAQlpxb/5pdJa1bGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYFQgghlfyiDcogVjCqTGYU4gXoLGAEKhEkCF4NHITQYAQM?= =?us-ascii?q?BAQIBAQJtHAyFOQIBAwEBIUQHCxACAQg1CgMCAgIlCxQRAgQOBYMhAYEdZA+?= =?us-ascii?q?oNoEuhCwDRIUVBYpoF4FBP4ESJx+CTIMbAQGBeIJqMYImAo1LjnMJApASF48?= =?us-ascii?q?IlCACERSBJR04gVVwFTsqAYJBixWFPm+OXgEB?=
X-IronPort-AV: E=Sophos;i="5.53,375,1531785600";  d="scan'208,217";a="452526246"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Sep 2018 05:19:36 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id w8F5JasT001722 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 15 Sep 2018 05:19:36 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 15 Sep 2018 00:19:35 -0500
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1395.000; Sat, 15 Sep 2018 00:19:35 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Lee Howard <lee@asgard.org>
CC: Ole Troan <otroan@employees.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] NAT64 prefix configuration
Thread-Index: AQHUTEuEJ70zS6cuBkaJQYTzSqlLNKTwXmaAgAASv4CAAF2meQ==
Date: Sat, 15 Sep 2018 05:19:35 +0000
Message-ID: <344AB825-D166-4EB6-933E-503C4C5D45C6@cisco.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org>, <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org>
In-Reply-To: <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_344AB825D1664EB6933E503C4C5D45C6ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/03NMVQ_pV-EsQDgD7-4-2bvtJQc>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 15 Sep 2018 05:19:44 -0000

--_000_344AB825D1664EB6933E503C4C5D45C6ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCiJuYXRpdmUuIiAgSW4gdGhlIG9yaWdpbmFsIGNvbnRleHQsIEkgYWdyZWUgdGhhdCBhIGRl
dmljZSBvZmZlcmluZyBDTEFULCBzdWNoIGFzIGEgaG9tZSBnYXRld2F5IG9yIG1vYmlsZSBob3Rz
cG90IG9mZmVyaW5nIENMQVQsIHNob3VsZCBub3QgdXNlIHRoZSBpcHY2b25seS1mbGFnLg0KDQpJ
IGFncmVlLiBJdCB3b3VsZCBiZSB2ZXJ5IGNvbmZ1c2luZyB0byB1c2Ugc3VjaCBhIGZsYWcuDQoN
ClhMQVQsIE1BUCBldGMuIGFsbG93IGZvciBib3RoIHY2IGFuZCB2NCB0byB0aGUgZW5kIGhvc3Rz
IChvbiBMQU4pIG9yIGVuZCBhcHBsaWNhdGlvbnMgKG9uIHRoZSBidW1wL2Zha2UgTEFOICkNCg0K
QW5kIGEgZGV2aWNlIGltcGxlbWVudGluZyBYTEFULCBNQVAgZXRjLiBtdXN0IHN1cHBvcnQgYm90
aCB2NiBhbmQgdjQgYWthIGR1YWwtc3RhY2ssIGV2ZW4gaWYgcmVzdHJpY3RlZCB0byBhIHN1YnNl
dCBvZiBpbnRlcmZhY2VzLg0KDQpNYXliZSB3ZSBuZWVkIGFuICJpcHY0LXNvcnRhIiBmbGFnPw0K
DQpJTUhPLCB3ZSBkb27igJl0LiA6LSkNCg0KQSBtb2JpbGUgaGFuZHNldCB3aXRoIENMQVQgYnVp
bHQgaW4gaXMgYSBob3N0IHRoYXQgb25seSBoYXMgbmF0aXZlIElQdjYsIGFuZCBpcyBkb2luZyBJ
UHY0IGluIHRyYW5zbGF0aW9uIG9ubHksIHJpZ2h0PyBUaGF0IGhvc3QgY291bGRuJ3QgYmUgY29u
c2lkZXJlZCAibmF0aXZlIGR1YWwtc3RhY2ssIiBjb3VsZCBpdD8NCg0KTGV04oCZcyBwdXQgaXQg
dGhlIG90aGVyIHdheSAtIFRoZSBob3N0cyBjb3VsZCBOT1QgYmUgY29uc2lkZXJlZCBJUHY2LW9u
bHkgZm9yIHN1cmUsIElmIHRoZXkgd2VyZSBvZmZlcmVkIHY0IGFuZCB2NiBwcmVmaXhlcy4NCg0K
DQpDaGVlcnMsDQpSYWppdg0KDQoNCk9uIFNlcCAxNSwgMjAxOCwgYXQgMTI6MTUgQU0sIExlZSBI
b3dhcmQgPGxlZUBhc2dhcmQub3JnPG1haWx0bzpsZWVAYXNnYXJkLm9yZz4+IHdyb3RlOg0KDQoN
Cg0KT24gMDkvMTQvMjAxOCAwMTozNyBQTSwgT2xlIFRyb2FuIHdyb3RlOg0KDQpPbiAxNCBTZXAg
MjAxOCwgYXQgMTg6NTIsIExlZSBIb3dhcmQgPGxlZUBhc2dhcmQub3JnPG1haWx0bzpsZWVAYXNn
YXJkLm9yZz4+IHdyb3RlOg0KDQpJZiB5b3UgbWVudGlvbmVkIHRoZSBpcHY2b25seS1mbGFnIGRy
YWZ0IGluIHRoZSBjb250ZXh0IDQ2NFhMQVQuIDQ2NFhMQVQgb2ZmZXJzIGEgbmF0aXZlIGR1YWwt
c3RhY2sgc2VydmljZSwgYW5kIHRoYXTigJlzIG5vdCB3aGF0IHRoZSBpcHY2b25seS1mbGFnIGRy
YWZ0IGlzIGFib3V0Lg0KVGhhdOKAmXMgYWJvdXQgdHJ1ZSBJUHY2IG9ubHkgbGlua3MsIHdoZXJl
IHRoZXJlIGlzIG5vIElQdjQgcGFja2V0cyBvbiB0aGUgbGluay4NClRoZSBzdGF0ZW1lbnQgIjQ2
NFhMQVQgb2ZmZXJzIGEgbmF0aXZlIGR1YWwtc3RhY2sgc2VydmljZSIgaXMgdGhlIGNvbXBsZXRl
IG9wcG9zaXRlIHRvIG15IHVuZGVyc3RhbmRpbmcgb2YgIm5hdGl2ZS4iIFdoYXQgZG8geW91IG1l
YW4/DQpZb3UgYXJlIG5vdCB0cm9sbGluZyBtZT8NCkFsbCB0aGUgSVB2NGFhUyBtZWNoYW5pc21z
IGhhdmUgYXMgdGhlaXIgcHVycG9zZSB0byBvZmZlciBJUHY0IHNlcnZpY2UgdG8gaG9zdHMuIElu
IDQ2NHhsYXQsIGFzIHRoZSBvdGhlcnMgdGhleSBob3N0cyBvbiBsaW5rcyBiZWhpbmQgb25lIG9m
IHRoZXNlIGRldmljZXMgZ2V0IG5hdGl2ZSBJUHY0LiBJUHY0IEV0aGVybmV0IDB4ODAwLiBJbiB0
aGUgdHlwaWNhbCA0NjR4bGF0IGNhc2UsIHRyaXBsZSBOQVR0ZWQsIGJ1dCBpbmRpc3Rpbmd1aXNo
YWJsZSBmcm9tIGFueSBvdGhlciBJUHY0IHNlcnZpY2UuIElmIHRoYXQgd2FzIGNhcnJpZWQgb3Zl
ciBNUExTLCBFdGhlcm5ldCBvciBQUFAgdXBzdHJlYW0uDQoNCklmIEknbSB0cm9sbGluZywgSSBz
d2VhciBpdCdzIHVuaW50ZW50aW9uYWwuDQpBIG1vYmlsZSBoYW5kc2V0IHdpdGggQ0xBVCBidWls
dCBpbiBpcyBhIGhvc3QgdGhhdCBvbmx5IGhhcyBuYXRpdmUgSVB2NiwgYW5kIGlzIGRvaW5nIElQ
djQgaW4gdHJhbnNsYXRpb24gb25seSwgcmlnaHQ/IFRoYXQgaG9zdCBjb3VsZG4ndCBiZSBjb25z
aWRlcmVkICJuYXRpdmUgZHVhbC1zdGFjaywiIGNvdWxkIGl0PyBFdmVuIHRoZSBidW1wIHRoYXQg
cHJvdmlkZXMgSVB2NCB0byB0aGUgYXBwbGljYXRpb24gaXMgZmFraW5nIGl0OiBpdCdzIG5vdCBw
cm92aWRpbmcgbmF0aXZlIElQdjQsIGl0J3MgcHJvdmlkaW5nIHRyYW5zbGF0ZWQgSVB2NC4NCg0K
VGhlbiB0aGVyZSdzIHRoZSBtdWNoIHJhcmVyIGNhc2Ugb2YgQ0xBVCBpbiBhIGhvbWUgZ2F0ZXdh
eSAoSSdkIGxvdmUgdG8gZmluZCBvbmUgdGhhdCB3b3JrIHdlbGwhKS4gIE1heWJlIHlvdSBjb3Vs
ZCBzYXkgdGhleSBoYXZlIG5hdGl2ZSBJUHY0IGFjY2VzcyB0byBob3N0cyBvbiB0aGUgTEFOLCBt
YXliZSBldmVuIHRocm91Z2hvdXQgdGhlIGhvdXNlLCBidXQgdGhleSBkb24ndCBoYXZlIG5hdGl2
ZSBJUHY0IEludGVybmV0IGFjY2VzcywgZG8gdGhleT8NCg0KSWYgeW91ciBJU1AgcHJvdmlzaW9u
ZWQgeW91ciBob21lIHdpdGggSVB2Nis0NjR4bGF0IGFuZCBjYWxsZWQgaXQgIm5hdGl2ZSBkdWFs
LXN0YWNrLCIgd291bGQgeW91IGJlIHNhdGlzZmllZCB3aXRoIHRoZWlyIHJlcHJlc2VudGF0aW9u
IG9mIHRoZWlyIHNlcnZpY2U/DQoNCkFsbCBvZiB0aGF0IHdhcyBhYm91dCB0aGUgZGVmaW5pdGlv
biBvZiAibmF0aXZlLiIgIEluIHRoZSBvcmlnaW5hbCBjb250ZXh0LCBJIGFncmVlIHRoYXQgYSBk
ZXZpY2Ugb2ZmZXJpbmcgQ0xBVCwgc3VjaCBhcyBhIGhvbWUgZ2F0ZXdheSBvciBtb2JpbGUgaG90
c3BvdCBvZmZlcmluZyBDTEFULCBzaG91bGQgbm90IHVzZSB0aGUgaXB2Nm9ubHktZmxhZy4gTWF5
YmUgd2UgbmVlZCBhbiAiaXB2NC1zb3J0YSIgZmxhZz8gKG9rYXksIG5vdyBJJ20gdHJvbGxpbmcp
DQoNCkxlZQ0KDQoNCk9sZQ0KDQoNCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQp2Nm9wcyBtYWlsaW5nIGxpc3QNCnY2b3BzQGlldGYub3JnPG1h
aWx0bzp2Nm9wc0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vdjZvcHMNCg==

--_000_344AB825D1664EB6933E503C4C5D45C6ciscocom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGRpcj0iYXV0byI+DQo8
ZGl2PjxzcGFuPjwvc3Bhbj48L2Rpdj4NCjxkaXY+DQo8ZGl2PjxzcGFuPjwvc3Bhbj48L2Rpdj4N
CjxkaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1j
b2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxicj4NCjwvc3Bhbj48L2Rpdj4NCjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiPjxmb250IGNvbG9yPSIjMDAwMDAwIj48c3BhbiBzdHlsZT0iY2Fy
ZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwg
MjU1LCAwKTsiPiZxdW90O25hdGl2ZS4mcXVvdDsmbmJzcDsgSW4gdGhlIG9yaWdpbmFsIGNvbnRl
eHQsIEkgYWdyZWUgdGhhdCBhIGRldmljZSBvZmZlcmluZyBDTEFULCBzdWNoIGFzIGEgaG9tZSBn
YXRld2F5IG9yIG1vYmlsZSBob3RzcG90IG9mZmVyaW5nIENMQVQsDQogc2hvdWxkIG5vdCB1c2Ug
dGhlIGlwdjZvbmx5LWZsYWcuIDwvc3Bhbj48L2ZvbnQ+PC9ibG9ja3F1b3RlPg0KPGRpdj48YnI+
DQo8L2Rpdj4NCkkgYWdyZWUuIEl0IHdvdWxkIGJlIHZlcnkgY29uZnVzaW5nIHRvIHVzZSBzdWNo
IGEgZmxhZy4mbmJzcDsNCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj48c3BhbiBzdHls
ZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPlhMQVQsIE1BUCBl
dGMuIGFsbG93IGZvciBib3RoIHY2IGFuZCB2NCB0byB0aGUgZW5kIGhvc3RzIChvbiBMQU4pIG9y
IGVuZCBhcHBsaWNhdGlvbnMgKG9uIHRoZSBidW1wL2Zha2UgTEFOICk8L3NwYW4+PC9kaXY+DQo8
ZGl2PjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDAp
OyI+PGJyPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xv
cjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPkFuZCBhIGRldmljZSBpbXBsZW1lbnRpbmcgWExB
VCwgTUFQIGV0Yy4gbXVzdCBzdXBwb3J0IGJvdGggdjYgYW5kIHY0IGFrYSBkdWFsLXN0YWNrLCBl
dmVuIGlmIHJlc3RyaWN0ZWQgdG8gYSBzdWJzZXQgb2YgaW50ZXJmYWNlcy4mbmJzcDs8L3NwYW4+
PC9kaXY+DQo8ZGl2Pjxicj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxmb250IGNvbG9yPSIj
MDAwMDAwIj48c3BhbiBzdHlsZT0iY2FyZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgYmFja2dyb3Vu
ZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPk1heWJlIHdlIG5lZWQgYW4gJnF1b3Q7
aXB2NC1zb3J0YSZxdW90OyBmbGFnPzwvc3Bhbj48L2ZvbnQ+PC9ibG9ja3F1b3RlPg0KPGRpdj48
YnI+DQo8L2Rpdj4NCklNSE8sIHdlIGRvbuKAmXQuIDotKTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48Zm9udCBjb2xvcj0iIzAwMDAwMCI+
PHNwYW4gc3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7IGJhY2tncm91bmQtY29sb3I6
IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij5BIG1vYmlsZSBoYW5kc2V0IHdpdGggQ0xBVCBidWls
dCBpbiBpcyBhIGhvc3QgdGhhdCBvbmx5IGhhcyBuYXRpdmUgSVB2NiwgYW5kIGlzIGRvaW5nIElQ
djQgaW4gdHJhbnNsYXRpb24gb25seSwgcmlnaHQ/IFRoYXQgaG9zdA0KIGNvdWxkbid0IGJlIGNv
bnNpZGVyZWQgJnF1b3Q7bmF0aXZlIGR1YWwtc3RhY2ssJnF1b3Q7IGNvdWxkIGl0Pzwvc3Bhbj48
L2ZvbnQ+PC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5MZXTi
gJlzIHB1dCBpdCB0aGUgb3RoZXIgd2F5IC0gVGhlIGhvc3RzIGNvdWxkIE5PVCBiZSBjb25zaWRl
cmVkIElQdjYtb25seSBmb3Igc3VyZSwgSWYgdGhleSB3ZXJlIG9mZmVyZWQgdjQgYW5kIHY2IHBy
ZWZpeGVzLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPGRpdj5D
aGVlcnMsDQo8ZGl2PlJhaml2ICZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjwvZGl2
Pg0KPGRpdj48YnI+DQpPbiBTZXAgMTUsIDIwMTgsIGF0IDEyOjE1IEFNLCBMZWUgSG93YXJkICZs
dDs8YSBocmVmPSJtYWlsdG86bGVlQGFzZ2FyZC5vcmciPmxlZUBhc2dhcmQub3JnPC9hPiZndDsg
d3JvdGU6PGJyPg0KPGJyPg0KPC9kaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj4NCjxkaXY+
PHNwYW4+PC9zcGFuPjxicj4NCjxzcGFuPjwvc3Bhbj48YnI+DQo8c3Bhbj5PbiAwOS8xNC8yMDE4
IDAxOjM3IFBNLCBPbGUgVHJvYW4gd3JvdGU6PC9zcGFuPjxicj4NCjxibG9ja3F1b3RlIHR5cGU9
ImNpdGUiPjxzcGFuPjwvc3Bhbj48YnI+DQo8L2Jsb2NrcXVvdGU+DQo8YmxvY2txdW90ZSB0eXBl
PSJjaXRlIj48c3Bhbj5PbiAxNCBTZXAgMjAxOCwgYXQgMTg6NTIsIExlZSBIb3dhcmQgJmx0Ozxh
IGhyZWY9Im1haWx0bzpsZWVAYXNnYXJkLm9yZyI+bGVlQGFzZ2FyZC5vcmc8L2E+Jmd0OyB3cm90
ZTo8L3NwYW4+PGJyPg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNw
YW4+PC9zcGFuPjxicj4NCjwvYmxvY2txdW90ZT4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPg0K
PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5J
ZiB5b3UgbWVudGlvbmVkIHRoZSBpcHY2b25seS1mbGFnIGRyYWZ0IGluIHRoZSBjb250ZXh0IDQ2
NFhMQVQuIDQ2NFhMQVQgb2ZmZXJzIGEgbmF0aXZlIGR1YWwtc3RhY2sgc2VydmljZSwgYW5kIHRo
YXTigJlzIG5vdCB3aGF0IHRoZSBpcHY2b25seS1mbGFnIGRyYWZ0IGlzIGFib3V0Ljwvc3Bhbj48
YnI+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8YmxvY2tx
dW90ZSB0eXBlPSJjaXRlIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPg0KPGJsb2NrcXVvdGUg
dHlwZT0iY2l0ZSI+PHNwYW4+VGhhdOKAmXMgYWJvdXQgdHJ1ZSBJUHY2IG9ubHkgbGlua3MsIHdo
ZXJlIHRoZXJlIGlzIG5vIElQdjQgcGFja2V0cyBvbiB0aGUgbGluay48L3NwYW4+PGJyPg0KPC9i
bG9ja3F1b3RlPg0KPC9ibG9ja3F1b3RlPg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgdHlw
ZT0iY2l0ZSI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5UaGUgc3RhdGVtZW50ICZx
dW90OzQ2NFhMQVQgb2ZmZXJzIGEgbmF0aXZlIGR1YWwtc3RhY2sgc2VydmljZSZxdW90OyBpcyB0
aGUgY29tcGxldGUgb3Bwb3NpdGUgdG8gbXkgdW5kZXJzdGFuZGluZyBvZiAmcXVvdDtuYXRpdmUu
JnF1b3Q7IFdoYXQgZG8geW91IG1lYW4/PC9zcGFuPjxicj4NCjwvYmxvY2txdW90ZT4NCjwvYmxv
Y2txdW90ZT4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPllvdSBhcmUgbm90IHRyb2xs
aW5nIG1lPzwvc3Bhbj48YnI+DQo8L2Jsb2NrcXVvdGU+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRl
Ij48c3Bhbj5BbGwgdGhlIElQdjRhYVMgbWVjaGFuaXNtcyBoYXZlIGFzIHRoZWlyIHB1cnBvc2Ug
dG8gb2ZmZXIgSVB2NCBzZXJ2aWNlIHRvIGhvc3RzLiBJbiA0NjR4bGF0LCBhcyB0aGUgb3RoZXJz
IHRoZXkgaG9zdHMgb24gbGlua3MgYmVoaW5kIG9uZSBvZiB0aGVzZSBkZXZpY2VzIGdldCBuYXRp
dmUgSVB2NC4gSVB2NCBFdGhlcm5ldCAweDgwMC4gSW4gdGhlIHR5cGljYWwgNDY0eGxhdCBjYXNl
LCB0cmlwbGUNCiBOQVR0ZWQsIGJ1dCBpbmRpc3Rpbmd1aXNoYWJsZSBmcm9tIGFueSBvdGhlciBJ
UHY0IHNlcnZpY2UuIElmIHRoYXQgd2FzIGNhcnJpZWQgb3ZlciBNUExTLCBFdGhlcm5ldCBvciBQ
UFAgdXBzdHJlYW0uPC9zcGFuPjxicj4NCjwvYmxvY2txdW90ZT4NCjxzcGFuPjwvc3Bhbj48YnI+
DQo8c3Bhbj5JZiBJJ20gdHJvbGxpbmcsIEkgc3dlYXIgaXQncyB1bmludGVudGlvbmFsLjwvc3Bh
bj48YnI+DQo8c3Bhbj5BIG1vYmlsZSBoYW5kc2V0IHdpdGggQ0xBVCBidWlsdCBpbiBpcyBhIGhv
c3QgdGhhdCBvbmx5IGhhcyBuYXRpdmUgSVB2NiwgYW5kIGlzIGRvaW5nIElQdjQgaW4gdHJhbnNs
YXRpb24gb25seSwgcmlnaHQ/IFRoYXQgaG9zdCBjb3VsZG4ndCBiZSBjb25zaWRlcmVkICZxdW90
O25hdGl2ZSBkdWFsLXN0YWNrLCZxdW90OyBjb3VsZCBpdD8gRXZlbiB0aGUgYnVtcCB0aGF0IHBy
b3ZpZGVzIElQdjQgdG8gdGhlIGFwcGxpY2F0aW9uIGlzIGZha2luZyBpdDogaXQncw0KIG5vdCBw
cm92aWRpbmcgbmF0aXZlIElQdjQsIGl0J3MgcHJvdmlkaW5nIHRyYW5zbGF0ZWQgSVB2NC48L3Nw
YW4+PGJyPg0KPHNwYW4+PC9zcGFuPjxicj4NCjxzcGFuPlRoZW4gdGhlcmUncyB0aGUgbXVjaCBy
YXJlciBjYXNlIG9mIENMQVQgaW4gYSBob21lIGdhdGV3YXkgKEknZCBsb3ZlIHRvIGZpbmQgb25l
IHRoYXQgd29yayB3ZWxsISkuJm5ic3A7IE1heWJlIHlvdSBjb3VsZCBzYXkgdGhleSBoYXZlIG5h
dGl2ZSBJUHY0IGFjY2VzcyB0byBob3N0cyBvbiB0aGUgTEFOLCBtYXliZSBldmVuIHRocm91Z2hv
dXQgdGhlIGhvdXNlLCBidXQgdGhleSBkb24ndCBoYXZlIG5hdGl2ZSBJUHY0IEludGVybmV0IGFj
Y2VzcywNCiBkbyB0aGV5Pzwvc3Bhbj48YnI+DQo8c3Bhbj48L3NwYW4+PGJyPg0KPHNwYW4+SWYg
eW91ciBJU1AgcHJvdmlzaW9uZWQgeW91ciBob21lIHdpdGggSVB2NiYjNDM7NDY0eGxhdCBhbmQg
Y2FsbGVkIGl0ICZxdW90O25hdGl2ZSBkdWFsLXN0YWNrLCZxdW90OyB3b3VsZCB5b3UgYmUgc2F0
aXNmaWVkIHdpdGggdGhlaXIgcmVwcmVzZW50YXRpb24gb2YgdGhlaXIgc2VydmljZT88L3NwYW4+
PGJyPg0KPHNwYW4+PC9zcGFuPjxicj4NCjxzcGFuPkFsbCBvZiB0aGF0IHdhcyBhYm91dCB0aGUg
ZGVmaW5pdGlvbiBvZiAmcXVvdDtuYXRpdmUuJnF1b3Q7Jm5ic3A7IEluIHRoZSBvcmlnaW5hbCBj
b250ZXh0LCBJIGFncmVlIHRoYXQgYSBkZXZpY2Ugb2ZmZXJpbmcgQ0xBVCwgc3VjaCBhcyBhIGhv
bWUgZ2F0ZXdheSBvciBtb2JpbGUgaG90c3BvdCBvZmZlcmluZyBDTEFULCBzaG91bGQgbm90IHVz
ZSB0aGUgaXB2Nm9ubHktZmxhZy4gTWF5YmUgd2UgbmVlZCBhbiAmcXVvdDtpcHY0LXNvcnRhJnF1
b3Q7IGZsYWc/IChva2F5LCBub3cgSSdtDQogdHJvbGxpbmcpPC9zcGFuPjxicj4NCjxzcGFuPjwv
c3Bhbj48YnI+DQo8c3Bhbj5MZWU8L3NwYW4+PGJyPg0KPHNwYW4+PC9zcGFuPjxicj4NCjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPjwvc3Bhbj48YnI+DQo8L2Jsb2NrcXVvdGU+DQo8Ymxv
Y2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj5PbGU8L3NwYW4+PGJyPg0KPC9ibG9ja3F1b3RlPg0K
PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxicj4NCjwvYmxvY2txdW90ZT4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPjwvc3Bhbj48YnI+DQo8L2Jsb2NrcXVvdGU+
DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj48L3NwYW4+PGJyPg0KPC9ibG9ja3F1b3Rl
Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxicj4NCjwvYmxvY2txdW90
ZT4NCjxzcGFuPjwvc3Bhbj48YnI+DQo8c3Bhbj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzwvc3Bhbj48YnI+DQo8c3Bhbj52Nm9wcyBtYWlsaW5nIGxpc3Q8
L3NwYW4+PGJyPg0KPHNwYW4+PGEgaHJlZj0ibWFpbHRvOnY2b3BzQGlldGYub3JnIj52Nm9wc0Bp
ZXRmLm9yZzwvYT48L3NwYW4+PGJyPg0KPHNwYW4+PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcyI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby92Nm9wczwvYT48L3NwYW4+PGJyPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_344AB825D1664EB6933E503C4C5D45C6ciscocom_--


From nobody Fri Sep 14 22:36:23 2018
Return-Path: <rajiva@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66806130DF7; Fri, 14 Sep 2018 22:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 HNuwClnY0YXO; Fri, 14 Sep 2018 22:36:13 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D884129C6B; Fri, 14 Sep 2018 22:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8071; q=dns/txt; s=iport; t=1536989773; x=1538199373; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Z4CRhhVGUsl/jNbWw+oyvpmxfviXyI/sPpxR+VJ8YcY=; b=kj46UE20VF+mF0qXLvO8ItjTCAUHBfULZW59LPxSBZiqWRPVgWs0Y9Nx jxIphbeWWAgL6bLeGOdlUb6yXIsW2Xtig/HeXqTI1FTuE6mueutSYiT8a 0tMhbHWl8VGTXGf9MXznilDrsJbffpuUlB9wkuL/1vg+qzJrlQGa4cgKe E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A2AACqmZxb/5JdJa1aGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYFQgghlfyiDcogVjCqBaIEdkBSFOIF6CxgBCoRJAheDRyE?= =?us-ascii?q?0GAEDAQECAQECbRwMhTkCAQMBASFEBwsOAgIBCDUKAwICAhkMCxQRAgQOBYM?= =?us-ascii?q?hAYEdZA+oPIEuiggFBYpjF4FBP4ERKAwTghc1gxsBAQOBOD2CajGCJgKINoU?= =?us-ascii?q?VhWeJDAkChjqJWBePCItXiEkCERSBJR04gVVwFTsqAYJBixWFPm+ME4JLAQE?=
X-IronPort-AV: E=Sophos;i="5.53,375,1531785600";  d="scan'208,217";a="449405305"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Sep 2018 05:36:08 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id w8F5a84X002398 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 15 Sep 2018 05:36:08 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 15 Sep 2018 00:36:07 -0500
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1395.000; Sat, 15 Sep 2018 00:36:07 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: V6 Ops List <v6ops@ietf.org>, Mark Andrews <marka@isc.org>, 6man WG <ipv6@ietf.org>, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
Thread-Topic: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
Thread-Index: AQHUTBuxz+fz5iZxTkOc02qXaho5V6TwnE0AgAAN+ACAAAGugIAAEuwAgAAU6n8=
Date: Sat, 15 Sep 2018 05:36:07 +0000
Message-ID: <946E75AE-DD4A-4421-858E-38946F3AA17A@cisco.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es> <69A473AC-E52E-48E3-B31C-15C7E17C607F@isc.org> <86710663-6F7A-4A6E-8F46-C62D46DD0DDB@consulintel.es>, <F4F32082-3437-401A-B848-3392B261C42C@isc.org>
In-Reply-To: <F4F32082-3437-401A-B848-3392B261C42C@isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_946E75AEDD4A4421858E38946F3AA17Aciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uPS8j24bzKAsbApImdhfDDpc_5M>
Subject: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 15 Sep 2018 05:36:15 -0000

--_000_946E75AEDD4A4421858E38946F3AA17Aciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpCb3RoIE5BVDQ0IGFuZCBOQVQ2NCBhcmUgdHlwZXMgb2YgQ0dOLCBhcyBsb25nIGFzIHRoZXkg
c2F0aXNmeSB0aGUgcmVxdWlyZW1lbnRzIG91dGxpbmVkIGluIFJGQzY4ODguDQoNCi8vDQoNCkNh
cnJpZXItR3JhZGUgTkFUIChDR04pOiAgQSBOQVQtYmFzZWQgW1JGQzI2NjM8aHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL3JmYzI2NjM+XSBsb2dpY2FsIGZ1bmN0aW9uIHVzZWQNCiAgICAgIHRv
IHNoYXJlIHRoZSBzYW1lIElQdjQgYWRkcmVzcyBhbW9uZyBzZXZlcmFsIHN1YnNjcmliZXJzLiAg
QSBDR04NCiAgICAgIGlzIG5vdCBtYW5hZ2VkIGJ5IHRoZSBzdWJzY3JpYmVycy4NCg0KLy8NCg0K
SSBzb21ld2hhdCBhZ3JlZSB3aXRoIE1hcmsuDQoNCkNoZWVycywNClJhaml2DQoNCk9uIFNlcCAx
NSwgMjAxOCwgYXQgMToyMyBBTSwgTWFyayBBbmRyZXdzIDxtYXJrYUBpc2Mub3JnPG1haWx0bzpt
YXJrYUBpc2Mub3JnPj4gd3JvdGU6DQoNCg0KDQpPbiAxNSBTZXAgMjAxOCwgYXQgODoxMyBhbSwg
Sk9SREkgUEFMRVQgTUFSVElORVogPGpvcmRpLnBhbGV0QGNvbnN1bGludGVsLmVzPG1haWx0bzpq
b3JkaS5wYWxldEBjb25zdWxpbnRlbC5lcz4+IHdyb3RlOg0KDQpIaSBNYXJrLA0KDQpJdCBtYXkg
ZGVwZW5kIG9uIHRoZSBzcGVjaWZpYyBDR04gaW1wbGVtZW50YXRpb24gcHJvdG9jb2wsIGJ1dCBp
biBDR04geW91IHByZS1hbGxvY2F0ZSBhIGdpdmVuIG51bWJlciBvZiBwb3J0cyBwZXIgdXNlci4N
Cg0KSXTigJlzIGRlZmluaXRlbHkgaW1wbGVtZW50YXRpb24gc3BlY2lmaWMuICBZb3UgY2FuIGRv
IHRoZSBzYW1lIHRoaW5nIHdpdGggYSBOQVQ2NCBib3ggKElQdjYgcHJlZml4IHRvIElQdjQgPGFk
ZHJlc3MscG9ydC1yYW5nZT4pLiAgSXTigJlzIGFsbCBhYm91dCBsb2dnaW5nIHRyYWRlIG9mZnMu
ICBUaGVyZSBpcyBub3RoaW5nIGluIHRoZSB0d28gdGVjaG5vbG9naWVzIHJlcXVpcmluZyBpdCBv
ciBwcm9oaWJpdGluZyBpdC4gIEluIG1hbnkgY2FzZXMgdGhvc2UgbG9nZ2luZyB0cmFkZSBvZmZz
IGFyZSBkcml2ZW4gYnkgbGVnaXNsYXRpdmUgcmVxdWlyZW1lbnRzIHRvIGJlIGFibGUgdG8gdHJh
Y2UgYmFjayB0byBzcGVjaWZpYyBjdXN0b21lcnMgZm9yIHRyYWZmaWMgdGhhdCBpcyB5ZWFycyBv
bGQuDQoNCklzIG5vdCByZWxldmFudCBpZiB0aGF0IHVzZXIgYWN0dWFsbHkgdXNlcyBhbGwgdGhv
c2UgcG9ydHMgb3IgbmVlZHMgbW9yZS4gVGhleSBhcmVuJ3QgYXZhaWxhYmxlIGZvciBvdGhlciB1
c2VycyBhbmQgZWFjaCB1c2VyIGhhcyBhIHNwZWNpZmljIGxpbWl0IG9uIHRoZSBudW1iZXIgb2Yg
cG9ydHMuDQoNCkluIE5BVDY0LCB0aGUgcG9ydHMgZ2V0IGFsbG9jYXRlZCBvbiB0aGUgZmx5IGFz
IG5lZWRlZCBmb3IgZWFjaCB1c2VyLiBTbyBJIHRoaW5rIGl0IGlzIGNsZWFyIHRoYXQgaXQgaXMg
bXVjaCBtb3JlIGVmZmljaWVudC4NCg0KUmVnYXJzLA0KSm9yZGkNCi0tDQpNYXJrIEFuZHJld3Ms
IElTQw0KMSBTZXltb3VyIFN0LiwgRHVuZGFzIFZhbGxleSwgTlNXIDIxMTcsIEF1c3RyYWxpYQ0K
UEhPTkU6ICs2MSAyIDk4NzEgNDc0MiAgICAgICAgICAgICAgSU5URVJORVQ6IG1hcmthQGlzYy5v
cmc8bWFpbHRvOm1hcmthQGlzYy5vcmc+DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpJRVRGIElQdjYgd29ya2lu
ZyBncm91cCBtYWlsaW5nIGxpc3QNCmlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+
DQpBZG1pbmlzdHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9pcHY2DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K

--_000_946E75AEDD4A4421858E38946F3AA17Aciscocom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGRpcj0iYXV0byI+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdi
YSgyNTUsIDI1NSwgMjU1LCAwKTsiPkJvdGggTkFUNDQgYW5kIE5BVDY0IGFyZSB0eXBlcyBvZiBD
R04sIGFzIGxvbmcgYXMgdGhleSBzYXRpc2Z5IHRoZSByZXF1aXJlbWVudHMgb3V0bGluZWQgaW4g
UkZDNjg4OC4mbmJzcDs8L3NwYW4+PC9kaXY+DQo8ZGl2PjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+Ly88YnI+DQo8ZGl2Pg0KPHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9Im1hcmdp
bi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBicmVhay1iZWZvcmU6IHBhZ2U7Ij48Zm9u
dCBmYWNlPSJVSUNURm9udFRleHRTdHlsZUJvZHkiPjxzcGFuIHN0eWxlPSJ3aGl0ZS1zcGFjZTog
bm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyI+Q2Fycmll
ci1HcmFkZSBOQVQgKENHTik6ICBBIE5BVC1iYXNlZCBbPGEgaHJlZj0iaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL3JmYzI2NjMiIHRpdGxlPSImcXVvdDtJUCBOZXR3b3JrIEFkZHJlc3MgVHJh
bnNsYXRvciAoTkFUKSBUZXJtaW5vbG9neSBhbmQgQ29uc2lkZXJhdGlvbnMmcXVvdDsiPlJGQzI2
NjM8L2E+XSBsb2dpY2FsIGZ1bmN0aW9uIHVzZWQNCiAgICAgIHRvIHNoYXJlIHRoZSBzYW1lIElQ
djQgYWRkcmVzcyBhbW9uZyBzZXZlcmFsIHN1YnNjcmliZXJzLiAgQSBDR04NCiAgICAgIGlzIG5v
dCBtYW5hZ2VkIGJ5IHRoZSBzdWJzY3JpYmVycy48L3NwYW4+PC9mb250PjwvcHJlPg0KPC9kaXY+
DQo8ZGl2Pi8vPGJyPg0KPGJyPg0KSSBzb21ld2hhdCBhZ3JlZSB3aXRoIE1hcmsuJm5ic3A7PC9k
aXY+DQo8ZGl2Pjxicj4NCjxkaXY+Q2hlZXJzLA0KPGRpdj5SYWppdiAmbmJzcDs8L2Rpdj4NCjwv
ZGl2Pg0KPGRpdj48YnI+DQpPbiBTZXAgMTUsIDIwMTgsIGF0IDE6MjMgQU0sIE1hcmsgQW5kcmV3
cyAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1hcmthQGlzYy5vcmciPm1hcmthQGlzYy5vcmc8L2E+Jmd0
OyB3cm90ZTo8YnI+DQo8YnI+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPg0KPGRp
dj48c3Bhbj48L3NwYW4+PGJyPg0KPHNwYW4+PC9zcGFuPjxicj4NCjxibG9ja3F1b3RlIHR5cGU9
ImNpdGUiPjxzcGFuPk9uIDE1IFNlcCAyMDE4LCBhdCA4OjEzIGFtLCBKT1JESSBQQUxFVCBNQVJU
SU5FWiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvcmRpLnBhbGV0QGNvbnN1bGludGVsLmVzIj5qb3Jk
aS5wYWxldEBjb25zdWxpbnRlbC5lczwvYT4mZ3Q7IHdyb3RlOjwvc3Bhbj48YnI+DQo8L2Jsb2Nr
cXVvdGU+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3Bhbj48L3NwYW4+PGJyPg0KPC9ibG9j
a3F1b3RlPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+SGkgTWFyayw8L3NwYW4+PGJy
Pg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxi
cj4NCjwvYmxvY2txdW90ZT4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPkl0IG1heSBk
ZXBlbmQgb24gdGhlIHNwZWNpZmljIENHTiBpbXBsZW1lbnRhdGlvbiBwcm90b2NvbCwgYnV0IGlu
IENHTiB5b3UgcHJlLWFsbG9jYXRlIGEgZ2l2ZW4gbnVtYmVyIG9mIHBvcnRzIHBlciB1c2VyLjwv
c3Bhbj48YnI+DQo8L2Jsb2NrcXVvdGU+DQo8c3Bhbj48L3NwYW4+PGJyPg0KPHNwYW4+SXTigJlz
IGRlZmluaXRlbHkgaW1wbGVtZW50YXRpb24gc3BlY2lmaWMuICZuYnNwO1lvdSBjYW4gZG8gdGhl
IHNhbWUgdGhpbmcgd2l0aCBhIE5BVDY0IGJveCAoSVB2NiBwcmVmaXggdG8gSVB2NCAmbHQ7YWRk
cmVzcyxwb3J0LXJhbmdlJmd0OykuICZuYnNwO0l04oCZcyBhbGwgYWJvdXQgbG9nZ2luZyB0cmFk
ZSBvZmZzLiAmbmJzcDtUaGVyZSBpcyBub3RoaW5nIGluIHRoZSB0d28gdGVjaG5vbG9naWVzIHJl
cXVpcmluZyBpdCBvciBwcm9oaWJpdGluZyBpdC4gJm5ic3A7SW4gbWFueSBjYXNlcw0KIHRob3Nl
IGxvZ2dpbmcgdHJhZGUgb2ZmcyBhcmUgZHJpdmVuIGJ5IGxlZ2lzbGF0aXZlIHJlcXVpcmVtZW50
cyB0byBiZSBhYmxlIHRvIHRyYWNlIGJhY2sgdG8gc3BlY2lmaWMgY3VzdG9tZXJzIGZvciB0cmFm
ZmljIHRoYXQgaXMgeWVhcnMgb2xkLjwvc3Bhbj48YnI+DQo8c3Bhbj48L3NwYW4+PGJyPg0KPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+SXMgbm90IHJlbGV2YW50IGlmIHRoYXQgdXNlciBh
Y3R1YWxseSB1c2VzIGFsbCB0aG9zZSBwb3J0cyBvciBuZWVkcyBtb3JlLiBUaGV5IGFyZW4ndCBh
dmFpbGFibGUgZm9yIG90aGVyIHVzZXJzIGFuZCBlYWNoIHVzZXIgaGFzIGEgc3BlY2lmaWMgbGlt
aXQgb24gdGhlIG51bWJlciBvZiBwb3J0cy48L3NwYW4+PGJyPg0KPC9ibG9ja3F1b3RlPg0KPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxicj4NCjwvYmxvY2txdW90ZT4NCjxi
bG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPkluIE5BVDY0LCB0aGUgcG9ydHMgZ2V0IGFsbG9j
YXRlZCBvbiB0aGUgZmx5IGFzIG5lZWRlZCBmb3IgZWFjaCB1c2VyLiBTbyBJIHRoaW5rIGl0IGlz
IGNsZWFyIHRoYXQgaXQgaXMgbXVjaCBtb3JlIGVmZmljaWVudC48L3NwYW4+PGJyPg0KPC9ibG9j
a3F1b3RlPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+PC9zcGFuPjxicj4NCjwvYmxv
Y2txdW90ZT4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuPlJlZ2Fycyw8L3NwYW4+PGJy
Pg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4+Sm9yZGk8L3Nw
YW4+PGJyPg0KPC9ibG9ja3F1b3RlPg0KPHNwYW4+LS0gPC9zcGFuPjxicj4NCjxzcGFuPk1hcmsg
QW5kcmV3cywgSVNDPC9zcGFuPjxicj4NCjxzcGFuPjEgU2V5bW91ciBTdC4sIER1bmRhcyBWYWxs
ZXksIE5TVyAyMTE3LCBBdXN0cmFsaWE8L3NwYW4+PGJyPg0KPHNwYW4+UEhPTkU6ICYjNDM7NjEg
MiA5ODcxIDQ3NDIgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7SU5URVJORVQ6IDxhIGhyZWY9Im1haWx0
bzptYXJrYUBpc2Mub3JnIj4NCm1hcmthQGlzYy5vcmc8L2E+PC9zcGFuPjxicj4NCjxzcGFuPjwv
c3Bhbj48YnI+DQo8c3Bhbj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvc3Bhbj48YnI+DQo8c3Bhbj5JRVRGIElQdjYg
d29ya2luZyBncm91cCBtYWlsaW5nIGxpc3Q8L3NwYW4+PGJyPg0KPHNwYW4+PGEgaHJlZj0ibWFp
bHRvOmlwdjZAaWV0Zi5vcmciPmlwdjZAaWV0Zi5vcmc8L2E+PC9zcGFuPjxicj4NCjxzcGFuPkFk
bWluaXN0cmF0aXZlIFJlcXVlc3RzOiA8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2lwdjYiPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9pcHY2PC9hPjwvc3Bhbj48YnI+DQo8c3Bhbj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvc3Bhbj48YnI+DQo8L2Rp
dj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_946E75AEDD4A4421858E38946F3AA17Aciscocom_--


From nobody Fri Sep 14 22:47:53 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E83C4130DF5 for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 22:47:50 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 zzW0ewfbfXgr for <v6ops@ietfa.amsl.com>; Fri, 14 Sep 2018 22:47:48 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 44EA4129C6B for <v6ops@ietf.org>; Fri, 14 Sep 2018 22:47:48 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id s15-v6so5320111pgv.8 for <v6ops@ietf.org>; Fri, 14 Sep 2018 22:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=/7YXXIMqYFasUzzlqxGkcrG/EiTNvZ31wwDQzu8ybb4=; b=OClP6it/v1s30RSStUxYaSzaSM1JVMBrIUe/LCTVBH2mXZoXYOxmXqP1E9F1t2HC9D 1djwC8hpd5Guq329zUvghwnideqyaF3vKPmJY5cJ6d3tTOJB4YfGJ85XQbb7a09enZCR L81q2rQcZ9vhO4B5YSKzoO9D5XA3EjvMuaX5bA9MKlsw8WUkkh0PdoeGdwpqnPaKlUvD Co9puINz+aTPY9RF6GvoMmDtjFDNt9MeUM6nQzmKWLp20yyjuCTH/lPvmljxenZ/mHNs JUFcnBuL63Iv1Zr6UayWY0k1sCC5uJBnViIlxpY5B0kE/sLmsq1W5xd1S/JA8lu9GwZT FXBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/7YXXIMqYFasUzzlqxGkcrG/EiTNvZ31wwDQzu8ybb4=; b=eCUO0CILbVDjf0yW9lhmDHPEcg5u1dm7e2gJQUZg1Mbf4Li2dghHI4t3bFvLyHpyOC FjogKx6nDdyjAQQap2VlESOdiBbd9iUZPkpY8dcf/2JklPOPs5mtZ4Teqq5MLAfsFwDw v4pUB4Auv20Gt/8FMXSuZd2X33vNUq6gcyDHVVGH0yYzsr1ZpiAxqc/AlLNRhFvuZRU1 2LO2R1xCSBNxiRBiarzT1yCEq/+cG2gS5IwasgKRLwFpMtM5Ihi4aD83THsdV+Xu534u 7le0xlnfk9O5NCGGeyUSyko+VgzTu8famx2H4IAnWOvcolOX/43TM+mvdZcNCUgc4hpe +b+A==
X-Gm-Message-State: APzg51Cy/u8AcPuMyWC3MaSvH89Al/vbFJyc+E7sGgrlQlZFL0K8zncQ 2Np/cQ1dSTMs2/3GGVbnWF8/SXKm
X-Google-Smtp-Source: ANB0VdYd4ZzZGkD3Z5lTuEfg6iwK9DhWchzG5OBvAS5ECX33TKsYEIazpsgFlZ2lzUDj2R0wHqJ3mA==
X-Received: by 2002:a63:4909:: with SMTP id w9-v6mr14552068pga.123.1536990467337;  Fri, 14 Sep 2018 22:47:47 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id x4-v6sm10220828pfm.119.2018.09.14.22.47.45 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Sep 2018 22:47:46 -0700 (PDT)
To: v6ops@ietf.org
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <8e5ec521-3fba-9de0-34e3-2fd8123c6974@asgard.org> <E684A18F-8C8F-48D9-9DBC-3CDCD8A944F8@employees.org> <5db4bec8-4109-e5e2-025d-66fe705745b4@asgard.org> <344AB825-D166-4EB6-933E-503C4C5D45C6@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7126e9ee-2e82-ccd8-48c9-ab09fd2e8cb9@gmail.com>
Date: Sat, 15 Sep 2018 17:47:41 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <344AB825-D166-4EB6-933E-503C4C5D45C6@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/F2RBrglN7xAflUFQ1g0AKCkTu6w>
Subject: Re: [v6ops] NAT64 prefix configuration
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 15 Sep 2018 05:47:51 -0000

On 2018-09-15 17:19, Rajiv Asati (rajiva) wrote:
>=20
>=20
>> "native."=C2=A0 In the original context, I agree that a device offerin=
g CLAT, such as a home gateway or mobile hotspot offering CLAT, should no=
t use the ipv6only-flag.=20
>=20
> I agree. It would be very confusing to use such a flag.

It would be plain wrong. The flag (if the IETF chooses to standardise it)=

would apply strictly to the link on which the RA arrives, and in this
case the link would provide IPv4 service, so the flag would be zero.
It's completely irrelevant how the IPv4 service is carried on the uplink.=


> XLAT, MAP etc. allow for both v6 and v4 to the end hosts (on LAN) or en=
d applications (on the bump/fake LAN )
>=20
> And a device implementing XLAT, MAP etc. must support both v6 and v4 ak=
a dual-stack, even if restricted to a subset of interfaces.=C2=A0
>=20
>> Maybe we need an "ipv4-sorta" flag?
>=20
> IMHO, we don=E2=80=99t. :-)

Definitely not.

   Brian

>=20
>> A mobile handset with CLAT built in is a host that only has native IPv=
6, and is doing IPv4 in translation only, right? That host couldn't be co=
nsidered "native dual-stack," could it?
>=20
> Let=E2=80=99s put it the other way - The hosts could NOT be considered =
IPv6-only for sure, If they were offered v4 and v6 prefixes.=C2=A0
>=20
>=20
> Cheers,
> Rajiv =C2=A0
>=20
>=20
> On Sep 15, 2018, at 12:15 AM, Lee Howard <lee@asgard.org <mailto:lee@as=
gard.org>> wrote:
>=20
>>
>>
>> On 09/14/2018 01:37 PM, Ole Troan wrote:
>>>
>>> On 14 Sep 2018, at 18:52, Lee Howard <lee@asgard.org <mailto:lee@asga=
rd.org>> wrote:
>>>
>>>>> If you mentioned the ipv6only-flag draft in the context 464XLAT. 46=
4XLAT offers a native dual-stack service, and that=E2=80=99s not what the=
 ipv6only-flag draft is about.
>>>>> That=E2=80=99s about true IPv6 only links, where there is no IPv4 p=
ackets on the link.
>>>> The statement "464XLAT offers a native dual-stack service" is the co=
mplete opposite to my understanding of "native." What do you mean?
>>> You are not trolling me?
>>> All the IPv4aaS mechanisms have as their purpose to offer IPv4 servic=
e to hosts. In 464xlat, as the others they hosts on links behind one of t=
hese devices get native IPv4. IPv4 Ethernet 0x800. In the typical 464xlat=
 case, triple NATted, but indistinguishable from any other IPv4 service. =
If that was carried over MPLS, Ethernet or PPP upstream.
>>
>> If I'm trolling, I swear it's unintentional.
>> A mobile handset with CLAT built in is a host that only has native IPv=
6, and is doing IPv4 in translation only, right? That host couldn't be co=
nsidered "native dual-stack," could it? Even the bump that provides IPv4 =
to the application is faking it: it's not providing native IPv4, it's pro=
viding translated IPv4.
>>
>> Then there's the much rarer case of CLAT in a home gateway (I'd love t=
o find one that work well!).=C2=A0 Maybe you could say they have native I=
Pv4 access to hosts on the LAN, maybe even throughout the house, but they=
 don't have native IPv4 Internet access, do they?
>>
>> If your ISP provisioned your home with IPv6+464xlat and called it "nat=
ive dual-stack," would you be satisfied with their representation of thei=
r service?
>>
>> All of that was about the definition of "native."=C2=A0 In the origina=
l context, I agree that a device offering CLAT, such as a home gateway or=
 mobile hotspot offering CLAT, should not use the ipv6only-flag. Maybe we=
 need an "ipv4-sorta" flag? (okay, now I'm trolling)
>>
>> Lee
>>
>>>
>>> Ole
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org <mailto:v6ops@ietf.org>
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


From nobody Mon Sep 17 01:15:31 2018
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D1DA130DDB for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 01:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 FDuNzv0PVGPi for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 01:15:26 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 E7902130DCF for <v6ops@ietf.org>; Mon, 17 Sep 2018 01:15:25 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w8H8DuSs025300 for <v6ops@ietf.org>; Mon, 17 Sep 2018 01:15:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=Qk240r3trZF2ZqO2nb8mTB6oP++mWdCnRpCreRZNWrw=; b=O86a58k3P7VO+adj9Q66kJ4rIfOQ/QuWz5wyLWYSGCPJqZrrZrI1mnTx8O2Fnt7dRyMw bW+YnUj0RIfh8wE2r+FeH7/874eG1dbp2m9Uf3wqZGW6UmbW4ma3/ejhlfWG/Hsq7GQB IRzRynKXzI3ffuzVgHSG+Cq19rcPVLuHBSxqTEKti0Dsu/PjG4a+tn7y//7vSsaqzFu2 9Wdz0u2HJUid3ygSlBv2k40CRqaLfCuKGnt8wik1s/4ne80qoYI8I3ZFS+ZgWcm1S5yS u1TKFVXEpTPZkeL0aq/5c3V3dVpNvYKetF5PlmQIhhvahEOgD/yEm37Xhk4zbVlPTtxW Eg== 
Received: from nam04-co1-obe.outbound.protection.outlook.com (mail-co1nam04lp0054.outbound.protection.outlook.com [216.32.181.54]) by mx0b-00273201.pphosted.com with ESMTP id 2mj8gn008n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <v6ops@ietf.org>; Mon, 17 Sep 2018 01:15:24 -0700
Received: from BYAPR05MB4245.namprd05.prod.outlook.com (20.176.252.26) by BYAPR05MB4263.namprd05.prod.outlook.com (20.176.252.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1164.9; Mon, 17 Sep 2018 08:15:23 +0000
Received: from BYAPR05MB4245.namprd05.prod.outlook.com ([fe80::2daa:28b1:6738:5603]) by BYAPR05MB4245.namprd05.prod.outlook.com ([fe80::2daa:28b1:6738:5603%2]) with mapi id 15.20.1143.014; Mon, 17 Sep 2018 08:15:23 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: draft-shytyi-v6ops-danir 
Thread-Index: AdROXmhw8x3KPABOQ8WPYOWXY3TXrQ==
Date: Mon, 17 Sep 2018 08:15:22 +0000
Message-ID: <BYAPR05MB42459628A9152DD600CA1F0DAE1E0@BYAPR05MB4245.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.500.58
dlp-reaction: no-action
x-originating-ip: [116.197.184.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4263; 6:9X6JhA4uOYUeM46ckJrUtuPPX33C/QaqV3ankM87LUjBcMKf7GeJ+dvekLy7kDjDCU3azc6TDR7fdeEA5ROemeSFMHHCgvry3WL1vaRVU70Om350oMPmHNPJkIgqc7Wlu7u5stuijKwEe2Y+lbupOEyLH4FJLPNZDRIP+yAUhhWdW1wM7TT+x+NMunWjUWLTobtJ7rWS2W6nPLLzfu7B8Fqsuae0aFMcsdeZGRLAbH2VRFmSY9xteKJHgdYWeldfAlGvIqElExQ8Qwx+pjBQXtU94A7svbv87a0XZ0VMjtM92ghKS8XOtNWpruSWZkBktKQv4MD1LQquuWhPL77uoWJFij5U/sqHyHhwshx2DA3Niz4IUU8Ho2Ncp6LRZ8V6CTMyk5oHyLtvcwXJDAwHD3Dtx8uxFuAegTtVUBEIz2p29haRMA3oUtfjjJTrKUJcgs8tvuIRkzu434gFuIZwbQ==; 5:fSspB2hmu9xl257aESGWDfdCYM3yWqaRYsWDFcxUbOjC+ibinG4VNfkM1diP2dnap8DSWGP0x/uECQnuDKG2gK0lhx/VBqMSysaro1WSxJgx/qu6jLES4kRlAJqrFf6mCQ5DTShBPwCcFEVUGZFAtQRMNGguWaYQ6eVvd+ApJbU=; 7:CqohWOioG5EuaHjJJlZ2PIFQEripwtGDp5lVuCtJD7pskbEgo4ZyLKGeu2B9JtKwg/ENOOfMbe9eNMgZ/sI8a+Y/2rfr+y5t6pXIeafjF+ZZoTgpmkHeZ8xZ7ChMgeGpjRbOpmh7Booj0t4m500TL7IJgE3coq8HbPDoSm3SgvOmm2uz9vMK1Ii5oZRHAalvBEnksZ66JbPAdW72RzkFZSLuAwXrc7sX5eFBuNe5oqsOmZSXnm7/I36+fMaB/rpo
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 7c8f9661-bcdd-4d2b-f188-08d61c75b741
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4263; 
x-ms-traffictypediagnostic: BYAPR05MB4263:
x-microsoft-antispam-prvs: <BYAPR05MB4263AB6135969BB66CD60219AE1E0@BYAPR05MB4263.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231355)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(201708071742011)(7699050); SRVR:BYAPR05MB4263; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4263; 
x-forefront-prvs: 0798146F16
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(366004)(39860400002)(136003)(346002)(199004)(189003)(6916009)(105586002)(256004)(3846002)(9686003)(6116002)(66066001)(5250100002)(86362001)(316002)(5660300001)(2351001)(2906002)(25786009)(106356001)(97736004)(8676002)(26005)(74316002)(81156014)(4743002)(55016002)(5640700003)(99286004)(6436002)(33656002)(2501003)(486006)(558084003)(8936002)(305945005)(6506007)(7736002)(68736007)(14454004)(2900100001)(476003)(186003)(102836004)(53936002)(478600001)(81166006)(7696005); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4263; H:BYAPR05MB4245.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: r3BhNJBlYisfjZc9AwKhsWzmdgq/aj0HHDZ8E3Cnl1Ad3KQSf9NpGD1yECL4WXW5QniCyxDYe+BCILEik7I5dEidlXMFieCqp5WA7M9dDP7w3mMHClnESd85oRvlj9fLGNDd0Ji7DATo6282fCwYXASOqLJbdsVPy1hEScpmN4TXbPQYK4SPswJAeQ+2vmAjNxHGetapdrJPxEk1QhFXWop2vtA8hrFET/AiNXSNa5VvD02EnC/sBZaXwp3PXl3aC86cOH1LRppHnmcdxn8reL8HiS4bS6Zw16FVlImeYCyNjxxop4DsDY/f05cMJqbbrDWWIxQKyxvpp32G1QYhETlVBc5BDibgwL0vgBPMc1I=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 7c8f9661-bcdd-4d2b-f188-08d61c75b741
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Sep 2018 08:15:22.9557 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4263
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-17_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=423 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809170088
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LY_rn4ePFoTPPhFpPKcy_07neqs>
Subject: [v6ops] draft-shytyi-v6ops-danir
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 Sep 2018 08:15:28 -0000

Folks,

Each week between now and IETF 103, we will review and discuss one draft wi=
th an eye towards progressing it.

This week, please review and comment on draft-shytyi-v6ops-danir

                                                             Fred and Ron


From nobody Mon Sep 17 01:37:47 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33FB91277D2 for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 01:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 y1ZE123Z2m3C for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 01:37:43 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE9841292AD for <v6ops@ietf.org>; Mon, 17 Sep 2018 01:37:43 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 9ECB6FECBB47; Mon, 17 Sep 2018 08:37:42 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id BE99C5BE4E3; Mon, 17 Sep 2018 10:37:40 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <BYAPR05MB42459628A9152DD600CA1F0DAE1E0@BYAPR05MB4245.namprd05.prod.outlook.com>
Date: Mon, 17 Sep 2018 10:37:40 +0200
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <15F8220B-93F7-4D86-9E1F-311D8D4403E2@employees.org>
References: <BYAPR05MB42459628A9152DD600CA1F0DAE1E0@BYAPR05MB4245.namprd05.prod.outlook.com>
To: Ron Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Y-VPpPT4BL7FJNaIcskXaS-nojw>
Subject: Re: [v6ops] draft-shytyi-v6ops-danir
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 Sep 2018 08:37:45 -0000

> This week, please review and comment on draft-shytyi-v6ops-danir

This document reads like the notes an implementor wrote when doing an =
implementation.
It contains snippets from the standard documents used, packets formats =
and so on.

One could have hoped for some specific implementation advice or findings =
of holes or ambiguities in the underlaying standards. I find no =
indication of that in the document.
If an ennumeration of how to implement a =E2=80=9CCE style router=E2=80=9D=
 is needed I am unsure if this adds much over what=E2=80=99s already in =
RFC7084.

Ole


From nobody Mon Sep 17 07:56:45 2018
Return-Path: <lencse@hit.bme.hu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBDF3130DFF for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 07:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 hKZDP7O8r_M9 for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 07:56:32 -0700 (PDT)
Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [IPv6:2001:738:2001:4020::2c]) (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 5F05D130DE6 for <v6ops@ietf.org>; Mon, 17 Sep 2018 07:56:31 -0700 (PDT)
Received: from [192.168.1.134] (host-79-121-41-162.kabelnet.hu [79.121.41.162]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id w8HEtsRm085556 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 17 Sep 2018 16:56:01 +0200 (CEST) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-41-162.kabelnet.hu [79.121.41.162] claimed to be [192.168.1.134]
To: "v6ops@ietf.org list" <v6ops@ietf.org>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com>
Cc: jordi.palet=40consulintel.es@dmarc.ietf.org, Lee Howard <lee@asgard.org>,  Richard Patterson <richard@helix.net.nz>
From: =?UTF-8?Q?Lencse_G=c3=a1bor?= <lencse@hit.bme.hu>
Message-ID: <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu>
Date: Mon, 17 Sep 2018 16:55:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------5C1D3536652C8F731566486F"
X-Virus-Scanned: clamav-milter 0.100.1 at frogstar.hit.bme.hu
X-Virus-Status: Clean
Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.41.162; helo=[192.168.1.134]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; 
X-DCC--Metrics: frogstar.hit.bme.hu; whitelist
X-Scanned-By: MIMEDefang 2.79 on 152.66.248.44
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/vM2rTGSahHjkoYpIoUctqMRf56U>
Subject: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 Sep 2018 14:56:37 -0000

This is a multi-part message in MIME format.
--------------5C1D3536652C8F731566486F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Dear v6ops Members,

With Jordi, Lee and Richard, we have put together a table about the 
advantages and disadvantages of the five IPv4aaS technologies (464XLAT, 
DS-Lite, lw4o6, MAP-E, MAP-T), which can serve as a starting point for 
collecting further information. It can be edited by anyone using the 
following URL:

https://docs.google.com/spreadsheets/d/1W3Px8I_RyLA_tnmmNkJj6qJS0tvg93oCU0XfZzlljto/edit#gid=0

For archival purposes, I copy here its current content:

Aspect 	464XLAT 	DS-Lite 	lw4o6 	MAP-E 	MAP-T 	
	Key 	Meaning
Tunnel (T) / Translation (X) ((neither pro nor con)) 	X (46, 64) 	T 
(4in6) 	T (4in6) 	T (4in6) 	X (46, 64) 	
	+ 	Positive
Can carry any protocol, not only TCP/UDP/ICMP 	- 	+ 	+ 	- 	- 	
	- 	Negative
The following header fields are changed 	
	
	
	
	
	
	| 	Neutral
- TCP/UDP source port number 	may be replaced 	may be replaced 
restricted 	restricted 	restricted 	
	/ 	Not Applicable
- IP version, source and destination addresses 	4-->6-->4 	/ 	/ 	/ 
4-->6-->4 	
	
	
- fields for fragmantation
(DF, MF, fragment offset, identification) 	discarded at
4-->6 translation 	/ 	/ 	/ 	discarded at
4-->6 translation 	
	
	
- IP options 	discarded? 	/ 	/ 	/ 	discarded? 	
I think it depends on the implementation if they are discarded or not
	
	
- further fields shoud go here 	
	
	
	
	
	
	
	
port number efficiency (for ISPs) 	+ 	- 	- 	- 	- 	
	
	
unlimited number of ports for users, when used
for public IPv4 address sharing 	+ 	- 	- 	- 	- 	
	
	
can keep source port numbers unmodified, when used
without public IPv4 address sharing 	+ 	- 	- 	+ 	+ 	
I think is is implementation dependent, at least in the case of NAT64
	
	
Translation at ISP with or without state 	with 	with 	/ 	w/o 	w/o 	
	
	
stateless (num. of states may not cause scalability issue) 	- 	- 	+ 	+ 	+ 	
	
	
allows unsolicited inbound connections 	- 	
	
	+ 	+ 	
I think is is implementation dependent, at least in the case of NAT64
	
	
overhead (Bytes) 	20 	40 	40 	40 	20 	
	
	
Impact in IPv6 addressing plan 	no (+) 	no (+) 	no (+) 	yes (-) 	yes (-) 	
	
	
backbone traffic is like normal IPv6 traffic 	+, but not exactly {1} 	- 
- 	- 	+, but not exactly {1} 	
	
	
logging 	flow/block 	flow/block 	algorithmic 	algorithmic 	algorithmic 	
	
	
Client support in Windows 10 	+ 	- 	- 	- 	- 	
Arguably all the other columns should be marked as N/A as opposed to a 
negative?
	
	
Client support in Linux 	+ 	- 	- 	- 	- 	
It does raise the question about comparing "end-host"-based methods with 
network-based ones.
	
	
Client support in Android 	+ 	- 	- 	- 	- 	
Jordi: From the perspective of "how good is the support" is "-" not N/A 
- For example, if a mechanism is not supported in cellular phones, then 
is a bad option for an ISP to choose it!
	
	
Client support in iOS 	- 	- 	- 	- 	- 	
	
	
Client support in Windows Mobile 	+ 	- 	- 	- 	- 	
	
	
Client support in Chrome OS 	+ 	- 	- 	- 	- 	
	
	
Client support in MacOS 	- 	- 	- 	- 	- 	
	
	
OpenWRT CPE code in kBs (lower is better) 	17 	15 	35 	35 	48 	
	
	
DNS mangling / synthesizing 	- 	
	/ 	/ 	/ 	
Jordi: This is not true. You can deploy 464XLAT with or without DNS64 
see draft-palet-v6ops-nat64-deployment and also the 464XLAT explains it
	
	
BR/AFTR Bypass for CDN 	
	/ 	/ 	/ 	+ 	
I think this is applicable to every transition mechanism, so no need for 
this raw as all can do it
	
	
Support in cellular networks 	+ 	- 	- 	- 	- 	
	
	
Danger of DNS cache poisoning 	somewhat {2} 	somewhat {2} 	high {2} 
high {2} 	high {2} 	
	
	
- further aspects should go here 	
	
	
	
	
	
	
	

	
	
	
	
	
	
	
	
Area for footnotes (please use numbers in braces) 	
	
	
	
	
	
	
	
{1} Both 464XLAT and MAP-T change the distribution of the port numbers, 
thus they may break the port number rules for RTP (even number) and the 
corresponding RTP (next odd number), see RFC 3605 Section 3.2. How much 
important is that ? Why is not key for cellular?
	
	
	
	
	
	
	
	
{2} For all five technologies, CE device SHOULD contain a DNS proxy. 
However, the user may change DNS settings. The restricted port set of 
lw4o6, MAP-E and MAP-T makes these techologies less resilient against 
cache poisoning, see RFC 5452.
	
	
	
	
	
	
	
	



This table is surely neither complete nor error free: This is why we ask 
your help.

As it became evident from the many mails concerning 
draft-ietf-v6ops-transition-ipv4aas (see some of them below) that 
neither of the above 5 technologies are better than all the others in 
all aspects. Perhaps one if them is the best choice for a given 
communication scenario, but another one is much better for another 
scenario. Therefore, an Internet Draft based on a more complete version 
of the table could server as a good selection guide for network operators.

Depending on how much and fast you will contribute, we would like to put 
together the initial version of the draft either for IETF 103 or IETF 104.

Thank you very much for your help in advance,

Best regards,

Gábor


6/19/2018 10:29 AM keltezéssel, Richard Patterson írta:
> Hi Lencse,
>
> I'd be happy to help also.
>
> -Richard
> On Tue, 19 Jun 2018 at 08:09, Lencse Gábor <lencse@hit.bme.hu> wrote:
>> Dear Lee,
>>
>> Thank you very much for offering your help and participation. I have decided to write the draft and I invite you to be a co-author.
>>
>> Are there some other people, who would like to join us?
>>
>> I plan to put together a table with the information extracted from past e-mails on the list and send it to Lee (and possibly other participants) first, and send the Google docs URL to the list after we agreed on its initial content.
>>
>> Best regards,
>>
>> Gábor
>>
>>
>> 6/18/2018 4:38 PM keltezéssel, Lee Howard írta:
>>
>> Apparently I'm a week late on this thread. Sorry.
>>
>> I think an internet-draft in this case would be useful for reflecting the current best knowledge about the technologies. Even if it takes two years or more to publish, a draft is useful to collect  and summarize the detailed academic papers being published, and the structure of writing the draft will help point out areas where further research is needed.
>>
>> I'm also interested in supporting this work, up to and including working with your students,  providing my own test results, and/or co-authoring.
>>
>> Lee
>>
>>
>> On 06/15/2018 10:04 AM, JORDI PALET MARTINEZ wrote:
>>
>> I’m not sure it makes sense something that is not published in, let’s say, maximum one year from now.
>>
>>
>>
>> Anyway, I’m happy to help.
>>
>>
>>
>> By the way, I got some private questions about this … The table that I’ve posted yesterday, was developed about 3 years ago, and I’ve not updated it since them. Actually from emails exchanged today, I discovered a couple of mistakes and also things that can be improved, so if needed I can update it as well.
>>
>>
>> Regards,
>>
>> Jordi
>>
>>
>>
>>
>>
>>
>>
>> De: v6ops <v6ops-bounces@ietf.org> en nombre de Lencse Gábor <lencse@hit.bme.hu>
>> Fecha: viernes, 15 de junio de 2018, 14:25
>> Para: Fred Baker <fredbaker.ietf@gmail.com>
>> CC: <v6ops@ietf.org>
>> Asunto: [v6ops] Pros and Cons of IPv6 Transition Technologies for IPv4aaS -- Re: no need to update RFC8026 in draft-ietf-v6ops-transition-ipv4aas
>>
>>
>>
>> Dear Fred,
>>
>> Thank you very much for your invitation. I am willing to accept it, but I would like to clarify your expectations before saying 'yes'.
>>
>> I have several questions.
>>
>> 1. Depth of the analysis
>>
>> - Basic level: well-known advantages and disadvantages, similarly as people wrote about MAP-T/E and 464XLAT, but also about DS-Lite and lw4o6.
>> - Advanced level: basic level + security analysis using the methodology defined in [1] + performance analysis according to RFC 8219.
>>
>> What depth do you recommend?
>>
>> 2. Method for getting the results and their publication
>>
>> As for the information for the basic level, I would prepare a google docs table, fill in the information I have and send the link to the v6ops list asking contributions.
>> After commenting and discussing, I would compile it to an I-D.
>>
>> Do you think that v6ops WG would finally agree to publish it as an RFC?
>>
>> As for the information for the advanced level, I would work together with my students and PhD students, and publish our results first in academic papers and then include their most important lessons into the I-D.
>>
>> What do you think of it?
>>
>> 3. Timeline
>>
>> I think that I could put together the first table in a few weeks. The contribution of the v6ops list members and the discussion could be done in a few months and then I could compile the results into an I-D in a few weeks. Perhaps, it could be presented at IETF 103.
>>
>> The further parts would require much more time and results could be included gradually in 1-2 years.
>>
>> 4. Scope
>>
>> The smallest natural scope includes the technologies for IPv4AAS, that is: 464XLAT, DS-Lite, MAP-T/E and lw4o6.
>>
>> IPv6 transition technologies for other carefully selected scenarios might also be included. E.g. I have significant amount of results in benchmarking DNS64 servers, having a testing tool [2], a well defined methodology [3] and ready to use results concerning the DNS64 performance of BIND, PowerDNS and Unbound [4].
>> One of my PhD students is currently benchmarking some sateless NAT64 implementations according the the dual DUT setup of RFC 8219 using an RFC 2544 compatible Tester. Another PhD student is currently working on a RFC 8219 compliant NAT64 tester program (using DPDK) to be able to perform single DUT setup NAT64 benchmarking tests.
>>
>> Thus, the scope can be widened, if you would like to.
>>
>> What do you think about my recommendations?
>>
>> Best regards,
>>
>> Gábor
>>
>> References:
>>
>> [1] G. Lencse and Y. Kadobayashi, "Methodology for the identification of potential security issues of different IPv6 transition technologies: Threat analysis of DNS64 and stateful NAT64", Computers & Security (Elsevier), vol. 77, no. 1, pp. 397-411, August 1, 2018, DOI: 10.1016/j.cose.2018.04.012
>>
>> [2] G. Lencse, D. Bakai, "Design and implementation of a test program for benchmarking DNS64 servers", IEICE Transactions on Communications, vol. E100-B, no. 6. pp. 948-954, June 2017. DOI: 10.1587/transcom.2016EBN0007
>>
>> [3] G. Lencse, M. Georgescu, and Y. Kadobayashi, "Benchmarking Methodology for DNS64 Servers", Computer Communications (Elsevier), vol. 109, no. 1, pp. 162-175, September 1, 2017, DOI: 10.1016/j.comcom.2017.06.004
>>
>> [4] G. Lencse and Y. Kadobayashi, "Benchmarking DNS64 Implementations: Theory and Practice", Computer Communications (Elsevier), vol. 127, no. 1, pp. 61-74, September 1, 2018, DOI: 10.1016/j.comcom.2018.05.005
>>
>> 6/14/2018 10:42 PM keltezéssel, Fred Baker írta:
>>
>>
>>
>> On Jun 14, 2018, at 1:15 PM, Lencse Gábor <lencse@hit.bme.hu> wrote:
>>
>> I have an idea: perhaps you could add a section about the pros and cons of each transition technology covered by the draft. (It could be helpful for the network operators when selecting the technology matching their need the best. However, I am not sure whether it is in the scope of this draft.)
>>
>> It would be incredibly useful. That said, it often involves value judgements, which are essentially in the eye of the beholder.
>>
>>
>>
>> We have had a recent thread regarding 464xlat and MAP-T. If I can say this without actually putting words into Lorenzo's mouth, his issues with translation in general are probably summarized in RFC 2993, and I would agree with him. The distinction between 464xlat and MAP-T you'll have to find in his emails; they are both services an ISP might deploy, and while they use the same tool (translation) they are not the same service. It seems to be generally agreed that MAP-T is more expensive to deploy than 464xlat; the question is what the extra expense buys, and whether someone agrees that the result is worth the cost.
>>
>>
>>
>> So in your proposed section, I would have to ask Jordi to not only say "MAP-T costs more to deploy than 464xlat", but gives the argument that might lead someone to choose MAP-T.
>>
>>
>>
>> And then we get to the large variety of other technologies, some of which presume an IPv4 core network and some an IPv6 core network (and none of which assume an MPLS core network carrying both kinds of traffic).
>>
>>
>>
>> If you would like to write such a document, please be my guest, by all means. But I'm not going to expect Jordi to do all that in the coming two weeks...
>>
>>
>> _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>>
>>
>> **********************************************
>> 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 confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
>>
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>>
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops


--------------5C1D3536652C8F731566486F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear v6ops Members,<br>
    <br>
    With Jordi, Lee and Richard, we have put together a table about the
    advantages and disadvantages of the five IPv4aaS technologies
    (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T), which can serve as a
    starting point for collecting further information. It can be edited
    by anyone using the following URL:  <br>
    <br>
<a class="moz-txt-link-freetext" href="https://docs.google.com/spreadsheets/d/1W3Px8I_RyLA_tnmmNkJj6qJS0tvg93oCU0XfZzlljto/edit#gid=0">https://docs.google.com/spreadsheets/d/1W3Px8I_RyLA_tnmmNkJj6qJS0tvg93oCU0XfZzlljto/edit#gid=0</a><br>
    <br>
    For archival purposes, I copy here its current content:<br>
    <br>
    <meta name="generator" content="Sheets">
    <table xmlns="http://www.w3.org/1999/xhtml" dir="ltr"
style="table-layout:fixed;font-size:10pt;font-family:arial,sans,sans-serif;width:0px;border-collapse:collapse;border:none"
      border="1" cellpadding="0" cellspacing="0">
      <colgroup><col width="327"><col width="127"><col width="103"><col
          width="73"><col width="73"><col width="127"><col width="100"><col
          width="100"><col width="100"></colgroup><tbody>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:bold;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Aspect&quot;}">Aspect</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:bold;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;464XLAT&quot;}">464XLAT</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:bold;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;DS-Lite&quot;}">DS-Lite</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:bold;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;lw4o6&quot;}">lw4o6</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:bold;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;MAP-E&quot;}">MAP-E</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:bold;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;MAP-T&quot;}">MAP-T</td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-top:1px solid #000000;border-bottom:1px
            solid #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;font-weight:bold;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Key&quot;}">Key</td>
          <td style="border-top:1px solid #000000;border-right:1px solid
            #000000;border-bottom:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;font-weight:bold;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Meaning&quot;}">Meaning</td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Tunnel (T) /
            Translation (X) ((neither pro nor con))&quot;}">Tunnel (T) /
            Translation (X) ((neither pro nor con))</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;X
            (46, 64)&quot;}">X (46, 64)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;T
            (4in6)&quot;}">T (4in6)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;T
            (4in6)&quot;}">T (4in6)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;T
            (4in6)&quot;}">T (4in6)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;X
            (46, 64)&quot;}">X (46, 64)</td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Positive&quot;}">Positive</td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Can
            carry any protocol, not only TCP/UDP/ICMP&quot;}">Can carry
            any protocol, not only TCP/UDP/ICMP</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;,&quot;6&quot;:1}">-</td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Negative&quot;}">Negative</td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;The
            following header fields are changed&quot;}">The following
            header fields are changed</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;|&quot;}">|</td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Neutral&quot;}">Neutral</td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-
            TCP/UDP source port number&quot;}">- TCP/UDP source port
            number</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;may
            be replaced&quot;}">may be replaced</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;may
            be replaced&quot;}">may be replaced</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;restricted&quot;}">restricted</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;restricted&quot;}">restricted</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;restricted
            &quot;}">restricted </td>
          <td style="border-right:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-bottom:1px solid
            #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="border-right:1px solid #000000;border-bottom:1px
            solid #000000;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Not
            Applicable&quot;}">Not Applicable</td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;- IP
            version, source and destination addresses&quot;}">- IP
            version, source and destination addresses</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;4--&gt;6--&gt;4&quot;}">4--&gt;6--&gt;4</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;4--&gt;6--&gt;4&quot;}">4--&gt;6--&gt;4</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-
            fields for fragmantation \n (DF, MF, fragment offset,
            identification)&quot;}">- fields for fragmantation <br>
            (DF, MF, fragment offset, identification)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;discarded
            at\n4--&gt;6 translation&quot;}">discarded at<br>
            4--&gt;6 translation</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;discarded
            at\n4--&gt;6 translation&quot;}">discarded at<br>
            4--&gt;6 translation</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;- IP
            options&quot;}">- IP options</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;discarded?&quot;}">discarded?</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;discarded?&quot;}">discarded?</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;I
            think it depends on the implementation if they are discarded
            or not&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:398px;left:3px;">
              <div style="float:left;">I think it depends on the
                implementation if they are discarded or not</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-
            further fields shoud go here&quot;}">- further fields shoud
            go here</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;port
            number efficiency (for ISPs)&quot;}">port number efficiency
            (for ISPs)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:35px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;unlimited number
            of ports for users, when used\nfor public IPv4 address
            sharing&quot;}">unlimited number of ports for users, when
            used<br>
            for public IPv4 address sharing</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:36px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;can
            keep source port numbers unmodified, when used\nwithout
            public IPv4 address sharing&quot;}">can keep source port
            numbers unmodified, when used<br>
            without public IPv4 address sharing</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;I
            think is is implementation dependent, at least in the case
            of NAT64&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:398px;left:3px;">
              <div style="float:left;">I think is is implementation
                dependent, at least in the case of NAT64</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Translation at
            ISP with or without state&quot;}">Translation at ISP with or
            without state</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;with&quot;}">with</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;with&quot;}">with</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;w/o&quot;}">w/o</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;w/o&quot;}">w/o</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;stateless (num.
            of states may not cause scalability issue)&quot;}">stateless
            (num. of states may not cause scalability issue)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;,&quot;6&quot;:1}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;allows
            unsolicited inbound connections&quot;}">allows unsolicited
            inbound connections</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;I
            think is is implementation dependent, at least in the case
            of NAT64&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:398px;left:3px;">
              <div style="float:left;">I think is is implementation
                dependent, at least in the case of NAT64</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;overhead
            (Bytes)&quot;}">overhead (Bytes)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:20}">20</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:40}">40</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:40}">40</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:40}">40</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:20}">20</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Impact in IPv6
            addressing plan&quot;}">Impact in IPv6 addressing plan</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;no
            (+)&quot;}">no (+)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;no
            (+)&quot;}">no (+)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;no
            (+)&quot;}">no (+)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;yes
            (-)&quot;}">yes (-)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;yes
            (-)&quot;}">yes (-)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;backbone traffic
            is like normal IPv6 traffic&quot;}">backbone traffic is like
            normal IPv6 traffic</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+,
            but not exactly {1}&quot;,&quot;6&quot;:1}">+, but not
            exactly {1}</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+,
            but not exactly {1}&quot;,&quot;6&quot;:1}">+, but not
            exactly {1}</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;logging&quot;}">logging</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;flow/block&quot;}">flow/block</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;flow/block&quot;}">flow/block</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;algorithmic&quot;}">algorithmic</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;algorithmic&quot;}">algorithmic</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;algorithmic&quot;}">algorithmic</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Client support
            in Windows 10&quot;}">Client support in Windows 10</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Arguably
            all the other columns should be marked as N/A as opposed to
            a negative?&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:499px;left:3px;">
              <div style="float:left;">Arguably all the other columns
                should be marked as N/A as opposed to a negative?</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Client support
            in Linux&quot;}">Client support in Linux</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;It
            does raise the question about comparing
            \&quot;end-host\&quot;-based methods with network-based
            ones.&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:600px;left:3px;">
              <div style="float:left;">It does raise the question about
                comparing "end-host"-based methods with network-based
                ones.</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Client support
            in Android&quot;}">Client support in Android</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Jordi:
            From the perspective of \&quot;how good is the
            support\&quot; is \&quot;-\&quot; not N/A - For example, if
            a mechanism is not supported in cellular phones, then is a
            bad option for an ISP to choose it!&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:1105px;left:3px;">
              <div style="float:left;">Jordi: From the perspective of
                "how good is the support" is "-" not N/A - For example,
                if a mechanism is not supported in cellular phones, then
                is a bad option for an ISP to choose it!</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Client support
            in iOS&quot;}">Client support in iOS</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Client support
            in Windows Mobile&quot;}">Client support in Windows Mobile</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Client support
            in Chrome OS&quot;}">Client support in Chrome OS</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Client support
            in MacOS&quot;}">Client support in MacOS</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;OpenWRT CPE code
            in kBs (lower is better)&quot;}">OpenWRT CPE code in kBs
            (lower is better)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:17}">17</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:15}">15</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:35}">35</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:35}">35</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
            data-sheets-value="{&quot;1&quot;:3,&quot;3&quot;:48}">48</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-decoration:line-through;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;DNS
            mangling / synthesizing&quot;}">DNS mangling / synthesizing</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;text-decoration:line-through;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;text-decoration:line-through;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;text-decoration:line-through;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;text-decoration:line-through;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Jordi:
            This is not true. You can deploy 464XLAT with or without
            DNS64 see draft-palet-v6ops-nat64-deployment and also the
            464XLAT explains it&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:903px;left:3px;">
              <div style="float:left;">Jordi: This is not true. You can
                deploy 464XLAT with or without DNS64 see
                draft-palet-v6ops-nat64-deployment and also the 464XLAT
                explains it</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;BR/AFTR
            Bypass for CDN&quot;}">BR/AFTR Bypass for CDN</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;/&quot;}">/</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;I
            think this is applicable to every transition mechanism, so
            no need for this raw as all can do it&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:600px;left:3px;">
              <div style="float:left;">I think this is applicable to
                every transition mechanism, so no need for this raw as
                all can do it</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Support
            in cellular networks&quot;}">Support in cellular networks</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;+&quot;,&quot;6&quot;:1}">+</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
3px;vertical-align:bottom;font-family:Calibri;font-size:11pt;font-weight:normal;color:#000000;text-align:center;"
data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-&quot;}">-</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Danger
            of DNS cache poisoning&quot;}">Danger of DNS cache poisoning</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;somewhat
            {2}&quot;}">somewhat {2}</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;somewhat
            {2}&quot;}">somewhat {2}</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;high
            {2}&quot;}">high {2}</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;high
            {2}&quot;}">high {2}</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;text-align:center;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;high
            {2}&quot;}">high {2}</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;-
            further aspects should go here&quot;}">- further aspects
            should go here</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 0px 2px
            0px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="overflow:hidden;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;Area
            for footnotes (please use numbers in braces)&quot;}">Area
            for footnotes (please use numbers in braces)</td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;{1}
            Both 464XLAT and MAP-T change the distribution of the port
            numbers, thus they may break the port number rules for RTP
            (even number) and the corresponding RTP (next odd number),
            see RFC 3605 Section 3.2. How much important is that ? Why
            is not key for cellular?&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:1638px;left:3px;">
              <div style="float:left;">{1} Both 464XLAT and MAP-T change
                the distribution of the port numbers, thus they may
                break the port number rules for RTP (even number) and
                the corresponding RTP (next odd number), see RFC 3605
                Section 3.2. How much important is that ? Why is not key
                for cellular?</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
        <tr style="height:21px;">
          <td style="border-right:1px solid
            transparent;overflow:visible;padding:2px 0px 2px
            0px;vertical-align:bottom;"
            data-sheets-value="{&quot;1&quot;:2,&quot;2&quot;:&quot;{2}
            For all five technologies, CE device SHOULD contain a DNS
            proxy. However, the user may change DNS settings. The
            restricted port set of lw4o6, MAP-E and MAP-T makes these
            techologies less resilient against cache poisoning, see RFC
            5452.&quot;}">
            <div
style="white-space:nowrap;overflow:hidden;position:relative;width:1436px;left:3px;">
              <div style="float:left;">{2} For all five technologies, CE
                device SHOULD contain a DNS proxy. However, the user may
                change DNS settings. The restricted port set of lw4o6,
                MAP-E and MAP-T makes these techologies less resilient
                against cache poisoning, see RFC 5452.</div>
            </div>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
          <td style="border-right:1px solid
            transparent;overflow:hidden;padding:2px 3px 2px
            3px;vertical-align:bottom;"><br>
          </td>
        </tr>
      </tbody>
    </table>
    <style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style><br>
    <br>
    This table is surely neither complete nor error free: This is why we
    ask your help.<br>
    <br>
    As it became evident from the many mails concerning
    draft-ietf-v6ops-transition-ipv4aas (see some of them below) that
    neither of the above 5 technologies are better than all the others
    in all aspects. Perhaps one if them is the best choice for a given
    communication scenario, but another one is much better for another
    scenario. Therefore, an Internet Draft based on a more complete
    version of the table could server as a good selection guide for
    network operators. <br>
    <br>
    Depending on how much and fast you will contribute, we would like to
    put together the initial version of the draft either for IETF 103 or
    IETF 104.<br>
    <br>
    Thank you very much for your help in advance,<br>
    <br>
    Best regards,<br>
    <br>
    Gábor<br>
    <br>
    <br>
    <div class="moz-cite-prefix">6/19/2018 10:29 AM keltezéssel, Richard
      Patterson írta:<br>
    </div>
    <blockquote
cite="mid:CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com"
      type="cite">
      <pre wrap="">Hi Lencse,

I'd be happy to help also.

-Richard
On Tue, 19 Jun 2018 at 08:09, Lencse Gábor <a class="moz-txt-link-rfc2396E" href="mailto:lencse@hit.bme.hu">&lt;lencse@hit.bme.hu&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">
Dear Lee,

Thank you very much for offering your help and participation. I have decided to write the draft and I invite you to be a co-author.

Are there some other people, who would like to join us?

I plan to put together a table with the information extracted from past e-mails on the list and send it to Lee (and possibly other participants) first, and send the Google docs URL to the list after we agreed on its initial content.

Best regards,

Gábor


6/18/2018 4:38 PM keltezéssel, Lee Howard írta:

Apparently I'm a week late on this thread. Sorry.

I think an internet-draft in this case would be useful for reflecting the current best knowledge about the technologies. Even if it takes two years or more to publish, a draft is useful to collect  and summarize the detailed academic papers being published, and the structure of writing the draft will help point out areas where further research is needed.

I'm also interested in supporting this work, up to and including working with your students,  providing my own test results, and/or co-authoring.

Lee


On 06/15/2018 10:04 AM, JORDI PALET MARTINEZ wrote:

I’m not sure it makes sense something that is not published in, let’s say, maximum one year from now.



Anyway, I’m happy to help.



By the way, I got some private questions about this … The table that I’ve posted yesterday, was developed about 3 years ago, and I’ve not updated it since them. Actually from emails exchanged today, I discovered a couple of mistakes and also things that can be improved, so if needed I can update it as well.


Regards,

Jordi







De: v6ops <a class="moz-txt-link-rfc2396E" href="mailto:v6ops-bounces@ietf.org">&lt;v6ops-bounces@ietf.org&gt;</a> en nombre de Lencse Gábor <a class="moz-txt-link-rfc2396E" href="mailto:lencse@hit.bme.hu">&lt;lencse@hit.bme.hu&gt;</a>
Fecha: viernes, 15 de junio de 2018, 14:25
Para: Fred Baker <a class="moz-txt-link-rfc2396E" href="mailto:fredbaker.ietf@gmail.com">&lt;fredbaker.ietf@gmail.com&gt;</a>
CC: <a class="moz-txt-link-rfc2396E" href="mailto:v6ops@ietf.org">&lt;v6ops@ietf.org&gt;</a>
Asunto: [v6ops] Pros and Cons of IPv6 Transition Technologies for IPv4aaS -- Re: no need to update RFC8026 in draft-ietf-v6ops-transition-ipv4aas



Dear Fred,

Thank you very much for your invitation. I am willing to accept it, but I would like to clarify your expectations before saying 'yes'.

I have several questions.

1. Depth of the analysis

- Basic level: well-known advantages and disadvantages, similarly as people wrote about MAP-T/E and 464XLAT, but also about DS-Lite and lw4o6.
- Advanced level: basic level + security analysis using the methodology defined in [1] + performance analysis according to RFC 8219.

What depth do you recommend?

2. Method for getting the results and their publication

As for the information for the basic level, I would prepare a google docs table, fill in the information I have and send the link to the v6ops list asking contributions.
After commenting and discussing, I would compile it to an I-D.

Do you think that v6ops WG would finally agree to publish it as an RFC?

As for the information for the advanced level, I would work together with my students and PhD students, and publish our results first in academic papers and then include their most important lessons into the I-D.

What do you think of it?

3. Timeline

I think that I could put together the first table in a few weeks. The contribution of the v6ops list members and the discussion could be done in a few months and then I could compile the results into an I-D in a few weeks. Perhaps, it could be presented at IETF 103.

The further parts would require much more time and results could be included gradually in 1-2 years.

4. Scope

The smallest natural scope includes the technologies for IPv4AAS, that is: 464XLAT, DS-Lite, MAP-T/E and lw4o6.

IPv6 transition technologies for other carefully selected scenarios might also be included. E.g. I have significant amount of results in benchmarking DNS64 servers, having a testing tool [2], a well defined methodology [3] and ready to use results concerning the DNS64 performance of BIND, PowerDNS and Unbound [4].
One of my PhD students is currently benchmarking some sateless NAT64 implementations according the the dual DUT setup of RFC 8219 using an RFC 2544 compatible Tester. Another PhD student is currently working on a RFC 8219 compliant NAT64 tester program (using DPDK) to be able to perform single DUT setup NAT64 benchmarking tests.

Thus, the scope can be widened, if you would like to.

What do you think about my recommendations?

Best regards,

Gábor

References:

[1] G. Lencse and Y. Kadobayashi, "Methodology for the identification of potential security issues of different IPv6 transition technologies: Threat analysis of DNS64 and stateful NAT64", Computers &amp; Security (Elsevier), vol. 77, no. 1, pp. 397-411, August 1, 2018, DOI: 10.1016/j.cose.2018.04.012

[2] G. Lencse, D. Bakai, "Design and implementation of a test program for benchmarking DNS64 servers", IEICE Transactions on Communications, vol. E100-B, no. 6. pp. 948-954, June 2017. DOI: 10.1587/transcom.2016EBN0007

[3] G. Lencse, M. Georgescu, and Y. Kadobayashi, "Benchmarking Methodology for DNS64 Servers", Computer Communications (Elsevier), vol. 109, no. 1, pp. 162-175, September 1, 2017, DOI: 10.1016/j.comcom.2017.06.004

[4] G. Lencse and Y. Kadobayashi, "Benchmarking DNS64 Implementations: Theory and Practice", Computer Communications (Elsevier), vol. 127, no. 1, pp. 61-74, September 1, 2018, DOI: 10.1016/j.comcom.2018.05.005

6/14/2018 10:42 PM keltezéssel, Fred Baker írta:



On Jun 14, 2018, at 1:15 PM, Lencse Gábor <a class="moz-txt-link-rfc2396E" href="mailto:lencse@hit.bme.hu">&lt;lencse@hit.bme.hu&gt;</a> wrote:

I have an idea: perhaps you could add a section about the pros and cons of each transition technology covered by the draft. (It could be helpful for the network operators when selecting the technology matching their need the best. However, I am not sure whether it is in the scope of this draft.)

It would be incredibly useful. That said, it often involves value judgements, which are essentially in the eye of the beholder.



We have had a recent thread regarding 464xlat and MAP-T. If I can say this without actually putting words into Lorenzo's mouth, his issues with translation in general are probably summarized in RFC 2993, and I would agree with him. The distinction between 464xlat and MAP-T you'll have to find in his emails; they are both services an ISP might deploy, and while they use the same tool (translation) they are not the same service. It seems to be generally agreed that MAP-T is more expensive to deploy than 464xlat; the question is what the extra expense buys, and whether someone agrees that the result is worth the cost.



So in your proposed section, I would have to ask Jordi to not only say "MAP-T costs more to deploy than 464xlat", but gives the argument that might lead someone to choose MAP-T.



And then we get to the large variety of other technologies, some of which presume an IPv4 core network and some an IPv6 core network (and none of which assume an MPLS core network carrying both kinds of traffic).



If you would like to write such a document, please be my guest, by all means. But I'm not going to expect Jordi to do all that in the coming two weeks...


_______________________________________________ v6ops mailing list <a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a> <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>


**********************************************
IPv4 is over
Are you ready for the new Internet ?
<a class="moz-txt-link-freetext" href="http://www.consulintel.es">http://www.consulintel.es</a>
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.



_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>




_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>


_______________________________________________
v6ops mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a>
</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------5C1D3536652C8F731566486F--


From nobody Mon Sep 17 09:42:20 2018
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C570130E82 for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 09:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level: 
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] 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 MeTf7eEUtsBK for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 09:42:16 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 62626130E36 for <v6ops@ietf.org>; Mon, 17 Sep 2018 09:42:16 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8HGgEoi024958 for <v6ops@ietf.org>; Mon, 17 Sep 2018 18:42:14 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 90A5E206FEF for <v6ops@ietf.org>; Mon, 17 Sep 2018 18:42:14 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 86F4C204250 for <v6ops@ietf.org>; Mon, 17 Sep 2018 18:42:14 +0200 (CEST)
Received: from [10.8.68.65] ([10.8.68.65]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8HGgDQY029535 for <v6ops@ietf.org>; Mon, 17 Sep 2018 18:42:14 +0200
To: v6ops@ietf.org
References: <BYAPR05MB42459628A9152DD600CA1F0DAE1E0@BYAPR05MB4245.namprd05.prod.outlook.com> <15F8220B-93F7-4D86-9E1F-311D8D4403E2@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b1d0c8a5-28bd-1694-5dea-54d6bd72ef51@gmail.com>
Date: Mon, 17 Sep 2018 18:42:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <15F8220B-93F7-4D86-9E1F-311D8D4403E2@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Gn5vfQNGpWDKxZqMMMFlFK3aJkM>
Subject: Re: [v6ops] draft-shytyi-v6ops-danir
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 Sep 2018 16:42:19 -0000

Thank you for looking at our draft!

We take the advice and will maybe update the draft accordingly.

One recommendation we suggest for DHCP is to _not_ use port 547 because
many people block it.  Use another one, like 25474, or maybe create a
method to dynamically negotiate such port number.

Another may have to do with Hop Limit and multicast scope in DHCP 
Solicit messages.  Make it larger and it will allow to put DHCP servers 
_outside_ the cellular network domain, and work with port numbers that 
we want, not only those that are imposed by RFC and blocked by those who 
ignore RFC.

-------------------------------------------------------------------------
Below this there is ranting.

Another recommendation I have is that the link layer protocol used to
make IPv6 addresses in 3GPP network be documented - and agreed - at
IETF, not only at 3GPP.  Without such document and agreement it is next
to impossible to discuss meaningfully about IPv6 and User Equipments at
IETF.

But I agree this latter recommendation is probably hard to follow.  It
needs much hardware and other expensive ressources and commitment,
together with an open mind.  Moreover, many people say such
recommendations are useless, because each SDO with its own tech.

(it's in the same list of recommendations I have, like the one to
document the Human Rights in an IETF document, rather than referring to
some 1947 UN outdated text).

Le 17/09/2018 à 10:37, Ole Troan a écrit :
>> This week, please review and comment on draft-shytyi-v6ops-danir
> 
> This document reads like the notes an implementor wrote when doing an
> implementation.

Yes, that is it.  I think there is nothing remotely even wrong with 
that, and it is a good way to write documents.

> It contains snippets from the standard documents
> used, packets formats and so on.

YEs, again, packet formats is what protocols are about.  The inner 
working of a protocol is in its packet format and field description.

Moreover, these are packets captured on the network, i.e. running code.

> 
> One could have hoped for some specific implementation advice or
> findings of holes or ambiguities in the underlaying standards. I find
> no indication of that in the document. If an ennumeration of how to
> implement a “CE style router” is needed I am unsure if this adds much
> over what’s already in RFC7084.

What is the RFC7084 'title'?

It is very often hard to follow discussions where there is talk about 
RFC numbers but we dont know what is the RFC about.  There are almost 
10.000 RFCs out there.  We know some of them by heart, but others no.

Of course, one could say this: with the RFC number just google and find 
it.  But there is some additional work to do: open the browser, type in, 
make sure you select the right answer, click, scroll, and read some 
part.  This work could have been saved by typing a short version of the 
title in the email referring to it.

Alex

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


From nobody Mon Sep 17 10:11:28 2018
Return-Path: <ietf.dmytro@shytyi.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33F9E130E72 for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 10:11:27 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=shytyi.net
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 IScPN8glfxX1 for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 10:11:24 -0700 (PDT)
Received: from sender-of-o52.zoho.eu (sender-of-o52.zoho.eu [31.186.226.248]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 090CD1274D0 for <v6ops@ietf.org>; Mon, 17 Sep 2018 10:11:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1537204280;  s=hs; d=shytyi.net; i=ietf.dmytro@shytyi.net; h=Date:From:To:Message-Id:In-Reply-To:References:Subject:MIME-Version:Content-Type; l=15886; bh=TxZoChZtKeIwhrwwLEYGcIoXTS56IlW/Cm1jJJK9cfc=; b=dvFTymbhAPOPZYAv34SgK7fK/b+ObPFpXzsy1CZwqrNnZZoE8yNu+aW1DnJ+gYSu H4FReRyvNsSd5oBOF+OaiZ3+ws1ccMEE1AdeqUH1e81Sjoy79rXIb3I3QPogGcgVeK0 tEmjlHKaSbj0XdPAR4nnK13UXNUGuXaIwRd5P4eg=
Received: from sender.zoho.eu (172.26.23.78 [172.26.23.78]) by mx.zoho.eu with SMTPS id 1537204279732502.4235835253635; Mon, 17 Sep 2018 19:11:19 +0200 (CEST)
Received: from mail.zoho.eu by mx.zoho.eu with SMTP id 1537204279649654.1134570522482; Mon, 17 Sep 2018 19:11:19 +0200 (CEST)
Date: Mon, 17 Sep 2018 19:11:19 +0200
From: Dmytro Shytyi <ietf.dmytro@shytyi.net>
To: <v6ops@ietf.org>
Message-Id: <165e883d95d.ac21c0fe172547.1220214479113257130@shytyi.net>
In-Reply-To: <b1d0c8a5-28bd-1694-5dea-54d6bd72ef51@gmail.com>
References: <BYAPR05MB42459628A9152DD600CA1F0DAE1E0@BYAPR05MB4245.namprd05.prod.outlook.com> <15F8220B-93F7-4D86-9E1F-311D8D4403E2@employees.org> <b1d0c8a5-28bd-1694-5dea-54d6bd72ef51@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_452630_1435364264.1537204279645"
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/G7QUB-RMiwbqvkEPFMJxOOEEZqY>
Subject: Re: [v6ops] draft-shytyi-v6ops-danir
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 Sep 2018 17:11:27 -0000

------=_Part_452630_1435364264.1537204279645
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello, Thank you for considering of the draft-shytyi-v6ops-danir :) Your co=
mments are valuable for us. Also we have updated nits, but did not submit t=
he new versoin of the draft yet. I support the Alexandre Petrescu statement=
.=C2=A0 After these comments in the next version we may add the next inform=
ation: Recommendation #1: Hop limit should be set to some (say 42*) value t=
o avoid "packet drop" on the path to the DHCP server. Recommendation #2: DH=
CP in the cellular environment should use different port (static or via neg=
otiaiton method) *https://en.wikipedia.org/wiki/42_(number)#The_Hitchhiker'=
s_Guide_to_the_Galaxy "The number 42 is, in=C2=A0The Hitchhiker's Guide to =
the Galaxy=C2=A0by=C2=A0Douglas Adams, the "Answer to the Ultimate Question=
 of Life, the Universe, and Everything", calculated by=C2=A0an enormous sup=
ercomputer named Deep Thought=C2=A0over a period of 7.5 million years. Unfo=
rtunately, no one knows what the question is. Thus, to calculate the Ultima=
te Question, a special computer the size of a..." ______________ Dmytro SHY=
TYI ---- On Mon, 17 Sep 2018 18:42:13 +0200=C2=A0Alexandre Petrescu <alexan=
dre.petrescu@gmail.com> wrote ---- Thank you for looking at our draft! We t=
ake the advice and will maybe update the draft accordingly. One recommendat=
ion we suggest for DHCP is to _not_ use port 547 because many people block =
it. Use another one, like 25474, or maybe create a method to dynamically ne=
gotiate such port number. Another may have to do with Hop Limit and multica=
st scope in DHCP Solicit messages. Make it larger and it will allow to put =
DHCP servers _outside_ the cellular network domain, and work with port numb=
ers that we want, not only those that are imposed by RFC and blocked by tho=
se who ignore RFC. --------------------------------------------------------=
----------------- Below this there is ranting. Another recommendation I hav=
e is that the link layer protocol used to make IPv6 addresses in 3GPP netwo=
rk be documented - and agreed - at IETF, not only at 3GPP. Without such doc=
ument and agreement it is next to impossible to discuss meaningfully about =
IPv6 and User Equipments at IETF. But I agree this latter recommendation is=
 probably hard to follow. It needs much hardware and other expensive ressou=
rces and commitment, together with an open mind. Moreover, many people say =
such recommendations are useless, because each SDO with its own tech. (it's=
 in the same list of recommendations I have, like the one to document the H=
uman Rights in an IETF document, rather than referring to some 1947 UN outd=
ated text). Le 17/09/2018 =C3=A0 10:37, Ole Troan a =C3=A9crit : >> This we=
ek, please review and comment on draft-shytyi-v6ops-danir > > This document=
 reads like the notes an implementor wrote when doing an > implementation. =
Yes, that is it. I think there is nothing remotely even wrong with that, an=
d it is a good way to write documents. > It contains snippets from the stan=
dard documents > used, packets formats and so on. YEs, again, packet format=
s is what protocols are about. The inner working of a protocol is in its pa=
cket format and field description. Moreover, these are packets captured on =
the network, i.e. running code. > > One could have hoped for some specific =
implementation advice or > findings of holes or ambiguities in the underlay=
ing standards. I find > no indication of that in the document. If an ennume=
ration of how to > implement a =E2=80=9CCE style router=E2=80=9D is needed =
I am unsure if this adds much > over what=E2=80=99s already in RFC7084. Wha=
t is the RFC7084 'title'? It is very often hard to follow discussions where=
 there is talk about RFC numbers but we dont know what is the RFC about. Th=
ere are almost 10.000 RFCs out there. We know some of them by heart, but ot=
hers no. Of course, one could say this: with the RFC number just google and=
 find it. But there is some additional work to do: open the browser, type i=
n, make sure you select the right answer, click, scroll, and read some part=
. This work could have been saved by typing a short version of the title in=
 the email referring to it. Alex > > Ole > > ______________________________=
_________________ v6ops mailing list > v6ops@ietf.org https://www.ietf.org/=
mailman/listinfo/v6ops > _______________________________________________ v6=
ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
------=_Part_452630_1435364264.1537204279645
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>=
<meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"></h=
ead><body ><div style=3D'font-size:10pt;font-family:Verdana,Arial,Helvetica=
,sans-serif;color:#00000;'><div>Hello,<br></div><div><br></div><div>Thank y=
ou for considering of the draft-shytyi-v6ops-danir :)<br></div><div>Your co=
mments are valuable for us.<br></div><div><br>Also we have updated nits, bu=
t did not submit the new versoin of the draft<b><u> yet.</u></b></div><div>=
I support the Alexandre Petrescu statement.&nbsp; After these comments in t=
he next version we may add the next information:<br></div><ul><li>Recommend=
ation #1: Hop limit should be set to some (say 42*) value to avoid "packet =
drop" on the path to the DHCP server.<br></li><li>Recommendation #2: DHCP i=
n the cellular environment should use different port (static or via negotia=
iton method)<br></li></ul><div>*<a target=3D"_blank" href=3D"https://www.go=
ogle.fr/search?q=3Dwhat+is+the+answer+to+life+the+universe+and+everything&a=
mp;rlz=3D1C1GCEA_enFR791FR791&amp;oq=3Dwhat+is+the+unswer+&amp;aqs=3Dchrome=
.1.69i57j0l5.14941j0j7&amp;sourceid=3Dchrome&amp;ie=3DUTF-8"><a target=3D"_=
blank" href=3D"https://en.wikipedia.org/wiki/42_(number)#The_Hitchhiker's_G=
uide_to_the_Galaxy">https://en.wikipedia.org/wiki/42_(number)#The_Hitchhike=
r's_Guide_to_the_Galaxy</a></a><br></div><div><br></div><blockquote style=
=3D"border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: r=
gb(245, 245, 245);"><div><span class=3D"highlight" style=3D"background-colo=
r:rgb(255, 255, 255)"><span class=3D"colour" style=3D"color:rgb(34, 34, 34)=
"><span class=3D"font" style=3D"font-family:sans-serif"><span class=3D"size=
" style=3D"font-size:14px">"The number 42 is, in<span>&nbsp;</span></span><=
/span></span></span><i style=3D"color: rgb(34, 34, 34); font-family: sans-s=
erif; font-size: 14px; font-variant-ligatures: normal; font-variant-caps: n=
ormal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: st=
art; text-indent: 0px; text-transform: none; white-space: normal; widows: 2=
; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(=
255, 255, 255); text-decoration-style: initial; text-decoration-color: init=
ial;"><a href=3D"https://en.wikipedia.org/wiki/The_Hitchhiker%27s_Guide_to_=
the_Galaxy_(novel)" title=3D"The Hitchhiker's Guide to the Galaxy (novel)" =
style=3D"text-decoration: none; color: rgb(11, 0, 128); background: none;">=
The Hitchhiker's Guide to the Galaxy</a></i><span class=3D"highlight" style=
=3D"background-color:rgb(255, 255, 255)"><span class=3D"colour" style=3D"co=
lor:rgb(34, 34, 34)"><span class=3D"font" style=3D"font-family:sans-serif">=
<span class=3D"size" style=3D"font-size:14px"><span>&nbsp;</span>by<span>&n=
bsp;</span></span></span></span></span><a href=3D"https://en.wikipedia.org/=
wiki/Douglas_Adams" title=3D"Douglas Adams" style=3D"text-decoration: none;=
 color: rgb(11, 0, 128); background: none rgb(255, 255, 255); font-family: =
sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: no=
rmal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; =
orphans: 2; text-align: start; text-indent: 0px; text-transform: none; whit=
e-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0=
px;">Douglas Adams</a><span class=3D"highlight" style=3D"background-color:r=
gb(255, 255, 255)"><span class=3D"colour" style=3D"color:rgb(34, 34, 34)"><=
span class=3D"font" style=3D"font-family:sans-serif"><span class=3D"size" s=
tyle=3D"font-size:14px">, the "</span></span></span></span><a href=3D"https=
://en.wikipedia.org/wiki/Phrases_from_The_Hitchhiker%27s_Guide_to_the_Galax=
y#Answer_to_the_Ultimate_Question_of_Life,_the_Universe,_and_Everything_(42=
)" title=3D"Phrases from The Hitchhiker's Guide to the Galaxy" style=3D"tex=
t-decoration: none; color: rgb(11, 0, 128); background: none rgb(255, 255, =
255); font-family: sans-serif; font-size: 14px; font-style: normal; font-va=
riant-ligatures: normal; font-variant-caps: normal; font-weight: 400; lette=
r-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-stroke-width: 0px;">Answer to the Ultimate Question of Life, the Univer=
se, and Everything</a><span class=3D"highlight" style=3D"background-color:r=
gb(255, 255, 255)"><span class=3D"colour" style=3D"color:rgb(34, 34, 34)"><=
span class=3D"font" style=3D"font-family:sans-serif"><span class=3D"size" s=
tyle=3D"font-size:14px">", calculated by<span>&nbsp;</span></span></span></=
span></span><a href=3D"https://en.wikipedia.org/wiki/Deep_Thought_(The_Hitc=
hhiker%27s_Guide_to_the_Galaxy)" class=3D"mw-redirect" title=3D"Deep Though=
t (The Hitchhiker's Guide to the Galaxy)" style=3D"text-decoration: none; c=
olor: rgb(11, 0, 128); background: none rgb(255, 255, 255); font-family: sa=
ns-serif; font-size: 14px; font-style: normal; font-variant-ligatures: norm=
al; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; or=
phans: 2; text-align: start; text-indent: 0px; text-transform: none; white-=
space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px=
;">an enormous supercomputer named Deep Thought</a><span class=3D"highlight=
" style=3D"background-color:rgb(255, 255, 255)"><span class=3D"colour" styl=
e=3D"color:rgb(34, 34, 34)"><span class=3D"font" style=3D"font-family:sans-=
serif"><span class=3D"size" style=3D"font-size:14px"><span>&nbsp;</span>ove=
r a period of 7.5 million years. Unfortunately, no one knows what the quest=
ion is. Thus, to calculate the Ultimate Question, a special computer the si=
ze of a..."</span></span></span></span><br></div></blockquote><div><br></di=
v><div id=3D"Zm-_Id_-Sgn"><div><div>______________<br></div><div><b>Dmytro =
SHYTYI</b><br></div></div></div><div><br></div><div class=3D"zmail_extra"><=
div id=3D"Zm-_Id_-Sgn1"><div><br></div><div>---- On Mon, 17 Sep 2018 18:42:=
13 +0200&nbsp;<b>Alexandre Petrescu &lt;alexandre.petrescu@gmail.com&gt;</b=
> wrote ----<br></div></div><div><br></div><blockquote style=3D"border-left=
: 1px solid #cccccc; padding-left: 6px; margin:0 0 0 5px"><div><div>Thank y=
ou for looking at our draft!<br></div><div><br></div><div>We take the advic=
e and will maybe update the draft accordingly.<br></div><div><br></div><div=
>One recommendation we suggest for DHCP is to _not_ use port 547 because<br=
></div><div>many people block it.  Use another one, like 25474, or maybe cr=
eate a<br></div><div>method to dynamically negotiate such port number.<br><=
/div><div><br></div><div>Another may have to do with Hop Limit and multicas=
t scope in DHCP <br></div><div>Solicit messages.  Make it larger and it wil=
l allow to put DHCP servers <br></div><div>_outside_ the cellular network d=
omain, and work with port numbers that <br></div><div>we want, not only tho=
se that are imposed by RFC and blocked by those who <br></div><div>ignore R=
FC.<br></div><div><br></div><div>------------------------------------------=
-------------------------------<br></div><div>Below this there is ranting.<=
br></div><div><br></div><div>Another recommendation I have is that the link=
 layer protocol used to<br></div><div>make IPv6 addresses in 3GPP network b=
e documented - and agreed - at<br></div><div>IETF, not only at 3GPP.  Witho=
ut such document and agreement it is next<br></div><div>to impossible to di=
scuss meaningfully about IPv6 and User Equipments at<br></div><div>IETF.<br=
></div><div><br></div><div>But I agree this latter recommendation is probab=
ly hard to follow.  It<br></div><div>needs much hardware and other expensiv=
e ressources and commitment,<br></div><div>together with an open mind.  Mor=
eover, many people say such<br></div><div>recommendations are useless, beca=
use each SDO with its own tech.<br></div><div><br></div><div>(it's in the s=
ame list of recommendations I have, like the one to<br></div><div>document =
the Human Rights in an IETF document, rather than referring to<br></div><di=
v>some 1947 UN outdated text).<br></div><div><br></div><div>Le 17/09/2018 =
=C3=A0 10:37, Ole Troan a =C3=A9crit :<br></div><div>&gt;&gt; This week, pl=
ease review and comment on draft-shytyi-v6ops-danir<br></div><div>&gt; <br>=
</div><div>&gt; This document reads like the notes an implementor wrote whe=
n doing an<br></div><div>&gt; implementation.<br></div><div><br></div><div>=
Yes, that is it.  I think there is nothing remotely even wrong with <br></d=
iv><div>that, and it is a good way to write documents.<br></div><div><br></=
div><div>&gt; It contains snippets from the standard documents<br></div><di=
v>&gt; used, packets formats and so on.<br></div><div><br></div><div>YEs, a=
gain, packet formats is what protocols are about.  The inner <br></div><div=
>working of a protocol is in its packet format and field description.<br></=
div><div><br></div><div>Moreover, these are packets captured on the network=
, i.e. running code.<br></div><div><br></div><div>&gt; <br></div><div>&gt; =
One could have hoped for some specific implementation advice or<br></div><d=
iv>&gt; findings of holes or ambiguities in the underlaying standards. I fi=
nd<br></div><div>&gt; no indication of that in the document. If an ennumera=
tion of how to<br></div><div>&gt; implement a =E2=80=9CCE style router=E2=
=80=9D is needed I am unsure if this adds much<br></div><div>&gt; over what=
=E2=80=99s already in RFC7084.<br></div><div><br></div><div>What is the RFC=
7084 'title'?<br></div><div><br></div><div>It is very often hard to follow =
discussions where there is talk about <br></div><div>RFC numbers but we don=
t know what is the RFC about.  There are almost <br></div><div>10.000 RFCs =
out there.  We know some of them by heart, but others no.<br></div><div><br=
></div><div>Of course, one could say this: with the RFC number just google =
and find <br></div><div>it.  But there is some additional work to do: open =
the browser, type in, <br></div><div>make sure you select the right answer,=
 click, scroll, and read some <br></div><div>part.  This work could have be=
en saved by typing a short version of the <br></div><div>title in the email=
 referring to it.<br></div><div><br></div><div>Alex<br></div><div><br></div=
><div>&gt; <br></div><div>&gt; Ole<br></div><div>&gt; <br></div><div>&gt; _=
______________________________________________ v6ops mailing list <br></div=
><div>&gt; v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops<br></=
div><div>&gt; <br></div><div><br></div><div>_______________________________=
________________<br></div><div>v6ops mailing list<br></div><div>v6ops@ietf.=
org<br></div><div>https://www.ietf.org/mailman/listinfo/v6ops<br></div></di=
v></blockquote></div><div><br></div></div><br></body></html>
------=_Part_452630_1435364264.1537204279645--




From nobody Mon Sep 17 11:29:08 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA253130E7D for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 11:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 r3cbtB-TjL5R for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 11:29:04 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E24A3128CB7 for <v6ops@ietf.org>; Mon, 17 Sep 2018 11:29:04 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 9C9D4FECBE93; Mon, 17 Sep 2018 18:29:03 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id A17EF5C7DDD; Mon, 17 Sep 2018 20:29:01 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu>
Date: Mon, 17 Sep 2018 20:29:01 +0200
Cc: "v6ops@ietf.org list" <v6ops@ietf.org>, jordi.palet=40consulintel.es@dmarc.ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BAED6F00-D705-4137-9A03-280452557C07@employees.org>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu>
To: =?utf-8?Q?Lencse_G=C3=A1bor?= <lencse@hit.bme.hu>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/U4PgX9EMhLxCMjPiO6pSYhxwpEs>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 Sep 2018 18:29:07 -0000

Lencse,

I did a few corrections. You might want to split LW46, MAP-E and MAP-T =
into =E2=80=9Cshared address mode=E2=80=9D and =E2=80=9Cfull IPv4 =
address=E2=80=9D and possibly IPv4 prefix.
Obviously the first have similar properties to the NAT solutions, while =
the non-sharing ones are transparent with regards to IP protocol.

A few comments below.

> unlimited number of ports for users, when used
> for public IPv4 address sharing	+	-	-	-	=
-=09

I am not sure what that means. Any solution depending on a CGN will be =
port restricted in some fashion. Otherwise the operator would open =
itself to an attack.

> can keep source port numbers unmodified, when used
> without public IPv4 address sharing	+	-	-	+	=
+=09
> I think is is implementation dependent, at least in the case of NAT64

What does this mean?

> Translation at ISP with or without state	with	with	/	=
w/o	w/o=09

MAP-E should be changed to =E2=80=9C/=E2=80=9C

> stateless (num. of states may not cause scalability issue)	-	=
-	+	+	+=09
>=20
>=20
> allows unsolicited inbound connections	-=09
>=20
> +	+=09
> I think is is implementation dependent, at least in the case of NAT64
>=20
>=20
> overhead (Bytes)	20	40	40	40	20=09
>=20
>=20
> Impact in IPv6 addressing plan	no (+)	no (+)	no (+)	yes (-)	=
yes (-)=09

Perhaps rename this to =E2=80=9CIPv4 addresses are dependent on IPv6 =
addressing"

> backbone traffic is like normal IPv6 traffic	+, but not exactly {1}	=
-	-	-	+, but not exactly {1}=09
>=20
>=20
> logging	flow/block	flow/block	algorithmic	=
algorithmic	algorithmic=09
>=20
>=20
> Client support in Windows 10	+	-	-	-	-=09
> Arguably all the other columns should be marked as N/A as opposed to a =
negative?
>=20
>=20
> Client support in Linux	+	-	-	-	-=09
> It does raise the question about comparing "end-host"-based methods =
with network-based ones.
>=20
>=20
> Client support in Android	+	-	-	-	-=09
> Jordi: =46rom the perspective of "how good is the support" is "-" not =
N/A - For example, if a mechanism is not supported in cellular phones, =
then is a bad option for an ISP to choose it!
>=20
>=20
> Client support in iOS	-	-	-	-	-=09
>=20
>=20
> Client support in Windows Mobile	+	-	-	-	=
-=09
>=20
>=20
> Client support in Chrome OS	+	-	-	-	-=09
>=20
>=20
> Client support in MacOS	-	-	-	-	-=09
>=20
>=20
> OpenWRT CPE code in kBs (lower is better)	17	15	35	=
35	48=09
>=20
>=20
> DNS mangling / synthesizing	-=09
> /	/	/=09
> Jordi: This is not true. You can deploy 464XLAT with or without DNS64 =
see draft-palet-v6ops-nat64-deployment and also the 464XLAT explains it
>=20
>=20
> BR/AFTR Bypass for CDN=09
> /	/	/	+=09
> I think this is applicable to every transition mechanism, so no need =
for this raw as all can do it

What does this mean? As in IPv4 translated to IPv6 can talk directly to =
IPV6 services within the network? If so only MAP-T and 464XLAT can do =
that.

> Support in cellular networks	+	-	-	-	-=09

Cause cellular networks are not part of the Internet?

> Danger of DNS cache poisoning	somewhat {2}	somewhat {2}	high {2}	=
high {2}	high {2}=09

See below.

>=20
> Area for footnotes (please use numbers in braces)=09
>=20
> {1} Both 464XLAT and MAP-T change the distribution of the port =
numbers, thus they may break the port number rules for RTP (even number) =
and the corresponding RTP (next odd number), see RFC 3605 Section 3.2. =
How much important is that ? Why is not key for cellular?

DS-lite and 464XLAT uses whatever policy is set on the CGN.
LW46, MAP-T and MAP-E uses the PSID algorithm which does allocate =
multiple subsequent ports for this purpose.
Of course no modern RTP application depend on this behaviour any more.

> {2} For all five technologies, CE device SHOULD contain a DNS proxy. =
However, the user may change DNS settings. The restricted port set of =
lw4o6, MAP-E and MAP-T makes these techologies less resilient against =
cache poisoning, see RFC 5452.

a) why SHOULD CE devices contain a DNS proxy?
b) if it did, it would use IPv6 transport of course, and the problems =
you outline do not exist.

>=20
> This table is surely neither complete nor error free: This is why we =
ask your help.
>=20
> As it became evident from the many mails concerning =
draft-ietf-v6ops-transition-ipv4aas (see some of them below) that =
neither of the above 5 technologies are better than all the others in =
all aspects. Perhaps one if them is the best choice for a given =
communication scenario, but another one is much better for another =
scenario. Therefore, an Internet Draft based on a more complete version =
of the table could server as a good selection guide for network =
operators.=20
>=20
> Depending on how much and fast you will contribute, we would like to =
put together the initial version of the draft either for IETF 103 or =
IETF 104.
>=20
> Thank you very much for your help in advance,


Ole


From nobody Mon Sep 17 13:33:49 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4244E12F1A5 for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 13:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 n1q7puD1M56c for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 13:33:46 -0700 (PDT)
Received: from atl4mhob17.registeredsite.com (atl4mhob17.registeredsite.com [209.17.115.110]) (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 A1BFA1294D0 for <v6ops@ietf.org>; Mon, 17 Sep 2018 13:33:46 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail01pod6.registeredsite.com [10.30.71.209]) by atl4mhob17.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8HKXiEP018159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Mon, 17 Sep 2018 16:33:44 -0400
Received: (qmail 26276 invoked by uid 0); 17 Sep 2018 20:33:44 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 17 Sep 2018 20:33:44 -0000
To: v6ops@ietf.org
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <BAED6F00-D705-4137-9A03-280452557C07@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <e84171ce-3567-9086-8e8b-e36dc99172e0@asgard.org>
Date: Mon, 17 Sep 2018 16:33:43 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <BAED6F00-D705-4137-9A03-280452557C07@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Fbuy13B0iiqBCbU3VbhesjcvNPk>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 17 Sep 2018 20:33:48 -0000

On 09/17/2018 02:29 PM, Ole Troan wrote:
> Lencse,
>
> I did a few corrections. You might want to split LW46, MAP-E and MAP-T into “shared address mode” and “full IPv4 address” and possibly IPv4 prefix.
> Obviously the first have similar properties to the NAT solutions, while the non-sharing ones are transparent with regards to IP protocol.
>
> A few comments below.
>
>> unlimited number of ports for users, when used
>> for public IPv4 address sharing	+	-	-	-	-	
> I am not sure what that means. Any solution depending on a CGN will be port restricted in some fashion. Otherwise the operator would open itself to an attack.
>
>> can keep source port numbers unmodified, when used
>> without public IPv4 address sharing	+	-	-	+	+	
>> I think is is implementation dependent, at least in the case of NAT64
> What does this mean?

Some NAT devices rewrite the layer 4 source port. Presumably, this is 
because multiple devices inside the NAT might use the same source port 
number. Rewriting the source port isn't required if you aren't doing 
IPv4 address sharing; does the mechanism still rewrite it?

>
>> Translation at ISP with or without state	with	with	/	w/o	w/o	
> MAP-E should be changed to “/“
How is MAP-E different from MAP-T with regard to state at the ISP? (I 
think they're both stateless and should say w/o, but I may be confused).



>
>> Support in cellular networks	+	-	-	-	-	
> Cause cellular networks are not part of the Internet?
I think this is an observation of what mechanisms are currently 
supported in cellular architectures.
There's nothing preventing a DS-Lite B4 or MAP client implementation on 
a mobile device, but I don't know of any. As operational advice, I would 
advise an operator to deploy something that exists. :)

Is this not relevant, do you think?


Lee


From nobody Mon Sep 17 17:34:07 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DFDA130E01 for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 17:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 cFBeoNXkA4xu for <v6ops@ietfa.amsl.com>; Mon, 17 Sep 2018 17:34:03 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 B0C4F126BED for <v6ops@ietf.org>; Mon, 17 Sep 2018 17:34:03 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id D39E23AB042; Tue, 18 Sep 2018 00:34:01 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 913C9160044; Tue, 18 Sep 2018 00:34:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 7A23C1600A8; Tue, 18 Sep 2018 00:34:01 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id cjtYtfxfnOP0; Tue, 18 Sep 2018 00:34:01 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 48DCA160044; Tue, 18 Sep 2018 00:33:59 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu>
Date: Tue, 18 Sep 2018 10:33:55 +1000
Cc: "v6ops@ietf.org list" <v6ops@ietf.org>, jordi.palet=40consulintel.es@dmarc.ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <91A290C6-E187-439C-8916-E4720244A5A7@isc.org>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu>
To: =?utf-8?Q?Lencse_G=C3=A1bor?= <lencse@hit.bme.hu>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/psgg1zdqLqciJAm_r0SELjbgOvU>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Sep 2018 00:34:05 -0000

Requires using ISP=E2=80=99s recursive servers

Yes, No, No, No, No

We don=E2=80=99t yet have a NAT64 prefix discovery mechanism for 464XLAT =
that=20
doesn=E2=80=99t use the DNS.  This is not the same as requiring DNS64.  =
The
mapping can be in a locally served IPV4ONLY.ARPA zone (note this has
all the same DNSSEC issues as DNS64 because IANA=E2=80=99s IPV4ONLY.ARPA =
zone
is signed and securely delegated).

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Tue Sep 18 00:24:11 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F9B9130DED for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 00:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 vPt6ZVNeMW-1 for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 00:24:07 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8518F127AC2 for <v6ops@ietf.org>; Tue, 18 Sep 2018 00:24:07 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id E12C7FECBE95; Tue, 18 Sep 2018 07:24:05 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id F1AC75CA9E2; Tue, 18 Sep 2018 09:24:03 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <e84171ce-3567-9086-8e8b-e36dc99172e0@asgard.org>
Date: Tue, 18 Sep 2018 09:24:03 +0200
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3537301A-9983-4807-A5E8-52358BA8A748@employees.org>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <BAED6F00-D705-4137-9A03-280452557C07@employees.org> <e84171ce-3567-9086-8e8b-e36dc99172e0@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tnZIRzONx862R_hReYUYiLYmvR4>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Sep 2018 07:24:09 -0000

>> I did a few corrections. You might want to split LW46, MAP-E and =
MAP-T into =E2=80=9Cshared address mode=E2=80=9D and =E2=80=9Cfull IPv4 =
address=E2=80=9D and possibly IPv4 prefix.
>> Obviously the first have similar properties to the NAT solutions, =
while the non-sharing ones are transparent with regards to IP protocol.
>>=20
>> A few comments below.
>>=20
>>> unlimited number of ports for users, when used
>>> for public IPv4 address sharing	+	-	-	-	=
-=09
>> I am not sure what that means. Any solution depending on a CGN will =
be port restricted in some fashion. Otherwise the operator would open =
itself to an attack.
>>=20
>>> can keep source port numbers unmodified, when used
>>> without public IPv4 address sharing	+	-	-	+	=
+=09
>>> I think is is implementation dependent, at least in the case of =
NAT64
>> What does this mean?
>=20
> Some NAT devices rewrite the layer 4 source port. Presumably, this is =
because multiple devices inside the NAT might use the same source port =
number. Rewriting the source port isn't required if you aren't doing =
IPv4 address sharing; does the mechanism still rewrite it?

I wonder if it would be cleaner to split out non IPv4 sharing modes into =
separate columns. Because they behave quite differently.
With regards to protocol transparency (TCP, UDP, ..) with regards to =
fragmentation behaviour and so on. What thinks?

>>> Translation at ISP with or without state	with	with	/	=
w/o	w/o=09
>> MAP-E should be changed to =E2=80=9C/=E2=80=9C
> How is MAP-E different from MAP-T with regard to state at the ISP? (I =
think they're both stateless and should say w/o, but I may be confused).

I just triggered on the word =E2=80=9CTranslation=E2=80=9D and why LW46 =
had a / while MAP-E had a w/o.
There isn=E2=80=99t a difference between MAP-E and LW46 here.

>>> Support in cellular networks	+	-	-	-	=
-=09
>> Cause cellular networks are not part of the Internet?
> I think this is an observation of what mechanisms are currently =
supported in cellular architectures.
> There's nothing preventing a DS-Lite B4 or MAP client implementation =
on a mobile device, but I don't know of any. As operational advice, I =
would advise an operator to deploy something that exists. :)
>=20
> Is this not relevant, do you think?

I think it might just have been phrasing. It isn=E2=80=99t the cellular =
architecture (or specifications), but client support. Which of course is =
important.

Cheers,
Ole=


From nobody Tue Sep 18 08:19:51 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51918130E4D for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 08:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 UyGH_Tli58sx for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 08:19:48 -0700 (PDT)
Received: from atl4mhob22.registeredsite.com (atl4mhob22.registeredsite.com [209.17.115.116]) (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 C86CE130E21 for <v6ops@ietf.org>; Tue, 18 Sep 2018 08:19:48 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob22.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8IFJj62193097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Tue, 18 Sep 2018 11:19:46 -0400
Received: (qmail 20935 invoked by uid 0); 18 Sep 2018 15:19:45 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 18 Sep 2018 15:19:45 -0000
To: Ole Troan <otroan@employees.org>
Cc: v6ops@ietf.org
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <BAED6F00-D705-4137-9A03-280452557C07@employees.org> <e84171ce-3567-9086-8e8b-e36dc99172e0@asgard.org> <3537301A-9983-4807-A5E8-52358BA8A748@employees.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <4f002b8e-44e8-2c99-f769-6a0f77303d98@asgard.org>
Date: Tue, 18 Sep 2018 11:19:44 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <3537301A-9983-4807-A5E8-52358BA8A748@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9e7L1yD4JJcSBdESujhTxGMdgW0>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Sep 2018 15:19:50 -0000

I agree with what you say here, and think that if this proceeds to a 
draft we should include these notes and distinctions.


Lee


On 09/18/2018 03:24 AM, Ole Troan wrote:
>>> I did a few corrections. You might want to split LW46, MAP-E and MAP-T into “shared address mode” and “full IPv4 address” and possibly IPv4 prefix.
>>> Obviously the first have similar properties to the NAT solutions, while the non-sharing ones are transparent with regards to IP protocol.
>>>
>>> A few comments below.
>>>
>>>> unlimited number of ports for users, when used
>>>> for public IPv4 address sharing	+	-	-	-	-	
>>> I am not sure what that means. Any solution depending on a CGN will be port restricted in some fashion. Otherwise the operator would open itself to an attack.
>>>
>>>> can keep source port numbers unmodified, when used
>>>> without public IPv4 address sharing	+	-	-	+	+	
>>>> I think is is implementation dependent, at least in the case of NAT64
>>> What does this mean?
>> Some NAT devices rewrite the layer 4 source port. Presumably, this is because multiple devices inside the NAT might use the same source port number. Rewriting the source port isn't required if you aren't doing IPv4 address sharing; does the mechanism still rewrite it?
> I wonder if it would be cleaner to split out non IPv4 sharing modes into separate columns. Because they behave quite differently.
> With regards to protocol transparency (TCP, UDP, ..) with regards to fragmentation behaviour and so on. What thinks?
>
>>>> Translation at ISP with or without state	with	with	/	w/o	w/o	
>>> MAP-E should be changed to “/“
>> How is MAP-E different from MAP-T with regard to state at the ISP? (I think they're both stateless and should say w/o, but I may be confused).
> I just triggered on the word “Translation” and why LW46 had a / while MAP-E had a w/o.
> There isn’t a difference between MAP-E and LW46 here.
>
>>>> Support in cellular networks	+	-	-	-	-	
>>> Cause cellular networks are not part of the Internet?
>> I think this is an observation of what mechanisms are currently supported in cellular architectures.
>> There's nothing preventing a DS-Lite B4 or MAP client implementation on a mobile device, but I don't know of any. As operational advice, I would advise an operator to deploy something that exists. :)
>>
>> Is this not relevant, do you think?
> I think it might just have been phrasing. It isn’t the cellular architecture (or specifications), but client support. Which of course is important.
>
> Cheers,
> Ole


From nobody Tue Sep 18 08:23:32 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1C1129385 for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 08:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 1qy_Tif4ENKQ for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 08:23:29 -0700 (PDT)
Received: from atl4mhob21.registeredsite.com (atl4mhob21.registeredsite.com [209.17.115.115]) (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 DFB0F128CF3 for <v6ops@ietf.org>; Tue, 18 Sep 2018 08:23:28 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail02pod6.registeredsite.com [10.30.71.210]) by atl4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8IFNQfv083082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Tue, 18 Sep 2018 11:23:26 -0400
Received: (qmail 26025 invoked by uid 0); 18 Sep 2018 15:23:26 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 18 Sep 2018 15:23:26 -0000
To: v6ops@ietf.org
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
Date: Tue, 18 Sep 2018 11:23:23 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <91A290C6-E187-439C-8916-E4720244A5A7@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/fM6N68cEsA3Qkztwx_8snyQInLY>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Sep 2018 15:23:30 -0000

On 09/17/2018 08:33 PM, Mark Andrews wrote:
> Requires using ISP’s recursive servers
>
> Yes, No, No, No, No
>
> We don’t yet have a NAT64 prefix discovery mechanism for 464XLAT that
> doesn’t use the DNS.  This is not the same as requiring DNS64.  The
> mapping can be in a locally served IPV4ONLY.ARPA zone (note this has
> all the same DNSSEC issues as DNS64 because IANA’s IPV4ONLY.ARPA zone
> is signed and securely delegated).
>
As I think about it, Google has public DNS64 servers that return a 
synthesized address using the WKP 64:ff9b::/96. So you might not be 
required to use the ISP's DNS (if the ISP uses the WKP).
Or, as you say, other DNS shenanigans.

Lee


From nobody Tue Sep 18 08:59:00 2018
Return-Path: <edwin@scordeiro.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 868CE130E18 for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 08:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 MabbbXhJVZsI for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 08:58:55 -0700 (PDT)
Received: from p3plsmtpa06-06.prod.phx3.secureserver.net (p3plsmtpa06-06.prod.phx3.secureserver.net [173.201.192.107]) (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 44DC9130E14 for <v6ops@ietf.org>; Tue, 18 Sep 2018 08:58:55 -0700 (PDT)
Received: from mail-oi0-f47.google.com ([209.85.218.47]) by :SMTPAUTH: with ESMTPSA id 2IOrgKJexntoI2IOsgdnm7; Tue, 18 Sep 2018 08:58:54 -0700
Received: by mail-oi0-f47.google.com with SMTP id p84-v6so2267182oic.4 for <v6ops@ietf.org>; Tue, 18 Sep 2018 08:58:54 -0700 (PDT)
X-Gm-Message-State: APzg51CFunxBjhL7HMtDgRHN0R440yXUYK9qjilbLVpc0TiJrfGwjTiI tcOPpK3P3TCBTBy0wiQWN/5hZQUfhtrFhAYEa5k=
X-Google-Smtp-Source: ANB0VdbtZ91J91KfDLfivtYNqY+/527r4jFVo/fX3eOCIg8706vivENzvpMQ48lHYjwmsrw6pLLkoHiHzyO9l3enBEQ=
X-Received: by 2002:aca:d846:: with SMTP id p67-v6mr1912708oig.42.1537286333592;  Tue, 18 Sep 2018 08:58:53 -0700 (PDT)
MIME-Version: 1.0
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org> <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
In-Reply-To: <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
From: Edwin Cordeiro <edwin@scordeiro.net>
Date: Tue, 18 Sep 2018 17:58:26 +0200
X-Gmail-Original-Message-ID: <CAERpkxBmQOH10W2c-SumYbS84UKQapo50bKVeunpJBOBm3ci1Q@mail.gmail.com>
Message-ID: <CAERpkxBmQOH10W2c-SumYbS84UKQapo50bKVeunpJBOBm3ci1Q@mail.gmail.com>
To: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d500480576275da1"
X-CMAE-Envelope: MS4wfCXMaxvfzSNgBXX6P/OTvQDn3z5zDI6PsuqtiPXW4C0LYKAZSJPjtJrvCoGvzhxUBLJI8BdeU6KWsCjEs1w2iJcGHE3AF/WWDK5qbO9TO+lMHMdI6rPn 0fEV2Ghx1Ti0m541C87ZXoCZRoG/CPsrtBm++vVZVWgClIddxifCy91Pkm8+QbAOElT54qblpOl81g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/niHBV3ymBfWHFGqKhMPP4MnsYEE>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Sep 2018 15:58:59 -0000

--000000000000d500480576275da1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I did an analysis on some of the techniques a few years ago, not sure if it
would still be useful:
http://edwin.scordeiro.net/wp-content/uploads/2016/04/ComparisonBetweenIPv4=
toIPv6TransitionTechniques.pdf

In the unlikely case you speak Portuguese all the details are available at:
http://edwin.scordeiro.net/wp-content/uploads/2016/04/Edwin_Cordeiro_Mestra=
do_IPT.pdf

Edwin Cordeiro


On Tue, Sep 18, 2018 at 5:23 PM Lee Howard <lee@asgard.org> wrote:

>
>
> On 09/17/2018 08:33 PM, Mark Andrews wrote:
> > Requires using ISP=E2=80=99s recursive servers
> >
> > Yes, No, No, No, No
> >
> > We don=E2=80=99t yet have a NAT64 prefix discovery mechanism for 464XLA=
T that
> > doesn=E2=80=99t use the DNS.  This is not the same as requiring DNS64. =
 The
> > mapping can be in a locally served IPV4ONLY.ARPA zone (note this has
> > all the same DNSSEC issues as DNS64 because IANA=E2=80=99s IPV4ONLY.ARP=
A zone
> > is signed and securely delegated).
> >
> As I think about it, Google has public DNS64 servers that return a
> synthesized address using the WKP 64:ff9b::/96. So you might not be
> required to use the ISP's DNS (if the ISP uses the WKP).
> Or, as you say, other DNS shenanigans.
>
> Lee
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--000000000000d500480576275da1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_defa=
ult" style=3D"font-family:verdana,sans-serif;font-size:small">I did an anal=
ysis on some of the techniques a few years ago, not sure if it would still =
be useful:</div><div class=3D"gmail_default"><font face=3D"verdana, sans-se=
rif"><a href=3D"http://edwin.scordeiro.net/wp-content/uploads/2016/04/Compa=
risonBetweenIPv4toIPv6TransitionTechniques.pdf">http://edwin.scordeiro.net/=
wp-content/uploads/2016/04/ComparisonBetweenIPv4toIPv6TransitionTechniques.=
pdf</a></font><br></div><div class=3D"gmail_default"><font face=3D"verdana,=
 sans-serif"><br></font></div><div class=3D"gmail_default"><font face=3D"ve=
rdana, sans-serif">In the unlikely case you speak Portuguese all the detail=
s are available at:</font></div><div class=3D"gmail_default"><font face=3D"=
verdana, sans-serif"><a href=3D"http://edwin.scordeiro.net/wp-content/uploa=
ds/2016/04/Edwin_Cordeiro_Mestrado_IPT.pdf">http://edwin.scordeiro.net/wp-c=
ontent/uploads/2016/04/Edwin_Cordeiro_Mestrado_IPT.pdf</a><br></font></div>=
<div class=3D"gmail_default"><font face=3D"verdana, sans-serif"><br></font>=
</div><div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div=
><div dir=3D"ltr"><font face=3D"verdana, sans-serif">Edwin Cordeiro</font><=
br></div></div></div></div></div><br></div></div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr">On Tue, Sep 18, 2018 at 5:23 PM Lee Howard &lt;=
<a href=3D"mailto:lee@asgard.org">lee@asgard.org</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><br>
<br>
On 09/17/2018 08:33 PM, Mark Andrews wrote:<br>
&gt; Requires using ISP=E2=80=99s recursive servers<br>
&gt;<br>
&gt; Yes, No, No, No, No<br>
&gt;<br>
&gt; We don=E2=80=99t yet have a NAT64 prefix discovery mechanism for 464XL=
AT that<br>
&gt; doesn=E2=80=99t use the DNS.=C2=A0 This is not the same as requiring D=
NS64.=C2=A0 The<br>
&gt; mapping can be in a locally served IPV4ONLY.ARPA zone (note this has<b=
r>
&gt; all the same DNSSEC issues as DNS64 because IANA=E2=80=99s IPV4ONLY.AR=
PA zone<br>
&gt; is signed and securely delegated).<br>
&gt;<br>
As I think about it, Google has public DNS64 servers that return a <br>
synthesized address using the WKP 64:ff9b::/96. So you might not be <br>
required to use the ISP&#39;s DNS (if the ISP uses the WKP).<br>
Or, as you say, other DNS shenanigans.<br>
<br>
Lee<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div>

--000000000000d500480576275da1--


From nobody Tue Sep 18 12:06:49 2018
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF80130E5A for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 12:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Dzg8VMvhclZN for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 12:06:45 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914D2130E4E for <v6ops@ietf.org>; Tue, 18 Sep 2018 12:06:45 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from simons-macbookpro.thehobsons.co.uk (Simons-MacBookPro.thehobsons.co.uk [192.168.137.111]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id C3E511A071 for <v6ops@ietf.org>; Tue, 18 Sep 2018 19:06:38 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <e84171ce-3567-9086-8e8b-e36dc99172e0@asgard.org>
Date: Tue, 18 Sep 2018 20:06:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E03054A-3ECD-4835-AA47-6E26F783750A@thehobsons.co.uk>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <BAED6F00-D705-4137-9A03-280452557C07@employees.org> <e84171ce-3567-9086-8e8b-e36dc99172e0@asgard.org>
To: "v6ops@ietf.org list" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1Q1tObkc711MIlBg2vHZ7gRJL20>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Sep 2018 19:06:48 -0000

Lee Howard <lee@asgard.org> wrote:

> Some NAT devices rewrite the layer 4 source port. Presumably, this is =
because multiple devices inside the NAT might use the same source port =
number.

Indeed, that is a requirement - though strictly speaking it's possible =
to share the same source address and port for different destination =
address/port pairs, the requirement is that the source address-port/dest =
address-port quartet needs to be unique.

As an aside, I've come across NAT implementations that deliberately =
change (randomise) source port even when not required. A right PITA when =
trying to get SIP devices to work - STUN finds one translation but the =
SIP connection gets given another. Thank you Zyxel with your "never mind =
what it breaks, it's secure" approach :-/


From nobody Tue Sep 18 17:47:20 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C7F130EB8 for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 17:47:18 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 R-k5lXVjCrQ0 for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 17:47:17 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 EEB72130ECA for <v6ops@ietf.org>; Tue, 18 Sep 2018 17:47:16 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id d10-v6so5970327itj.5 for <v6ops@ietf.org>; Tue, 18 Sep 2018 17:47:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=v5M9L8j0ugMSxXDinicPwDnO///cd1/Z7cvzZdDpBYQ=; b=He3IhNY0e33fUox+fm0er9vJEItCBxtdiPmnljicC/u2hL526CAYb+AVPbU1WVHMWR Ivn/NmKLiynndd0iHHnVU/tXMV20kpB4JMol7b7RO0QmOMPh3en6N4Y9UDRAtDQRKIfd Rb2HpVxKXGcAGlrv/JdSUoEPiu5pUzIBDxjPhcoyN/oVroPU+7JL0nNhm2kVN6Q2oyAr lUNJx8BtinJ1gDnS+EEg8z8fuOB2k0XAnafX6Ech3ltMqDeqXlRXbnfrs3qgc+V/EyzV I177MQpbY9V2uMrow9D2nTS2h5oTMgJvMwvCV3B7Iarheh5824mPVe9Zbpv+g1JzD6a6 IeAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=v5M9L8j0ugMSxXDinicPwDnO///cd1/Z7cvzZdDpBYQ=; b=Rm4+NFR/D22kxtLelNEle8sLkNrta2fnroINXqggkNvH+F5LPaoiVfp8eiRBuWkvX1 bxsp1Ncqzlclj5MuH/A0PBktwUdlyC8s3ZREoTHkG9Q1EfI55jfBYD96V21vOQV56D4W DeFJNRhCMi2rLRLpqH3SjVv/tmfkiSrPuNw4a0KVoG6BzYUyqHaqCpB+fI0N67wTwqV8 Iwn2vY0XkC0/zPOuQGZeC4tIduzMPQnDNzJf6JWYAoM3zKwRTHGmbp4Y7UFrxaFJiuJa 1doftHkl0ztleZ13cuAJSxaefsuJQkB4gsXloDSb502xevVL8DipbwiaY7rpL0eziTRb I8yw==
X-Gm-Message-State: APzg51ArQSU3aBN6gct6LYKrcbeP+u0QNBoNzxZTOGZ1XLq5GZEVYh4E smd7aQmm1pDVhR7c43HKgwIbOr31
X-Google-Smtp-Source: ANB0VdZnUVwZWKnx8OrJO13WWqsmqzX/VdxHeqV3VMjQHJl7rAxgLc1QEeCANpuvBH/SVrNnZIkmGQ==
X-Received: by 2002:a24:4c8d:: with SMTP id a135-v6mr19264713itb.110.1537318036357;  Tue, 18 Sep 2018 17:47:16 -0700 (PDT)
Received: from [172.30.225.5] ([67.133.97.98]) by smtp.gmail.com with ESMTPSA id 68-v6sm6906637itx.19.2018.09.18.17.47.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Sep 2018 17:47:15 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <F1F73F2C-A567-42B4-BE53-B65E8438363B@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_610E6E75-D8D6-4100-9646-9A8F280604DB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 18 Sep 2018 20:44:28 -0400
In-Reply-To: <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
Cc: v6ops@ietf.org
To: Lee Howard <Lee@asgard.org>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org> <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/5IA6InQ_yms_Ny1pbzKuTuWiIrY>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 00:47:19 -0000

--Apple-Mail=_610E6E75-D8D6-4100-9646-9A8F280604DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Sep 18, 2018, at 11:23 AM, Lee Howard <Lee@asgard.org> wrote:
>=20
> As I think about it, Google has public DNS64 servers that return a =
synthesized address using the WKP 64:ff9b::/96. So you might not be =
required to use the ISP's DNS (if the ISP uses the WKP).

Of course, if you have an ISP-supplied DNS server that is doing the same =
but with a different prefix, and you're overriding to the Google server, =
you have a protocol failure.

=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_610E6E75-D8D6-4100-9646-9A8F280604DB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluhm+wACgkQEhdRnd2G
P+AhrA/9FQ/SLsO0KX0XMS5J/lGTOKTAI1R8U1mwIk+AOV07O4lPYJ0h1uwsFiNZ
rT5P0BoMozF1aPnJNurIT8o50Qm03Ph7qu557AuvfkcyqZFnoHClSNYO/4kKIBEl
cwIuiWJsMBRSblLKNAiRDgto1lPHevvURSmLhnV6U7k2lxyH3BqtF3hMYb01gA6T
q0od8ZPT1dpL0ualwQ6WN+4PM1wpI3zNZTT0c197Dt5pVut3rHf6/gRG0RrQipRZ
o6oxrFyCntQUZvYKNTSUqeYve/mseZ+C5d7DCd/FmjOKtk38ma7gvNfDUIcJVi8/
4gV4VG+NlqKjHdhD3ncvKnUgRFKL34O/GtFPSrIteBgHfleP5YesSw3dvMR35ex2
3jMaSgp4XXnSSGKqHm/lgCltrn1zv6cVPNsgXbZ25EWCpfuUqpThRNlow5gLsWJE
vzYwS5CM0vxrK5faFJcqxFFgOTwxUFM67LPYCK5a9l5uTdPLhelL2xtGo+ss8tK7
F36tQ/Ztfh7RTcSeRMJjcJeQnTD1FrWndyxoPtAx8FxuP00wa4BgWPlbKzONZmJ2
+v8GY0dbNRDzBz+UND+7fq60FU02dWoQEyhHUklOUifOGaJVbh10j3Gl4FuU5/9X
KpdCG7E8RFINhoqYJjVAnTxxZH2PWHv8V5AOXHv0gI/PlTUxjbo=
=7Xin
-----END PGP SIGNATURE-----

--Apple-Mail=_610E6E75-D8D6-4100-9646-9A8F280604DB--


From nobody Tue Sep 18 17:47:32 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE0A0130EE4 for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 17:47:22 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 P3eimsBDaWud for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 17:47:21 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 19676130ED1 for <v6ops@ietf.org>; Tue, 18 Sep 2018 17:47:21 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id v14-v6so3115734iob.4 for <v6ops@ietf.org>; Tue, 18 Sep 2018 17:47:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=7e6Hg+gzeTaIOTz0OEQops2XQoc55KyFPx4dZZAKs88=; b=kTt1zzSylu0wkZGLZ9BlSqrENs9fDY/3lg/OQsRg8uFnGAkVQzED/Ff+hi+RKa0A0L 1z5vdeZ9/toPg12CGmSLIY4Rvh5W3GoHVfSD6gbuPJXXS532VrNYy7TZmXV95SrU9Pw8 odXAxkWSBfoTaTuOngGMqlo1EEHVgSBHyfPUtWiY0Xd+iZzuJhBDO3vRzjWUbmJ+C5I3 9hkGPtXaVQIMtdOStezPZNRoUajWdwRRs6ctU1b6MRcVFbYZHKsAPrkYRbl3mq2BbAhY Ru5Pkr8+zB5ENxAAbDwYrleL/QUEumoMBEQpr4nRJXAraXcjyyVmQqnG8ZhrblpbDKkm /QdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=7e6Hg+gzeTaIOTz0OEQops2XQoc55KyFPx4dZZAKs88=; b=CWss9+2E9ytdz+fHww2pvPo8rAUAlcEUr1EoSQ+G/tiqatHQdU+2vKynrDYiaslhWw gHMbIYn+AV5nAdYWodrz7wPN5xJ0INyT84dFmp53BgjCw+FmnMUL83eyyBp5Sz9955GU 20oEVkG7e2uZ04SLslfRgS0uxH/cY+xAFHUvgSnduDfn7DwVCa3XcKW0Dd0mSH+utbhc DT6xvHSw7FC0Xj5NCL8vi+vD3MJ1aSaRzy9vbgQtAqTgu01Y+e65SoMNXLaqBADbgC0C Kut7r7mhRcpxh6M2J+R0rPO8sVOe3jKHsiicXV3j18pLijOmanW8ohfr8Qecq43mWHzN xwAg==
X-Gm-Message-State: APzg51CcN+/jLR5eQQVKwmz31XIknLyXhtCBB+3pEVpNWf2OpmVDnnQt ifSZrKE547thLqcehG+hliFBIutQ
X-Google-Smtp-Source: ANB0Vdb473Rutm5ImmIR9z3UMRdKHlkLuAXoY+1+wnYo236BqMrz8luqAB4t4XIAHnniKV6708wLYQ==
X-Received: by 2002:a6b:c042:: with SMTP id q63-v6mr26539577iof.261.1537318040350;  Tue, 18 Sep 2018 17:47:20 -0700 (PDT)
Received: from [172.30.225.5] ([67.133.97.98]) by smtp.gmail.com with ESMTPSA id 68-v6sm6906637itx.19.2018.09.18.17.47.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Sep 2018 17:47:19 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <91A8CB55-8F34-463E-9390-A33F97B8A706@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8CC33392-E898-4DED-A686-9CA996D0DBE3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 18 Sep 2018 20:45:05 -0400
In-Reply-To: <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
Cc: v6ops@ietf.org
To: Lee Howard <Lee@asgard.org>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org> <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/stQ7N_YE8XDDRQqDaItJCpHYMss>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 00:47:30 -0000

--Apple-Mail=_8CC33392-E898-4DED-A686-9CA996D0DBE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Or for that matter, if your ISP has no translator at any prefix and =
you're using the Google server, you have an outage.

> On Sep 18, 2018, at 11:23 AM, Lee Howard <Lee@asgard.org> wrote:
>=20
> As I think about it, Google has public DNS64 servers that return a =
synthesized address using the WKP 64:ff9b::/96. So you might not be =
required to use the ISP's DNS (if the ISP uses the WKP).

=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_8CC33392-E898-4DED-A686-9CA996D0DBE3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluhnBEACgkQEhdRnd2G
P+DF5w//XQAE2QEwNvhyACou4sSk6wP6J84S5nrNfGqz3Y5UCWP0lo3Mt33y6HUN
HjptGClwgmHBduoHC4inGw6s7X5Ftdb2H+bm+EzNJbKaWUyputxSwoygN/hilQva
4vKH8TB90jcGe5+DhXANU56Z4y+CYa4YzUuBW1JPrDehT2WvUTsBkivq8xFtS9YG
8pNxqh9Ms0Z77LrRpgQC1nM925YV7C+rnQ4xtmejOCostS5GSk01Lj1S5k7fTmtz
FU9XqFqADri52MT1VdQd2BftaIwNuPCHty9sWC9zD4KGSzmL9LXXdUcDToMOVp4s
HUoDzWlAtNkOkSDrKciHxfGDjy93FRk/9Om6Rfdb1IK40HX62hugRATeTbzOC3Zg
WJPlU2Hg6GRRXJYUmAHfdMNKnpRdGPc0feXKwfGKux1yAAIvxxPwoW2mA6geM4M7
VwY80k55XtIReUsjR6HIvYLnZGsmW911yftRBlCrsr5vn1ta4HKEX4+QlD7cpdHL
vadxmpegdDlxFOzbnPF3se8oiJnTj2uoVbTrm0x1oAeDukNMosS/+X71+a+4MS0O
ERtb3qXC34INtBLIc3alfd3Fb9xXy3sGL4veRwPY62lhnw5Ds4CSyNIYQc0AFcEB
RzVB0NtY2RrBfUtCyec7MwRWo2SU6EDGLqfEcsvLo+APr7cRvrw=
=IHqg
-----END PGP SIGNATURE-----

--Apple-Mail=_8CC33392-E898-4DED-A686-9CA996D0DBE3--


From nobody Tue Sep 18 17:50:56 2018
Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A45A130ED1 for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 17:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 vxGWcclwbBRD for <v6ops@ietfa.amsl.com>; Tue, 18 Sep 2018 17:50:52 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 D9158128CF2 for <v6ops@ietf.org>; Tue, 18 Sep 2018 17:50:52 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 77D5F3AB001; Wed, 19 Sep 2018 00:50:52 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 52058160050; Wed, 19 Sep 2018 00:50:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 057391600AF; Wed, 19 Sep 2018 00:50:52 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id As2KKas8ylrH; Wed, 19 Sep 2018 00:50:51 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id D3CFC160050; Wed, 19 Sep 2018 00:50:50 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
Date: Wed, 19 Sep 2018 10:50:47 +1000
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C83413C2-596D-4826-AEA3-6DC065492B45@isc.org>
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org> <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org>
To: Lee Howard <lee@asgard.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OyZzaJbp642chkhY4WN-etrtYs4>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 00:50:55 -0000

> On 19 Sep 2018, at 1:23 am, Lee Howard <lee@asgard.org> wrote:
>=20
>=20
>=20
> On 09/17/2018 08:33 PM, Mark Andrews wrote:
>> Requires using ISP=E2=80=99s recursive servers
>>=20
>> Yes, No, No, No, No
>>=20
>> We don=E2=80=99t yet have a NAT64 prefix discovery mechanism for =
464XLAT that
>> doesn=E2=80=99t use the DNS.  This is not the same as requiring =
DNS64.  The
>> mapping can be in a locally served IPV4ONLY.ARPA zone (note this has
>> all the same DNSSEC issues as DNS64 because IANA=E2=80=99s =
IPV4ONLY.ARPA zone
>> is signed and securely delegated).
>>=20
> As I think about it, Google has public DNS64 servers that return a =
synthesized address using the WKP 64:ff9b::/96. So you might not be =
required to use the ISP's DNS (if the ISP uses the WKP).
> Or, as you say, other DNS shenanigans.

Which only works if your ISP is using the WKP which requires apiary =
knowledge (i.e. test your ISP=E2=80=99s nameservers or look it up on a =
web page).

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

--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org


From nobody Wed Sep 19 03:05:54 2018
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1D8130ECF for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 03:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level: 
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] 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 6TNeG8mHtdOs for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 03:05:50 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 EB54F130EE1 for <v6ops@ietf.org>; Wed, 19 Sep 2018 03:05:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8JA5m17015519 for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:05:48 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 077E1204AA0 for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:05:48 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id F0BBD204A7D for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:05:47 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8JA5l9I014053 for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:05:47 +0200
To: v6ops@ietf.org
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <4eb131bb-4ae7-5806-f160-f2a11c5970ab@gmail.com>
Date: Wed, 19 Sep 2018 12:05:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/31MFrHiYBrSogw4lHM1-tC2Eg8g>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 10:05:53 -0000

Thank you for this opportunity.

I added a column head called
'IPv4 and IPv6 side-by-side, or Double Stack'.

It is a way without any tunnelling, translation, routing header, 
explicit routing, DNS faking.

I have not yet filled the corresponding lines, and put 'TBD'.   Maybe later.

Alex

Le 17/09/2018 à 16:55, Lencse Gábor a écrit :
> Dear v6ops Members,
> 
> With Jordi, Lee and Richard, we have put together a table about the 
> advantages and disadvantages of the five IPv4aaS technologies (464XLAT, 
> DS-Lite, lw4o6, MAP-E, MAP-T), which can serve as a starting point for 
> collecting further information. It can be edited by anyone using the 
> following URL:
> 
> https://docs.google.com/spreadsheets/d/1W3Px8I_RyLA_tnmmNkJj6qJS0tvg93oCU0XfZzlljto/edit#gid=0
> 
> For archival purposes, I copy here its current content:
> 
> Aspect 	464XLAT 	DS-Lite 	lw4o6 	MAP-E 	MAP-T 	
> 	Key 	Meaning
> Tunnel (T) / Translation (X) ((neither pro nor con)) 	X (46, 64) 	T 
> (4in6) 	T (4in6) 	T (4in6) 	X (46, 64) 	
> 	+ 	Positive
> Can carry any protocol, not only TCP/UDP/ICMP 	- 	+ 	+ 	- 	- 	
> 	- 	Negative
> The following header fields are changed 	
> 	
> 	
> 	
> 	
> 	
> 	| 	Neutral
> - TCP/UDP source port number 	may be replaced 	may be replaced 
> restricted 	restricted 	restricted 	
> 	/ 	Not Applicable
> - IP version, source and destination addresses 	4-->6-->4 	/ 	/ 	/ 
> 4-->6-->4 	
> 	
> 	
> - fields for fragmantation
> (DF, MF, fragment offset, identification) 	discarded at
> 4-->6 translation 	/ 	/ 	/ 	discarded at
> 4-->6 translation 	
> 	
> 	
> - IP options 	discarded? 	/ 	/ 	/ 	discarded? 	
> I think it depends on the implementation if they are discarded or not
> 	
> 	
> - further fields shoud go here 	
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> port number efficiency (for ISPs) 	+ 	- 	- 	- 	- 	
> 	
> 	
> unlimited number of ports for users, when used
> for public IPv4 address sharing 	+ 	- 	- 	- 	- 	
> 	
> 	
> can keep source port numbers unmodified, when used
> without public IPv4 address sharing 	+ 	- 	- 	+ 	+ 	
> I think is is implementation dependent, at least in the case of NAT64
> 	
> 	
> Translation at ISP with or without state 	with 	with 	/ 	w/o 	w/o 	
> 	
> 	
> stateless (num. of states may not cause scalability issue) 	- 	- 	+ 	+ 	+ 	
> 	
> 	
> allows unsolicited inbound connections 	- 	
> 	
> 	+ 	+ 	
> I think is is implementation dependent, at least in the case of NAT64
> 	
> 	
> overhead (Bytes) 	20 	40 	40 	40 	20 	
> 	
> 	
> Impact in IPv6 addressing plan 	no (+) 	no (+) 	no (+) 	yes (-) 	yes (-) 	
> 	
> 	
> backbone traffic is like normal IPv6 traffic 	+, but not exactly 
> {1} 	- 	- 	- 	+, but not exactly {1} 	
> 	
> 	
> logging 	flow/block 	flow/block 	algorithmic 	algorithmic 	algorithmic 	
> 	
> 	
> Client support in Windows 10 	+ 	- 	- 	- 	- 	
> Arguably all the other columns should be marked as N/A as opposed to a 
> negative?
> 	
> 	
> Client support in Linux 	+ 	- 	- 	- 	- 	
> It does raise the question about comparing "end-host"-based methods with 
> network-based ones.
> 	
> 	
> Client support in Android 	+ 	- 	- 	- 	- 	
> Jordi: From the perspective of "how good is the support" is "-" not N/A 
> - For example, if a mechanism is not supported in cellular phones, then 
> is a bad option for an ISP to choose it!
> 	
> 	
> Client support in iOS 	- 	- 	- 	- 	- 	
> 	
> 	
> Client support in Windows Mobile 	+ 	- 	- 	- 	- 	
> 	
> 	
> Client support in Chrome OS 	+ 	- 	- 	- 	- 	
> 	
> 	
> Client support in MacOS 	- 	- 	- 	- 	- 	
> 	
> 	
> OpenWRT CPE code in kBs (lower is better) 	17 	15 	35 	35 	48 	
> 	
> 	
> DNS mangling / synthesizing 	- 	
> 	/ 	/ 	/ 	
> Jordi: This is not true. You can deploy 464XLAT with or without DNS64 
> see draft-palet-v6ops-nat64-deployment and also the 464XLAT explains it
> 	
> 	
> BR/AFTR Bypass for CDN 	
> 	/ 	/ 	/ 	+ 	
> I think this is applicable to every transition mechanism, so no need for 
> this raw as all can do it
> 	
> 	
> Support in cellular networks 	+ 	- 	- 	- 	- 	
> 	
> 	
> Danger of DNS cache poisoning 	somewhat {2} 	somewhat {2} 	high {2} 
> high {2} 	high {2} 	
> 	
> 	
> - further aspects should go here 	
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> 
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> Area for footnotes (please use numbers in braces) 	
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> {1} Both 464XLAT and MAP-T change the distribution of the port numbers, 
> thus they may break the port number rules for RTP (even number) and the 
> corresponding RTP (next odd number), see RFC 3605 Section 3.2. How much 
> important is that ? Why is not key for cellular?
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> {2} For all five technologies, CE device SHOULD contain a DNS proxy. 
> However, the user may change DNS settings. The restricted port set of 
> lw4o6, MAP-E and MAP-T makes these techologies less resilient against 
> cache poisoning, see RFC 5452.
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> 	
> 
> 
> 
> This table is surely neither complete nor error free: This is why we ask 
> your help.
> 
> As it became evident from the many mails concerning 
> draft-ietf-v6ops-transition-ipv4aas (see some of them below) that 
> neither of the above 5 technologies are better than all the others in 
> all aspects. Perhaps one if them is the best choice for a given 
> communication scenario, but another one is much better for another 
> scenario. Therefore, an Internet Draft based on a more complete version 
> of the table could server as a good selection guide for network operators.
> 
> Depending on how much and fast you will contribute, we would like to put 
> together the initial version of the draft either for IETF 103 or IETF 104.
> 
> Thank you very much for your help in advance,
> 
> Best regards,
> 
> Gábor
> 
> 
> 6/19/2018 10:29 AM keltezéssel, Richard Patterson írta:
>> Hi Lencse,
>>
>> I'd be happy to help also.
>>
>> -Richard
>> On Tue, 19 Jun 2018 at 08:09, Lencse Gábor<lencse@hit.bme.hu>  wrote:
>>> Dear Lee,
>>>
>>> Thank you very much for offering your help and participation. I have decided to write the draft and I invite you to be a co-author.
>>>
>>> Are there some other people, who would like to join us?
>>>
>>> I plan to put together a table with the information extracted from past e-mails on the list and send it to Lee (and possibly other participants) first, and send the Google docs URL to the list after we agreed on its initial content.
>>>
>>> Best regards,
>>>
>>> Gábor
>>>
>>>
>>> 6/18/2018 4:38 PM keltezéssel, Lee Howard írta:
>>>
>>> Apparently I'm a week late on this thread. Sorry.
>>>
>>> I think an internet-draft in this case would be useful for reflecting the current best knowledge about the technologies. Even if it takes two years or more to publish, a draft is useful to collect  and summarize the detailed academic papers being published, and the structure of writing the draft will help point out areas where further research is needed.
>>>
>>> I'm also interested in supporting this work, up to and including working with your students,  providing my own test results, and/or co-authoring.
>>>
>>> Lee
>>>
>>>
>>> On 06/15/2018 10:04 AM, JORDI PALET MARTINEZ wrote:
>>>
>>> I’m not sure it makes sense something that is not published in, let’s say, maximum one year from now.
>>>
>>>
>>>
>>> Anyway, I’m happy to help.
>>>
>>>
>>>
>>> By the way, I got some private questions about this … The table that I’ve posted yesterday, was developed about 3 years ago, and I’ve not updated it since them. Actually from emails exchanged today, I discovered a couple of mistakes and also things that can be improved, so if needed I can update it as well.
>>>
>>>
>>> Regards,
>>>
>>> Jordi
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> De: v6ops<v6ops-bounces@ietf.org>  en nombre de Lencse Gábor<lencse@hit.bme.hu>
>>> Fecha: viernes, 15 de junio de 2018, 14:25
>>> Para: Fred Baker<fredbaker.ietf@gmail.com>
>>> CC:<v6ops@ietf.org>
>>> Asunto: [v6ops] Pros and Cons of IPv6 Transition Technologies for IPv4aaS -- Re: no need to update RFC8026 in draft-ietf-v6ops-transition-ipv4aas
>>>
>>>
>>>
>>> Dear Fred,
>>>
>>> Thank you very much for your invitation. I am willing to accept it, but I would like to clarify your expectations before saying 'yes'.
>>>
>>> I have several questions.
>>>
>>> 1. Depth of the analysis
>>>
>>> - Basic level: well-known advantages and disadvantages, similarly as people wrote about MAP-T/E and 464XLAT, but also about DS-Lite and lw4o6.
>>> - Advanced level: basic level + security analysis using the methodology defined in [1] + performance analysis according to RFC 8219.
>>>
>>> What depth do you recommend?
>>>
>>> 2. Method for getting the results and their publication
>>>
>>> As for the information for the basic level, I would prepare a google docs table, fill in the information I have and send the link to the v6ops list asking contributions.
>>> After commenting and discussing, I would compile it to an I-D.
>>>
>>> Do you think that v6ops WG would finally agree to publish it as an RFC?
>>>
>>> As for the information for the advanced level, I would work together with my students and PhD students, and publish our results first in academic papers and then include their most important lessons into the I-D.
>>>
>>> What do you think of it?
>>>
>>> 3. Timeline
>>>
>>> I think that I could put together the first table in a few weeks. The contribution of the v6ops list members and the discussion could be done in a few months and then I could compile the results into an I-D in a few weeks. Perhaps, it could be presented at IETF 103.
>>>
>>> The further parts would require much more time and results could be included gradually in 1-2 years.
>>>
>>> 4. Scope
>>>
>>> The smallest natural scope includes the technologies for IPv4AAS, that is: 464XLAT, DS-Lite, MAP-T/E and lw4o6.
>>>
>>> IPv6 transition technologies for other carefully selected scenarios might also be included. E.g. I have significant amount of results in benchmarking DNS64 servers, having a testing tool [2], a well defined methodology [3] and ready to use results concerning the DNS64 performance of BIND, PowerDNS and Unbound [4].
>>> One of my PhD students is currently benchmarking some sateless NAT64 implementations according the the dual DUT setup of RFC 8219 using an RFC 2544 compatible Tester. Another PhD student is currently working on a RFC 8219 compliant NAT64 tester program (using DPDK) to be able to perform single DUT setup NAT64 benchmarking tests.
>>>
>>> Thus, the scope can be widened, if you would like to.
>>>
>>> What do you think about my recommendations?
>>>
>>> Best regards,
>>>
>>> Gábor
>>>
>>> References:
>>>
>>> [1] G. Lencse and Y. Kadobayashi, "Methodology for the identification of potential security issues of different IPv6 transition technologies: Threat analysis of DNS64 and stateful NAT64", Computers & Security (Elsevier), vol. 77, no. 1, pp. 397-411, August 1, 2018, DOI: 10.1016/j.cose.2018.04.012
>>>
>>> [2] G. Lencse, D. Bakai, "Design and implementation of a test program for benchmarking DNS64 servers", IEICE Transactions on Communications, vol. E100-B, no. 6. pp. 948-954, June 2017. DOI: 10.1587/transcom.2016EBN0007
>>>
>>> [3] G. Lencse, M. Georgescu, and Y. Kadobayashi, "Benchmarking Methodology for DNS64 Servers", Computer Communications (Elsevier), vol. 109, no. 1, pp. 162-175, September 1, 2017, DOI: 10.1016/j.comcom.2017.06.004
>>>
>>> [4] G. Lencse and Y. Kadobayashi, "Benchmarking DNS64 Implementations: Theory and Practice", Computer Communications (Elsevier), vol. 127, no. 1, pp. 61-74, September 1, 2018, DOI: 10.1016/j.comcom.2018.05.005
>>>
>>> 6/14/2018 10:42 PM keltezéssel, Fred Baker írta:
>>>
>>>
>>>
>>> On Jun 14, 2018, at 1:15 PM, Lencse Gábor<lencse@hit.bme.hu>  wrote:
>>>
>>> I have an idea: perhaps you could add a section about the pros and cons of each transition technology covered by the draft. (It could be helpful for the network operators when selecting the technology matching their need the best. However, I am not sure whether it is in the scope of this draft.)
>>>
>>> It would be incredibly useful. That said, it often involves value judgements, which are essentially in the eye of the beholder.
>>>
>>>
>>>
>>> We have had a recent thread regarding 464xlat and MAP-T. If I can say this without actually putting words into Lorenzo's mouth, his issues with translation in general are probably summarized in RFC 2993, and I would agree with him. The distinction between 464xlat and MAP-T you'll have to find in his emails; they are both services an ISP might deploy, and while they use the same tool (translation) they are not the same service. It seems to be generally agreed that MAP-T is more expensive to deploy than 464xlat; the question is what the extra expense buys, and whether someone agrees that the result is worth the cost.
>>>
>>>
>>>
>>> So in your proposed section, I would have to ask Jordi to not only say "MAP-T costs more to deploy than 464xlat", but gives the argument that might lead someone to choose MAP-T.
>>>
>>>
>>>
>>> And then we get to the large variety of other technologies, some of which presume an IPv4 core network and some an IPv6 core network (and none of which assume an MPLS core network carrying both kinds of traffic).
>>>
>>>
>>>
>>> If you would like to write such a document, please be my guest, by all means. But I'm not going to expect Jordi to do all that in the coming two weeks...
>>>
>>>
>>> _______________________________________________ v6ops mailing listv6ops@ietf.org  https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>>
>>> **********************************************
>>> 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 confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
>>>
>>>
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


From nobody Wed Sep 19 03:08:39 2018
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E87130ECF for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 03:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level: 
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] 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 34bsvVYwGmZf for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 03:08:35 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 48FF6130F4C for <v6ops@ietf.org>; Wed, 19 Sep 2018 03:08:35 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8JA8XZn016538 for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:08:33 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AA6A6204A20 for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:08:33 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A0811200CE2 for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:08:33 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8JA8XU9015770 for <v6ops@ietf.org>; Wed, 19 Sep 2018 12:08:33 +0200
To: v6ops@ietf.org
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org> <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org> <CAERpkxBmQOH10W2c-SumYbS84UKQapo50bKVeunpJBOBm3ci1Q@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <bde0e8dd-2657-1837-fda4-7fb4be538279@gmail.com>
Date: Wed, 19 Sep 2018 12:08:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAERpkxBmQOH10W2c-SumYbS84UKQapo50bKVeunpJBOBm3ci1Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RsHkodWsC5DYZCvKOYbSOZn74xU>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 10:08:38 -0000

Le 18/09/2018 à 17:58, Edwin Cordeiro a écrit :
> I did an analysis on some of the techniques a few years ago, not sure if 
> it would still be useful:
> http://edwin.scordeiro.net/wp-content/uploads/2016/04/ComparisonBetweenIPv4toIPv6TransitionTechniques.pdf

In that paper there is photo of skype session on transition technologies.

Is skype now working on IPv6?

Alex

> 
> In the unlikely case you speak Portuguese all the details are available at:
> http://edwin.scordeiro.net/wp-content/uploads/2016/04/Edwin_Cordeiro_Mestrado_IPT.pdf
> 
> Edwin Cordeiro
> 
> 
> On Tue, Sep 18, 2018 at 5:23 PM Lee Howard <lee@asgard.org 
> <mailto:lee@asgard.org>> wrote:
> 
> 
> 
>     On 09/17/2018 08:33 PM, Mark Andrews wrote:
>      > Requires using ISP’s recursive servers
>      >
>      > Yes, No, No, No, No
>      >
>      > We don’t yet have a NAT64 prefix discovery mechanism for 464XLAT that
>      > doesn’t use the DNS.  This is not the same as requiring DNS64.  The
>      > mapping can be in a locally served IPV4ONLY.ARPA zone (note this has
>      > all the same DNSSEC issues as DNS64 because IANA’s IPV4ONLY.ARPA zone
>      > is signed and securely delegated).
>      >
>     As I think about it, Google has public DNS64 servers that return a
>     synthesized address using the WKP 64:ff9b::/96. So you might not be
>     required to use the ISP's DNS (if the ISP uses the WKP).
>     Or, as you say, other DNS shenanigans.
> 
>     Lee
> 
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org <mailto:v6ops@ietf.org>
>     https://www.ietf.org/mailman/listinfo/v6ops
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


From nobody Wed Sep 19 06:51:38 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA411131002 for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 06:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 Krjigsn01-d3 for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 06:51:35 -0700 (PDT)
Received: from atl4mhob06.registeredsite.com (atl4mhob06.registeredsite.com [209.17.115.44]) (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 46C7F131001 for <v6ops@ietf.org>; Wed, 19 Sep 2018 06:51:35 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail01pod6.registeredsite.com [10.30.71.209]) by atl4mhob06.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8JDpVOn004513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Wed, 19 Sep 2018 09:51:31 -0400
Received: (qmail 2180 invoked by uid 0); 19 Sep 2018 13:51:31 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 19 Sep 2018 13:51:31 -0000
To: Mark Andrews <marka@isc.org>
Cc: v6ops@ietf.org
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org> <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org> <C83413C2-596D-4826-AEA3-6DC065492B45@isc.org>
From: Lee Howard <lee@asgard.org>
Message-ID: <6154499a-dc3b-7f11-193d-1b58d5222d8f@asgard.org>
Date: Wed, 19 Sep 2018 09:51:30 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <C83413C2-596D-4826-AEA3-6DC065492B45@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mH931GdCPWpI_FM7M2kgYoUU3Pg>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 13:51:37 -0000

As both you and Fred said. . .


On 09/18/2018 08:50 PM, Mark Andrews wrote:
>
>> On 19 Sep 2018, at 1:23 am, Lee Howard <lee@asgard.org> wrote:
>>
>>
>>
>> On 09/17/2018 08:33 PM, Mark Andrews wrote:
>>> Requires using ISP’s recursive servers
>>>
>>> Yes, No, No, No, No
>>>
>>> We don’t yet have a NAT64 prefix discovery mechanism for 464XLAT that
>>> doesn’t use the DNS.  This is not the same as requiring DNS64.  The
>>> mapping can be in a locally served IPV4ONLY.ARPA zone (note this has
>>> all the same DNSSEC issues as DNS64 because IANA’s IPV4ONLY.ARPA zone
>>> is signed and securely delegated).
>>>
>> As I think about it, Google has public DNS64 servers that return a synthesized address using the WKP 64:ff9b::/96. So you might not be required to use the ISP's DNS (if the ISP uses the WKP).
>> Or, as you say, other DNS shenanigans.
> Which only works if your ISP is using the WKP which requires apiary knowledge (i.e. test your ISP’s nameservers or look it up on a web page).

Absolutely true.
Except I don't know what birds have to do with it.

I'm only pointing out that there is a way out of DNS capture by the ISP, 
so it doesn't *require* ISP's recursive resolvers, except in every 
instance known in production.

Lee


From nobody Wed Sep 19 06:59:33 2018
Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49AD3130E1E for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 06:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 77bRJoFPqt3g for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 06:59:22 -0700 (PDT)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 0053C13101F for <v6ops@ietf.org>; Wed, 19 Sep 2018 06:59:21 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 7F01910AC for <v6ops@ietf.org>; Wed, 19 Sep 2018 13:59:21 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BtMIrZGLoodV for <v6ops@ietf.org>; Wed, 19 Sep 2018 08:59:21 -0500 (CDT)
Received: from mail-vk1-f198.google.com (mail-vk1-f198.google.com [209.85.221.198]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id C0279E05 for <v6ops@ietf.org>; Wed, 19 Sep 2018 08:58:46 -0500 (CDT)
Received: by mail-vk1-f198.google.com with SMTP id d189-v6so1440103vka.8 for <v6ops@ietf.org>; Wed, 19 Sep 2018 06:58:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3UWDoUu9foIDFanYpfGQkFSXmLA5awquIiDTXshmQGY=; b=i2s6JCMRZCqo4MuZcFs3o3Cuj9JSiBz60WtNFZDR/OhIbv7GyCCW0RrqQPZg9TisgN TJIuVadRrNpNUfULo3qTWoFwjduvMuHSo9JIDz8jU74E5J0noxE0eyZhk1KSC3YXck0i iDJI9j7494nHugcbz8I9siAjiZ7H3V5ZLOias4LfO1SflKk4IeAT+yeCA+BkG7Jb9QYc 1tRMX6kk6BpHKxMwzS4gPWqIQB5TRXL2Wxuydg6S1jBB8NJ/Wdw2P2diz6BeV9RD/Jvm Z1i2q16beEWLH5K/jY22eyrXW39sHMmKfoQDHoTGNhfFuHtO7ty2NPesCJNn0c9Rkp9c 6WLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3UWDoUu9foIDFanYpfGQkFSXmLA5awquIiDTXshmQGY=; b=GPYNvhAjxUviLP8DeU48DTvDHG/es3zbRUMCkYl7t9jdmB4po84uhIoI9dR7Za66r6 7BP6vAVvTPaWvXKkQ99WHRzYgG0dXH7Wp9aFkWgKZwgI9mf6x2kxBePKU0OlgXc0syGG Kp6ebs+Bo8GSGyHoIEHeTMNkvqU2EqVsJOnMdmBM9wo4xshVFRYUyBDa9v3efb+ikoJ6 Aicdrhag97UJvKme4Td2jjvz8cleW3/KfsB9imU8y0iLsTIk0kPYQFcH1cnRwVAvKAez Rnu8MRU0HV0r6vPiPJ4A6+2HncPO/Z4CMiRkngxTpL8IEpMpKWgoit1Ek84kI9VRqyuI oH5g==
X-Gm-Message-State: APzg51DWNJst+J/vvzMrg18fbqCrl1LvfiuX5z0uHjrUFd7BipbS2IcB C0abeceBMaez8NCnEJmL5OLPAXRh37IrrIbq3Ys4hS6wxbJiI5PVyK9dTLlQt5cA1fLx1m3h+2i hl5cDdqDn9/KAu1FqxZ3mYoQRtA==
X-Received: by 2002:ab0:7414:: with SMTP id r20-v6mr5315887uap.167.1537365525663;  Wed, 19 Sep 2018 06:58:45 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdYiy5yW5xLghljw6U3zlUAcV1jgixkiuC3LDZ9OidNavgVhtc5SX8eNEXnWtvqY4pN4fOZh/topCoTQg3lWbr8=
X-Received: by 2002:ab0:7414:: with SMTP id r20-v6mr5315871uap.167.1537365525271;  Wed, 19 Sep 2018 06:58:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a67:6042:0:0:0:0:0 with HTTP; Wed, 19 Sep 2018 06:58:44 -0700 (PDT)
In-Reply-To: <m1g2bCA-0000GqC@stereo.hq.phicoh.net>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <270E7E7C-D2C7-4725-939C-7B48C4558D72@jisc.ac.uk> <CAO42Z2zqivtrvcGgvS5KEJy6pquRp-m79ooBvR7ob4PBpnUP4g@mail.gmail.com> <fa723433-11da-f785-4e07-70cd5b661f05@foobar.org> <cd8c2e56-2cb7-644b-10c9-9bc7aa74b935@gmail.com> <6f23d206-5052-aadf-fb3a-9c39acd41ce7@foobar.org> <065d4d34-23a0-b8c9-83e0-e8ccf78d31c5@gmail.com> <d893d148-c087-81e4-9e83-806fdc136c9b@foobar.org> <CAO42Z2zs9AWf8D8rtYiyyKTbKRsajgS9UVferu=itUPfHcFp9A@mail.gmail.com> <m1g2O32-0000GmC@stereo.hq.phicoh.net> <d012fea0-aa37-d41c-5f30-eaf18449ae21@gmail.com> <m1g2a1R-0000GmC@stereo.hq.phicoh.net> <15B65172-138E-434B-B51A-C2CC3AF536AF@employees.org> <m1g2bCA-0000GqC@stereo.hq.phicoh.net>
From: David Farmer <farmer@umn.edu>
Date: Wed, 19 Sep 2018 08:58:44 -0500
Message-ID: <CAN-Dau0iRaBwsd1_gSm7kNJyfJErAtn+7KxExs-URFu_Epa2JQ@mail.gmail.com>
To: Philip Homburg <pch-ipv6-ietf-5@u-1.phicoh.com>
Cc: 6man WG <ipv6@ietf.org>, V6 Ops List <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000062558057639ce47"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ArIS4BQ8Crzhl_F52IkSUWpS-e8>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 13:59:25 -0000

--000000000000062558057639ce47
Content-Type: text/plain; charset="UTF-8"

On Wed, Sep 19, 2018 at 7:03 AM, Philip Homburg <pch-ipv6-ietf-5@u-1.phicoh.
com> wrote:

>
> So we can assume that to the extent that mDNS and SSDP are chatty, the host
> operating system vendor is perfectly okay with the resulting battery
> consumption. I.e. that rate already needs to be tuned for IPv4-only or
> dual stack operation. IPv6-only doesn't make it worse.
>

I think this is an interesting observation. However, I note that at least
one of the solution using mDNS does provide a mechanism to mitigate the
amount of battery power used by these functions.

https://en.wikipedia.org/wiki/Bonjour_Sleep_Proxy

I think mDNS in IPv6-only networks is an issue that should be brought to
the DNSSD working group.

Also, I note that DNSSD is already working on at least some of the issues
of service discovery in large-scale WiFi and more generally multi-segment
campus networks.

Further multicast service discovery of all types is frequently partially or
completely blocked or at least highly controlled in most large-scale WiFi
systems.

So, maybe we shouldn't take these as issues we need to solve here in 6MAN
maybe they are better solved in other WGs.

I think V6OPS should own the identification of IPv6-only problems and
issues but maybe other WGs are better-suited to actually solve them, and
maybe we should not assume they are IPv6 protocol issues to be solved in
6MAN.

I think RFC2563 is a good mitigation strategy for the immediate issues in
our IPv6-only experiments. I think we need to do more of these experiments
to find all issues, I'll bet we haven't found them all yet. :)

I'd like to suggest we not completely drop the IPv6-only flag work, at
least yet. I like us to talk with the DNSSD WG and probably DHC WG too,
maybe they will think it is the way to solve these issues or maybe they
have better solutions.

Thanks

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

--000000000000062558057639ce47
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">On Wed, Sep 19, 2018 at 7:03 AM, Philip Homburg <span dir=3D"l=
tr">&lt;<a href=3D"mailto:pch-ipv6-ietf-5@u-1.phicoh.com" target=3D"_blank"=
>pch-ipv6-ietf-5@u-1.phicoh.<wbr>com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><br>
So we can assume that to the extent that mDNS and SSDP are chatty, the host=
<br>
operating system vendor is perfectly okay with the resulting battery <br>
consumption. I.e. that rate already needs to be tuned for IPv4-only or<br>
dual stack operation. IPv6-only doesn&#39;t make it worse.<br></blockquote>=
</div><div class=3D"gmail_extra"><br></div>I think this is an interesting o=
bservation. However, I note that at least one of the solution using mDNS do=
es provide a mechanism to mitigate the amount=C2=A0of battery power used by=
 these functions.</div><div class=3D"gmail_extra"><br></div><div class=3D"g=
mail_extra"><a href=3D"https://en.wikipedia.org/wiki/Bonjour_Sleep_Proxy" t=
arget=3D"_blank">https://en.wikipedia.org/wiki/<wbr>Bonjour_Sleep_Proxy</a>=
<br clear=3D"all"><div><br></div><div>I think mDNS in IPv6-only networks is=
 an issue that should be brought to the DNSSD working group.</div><div><br>=
</div><div>Also, I note that DNSSD is already working on at least some of t=
he issues of service discovery in large-scale WiFi and more generally multi=
-segment campus networks.</div><div><br></div><div>Further multicast servic=
e discovery of all types is frequently partially=C2=A0or completely blocked=
 or at least highly controlled in most large-scale WiFi systems.</div><div>=
<br></div><div>So, maybe we shouldn&#39;t take these as issues we need to s=
olve here in 6MAN maybe they are better solved in other WGs.</div><div><br>=
</div><div>I think V6OPS should own the identification of IPv6-only problem=
s and issues but maybe other WGs are better-suited to actually solve them, =
and maybe we should not assume they are IPv6 protocol issues to be solved i=
n 6MAN.</div><div><br></div><div>I think RFC2563 is a good mitigation strat=
egy for the immediate=C2=A0issues in our IPv6-only experiments. I think we =
need to do more of these experiments to find all issues, I&#39;ll bet we ha=
ven&#39;t found them all yet. :)</div><div><br></div><div>I&#39;d like to s=
uggest we not completely=C2=A0drop the IPv6-only flag work, at least yet. I=
 like us to talk with the DNSSD WG and probably=C2=A0DHC WG too, maybe they=
 will think it is the way to solve these issues or maybe they have better s=
olutions.=C2=A0</div><div><br></div><div>Thanks</div><div><br></div>-- <br>=
<div class=3D"m_8328253295265933585gmail_signature">=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Af=
armer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &am=
p; Telecommunication Services<br>Office of Information Technology<br>Univer=
sity of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Ce=
ll: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D</div>
</div></div></div>

--000000000000062558057639ce47--


From nobody Wed Sep 19 07:19:24 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEAD131038 for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 07:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 N51e_I2XjnOh for <v6ops@ietfa.amsl.com>; Wed, 19 Sep 2018 07:19:20 -0700 (PDT)
Received: from atl4mhob20.registeredsite.com (atl4mhob20.registeredsite.com [209.17.115.114]) (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 164BB13101F for <v6ops@ietf.org>; Wed, 19 Sep 2018 07:19:19 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail01pod6.registeredsite.com [10.30.71.209]) by atl4mhob20.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8JEJGcK015276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Wed, 19 Sep 2018 10:19:16 -0400
Received: (qmail 15263 invoked by uid 0); 19 Sep 2018 14:19:16 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 19 Sep 2018 14:19:16 -0000
To: v6ops@ietf.org
References: <940CC666-9208-4784-B452-58D5482B7782@consulintel.es> <d8960bbf-ba84-e7e1-6d2b-63f973a7f33c@hit.bme.hu> <C40B15B6-4AB9-433F-94AD-A2624F359DC4@gmail.com> <6b691c03-a2ee-3656-e1bc-edbb17583216@hit.bme.hu> <1BFAD96D-F06E-4EBF-8751-761EF08E6EE0@consulintel.es> <67b5991a-e7ac-aef2-eeae-7531598428fe@asgard.org> <211c5c27-11a3-b264-3b5a-9d8f10f6ec45@hit.bme.hu> <CAHL_VyBcni90oJJTPVux5hcF+=ZUxvqs0-i=4XhvgE-KkSFU2g@mail.gmail.com> <1fd5d319-579d-ceed-c820-d43695e53a44@hit.bme.hu> <91A290C6-E187-439C-8916-E4720244A5A7@isc.org> <4ac93c8d-0919-6676-beed-8d31aacdc467@asgard.org> <CAERpkxBmQOH10W2c-SumYbS84UKQapo50bKVeunpJBOBm3ci1Q@mail.gmail.com> <bde0e8dd-2657-1837-fda4-7fb4be538279@gmail.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <39afbb58-6c8e-5dec-bd09-ceb26e87cfb8@asgard.org>
Date: Wed, 19 Sep 2018 10:19:15 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <bde0e8dd-2657-1837-fda4-7fb4be538279@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ALSYLkmFuOl26jaXCT7pVmVIRFg>
Subject: Re: [v6ops] Request for your two cents: Pros and Cons of IPv6 Transition Technologies for IPv4aaS (464XLAT, DS-Lite, lw4o6, MAP-E, MAP-T)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 14:19:23 -0000

On 09/19/2018 06:08 AM, Alexandre Petrescu wrote:
>
>
> Le 18/09/2018 à 17:58, Edwin Cordeiro a écrit :
>> I did an analysis on some of the techniques a few years ago, not sure 
>> if it would still be useful:
>> http://edwin.scordeiro.net/wp-content/uploads/2016/04/ComparisonBetweenIPv4toIPv6TransitionTechniques.pdf 
>>
>
> In that paper there is photo of skype session on transition technologies.
>
> Is skype now working on IPv6?

I started to test it (the web app, at least), but no AAAA for 
www.skype.com or web.skype.com
So, still no IPv6 support for Skype.

Lee

>
> Alex
>
>>
>> In the unlikely case you speak Portuguese all the details are 
>> available at:
>> http://edwin.scordeiro.net/wp-content/uploads/2016/04/Edwin_Cordeiro_Mestrado_IPT.pdf 
>>
>>
>> Edwin Cordeiro
>>
>>
>> On Tue, Sep 18, 2018 at 5:23 PM Lee Howard <lee@asgard.org 
>> <mailto:lee@asgard.org>> wrote:
>>
>>
>>
>>     On 09/17/2018 08:33 PM, Mark Andrews wrote:
>>      > Requires using ISP’s recursive servers
>>      >
>>      > Yes, No, No, No, No
>>      >
>>      > We don’t yet have a NAT64 prefix discovery mechanism for 
>> 464XLAT that
>>      > doesn’t use the DNS.  This is not the same as requiring 
>> DNS64.  The
>>      > mapping can be in a locally served IPV4ONLY.ARPA zone (note 
>> this has
>>      > all the same DNSSEC issues as DNS64 because IANA’s 
>> IPV4ONLY.ARPA zone
>>      > is signed and securely delegated).
>>      >
>>     As I think about it, Google has public DNS64 servers that return a
>>     synthesized address using the WKP 64:ff9b::/96. So you might not be
>>     required to use the ISP's DNS (if the ISP uses the WKP).
>>     Or, as you say, other DNS shenanigans.
>>
>>     Lee
>>
>>     _______________________________________________
>>     v6ops mailing list
>>     v6ops@ietf.org <mailto:v6ops@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/v6ops
>>
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Wed Sep 19 11:16:26 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C56BD130E84; Wed, 19 Sep 2018 11:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 q1qMOmuriZAa; Wed, 19 Sep 2018 11:16:16 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73819130E6A; Wed, 19 Sep 2018 11:16:16 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 760B1FECBC6D; Wed, 19 Sep 2018 18:16:15 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 937C4634E97; Wed, 19 Sep 2018 20:16:12 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAN-Dau0iRaBwsd1_gSm7kNJyfJErAtn+7KxExs-URFu_Epa2JQ@mail.gmail.com>
Date: Wed, 19 Sep 2018 20:16:12 +0200
Cc: Philip Homburg <pch-ipv6-ietf-5@u-1.phicoh.com>, V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <98C88286-F47E-4B02-A303-F4317A5A6482@employees.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <270E7E7C-D2C7-4725-939C-7B48C4558D72@jisc.ac.uk> <CAO42Z2zqivtrvcGgvS5KEJy6pquRp-m79ooBvR7ob4PBpnUP4g@mail.gmail.com> <fa723433-11da-f785-4e07-70cd5b661f05@foobar.org> <cd8c2e56-2cb7-644b-10c9-9bc7aa74b935@gmail.com> <6f23d206-5052-aadf-fb3a-9c39acd41ce7@foobar.org> <065d4d34-23a0-b8c9-83e0-e8ccf78d31c5@gmail.com> <d893d148-c087-81e4-9e83-806fdc136c9b@foobar.org> <CAO42Z2zs9AWf8D8rtYiyyKTbKRsajgS9UVferu=itUPfHcFp9A@mail.gmail.com> <m1g2O32-0000GmC@stereo.hq.phicoh.net> <d012fea0-aa37-d41c-5f30-eaf18449ae21@gmail.com> <m1g2a1R-0000GmC@stereo.hq.phicoh.net> <15B65172-138E-434B-B51A-C2CC3AF536AF@employees.org> <m1g2bCA-0000GqC@stereo.hq.phicoh.net> <CAN-Dau0iRaBwsd1_gSm7kNJyfJErAtn+7KxExs-URFu_Epa2JQ@mail.gmail.com>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Uj6p4hzF-0BqHStF5JhF9h5Pq8M>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 18:16:18 -0000

> I'd like to suggest we not completely drop the IPv6-only flag work, at =
least yet. I like us to talk with the DNSSD WG and probably DHC WG too, =
maybe they will think it is the way to solve these issues or maybe they =
have better solutions.=20

What=E2=80=99s the worst that can happen if we standardize this bit?

Given that it appears mostly harmless, I don=E2=80=99t see a big risk in =
standardizing it.

Ole=


From nobody Wed Sep 19 11:29:43 2018
Return-Path: <dschinazi@apple.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF57B130E6D; Wed, 19 Sep 2018 11:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 QBwHDoBfly5C; Wed, 19 Sep 2018 11:29:32 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) (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 2B25F127B92; Wed, 19 Sep 2018 11:29:32 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.22/8.16.0.22) with SMTP id w8JIR2hN048338; Wed, 19 Sep 2018 11:29:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=C3G48SZUVvb9yoMLK60q0aWSH/X2zyu2e1uqqkebqDY=; b=inogBs092gsf+VgAzcUb8OAN+AKoflkb4M2kJqiWhLVDdyb+FoLLRqdLP4WbC/NivD6E kIVIrIJ+iLqCaGArLHBWs57vVFGm2PN/rGiAH8JQbAMLXTmSOjl+sUToTU5n305ch1bL +k63u33M2nyn6SGAiB3CrZBvyu6ETjVTztEBEkTMb7z0fxC024JV+Qg0k6ZF5uN7qT12 D5I8iBcar4A4uEX3lSH5oIQks0jSUbMs0xBA4HvMomhizDgFiIsfEHp5ef9SmDhpXUwS jK0Z3UcoQdi7oEKl97EpTipBa4vZ87oAHSkt3K1J8+zE5VEaA3ql9KKAdJvzb/rgOL7p Aw== 
Received: from sng-mtap-sz01.asia.apple.com (sng-mtap-sz01.asia.apple.com [17.84.80.20]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2mk7ufqm1r-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 19 Sep 2018 11:29:29 -0700
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Received: from echium.asia.apple.com (echium.asia.apple.com [17.84.80.65]) by sng-mtap-sz01.asia.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PFB00229FD1IX00@sng-mtap-sz01.asia.apple.com>; Thu, 20 Sep 2018 02:29:25 +0800 (SGT)
Received: from process_viserion-daemon.echium.asia.apple.com by echium.asia.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PFB00300FBCCF00@echium.asia.apple.com>; Thu, 20 Sep 2018 02:29:25 +0800 (SGT)
X-Va-A: 
X-Va-T-CD: 8eba49e6cce957c9ed71045d4cee6d9a
X-Va-E-CD: c8e117a239cb4c1f86891c181b1e7532
X-Va-R-CD: 0fe506da7b22084a52375e3ccc0723e1
X-Va-CD: 0
X-Va-ID: bd066342-b050-4688-86f1-423a23085ce4
X-V-A: 
X-V-T-CD: 5ad60cfbcecc094e31500e3a3dc020d6
X-V-E-CD: c8e117a239cb4c1f86891c181b1e7532
X-V-R-CD: 0fe506da7b22084a52375e3ccc0723e1
X-V-CD: 0
X-V-ID: 575f4345-0a61-481e-b324-40ff700b9264
Received: from process_milters-daemon.echium.asia.apple.com by echium.asia.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PFB00F00D6T7K00@echium.asia.apple.com>; Thu, 20 Sep 2018 02:29:25 +0800 (SGT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-09-19_10:,, signatures=0
X-Proofpoint-Scanner-Instance: nwk-grpmailp-qapp18.corp.apple.com-10000_instance1
Received: from [17.192.155.180] by echium.asia.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PFB00DXBFCVJN20@echium.asia.apple.com>; Thu, 20 Sep 2018 02:29:23 +0800 (SGT)
Sender: dschinazi@apple.com
From: David Schinazi <dschinazi@apple.com>
In-reply-to: <98C88286-F47E-4B02-A303-F4317A5A6482@employees.org>
Date: Wed, 19 Sep 2018 11:29:19 -0700
Cc: David Farmer <farmer@umn.edu>, Philip Homburg <pch-ipv6-ietf-5@u-1.phicoh.com>, V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-transfer-encoding: quoted-printable
Message-id: <5A0F0BE1-DDDD-494C-9626-68751730ABF6@apple.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <270E7E7C-D2C7-4725-939C-7B48C4558D72@jisc.ac.uk> <CAO42Z2zqivtrvcGgvS5KEJy6pquRp-m79ooBvR7ob4PBpnUP4g@mail.gmail.com> <fa723433-11da-f785-4e07-70cd5b661f05@foobar.org> <cd8c2e56-2cb7-644b-10c9-9bc7aa74b935@gmail.com> <6f23d206-5052-aadf-fb3a-9c39acd41ce7@foobar.org> <065d4d34-23a0-b8c9-83e0-e8ccf78d31c5@gmail.com> <d893d148-c087-81e4-9e83-806fdc136c9b@foobar.org> <CAO42Z2zs9AWf8D8rtYiyyKTbKRsajgS9UVferu=itUPfHcFp9A@mail.gmail.com> <m1g2O32-0000GmC@stereo.hq.phicoh.net> <d012fea0-aa37-d41c-5f30-eaf18449ae21@gmail.com> <m1g2a1R-0000GmC@stereo.hq.phicoh.net> <15B65172-138E-434B-B51A-C2CC3AF536AF@employees.org> <m1g2bCA-0000GqC@stereo.hq.phicoh.net> <CAN-Dau0iRaBwsd1_gSm7kNJyfJErAtn+7KxExs-URFu_Epa2JQ@mail.gmail.com> <98C88286-F47E-4B02-A303-F4317A5A6482@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3445.9.1)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-19_10:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Ah_ek3_04w4zVWKzkVHtOTbZ_S4>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 18:29:34 -0000

> On Sep 19, 2018, at 11:16, Ole Troan <otroan@employees.org> wrote:
>=20
>> I'd like to suggest we not completely drop the IPv6-only flag work, =
at least yet. I like us to talk with the DNSSD WG and probably DHC WG =
too, maybe they will think it is the way to solve these issues or maybe =
they have better solutions.=20
>=20
> What=E2=80=99s the worst that can happen if we standardize this bit?
>=20
> Given that it appears mostly harmless, I don=E2=80=99t see a big risk =
in standardizing it.

This is not harmless. It costs us a bit from a limited pool, and will =
cause issues when trying to deploy the next version of IP after 6.

This problem can be solved at other layers. If the authors want to bring =
a draft to DNSSD recommending that hosts do not send mDNS over IPv4 =
link-local when there is routable IPv6 present, that would be a welcome =
discussion.

David=


From nobody Wed Sep 19 12:02:36 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA87E131072; Wed, 19 Sep 2018 12:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 j_HnSgzYDHqM; Wed, 19 Sep 2018 12:02:20 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 237801310DF; Wed, 19 Sep 2018 12:02:18 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 2F85FFECBC77; Wed, 19 Sep 2018 19:02:17 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 18D87635A3E; Wed, 19 Sep 2018 21:02:15 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <5A0F0BE1-DDDD-494C-9626-68751730ABF6@apple.com>
Date: Wed, 19 Sep 2018 21:02:14 +0200
Cc: David Farmer <farmer@umn.edu>, Philip Homburg <pch-ipv6-ietf-5@u-1.phicoh.com>, V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <112EDEC9-D5C1-41F9-AD5B-F8F6F5CBC72D@employees.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <270E7E7C-D2C7-4725-939C-7B48C4558D72@jisc.ac.uk> <CAO42Z2zqivtrvcGgvS5KEJy6pquRp-m79ooBvR7ob4PBpnUP4g@mail.gmail.com> <fa723433-11da-f785-4e07-70cd5b661f05@foobar.org> <cd8c2e56-2cb7-644b-10c9-9bc7aa74b935@gmail.com> <6f23d206-5052-aadf-fb3a-9c39acd41ce7@foobar.org> <065d4d34-23a0-b8c9-83e0-e8ccf78d31c5@gmail.com> <d893d148-c087-81e4-9e83-806fdc136c9b@foobar.org> <CAO42Z2zs9AWf8D8rtYiyyKTbKRsajgS9UVferu=itUPfHcFp9A@mail.gmail.com> <m1g2O32-0000GmC@stereo.hq.phicoh.net> <d012fea0-aa37-d41c-5f30-eaf18449ae21@gmail.com> <m1g2a1R-0000GmC@stereo.hq.phicoh.net> <15B65172-138E-434B-B51A-C2CC3AF536AF@employees.org> <m1g2bCA-0000GqC@stereo.hq.phicoh.net> <CAN-Dau0iRaBwsd1_gSm7kNJyfJErAtn+7KxExs-URFu_Epa2JQ@mail.gmail.com> <98C88286-F47E-4B02-A303-F4317A5A6482@employees.org> <5A0F0BE1-DDDD-494C-9626-68751730ABF6@apple.com>
To: David Schinazi <dschinazi@apple.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/DB-CeydWUBHEleNGy4P7Y4MSdjA>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 19:02:28 -0000

David,

>>> I'd like to suggest we not completely drop the IPv6-only flag work, =
at least yet. I like us to talk with the DNSSD WG and probably DHC WG =
too, maybe they will think it is the way to solve these issues or maybe =
they have better solutions.=20
>>=20
>> What=E2=80=99s the worst that can happen if we standardize this bit?
>>=20
>> Given that it appears mostly harmless, I don=E2=80=99t see a big risk =
in standardizing it.
>=20
> This is not harmless. It costs us a bit from a limited pool, and will =
cause issues when trying to deploy the next version of IP after 6.

We have RFC5175 so this is hardly a scarce resource.
The next version after IPv6? I certainly hope that=E2=80=99s going to be =
something a little more creative than existing within this version =
space=E2=80=A6

> This problem can be solved at other layers. If the authors want to =
bring a draft to DNSSD recommending that hosts do not send mDNS over =
IPv4 link-local when there is routable IPv6 present, that would be a =
welcome discussion.

It=E2=80=99s not quite obvious how mDNS can be repaired. Or if it=E2=80=99=
s worth the effort, over something as simple as a single flag.
Disabling IPv4 link-local has more promise. (Although it would have been =
nice to able to disable mDNS for IPv6 too.)

Cheers,
Ole



From nobody Wed Sep 19 15:51:32 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D55C130DCE; Wed, 19 Sep 2018 15:51:22 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 PKX5az-yvztY; Wed, 19 Sep 2018 15:51:20 -0700 (PDT)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (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 8F04912DD85; Wed, 19 Sep 2018 15:51:20 -0700 (PDT)
Received: by mail-pl1-x634.google.com with SMTP id 38-v6so3332692plc.10; Wed, 19 Sep 2018 15:51:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2Thzsk+BT6NAIWhgOyloQQg3RMqshOBHL7nbtWaSrh0=; b=kd1bUDPPzOPeLaTP91uvunwn3DPjOcZep63TlYCaHw7mGg/DxVRCmU4qbIYa5+HgKf 5sKeBRToMKIrZZRkT7cHGBeGz25VJuatuAveJ/Nlvi3p49pezHhcEvmD3tuKVbc1Zigh VZWabtc3iAz+Zv9L59BeUjRGLC2OfXun3z+SYqm44OY6zH3QOReYTAq0ZmsUb+BcfopN xNFShGLvsVotO2hSfx88N1ShaeLYGpwWp3Kl0QsC6oOjzCxTPqxhu9fbeH64JTSDTmby cgUjwvg/F5vFcy5xHo6XPx3LbD7IOSXio53SUFcQVkx/5bPPWqgzxSBeM1by6vYNfp4E Db8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=2Thzsk+BT6NAIWhgOyloQQg3RMqshOBHL7nbtWaSrh0=; b=JqECMm/bBVZ2eWd6Xj+eKa4FCWEZLo50MixeJ9wPC4b75NsMwEq0nGBjyRTi1TF+Ya T0oGWHVWYfVNo6hhyoitnd8sCFajNVT8YdR2NZFaMlJUHboUFOzqrDzP1xsX/BeA8+Ec xO6MPcmtWDYdpjAHZC07C6x+0it+21CJ6vCf6mgkCSwA426nk35Rlbefb3zUg0hr2kR1 SlOSfQbNmITHXuizgROBTaSfJLAF+3IlMAtGerr/DhSob1v1L1UzwPggSqe6n9Pg0Pyt t7rLGKBN/ubv8ITKxRPNEDhf9a87nI3Sf2EBDK63KGoWhHX8NXayLgIeGU5fvgkixNYF iUqg==
X-Gm-Message-State: APzg51ByQirVB+3NzYK1S+DzeSaXhDCbZ5Pc8LAnhn8Bc4P2KdrY22hz OEal0/6slrwJRpKRjLFGil3FBEl2
X-Google-Smtp-Source: ANB0VdaBN21wHPIyiwmX1hnBywgU+pQO1LkMb3Y4RI/DYP1+qg+PGGwkW7scIcOGiCOpgVyltNPyIg==
X-Received: by 2002:a17:902:b58a:: with SMTP id a10-v6mr36820807pls.306.1537397478702;  Wed, 19 Sep 2018 15:51:18 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id a16-v6sm23637857pgv.29.2018.09.19.15.51.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Sep 2018 15:51:17 -0700 (PDT)
To: Ole Troan <otroan@employees.org>, David Farmer <farmer@umn.edu>
Cc: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <270E7E7C-D2C7-4725-939C-7B48C4558D72@jisc.ac.uk> <CAO42Z2zqivtrvcGgvS5KEJy6pquRp-m79ooBvR7ob4PBpnUP4g@mail.gmail.com> <fa723433-11da-f785-4e07-70cd5b661f05@foobar.org> <cd8c2e56-2cb7-644b-10c9-9bc7aa74b935@gmail.com> <6f23d206-5052-aadf-fb3a-9c39acd41ce7@foobar.org> <065d4d34-23a0-b8c9-83e0-e8ccf78d31c5@gmail.com> <d893d148-c087-81e4-9e83-806fdc136c9b@foobar.org> <CAO42Z2zs9AWf8D8rtYiyyKTbKRsajgS9UVferu=itUPfHcFp9A@mail.gmail.com> <m1g2O32-0000GmC@stereo.hq.phicoh.net> <d012fea0-aa37-d41c-5f30-eaf18449ae21@gmail.com> <m1g2a1R-0000GmC@stereo.hq.phicoh.net> <15B65172-138E-434B-B51A-C2CC3AF536AF@employees.org> <m1g2bCA-0000GqC@stereo.hq.phicoh.net> <CAN-Dau0iRaBwsd1_gSm7kNJyfJErAtn+7KxExs-URFu_Epa2JQ@mail.gmail.com> <98C88286-F47E-4B02-A303-F4317A5A6482@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <6f552352-f0ae-af72-cf5f-11b6a58697a4@gmail.com>
Date: Thu, 20 Sep 2018 10:51:12 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <98C88286-F47E-4B02-A303-F4317A5A6482@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gHooRqNuH8jJOkK1FgkY_44rPs4>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Sep 2018 22:51:23 -0000

On 2018-09-20 06:16, Ole Troan wrote:
>> I'd like to suggest we not completely drop the IPv6-only flag work, at=
 least yet. I like us to talk with the DNSSD WG and probably DHC WG too, =
maybe they will think it is the way to solve these issues or maybe they h=
ave better solutions.=20
>=20
> What=E2=80=99s the worst that can happen if we standardize this bit?

The bit would no longer be available for future assignment, and
since it's in a one-byte field, that is significant. For example,
if we ever decided to modify the semantics of the much discussed
M and O bits, we'd only have one more reserved bit to play with.

I take that argument quite seriously, so we do need to be 100% sure
of the value of standardizing the proposal.

> Given that it appears mostly harmless, I don=E2=80=99t see a big risk i=
n standardizing it.

There are some missing security considerations in the draft,=20
specifically about the bit being used as an attack on IPv4 services,
but (unlike some other people) I think that "mostly harmless" is
accurate. So "often useful" vs "mostly useless" is the big question
for me.

   Brian


From nobody Thu Sep 20 23:32:09 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B36130DCB for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2018 23:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, 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 CpYuFzZljF4C for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2018 23:32:04 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 4F262130DF3 for <v6ops@ietf.org>; Thu, 20 Sep 2018 23:32:04 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id l16-v6so239013qtq.10 for <v6ops@ietf.org>; Thu, 20 Sep 2018 23:32:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=z9GPp8mLKVLlBzNpzKmU08h+t57TjgE5BFXE5CWyJPA=; b=eBn2WxkwIhDGzDCWLOYKX1QjV7GW+eA3F1w6JalVt0tVMiZ72gXC+WvonbMJX9QOnC B+MqVelKkqkNOrW1psfYbmTyZnkPG1ghP+/jiAyiXuZQKfrGGHhSKQBZhzNyqUtXkJun QrJizWrYxu5Ye38ZwKpOJbC2L8WN/eJuJ48ibX97TDVn6X++/7MNidjofNevzneBNhxN 3tmZsuE3bcR8EpWcLIDFb0r1BotQrYxXFfqswiMkskb3RbGULea/yAQ/KSpmBFQmKiJ+ RhHDAYfbe3fNnafQ1zm/5sR7Awwhfxg6Ag/fF07gOPeS++mfot8ewCp2NTCv5iLrjt1a AQDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=z9GPp8mLKVLlBzNpzKmU08h+t57TjgE5BFXE5CWyJPA=; b=KlidNiCph15/tKEQHm7B6n+4dFd7+7b1FduT/wQDQTPQHsSmIvEvWZSFIstOokUg6+ wg1Y8a1PgBHUGWORiiB5GeP81YwQfG9bN9r9OmrS4aJ7kQBsTaujyFNUrMlwtdnCh9uc RTxZWb9tCtWiD9Cui1pbZVIU9iG7Vvf9EQpvxC6JBGIBkBtoVaCSq9dajJ+8XOW9BiRc BsDwCLXm0tSjc6iATfn7qpCBxmITA8UBSJZcjG+9RYaLShjHY5lClp2F5a67wb/1oiSE 7sAiqSqtEu8vcG5SunV0gCo0Z7B5kAlxyOqTYO8NWuXvWwRG8SU0kPkgRyn9diH+ro1v xwSw==
X-Gm-Message-State: APzg51Cy9aV/xBa694CC/RtM8nN0FkNkbKQTEGM4N7tIUTdHlrZ+kplA q/DnQJfD4D2CaJ65iqyhXy+tDdK1DpTqEHXcaJGsew==
X-Google-Smtp-Source: ANB0VdbyM42zsmW6wYt3+IUgQzrkrjLgbZte+XD70eDbZ8CaufVnwE3Yh559p2oCP7gVJCU9jS3sfZ22io6PBt8NA2E=
X-Received: by 2002:a0c:ab15:: with SMTP id h21-v6mr30562278qvb.96.1537511523110;  Thu, 20 Sep 2018 23:32:03 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com>
In-Reply-To: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com>
From: Davey Song <songlinjian@gmail.com>
Date: Fri, 21 Sep 2018 14:31:50 +0800
Message-ID: <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com>
To: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002c583405765bcc8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0_5wPyM4bykRaKLpis0fp5QhVsk>
Subject: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Sep 2018 06:32:07 -0000

--0000000000002c583405765bcc8b
Content-Type: text/plain; charset="UTF-8"

Hi folks,

I just submited a new draft intending to provide better connectivity from
network side function . Comments are welcome.

Best regares,
Davey

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Fri, 21 Sep 2018 at 14:15
Subject: New Version Notification for
draft-v6ops-xie-network-happyeyeballs-00.txt
To: Chongfeng Xie <xiechf.bri@chinatelecom.cn>, Linjian Song <
songlinjian@gmail.com>



A new version of I-D, draft-v6ops-xie-network-happyeyeballs-00.txt
has been successfully submitted by Linjian Song and posted to the
IETF repository.

Name:           draft-v6ops-xie-network-happyeyeballs
Revision:       00
Title:          Network-side Happy Eyeballs based on accurate IPv6
measurement
Document date:  2018-09-20
Group:          Individual Submission
Pages:          9
URL:
https://www.ietf.org/internet-drafts/draft-v6ops-xie-network-happyeyeballs-00.txt
Status:
https://datatracker.ietf.org/doc/draft-v6ops-xie-network-happyeyeballs/
Htmlized:
https://tools.ietf.org/html/draft-v6ops-xie-network-happyeyeballs-00
Htmlized:
https://datatracker.ietf.org/doc/html/draft-v6ops-xie-network-happyeyeballs


Abstract:
   During the period of IPv6 transition, both ISP and ICP (Internet
   Content Provider) care about user's experience in dual-stack network.
   They hesitate to provide IPv6 to their users due to the fear of poor
   IPv6 performance.  Network-based Happy Eyeballs (NHE) is proposed in
   this memo as a approach to provide better connectivity to end users
   by doing accurate measurement and comparison on IPv6/IPv4 performance
   on the network side other than client-side Happy Eyeballs (HE)
   ([RFC8305]).  It works independently with client's adoption of HE.

   REMOVE BEFORE PUBLICATION: The source of the document with test
   script is currently placed at GitHub [NHE-GitHub].  Comments and pull
   request are welcome.




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.

The IETF Secretariat

--0000000000002c583405765bcc8b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi folks,<div>=C2=A0</div><div>I just submited a new draft=
 intending to provide better connectivity from network side function . Comm=
ents are welcome.<br></div><div><br></div><div>Best regares,</div><div>Dave=
y=C2=A0<br><br><div class=3D"gmail_quote"><div dir=3D"ltr">---------- Forwa=
rded message ---------<br>From: <span dir=3D"ltr">&lt;<a href=3D"mailto:int=
ernet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;</span><br>Date: Fri=
, 21 Sep 2018 at 14:15<br>Subject: New Version Notification for draft-v6ops=
-xie-network-happyeyeballs-00.txt<br>To: Chongfeng Xie &lt;<a href=3D"mailt=
o:xiechf.bri@chinatelecom.cn">xiechf.bri@chinatelecom.cn</a>&gt;, Linjian S=
ong &lt;<a href=3D"mailto:songlinjian@gmail.com">songlinjian@gmail.com</a>&=
gt;<br></div><br><br><br>
A new version of I-D, draft-v6ops-xie-network-happyeyeballs-00.txt<br>
has been successfully submitted by Linjian Song and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-v6ops-xie-network-happy=
eyeballs<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Network-side Happy Eyeballs based =
on accurate IPv6 measurement<br>
Document date:=C2=A0 2018-09-20<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 9<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-v6ops-xie-network-happyeyeballs-00.txt" rel=3D"nor=
eferrer" target=3D"_blank">https://www.ietf.org/internet-drafts/draft-v6ops=
-xie-network-happyeyeballs-00.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-v6ops-xie-network-happyeyeballs/" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/doc/draft-v6ops-xie-network-happye=
yeballs/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-v6ops-xie-network-happyeyeballs-00" rel=3D"noreferrer" target=3D"_bla=
nk">https://tools.ietf.org/html/draft-v6ops-xie-network-happyeyeballs-00</a=
><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-v6ops-xie-network-happyeyeballs" rel=3D"noreferrer" target=
=3D"_blank">https://datatracker.ietf.org/doc/html/draft-v6ops-xie-network-h=
appyeyeballs</a><br>
<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0During the period of IPv6 transition, both ISP and ICP (Intern=
et<br>
=C2=A0 =C2=A0Content Provider) care about user&#39;s experience in dual-sta=
ck network.<br>
=C2=A0 =C2=A0They hesitate to provide IPv6 to their users due to the fear o=
f poor<br>
=C2=A0 =C2=A0IPv6 performance.=C2=A0 Network-based Happy Eyeballs (NHE) is =
proposed in<br>
=C2=A0 =C2=A0this memo as a approach to provide better connectivity to end =
users<br>
=C2=A0 =C2=A0by doing accurate measurement and comparison on IPv6/IPv4 perf=
ormance<br>
=C2=A0 =C2=A0on the network side other than client-side Happy Eyeballs (HE)=
<br>
=C2=A0 =C2=A0([RFC8305]).=C2=A0 It works independently with client&#39;s ad=
option of HE.<br>
<br>
=C2=A0 =C2=A0REMOVE BEFORE PUBLICATION: The source of the document with tes=
t<br>
=C2=A0 =C2=A0script is currently placed at GitHub [NHE-GitHub].=C2=A0 Comme=
nts and pull<br>
=C2=A0 =C2=A0request are welcome.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div></div></div>

--0000000000002c583405765bcc8b--


From nobody Thu Sep 20 23:51:44 2018
Return-Path: <prvs=180204c826=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC4B6130DD0 for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2018 23:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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
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 fbM5PO5GnQPY for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2018 23:51:39 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2769130DFE for <v6ops@ietf.org>; Thu, 20 Sep 2018 23:51:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1537512697; x=1538117497; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type; bh=UFqMaZwd3iwZWv804KvpwOudJOMPtpm6Sx 4uTp4sg40=; b=MoC6S6hAappSMgcaUm1WS7c+s9Kf+mS6RrK2NoKaEnTnR7oUcU VM28mMS+cahonKTR7jeAtbkcKrPqoc6aAPjy8CjAXfMVe1pEwDFGAxy6F5ziiY/6 r9qCAuVdKDx15lnBrrJwTmrWt45kD1Z6LXM/y6QS/lYAdb6Y+HThF0B3A=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Fri, 21 Sep 2018 08:51:37 +0200
X-Spam-Processed: mail.consulintel.es, Fri, 21 Sep 2018 08:51:36 +0200
Received: from [10.10.10.128] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005885144.msg for <v6ops@ietf.org>; Fri, 21 Sep 2018 08:51:36 +0200
X-MDRemoteIP: 2001:470:1f09:495:8544:aaa8:c2e:a21
X-MDHelo: [10.10.10.128]
X-MDArrival-Date: Fri, 21 Sep 2018 08:51:36 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=180204c826=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Fri, 21 Sep 2018 08:51:31 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Davey Song <songlinjian@gmail.com>, <v6ops@ietf.org>
Message-ID: <C49A8009-519D-4B4B-B193-E6BED05FE5CA@consulintel.es>
Thread-Topic: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com>
In-Reply-To: <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3620364691_2075770507"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/AvWBq8yVk7IaQPlrx_WuRm6m7fM>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Sep 2018 06:51:43 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3620364691_2075770507
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Hi,

=20

I like this document.

=20

In fact, looks to me, somehow, as an alternative approach to what I was try=
ing in:

=20

https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00

=20

However, I=E2=80=99m missing some way to actually alert the ISP about the f=
ailures.

=20

If you think that this makes sense, I=E2=80=99m happy to contribute to that=
, as I was already working in an update of my document and alternatives to =
using syslog.


Regards,

Jordi

=20

=20

=20

De: v6ops <v6ops-bounces@ietf.org> en nombre de Davey Song <songlinjian@gma=
il.com>
Fecha: viernes, 21 de septiembre de 2018, 8:32
Para: <v6ops@ietf.org>
Asunto: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-h=
appyeyeballs-00.txt

=20

Hi folks,

=20

I just submited a new draft intending to provide better connectivity from n=
etwork side function . Comments are welcome.

=20

Best regares,

Davey=20

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Fri, 21 Sep 2018 at 14:15
Subject: New Version Notification for draft-v6ops-xie-network-happyeyeballs=
-00.txt
To: Chongfeng Xie <xiechf.bri@chinatelecom.cn>, Linjian Song <songlinjian@g=
mail.com>




A new version of I-D, draft-v6ops-xie-network-happyeyeballs-00.txt
has been successfully submitted by Linjian Song and posted to the
IETF repository.

Name:           draft-v6ops-xie-network-happyeyeballs
Revision:       00
Title:          Network-side Happy Eyeballs based on accurate IPv6 measurem=
ent
Document date:  2018-09-20
Group:          Individual Submission
Pages:          9
URL:            https://www.ietf.org/internet-drafts/draft-v6ops-xie-networ=
k-happyeyeballs-00.txt
Status:         https://datatracker.ietf.org/doc/draft-v6ops-xie-network-ha=
ppyeyeballs/
Htmlized:       https://tools.ietf.org/html/draft-v6ops-xie-network-happyey=
eballs-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-v6ops-xie-netwo=
rk-happyeyeballs


Abstract:
   During the period of IPv6 transition, both ISP and ICP (Internet
   Content Provider) care about user's experience in dual-stack network.
   They hesitate to provide IPv6 to their users due to the fear of poor
   IPv6 performance.  Network-based Happy Eyeballs (NHE) is proposed in
   this memo as a approach to provide better connectivity to end users
   by doing accurate measurement and comparison on IPv6/IPv4 performance
   on the network side other than client-side Happy Eyeballs (HE)
   ([RFC8305]).  It works independently with client's adoption of HE.

   REMOVE BEFORE PUBLICATION: The source of the document with test
   script is currently placed at GitHub [NHE-GitHub].  Comments and pull
   request are welcome.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________ v6ops mailing list v6ops@ie=
tf.org https://www.ietf.org/mailman/listinfo/v6ops=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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.


--B_3620364691_2075770507
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft=
 Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue vlink=
=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US=
 style=3D'mso-fareast-language:EN-US'>Hi,<o:p></o:p></span></p><p class=3DM=
soNormal><span lang=3DEN-US style=3D'mso-fareast-language:EN-US'><o:p>&nbsp=
;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fare=
ast-language:EN-US'>I like this document.<o:p></o:p></span></p><p class=3DM=
soNormal><span lang=3DEN-US style=3D'mso-fareast-language:EN-US'><o:p>&nbsp=
;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fare=
ast-language:EN-US'>In fact, looks to me, somehow, as an alternative approa=
ch to what I was trying in:<o:p></o:p></span></p><p class=3DMsoNormal><span=
 lang=3DEN-US style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-language:E=
N-US'>https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00<o:p></o=
:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-=
language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=
=3DEN-US style=3D'mso-fareast-language:EN-US'>However, I=E2=80=99m missing =
some way to actually alert the ISP about the failures.<o:p></o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-language:EN-U=
S'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US styl=
e=3D'mso-fareast-language:EN-US'>If you think that this makes sense, I=E2=
=80=99m happy to contribute to that, as I was already working in an update =
of my document and alternatives to using syslog.<o:p></o:p></span></p><div>=
<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt;color:bla=
ck'><br></span><span lang=3DES-TRAD style=3D'font-size:10.5pt;color:black'>=
Regards,<o:p></o:p></span></p><p class=3DMsoNormal style=3D'margin-bottom:1=
2.0pt'><span lang=3DES-TRAD style=3D'font-size:10.5pt;color:black;mso-farea=
st-language:EN-US'>Jordi<o:p></o:p></span></p><p class=3DMsoNormal style=3D=
'margin-bottom:12.0pt'><span lang=3DES-TRAD style=3D'font-size:10.5pt;color=
:black;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p></div><p cla=
ss=3DMsoNormal><span lang=3DES-TRAD style=3D'mso-fareast-language:EN-US'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DES-TRAD style=
=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div style=3D'b=
order:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p cla=
ss=3DMsoNormal style=3D'margin-left:35.4pt'><b><span style=3D'font-size:12.=
0pt;color:black'>De: </span></b><span style=3D'font-size:12.0pt;color:black=
'>v6ops &lt;v6ops-bounces@ietf.org&gt; en nombre de Davey Song &lt;songlinj=
ian@gmail.com&gt;<br><b>Fecha: </b>viernes, 21 de septiembre de 2018, 8:32<=
br><b>Para: </b>&lt;v6ops@ietf.org&gt;<br><b>Asunto: </b>[v6ops] Fwd: New V=
ersion Notification for draft-v6ops-xie-network-happyeyeballs-00.txt<o:p></=
o:p></span></p></div><div><p class=3DMsoNormal style=3D'margin-left:35.4pt'=
><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:=
35.4pt'>Hi folks,<o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-l=
eft:35.4pt'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'm=
argin-left:35.4pt'>I just submited a new draft intending to provide better =
connectivity from network side function . Comments are welcome.<o:p></o:p><=
/p></div><div><p class=3DMsoNormal style=3D'margin-left:35.4pt'><o:p>&nbsp;=
</o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:35.4pt'>Best=
 regares,<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>Dave=
y&nbsp;<o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'margin-left:3=
5.4pt'>---------- Forwarded message ---------<br>From: &lt;<a href=3D"mailt=
o:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;<br>Date: Fri, =
21 Sep 2018 at 14:15<br>Subject: New Version Notification for draft-v6ops-x=
ie-network-happyeyeballs-00.txt<br>To: Chongfeng Xie &lt;<a href=3D"mailto:=
xiechf.bri@chinatelecom.cn">xiechf.bri@chinatelecom.cn</a>&gt;, Linjian Son=
g &lt;<a href=3D"mailto:songlinjian@gmail.com">songlinjian@gmail.com</a>&gt=
;<o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><br><br><br>A =
new version of I-D, draft-v6ops-xie-network-happyeyeballs-00.txt<br>has bee=
n successfully submitted by Linjian Song and posted to the<br>IETF reposito=
ry.<br><br>Name:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;draft-v6ops-xie-ne=
twork-happyeyeballs<br>Revision:&nbsp; &nbsp; &nbsp; &nbsp;00<br>Title:&nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; Network-side Happy Eyeballs based on accurat=
e IPv6 measurement<br>Document date:&nbsp; 2018-09-20<br>Group:&nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; Individual Submission<br>Pages:&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; 9<br>URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href=3D=
"https://www.ietf.org/internet-drafts/draft-v6ops-xie-network-happyeyeballs=
-00.txt" target=3D"_blank">https://www.ietf.org/internet-drafts/draft-v6ops=
-xie-network-happyeyeballs-00.txt</a><br>Status:&nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;<a href=3D"https://datatracker.ietf.org/doc/draft-v6ops-xie-network-=
happyeyeballs/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-v6=
ops-xie-network-happyeyeballs/</a><br>Htmlized:&nbsp; &nbsp; &nbsp; &nbsp;<=
a href=3D"https://tools.ietf.org/html/draft-v6ops-xie-network-happyeyeballs=
-00" target=3D"_blank">https://tools.ietf.org/html/draft-v6ops-xie-network-=
happyeyeballs-00</a><br>Htmlized:&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"http=
s://datatracker.ietf.org/doc/html/draft-v6ops-xie-network-happyeyeballs" ta=
rget=3D"_blank">https://datatracker.ietf.org/doc/html/draft-v6ops-xie-netwo=
rk-happyeyeballs</a><br><br><br>Abstract:<br>&nbsp; &nbsp;During the period=
 of IPv6 transition, both ISP and ICP (Internet<br>&nbsp; &nbsp;Content Pro=
vider) care about user's experience in dual-stack network.<br>&nbsp; &nbsp;=
They hesitate to provide IPv6 to their users due to the fear of poor<br>&nb=
sp; &nbsp;IPv6 performance.&nbsp; Network-based Happy Eyeballs (NHE) is pro=
posed in<br>&nbsp; &nbsp;this memo as a approach to provide better connecti=
vity to end users<br>&nbsp; &nbsp;by doing accurate measurement and compari=
son on IPv6/IPv4 performance<br>&nbsp; &nbsp;on the network side other than=
 client-side Happy Eyeballs (HE)<br>&nbsp; &nbsp;([RFC8305]).&nbsp; It work=
s independently with client's adoption of HE.<br><br>&nbsp; &nbsp;REMOVE BE=
FORE PUBLICATION: The source of the document with test<br>&nbsp; &nbsp;scri=
pt is currently placed at GitHub [NHE-GitHub].&nbsp; Comments and pull<br>&=
nbsp; &nbsp;request are welcome.<br><br><br><br><br>Please note that it may=
 take a couple of minutes from the time of submission<br>until the htmlized=
 version and diff are available at <a href=3D"http://tools.ietf.org" target=
=3D"_blank">tools.ietf.org</a>.<br><br>The IETF Secretariat<o:p></o:p></p><=
/div></div></div><p class=3DMsoNormal style=3D'margin-left:35.4pt'>________=
_______________________________________ v6ops mailing list v6ops@ietf.org h=
ttps://www.ietf.org/mailman/listinfo/v6ops <o:p></o:p></p></div><br>*******=
***************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.consulintel.es<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.<br>
<br>
</body></html>

--B_3620364691_2075770507--


From nobody Fri Sep 21 06:45:43 2018
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AAF1130DE3; Fri, 21 Sep 2018 06:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 vfgMZQyGQXXe; Fri, 21 Sep 2018 06:45:37 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DC9E129385; Fri, 21 Sep 2018 06:45:37 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 42GvxW4cZ3z20gM; Fri, 21 Sep 2018 15:45:35 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.33]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 42GvxW3FG5zDq75; Fri, 21 Sep 2018 15:45:35 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM42.corporate.adroot.infra.ftgroup ([fe80::d5fd:9c7d:2ee3:39d9%19]) with mapi id 14.03.0415.000; Fri, 21 Sep 2018 15:45:34 +0200
From: <mohamed.boucadair@orange.com>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, "Ole Troan" <otroan@employees.org>, Fred Baker <fredbaker.ietf@gmail.com>
CC: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Thread-Topic: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
Thread-Index: AQHUTHCB40h3tFL8rkiX3hojU6migaT6x8Cw
Date: Fri, 21 Sep 2018 13:45:34 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DFE4E1B@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com> <D2A66229-94AA-4267-9C19-60A3979F646F@employees.org> <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es>
In-Reply-To: <1BCD3EA0-C94A-48C5-8762-2C948BD36AE0@consulintel.es>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/FsAKenl9KDP_hphaFlLAY1q9MYo>
Subject: Re: [v6ops] NAT64 prefix configuration (was: Re: ipv6only-flag-02 security)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Sep 2018 13:45:40 -0000

SGkgSm9yZGksIA0KDQpObyBzdXJlIHRvIHVuZGVyc3RhbmQgeW91ciBjb21tZW50LiANCg0KQXQg
bGVhc3QsIGZyb20gYW4gaW1wbGVtZW50YXRpb24gc3RhbmRhcmQsIG1vZGVybiBDR05zIGFuZCBO
QVQ2NCBhcmUgZm9sbG93aW5nIHRoZSBzYW1lIHJlY29tbWVuZGF0aW9ucyBmcm9tIHRoZSBJRVRG
LiBGb3IgZXhhbXBsZSwgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzc4NTcgaW5zcGly
ZXMgZnJvbSBOQVQ2NCAoZS5nLiwgVENQIHN0YXRlIG1hY2hpbmUpLiANCg0KVGhlIGFkZHJlc3Mg
c2hhcmluZyByYXRpbyAoYW5kIHBvcnRzIHRvIGJlIGFzc2lnbmVkIHBlciBkZXZpY2UvY3VzdG9t
ZXIpIGlzIGRlcGxveW1lbnQtc3BlY2lmaWMuICAgDQoNCkNoZWVycywNCk1lZA0KDQo+IC0tLS0t
TWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0KPiBEZcKgOiB2Nm9wcyBbbWFpbHRvOnY2b3BzLWJvdW5j
ZXNAaWV0Zi5vcmddIERlIGxhIHBhcnQgZGUgSk9SREkgUEFMRVQgTUFSVElORVoNCj4gRW52b3nD
qcKgOiB2ZW5kcmVkaSAxNCBzZXB0ZW1icmUgMjAxOCAyMzoxOA0KPiDDgMKgOiBPbGUgVHJvYW47
IEZyZWQgQmFrZXINCj4gQ2PCoDogVjYgT3BzIExpc3Q7IDZtYW4gV0cNCj4gT2JqZXTCoDogUmU6
IFt2Nm9wc10gTkFUNjQgcHJlZml4IGNvbmZpZ3VyYXRpb24gKHdhczogUmU6IGlwdjZvbmx5LWZs
YWctMDINCj4gc2VjdXJpdHkpDQo+IA0KPiBIaSBPbGUsDQo+IA0KPiBJIGRvbid0IHRoaW5rIHlv
dSBjYW4gY29tcGFyZSBDR04gd2l0aCBOQVQ2NC4NCj4gDQo+IE5BVDY0IGlzIGRvaW5nIGEgbXVj
aCBiZXR0ZXIgYW5kIGR5bmFtaWMgKG9uIGRlbWFuZCkgdXNhZ2Ugb2YgdGhlIHBvcnQgb2YgdGhl
DQo+IElQdjQgYWRkcmVzcyBwb29sLiBTbywgaXQgc2NhbGVzIG11Y2ggbW9yZSB0aGFuIENHTi4g
QXMgYSBjb25zZXF1ZW5jZSwgYW4gSVNQDQo+IG5lZWQgbXVjaCBsZXNzIElQdjQgYWRkcmVzc2Vz
IGZvciB0aGUgc2FtZSBudW1iZXIgb2YgY3VzdG9tZXJzIHdpdGggTkFUNjQNCj4gdGhhbiBDR04s
IGFuZCB5b3UgZG9uJ3QgaGF2ZSBtYW55IG9mIHRoZSBwcm9ibGVtcyB0aGF0IENHTiBwb3NlcyBi
ZWNhdXNlIHRoZQ0KPiByZXN0cmljdGlvbnMgaW4gdGhlIG51bWJlciBvZiBwb3J0cy4NCj4gDQo+
IFJlZ2FyZHMsDQo+IEpvcmRpDQo+IA0KPiANCj4gDQo+IO+7vy0tLS0tTWVuc2FqZSBvcmlnaW5h
bC0tLS0tDQo+IERlOiBpcHY2IDxpcHY2LWJvdW5jZXNAaWV0Zi5vcmc+IGVuIG5vbWJyZSBkZSBP
bGUgVHJvYW4NCj4gPG90cm9hbkBlbXBsb3llZXMub3JnPg0KPiBGZWNoYTogdmllcm5lcywgMTQg
ZGUgc2VwdGllbWJyZSBkZSAyMDE4LCAyMjoxMw0KPiBQYXJhOiBGcmVkIEJha2VyIDxmcmVkYmFr
ZXIuaWV0ZkBnbWFpbC5jb20+DQo+IENDOiBWNiBPcHMgTGlzdCA8djZvcHNAaWV0Zi5vcmc+LCA2
bWFuIFdHIDxpcHY2QGlldGYub3JnPg0KPiBBc3VudG86IE5BVDY0IHByZWZpeCBjb25maWd1cmF0
aW9uICh3YXM6IFJlOiBbdjZvcHNdIGlwdjZvbmx5LWZsYWctMDINCj4gc2VjdXJpdHkpDQo+IA0K
PiAgICAgRnJlZCwNCj4gDQo+ICAgICBEaWQgeW91IHBvc3QgdGhpcyBvbiB0aGUgd3JvbmcgdGhy
ZWFkPyBJIGFtIG5vdCBzdXJlIGhvdyB0aGlzIHJlbGF0ZXMgdG8NCj4gdGhlIGlwNm9ubHktZmxh
ZyBkcmFmdC4NCj4gICAgIENoYW5nZWQgc3ViamVjdC4NCj4gDQo+ICAgICA+IFNwZWFraW5nIHN0
cmljdGx5IGZvciBteXNlbGYsIGFsbCBvbmUgb2YgbWUuIEhvd2V2ZXIsIEknbSBjb3B5aW5nIHY2
b3BzDQo+IGluIGNhc2Ugc29tZW9uZSBvcGVyYXRpb25hbCB3aWxsIGRpc3B1dGUgbXkgdmlld3Bv
aW50IG9yIHN1cHBvcnQgaXQuDQo+ICAgICA+DQo+ICAgICA+IEkgd291bGQgZXhwZWN0IHRoYXQg
aWYgYW4gSVNQIGlzIG9mZmVyaW5nIG9ubHkgSVB2NiB0byB0aGUgQ1BFLCB0aGUgQ1BFDQo+IG1p
Z2h0IHdlbGwgaW1wbGVtZW50IGJvdGggYW4gSVB2NiByb3V0ZXIgYW5kIGEgNDY0WExBVCBDTEFU
IGZvciBJUHY0IHdpdGhpbg0KPiB0aGUgTEFOLiBUaGUgSVNQIHdpbGwgbmV2ZXIga25vdyB3aGV0
aGVyIHRoZXJlIGlzIGFjdHVhbCBJUHY0IGluIHRoZQ0KPiBob21lL1NPSE8vRW50ZXJwcmlzZSwg
b3RoZXIgdGhhbiB0aGF0IHRoZSBQTEFUIGl0IHByZXN1bWFibHkgaW1wbGVtZW50cyB3aWxsDQo+
IHNlZSB0cmFmZmljLiBJZiBpdCdzIGRvaW5nIENHTiwgTUFQLUUsIG9yIE1BUC1ULCBpdCBpcyBp
bXBsZW1lbnRpbmcgdGhlDQo+IG92ZXJsYXksIHdpbGwgYmUgYXdhcmUgb2YgaXQsIGFuZCB3aWxs
IGJlIHBheWluZyBmb3IgaXQ7IHRoZSA0NjRYTEFUIG1vZGVsDQo+IG1lYW5zIHRoYXQgaXQgZG9l
c24ndCBoYXZlIHRvIHRoaW5rIGFib3V0IGl0IChvciBwYXkgZm9yIGl0KSBiZXlvbmQgdGhlIFBM
QVQNCj4gYW5kIGl0cyBwcmVmaXguIEknbSBoZWFyaW5nIHJ1bWJsaW5ncyBmcm9tIHZhcmlvdXMg
b3BlcmF0b3JzIHRvIHRoZSBlZmZlY3QNCj4gdGhhdCBJUHY0IGlzIGJlY29taW5nIG9wZXJhdGlv
bmFsbHkgZXhwZW5zaXZlIC0gb25lIHRoYXQgaGFzIGJlZW4gaW4gdGhlIG5ld3MNCj4gcmVjZW50
bHkgd2FzIEF1c3NpZSBCcm9hZGJhbmQsIGJ1dCB0aGV5IGFyZSBpbiBubyBzZW5zZSB0aGUgb25s
eSBzb3VyY2Ugb2YNCj4gc3VjaCBydW1ibGluZ3MuDQo+IA0KPiAgICAgU3BlYWtpbmcgYXMgb25l
IG9mIHRoZSBlZGl0b3JzIG9mIHRoZSBNQVAgc2VyaWVzIGRvY3VtZW50cywgdGhhdOKAmXMgYQ0K
PiBtaXNyZXByZXNlbnRhdGlvbi4NCj4gICAgIFBMQVQgPSBzdGF0ZWZ1bCBOQVQ2NCBoYXMgc2lt
aWxhciBjb3N0cyBhbmQgc2NhbGluZyBwcm9wZXJ0aWVzIGFzIGEgQ0dOLg0KPiBUaGF0IGlzLCBz
aWduaWZpY2FudGx5IHdvcnNlIHRoYW4gc3RhdGVsZXNzIHNvbHV0aW9ucy4NCj4gDQo+ICAgICA+
IEZyb20gbXkgcGVyc3BlY3RpdmUsIDQ2NFhMQVQgcGx1cyBkcmFmdC1wcmVmNjRmb2xrcy02bWFu
LXJhLXByZWY2NCBpcw0KPiB0aGUgYmVzdCBjYXNlIGN1cnJlbnRseSBvbiB0aGUgdGFibGUuIElm
IDZtYW4gYWdyZWVzLCBJIHdvdWxkIHN1Z2dlc3QgdXNpbmcNCj4gZHJhZnQtcHJlZjY0Zm9sa3Mt
Nm1hbi1yYS1wcmVmNjQgYXQgUFMgdG8gZGVwcmVjYXRlIChtYWtlIGhpc3RvcmljL05PVA0KPiBS
RUNPTU1FTkRFRCkgUkZDcyA2MTQ3IGFuZCA3MDUwLiBJbiB0aGF0LCB0aGVyZSB3b3VsZCBiZSB2
YWx1ZSBpbiBhIHBsdWdmZXN0LA0KPiBwZXJoYXBzIGF0IElFVEYgMTAzIG9yIDEwNCBkdXJpbmcg
dGhlIEhhY2thdGhvbiwgdG8gbGV0IHZhcmlvdXMgaW1wbGVtZW50b3JzDQo+IGRlbW9uc3RyYXRl
IGRyYWZ0LWlldGYtdjZvcHMtdHJhbnNpdGlvbi1pcHY0YWFzIHVzaW5nIDQ2NFhMQVQrZHJhZnQt
DQo+IHByZWY2NGZvbGtzLTZtYW4tcmEtcHJlZjY0IGFuZCBzdGF0ZSB0aGVpciByb2xsLW91dCBw
bGFucy4NCj4gDQo+ICAgICBJIGRvbuKAmXQga25vdyBpZiA2bWFuIGhhcyBhIHBhcnRpY3VsYXIg
dmlldyBvbiBwcm92aXNpb2luaW5nIG9mIGEgTkFUNjQNCj4gcHJlZml4ZXMuIE5vciBkbyBJIGtu
b3cgaWYgd2Ugc2hvdWxkLg0KPiANCj4gICAgIElmIHlvdSBtZW50aW9uZWQgdGhlIGlwdjZvbmx5
LWZsYWcgZHJhZnQgaW4gdGhlIGNvbnRleHQgNDY0WExBVC4gNDY0WExBVA0KPiBvZmZlcnMgYSBu
YXRpdmUgZHVhbC1zdGFjayBzZXJ2aWNlLCBhbmQgdGhhdOKAmXMgbm90IHdoYXQgdGhlIGlwdjZv
bmx5LWZsYWcNCj4gZHJhZnQgaXMgYWJvdXQuDQo+ICAgICBUaGF04oCZcyBhYm91dCB0cnVlIElQ
djYgb25seSBsaW5rcywgd2hlcmUgdGhlcmUgaXMgbm8gSVB2NCBwYWNrZXRzIG9uIHRoZQ0KPiBs
aW5rLg0KPiANCj4gICAgIE9sZQ0KPiAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gICAgIElFVEYgSVB2NiB3
b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdA0KPiAgICAgaXB2NkBpZXRmLm9yZw0KPiAgICAgQWRt
aW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vaXB2Ng0KPiAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gDQo+IA0KPiANCj4gDQo+ICoqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gSVB2NCBpcyBvdmVyDQo+IEFy
ZSB5b3UgcmVhZHkgZm9yIHRoZSBuZXcgSW50ZXJuZXQgPw0KPiBodHRwOi8vd3d3LmNvbnN1bGlu
dGVsLmVzDQo+IFRoZSBJUHY2IENvbXBhbnkNCj4gDQo+IFRoaXMgZWxlY3Ryb25pYyBtZXNzYWdl
IGNvbnRhaW5zIGluZm9ybWF0aW9uIHdoaWNoIG1heSBiZSBwcml2aWxlZ2VkIG9yDQo+IGNvbmZp
ZGVudGlhbC4gVGhlIGluZm9ybWF0aW9uIGlzIGludGVuZGVkIHRvIGJlIGZvciB0aGUgZXhjbHVz
aXZlIHVzZSBvZiB0aGUNCj4gaW5kaXZpZHVhbChzKSBuYW1lZCBhYm92ZSBhbmQgZnVydGhlciBu
b24tZXhwbGljaWx0eSBhdXRob3JpemVkIGRpc2Nsb3N1cmUsDQo+IGNvcHlpbmcsIGRpc3RyaWJ1
dGlvbiBvciB1c2Ugb2YgdGhlIGNvbnRlbnRzIG9mIHRoaXMgaW5mb3JtYXRpb24sIGV2ZW4gaWYN
Cj4gcGFydGlhbGx5LCBpbmNsdWRpbmcgYXR0YWNoZWQgZmlsZXMsIGlzIHN0cmljdGx5IHByb2hp
Yml0ZWQgYW5kIHdpbGwgYmUNCj4gY29uc2lkZXJlZCBhIGNyaW1pbmFsIG9mZmVuc2UuIElmIHlv
dSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgYmUgYXdhcmUNCj4gdGhhdCBhbnkgZGlz
Y2xvc3VyZSwgY29weWluZywgZGlzdHJpYnV0aW9uIG9yIHVzZSBvZiB0aGUgY29udGVudHMgb2Yg
dGhpcw0KPiBpbmZvcm1hdGlvbiwgZXZlbiBpZiBwYXJ0aWFsbHksIGluY2x1ZGluZyBhdHRhY2hl
ZCBmaWxlcywgaXMgc3RyaWN0bHkNCj4gcHJvaGliaXRlZCwgd2lsbCBiZSBjb25zaWRlcmVkIGEg
Y3JpbWluYWwgb2ZmZW5zZSwgc28geW91IG11c3QgcmVwbHkgdG8gdGhlDQo+IG9yaWdpbmFsIHNl
bmRlciB0byBpbmZvcm0gYWJvdXQgdGhpcyBjb21tdW5pY2F0aW9uIGFuZCBkZWxldGUgaXQuDQo+
IA0KPiANCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+IHY2b3BzIG1haWxpbmcgbGlzdA0KPiB2Nm9wc0BpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2b3BzDQo=


From nobody Fri Sep 21 06:55:10 2018
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCB2130DC0; Fri, 21 Sep 2018 06:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] 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 4IiDHCv_mCw8; Fri, 21 Sep 2018 06:55:01 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF9B412F1A6; Fri, 21 Sep 2018 06:55:00 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 42Gw8M29rXz11jh; Fri, 21 Sep 2018 15:54:59 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.21]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 42Gw8M1Bf3z1xnt; Fri, 21 Sep 2018 15:54:59 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6C.corporate.adroot.infra.ftgroup ([fe80::d9f5:9741:7525:a199%18]) with mapi id 14.03.0415.000; Fri, 21 Sep 2018 15:54:58 +0200
From: <mohamed.boucadair@orange.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
CC: V6 Ops List <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Thread-Topic: ipv6only-flag-02 security
Thread-Index: AQHUS6j72QJPtFUIk0+tObomef7UvqT6zPAQ
Date: Fri, 21 Sep 2018 13:54:58 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DFE4E59@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <2D09D61DDFA73D4C884805CC7865E6114DEA863A@GAALPA1MSGUSRBF.ITServices.sbc.com> <19297.1536689674@localhost> <69D95A4A-3C25-4987-B3E8-7203CEA48017@employees.org> <c357daaf-6d3e-c0d0-c0b5-4fea421dbb30@moth.iki.fi> <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com>
In-Reply-To: <602A5DC3-7B86-4C55-8660-B1D7443218EA@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3L3Xjz82TjUml2gom6xlv8j1oVo>
Subject: Re: [v6ops] ipv6only-flag-02 security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Sep 2018 13:55:08 -0000

Hi Fred,=20

If the goal is to show 464xlat without 6147/7050, draft-ietf-v6ops-transiti=
on-ipv4aas provides only how to do that without requiring to modify access =
routers:

=3D=3D=3D
   464XLAT-6:  [RFC8115] MUST be implemented and a DHCPv6 Option
               "OPTION_V6_PREFIX64" ([RFC8115]), with zeroed
               ASM_mPrefix64 and SSM_mPrefix64, MUST also be considered
               as a valid NAT64 prefix (uPrefix64).

   464XLAT-7:  The priority for the NAT64 prefix, in case the network
               provides several choices, MUST be: 1) [RFC7225], 2)
               [RFC8115], and 3) [RFC7050].
=3D=3D=3D

Cheers,
Med

> -----Message d'origine-----
> De=A0: ipv6 [mailto:ipv6-bounces@ietf.org] De la part de Fred Baker
> Envoy=E9=A0: jeudi 13 septembre 2018 23:30
> =C0=A0: Markku Savela
> Cc=A0: V6 Ops List; 6man WG
> Objet=A0: Re: ipv6only-flag-02 security
>=20
> Speaking strictly for myself, all one of me. However, I'm copying v6ops i=
n
> case someone operational will dispute my viewpoint or support it.
>=20
> I would expect that if an ISP is offering only IPv6 to the CPE, the CPE m=
ight
> well implement both an IPv6 router and a 464XLAT CLAT for IPv4 within the
> LAN. The ISP will never know whether there is actual IPv4 in the
> home/SOHO/Enterprise, other than that the PLAT it presumably implements w=
ill
> see traffic. If it's doing CGN, MAP-E, or MAP-T, it is implementing the
> overlay, will be aware of it, and will be paying for it; the 464XLAT mode=
l
> means that it doesn't have to think about it (or pay for it) beyond the P=
LAT
> and its prefix. I'm hearing rumblings from various operators to the effec=
t
> that IPv4 is becoming operationally expensive - one that has been in the =
news
> recently was Aussie Broadband, but they are in no sense the only source o=
f
> such rumblings.
>=20
> From my perspective, 464XLAT plus draft-pref64folks-6man-ra-pref64 is the
> best case currently on the table. If 6man agrees, I would suggest using
> draft-pref64folks-6man-ra-pref64 at PS to deprecate (make historic/NOT
> RECOMMENDED) RFCs 6147 and 7050. In that, there would be value in a plugf=
est,
> perhaps at IETF 103 or 104 during the Hackathon, to let various implement=
ors
> demonstrate draft-ietf-v6ops-transition-ipv4aas using 464XLAT+draft-
> pref64folks-6man-ra-pref64 and state their roll-out plans.
>=20
> I find myself thinking about https://www.youtube.com/watch?v=3D_y36fG2Oba=
0.
> Yes, I think a day something like that is coming. First they ignore you; =
then
> they laugh at you, ...
>=20
> > On Sep 12, 2018, at 2:31 AM, Markku Savela <msa@moth.iki.fi> wrote:
> >
> > On 12/09/18 12:08, Ole Troan wrote:
> >>>> If there is a DHCPv4 response, then the host SHOULD NOT shut down IP=
v4
> >>>> operations. The RA flag is incorrectly configured.  Barbara
> >>> I don't agree.  If all the RAs have ipv6-only set, and there is still
> DHCPv4,
> >>> I'd conclude that the IPv4 is fake.
> >> Agree. From my perspective the whole point of this flag is to signal
> configuration information to hosts.
> >> A compliant host receiving this flag, should disable all IPv4 processi=
ng
> on the relevant interface.
> >
> > And if I have a home/site network
> >
> > - connected to ISP offering IPv6 only,
> >
> > - and internally using additional IPv4 addresses via local DHCP server =
(or
> via another ISP connection offering IPv4) to support locally IPv4 only le=
gacy
> devices (printers, etc.).
> >
> > As home/small site user (*), I may not have ANY control on RA's sent by=
 the
> first ISP. If they were to set this ipv6-only flag and, if this would dis=
able
> my IPv4 addressing, I would be a bit pissed off...
> >
> > (*) though, if ISP provided "home router" is configurable, and the ipv6=
-
> only flag in RA would be controllable by home user. Then maybe acceptable=
...
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>=20
> -------------------------------------------------------------------------=
----
> ---
> Victorious warriors win first and then go to war,
> Defeated warriors go to war first and then seek to win.
>      Sun Tzu


From nobody Sat Sep 22 00:26:27 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5D3130DCB for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 00:26:25 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-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 Yf8vgOP9TUpl for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 00:26:23 -0700 (PDT)
Received: from mail-qt1-x842.google.com (mail-qt1-x842.google.com [IPv6:2607:f8b0:4864:20::842]) (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 C9607128CF2 for <v6ops@ietf.org>; Sat, 22 Sep 2018 00:26:22 -0700 (PDT)
Received: by mail-qt1-x842.google.com with SMTP id z13-v6so4035647qts.5 for <v6ops@ietf.org>; Sat, 22 Sep 2018 00:26:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zZbE+fZRIWpiX1yDC1Oo9srVa4knBGG7xnhSVnWlYJA=; b=RexmHixtszlxovenN90uOouNhIE5yrOX5e8nod9ryZQu99+H8hG3zdpAFhW8827Vgz 1HAcjxXRARY3mhQqFtHaG1z399AnXhuJDruRgnI3ZOVMgTVCrpmz/EZv6+8mFRXJ25vG z4WZAJienMIc2oQM5KJlMN+HkP/qQm/xW7YLPuIRmCakJtsr6Lgzt+YRwurwF7p2NEFH wJy4KLurZ05vveZX9ZxOJu1hWkVB2hRpCoNU/aYv7LDUKlzq+2vv0rAD4RT2izsMitvW v2jjo6qCYxULn2qpPbpX7KMcJerEX5hYAwc8ovuaBEKOYK+PjzufwZbfB83DI+Nh8RvS D4Uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zZbE+fZRIWpiX1yDC1Oo9srVa4knBGG7xnhSVnWlYJA=; b=uaSxgYYPD17y9nEz/OoAY/a+2NtaXHmklg1s/nvSNjoozu35p9h1eLwo8L8rg6i3fj uZBGtIXOcX3TZ25GtEPy4ZJ3tf7oYo89W5QSS91PsaMKOJCchvpfgNZl2cjU8d1J9vrI V0uGwileYeS9re52wkk/iB26s+E0nvy8/Tv4QgVEtlW9Td9ZS04M066Bsmr+6crJts50 hUpiqDrA+brfPUwtR70J0Wi7p6c8G+x+qPmkNhWSVfAaQMncLp+vXS3G7r5UWNNl9Bdl gIbJNar9nwv5X1TYUomEMMM04DTvMav3/Fa4tEieggGIp/Px8l7EbwdVmcoE6dQOOt1O bSvA==
X-Gm-Message-State: APzg51Ctrl2rY5gxizSRUo5h/0ix0iz1Znk41WtQ43LU9LoQJPwh1a3H pfcQzzVOZXezJ39LQc0F7roRKcnUxo6W9ZHh1lff6Hfj
X-Google-Smtp-Source: ANB0Vdbsr/RWM8s2K/KvfnKCvUrcBp3gZJLAflVBaLO8fqxnnuyJfshx34asAMA2ScZRjQwPES4qS+aPq0eV8qguhKw=
X-Received: by 2002:ac8:6056:: with SMTP id k22-v6mr801098qtm.94.1537601181940;  Sat, 22 Sep 2018 00:26:21 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <C49A8009-519D-4B4B-B193-E6BED05FE5CA@consulintel.es>
In-Reply-To: <C49A8009-519D-4B4B-B193-E6BED05FE5CA@consulintel.es>
From: Davey Song <songlinjian@gmail.com>
Date: Sat, 22 Sep 2018 15:26:01 +0800
Message-ID: <CAAObRXJNsmbp9AAwz8UVyZaCojXMV=6_7XCZpADVmeW-6N81ow@mail.gmail.com>
To: jordi.palet@consulintel.es
Cc: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000418127057670ac7e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/e30eG-CUce7JJRAnEcFwaTEFvWo>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 22 Sep 2018 07:26:26 -0000

--000000000000418127057670ac7e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Jordi,

Thanks for your support. I read your draft. I think we target different
problems. NHE can avoid the operational issues but it is not the main
purpose. If you would like to improve NHE to do better performance
measurement or other extension, the authors are open for suggestions.

Btw, it is the vacation of Mid-Autumn day in China. Wish you all Happy
Mid-Autumn day : )

Best regards,
Davey

On Fri, 21 Sep 2018 at 14:51, JORDI PALET MARTINEZ <
jordi.palet@consulintel.es> wrote:

> Hi,
>
>
>
> I like this document.
>
>
>
> In fact, looks to me, somehow, as an alternative approach to what I was
> trying in:
>
>
>
> https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00
>
>
>
> However, I=E2=80=99m missing some way to actually alert the ISP about the=
 failures.
>
>
>
> If you think that this makes sense, I=E2=80=99m happy to contribute to th=
at, as I
> was already working in an update of my document and alternatives to using
> syslog.
>
>
> Regards,
>
> Jordi
>
>
>
>
>
>
>
> *De: *v6ops <v6ops-bounces@ietf.org> en nombre de Davey Song <
> songlinjian@gmail.com>
> *Fecha: *viernes, 21 de septiembre de 2018, 8:32
> *Para: *<v6ops@ietf.org>
> *Asunto: *[v6ops] Fwd: New Version Notification for
> draft-v6ops-xie-network-happyeyeballs-00.txt
>
>
>
> Hi folks,
>
>
>
> I just submited a new draft intending to provide better connectivity from
> network side function . Comments are welcome.
>
>
>
> Best regares,
>
> Davey
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Fri, 21 Sep 2018 at 14:15
> Subject: New Version Notification for
> draft-v6ops-xie-network-happyeyeballs-00.txt
> To: Chongfeng Xie <xiechf.bri@chinatelecom.cn>, Linjian Song <
> songlinjian@gmail.com>
>
>
>
>
> A new version of I-D, draft-v6ops-xie-network-happyeyeballs-00.txt
> has been successfully submitted by Linjian Song and posted to the
> IETF repository.
>
> Name:           draft-v6ops-xie-network-happyeyeballs
> Revision:       00
> Title:          Network-side Happy Eyeballs based on accurate IPv6
> measurement
> Document date:  2018-09-20
> Group:          Individual Submission
> Pages:          9
> URL:
> https://www.ietf.org/internet-drafts/draft-v6ops-xie-network-happyeyeball=
s-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-v6ops-xie-network-happyeyeballs/
> Htmlized:
> https://tools.ietf.org/html/draft-v6ops-xie-network-happyeyeballs-00
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-v6ops-xie-network-happyeyebal=
ls
>
>
> Abstract:
>    During the period of IPv6 transition, both ISP and ICP (Internet
>    Content Provider) care about user's experience in dual-stack network.
>    They hesitate to provide IPv6 to their users due to the fear of poor
>    IPv6 performance.  Network-based Happy Eyeballs (NHE) is proposed in
>    this memo as a approach to provide better connectivity to end users
>    by doing accurate measurement and comparison on IPv6/IPv4 performance
>    on the network side other than client-side Happy Eyeballs (HE)
>    ([RFC8305]).  It works independently with client's adoption of HE.
>
>    REMOVE BEFORE PUBLICATION: The source of the document with test
>    script is currently placed at GitHub [NHE-GitHub].  Comments and pull
>    request are welcome.
>
>
>
>
> 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.
>
> The IETF Secretariat
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
> **********************************************
> 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
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
>
>

--000000000000418127057670ac7e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Jordi,<div><br></div><div>Thanks for your support. I re=
ad your draft. I think we target different problems. NHE can avoid the oper=
ational issues but it is not the main purpose. If you would like to improve=
 NHE to do better performance measurement or other extension, the authors a=
re open for suggestions.=C2=A0</div><div><br></div><div>Btw, it is the vaca=
tion of Mid-Autumn day in China. Wish you all Happy Mid-Autumn day : )</div=
><div><br></div><div>Best regards,</div><div>Davey</div></div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr">On Fri, 21 Sep 2018 at 14:51, JORDI PALE=
T MARTINEZ &lt;<a href=3D"mailto:jordi.palet@consulintel.es">jordi.palet@co=
nsulintel.es</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div la=
ng=3D"ES" link=3D"blue" vlink=3D"purple"><div class=3D"m_263474456374635977=
0WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<u></u><u></u=
></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u=
></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">I like this documen=
t.<u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u><=
/u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">In f=
act, looks to me, somehow, as an alternative approach to what I was trying =
in:<u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u>=
</u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><a =
href=3D"https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00" targ=
et=3D"_blank">https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00=
</a><u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u=
></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Ho=
wever, I=E2=80=99m missing some way to actually alert the ISP about the fai=
lures.<u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">=
<u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">=
If you think that this makes sense, I=E2=80=99m happy to contribute to that=
, as I was already working in an update of my document and alternatives to =
using syslog.<u></u><u></u></span></p><div><p class=3D"MsoNormal"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;color:black"><br></span><span lang=3D=
"ES-TRAD" style=3D"font-size:10.5pt;color:black">Regards,<u></u><u></u></sp=
an></p><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"=
ES-TRAD" style=3D"font-size:10.5pt;color:black">Jordi<u></u><u></u></span><=
/p><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"ES-T=
RAD" style=3D"font-size:10.5pt;color:black"><u></u>=C2=A0<u></u></span></p>=
</div><p class=3D"MsoNormal"><span lang=3D"ES-TRAD"><u></u>=C2=A0<u></u></s=
pan></p><p class=3D"MsoNormal"><span lang=3D"ES-TRAD"><u></u>=C2=A0<u></u><=
/span></p><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:=
3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><b><=
span style=3D"font-size:12.0pt;color:black">De: </span></b><span style=3D"f=
ont-size:12.0pt;color:black">v6ops &lt;<a href=3D"mailto:v6ops-bounces@ietf=
.org" target=3D"_blank">v6ops-bounces@ietf.org</a>&gt; en nombre de Davey S=
ong &lt;<a href=3D"mailto:songlinjian@gmail.com" target=3D"_blank">songlinj=
ian@gmail.com</a>&gt;<br><b>Fecha: </b>viernes, 21 de septiembre de 2018, 8=
:32<br><b>Para: </b>&lt;<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank"=
>v6ops@ietf.org</a>&gt;<br><b>Asunto: </b>[v6ops] Fwd: New Version Notifica=
tion for draft-v6ops-xie-network-happyeyeballs-00.txt<u></u><u></u></span><=
/p></div><div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><u></u>=
=C2=A0<u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-left:35.=
4pt">Hi folks,<u></u><u></u></p><div><p class=3D"MsoNormal" style=3D"margin=
-left:35.4pt">=C2=A0<u></u><u></u></p></div><div><p class=3D"MsoNormal" sty=
le=3D"margin-left:35.4pt">I just submited a new draft intending to provide =
better connectivity from network side function . Comments are welcome.<u></=
u><u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"=
><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-=
left:35.4pt">Best regares,<u></u><u></u></p></div><div><p class=3D"MsoNorma=
l" style=3D"margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt">Davey=
=C2=A0<u></u><u></u></p><div><div><p class=3D"MsoNormal" style=3D"margin-le=
ft:35.4pt">---------- Forwarded message ---------<br>From: &lt;<a href=3D"m=
ailto:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org<=
/a>&gt;<br>Date: Fri, 21 Sep 2018 at 14:15<br>Subject: New Version Notifica=
tion for draft-v6ops-xie-network-happyeyeballs-00.txt<br>To: Chongfeng Xie =
&lt;<a href=3D"mailto:xiechf.bri@chinatelecom.cn" target=3D"_blank">xiechf.=
bri@chinatelecom.cn</a>&gt;, Linjian Song &lt;<a href=3D"mailto:songlinjian=
@gmail.com" target=3D"_blank">songlinjian@gmail.com</a>&gt;<u></u><u></u></=
p></div><p class=3D"MsoNormal" style=3D"margin-right:0cm;margin-bottom:12.0=
pt;margin-left:35.4pt"><br><br><br>A new version of I-D, draft-v6ops-xie-ne=
twork-happyeyeballs-00.txt<br>has been successfully submitted by Linjian So=
ng and posted to the<br>IETF repository.<br><br>Name:=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0draft-v6ops-xie-network-happyeyeballs<br>Revision:=C2=
=A0 =C2=A0 =C2=A0 =C2=A000<br>Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Netw=
ork-side Happy Eyeballs based on accurate IPv6 measurement<br>Document date=
:=C2=A0 2018-09-20<br>Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual S=
ubmission<br>Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 9<br>URL:=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/internet-dr=
afts/draft-v6ops-xie-network-happyeyeballs-00.txt" target=3D"_blank">https:=
//www.ietf.org/internet-drafts/draft-v6ops-xie-network-happyeyeballs-00.txt=
</a><br>Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatra=
cker.ietf.org/doc/draft-v6ops-xie-network-happyeyeballs/" target=3D"_blank"=
>https://datatracker.ietf.org/doc/draft-v6ops-xie-network-happyeyeballs/</a=
><br>Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/=
html/draft-v6ops-xie-network-happyeyeballs-00" target=3D"_blank">https://to=
ols.ietf.org/html/draft-v6ops-xie-network-happyeyeballs-00</a><br>Htmlized:=
=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org/doc/html=
/draft-v6ops-xie-network-happyeyeballs" target=3D"_blank">https://datatrack=
er.ietf.org/doc/html/draft-v6ops-xie-network-happyeyeballs</a><br><br><br>A=
bstract:<br>=C2=A0 =C2=A0During the period of IPv6 transition, both ISP and=
 ICP (Internet<br>=C2=A0 =C2=A0Content Provider) care about user&#39;s expe=
rience in dual-stack network.<br>=C2=A0 =C2=A0They hesitate to provide IPv6=
 to their users due to the fear of poor<br>=C2=A0 =C2=A0IPv6 performance.=
=C2=A0 Network-based Happy Eyeballs (NHE) is proposed in<br>=C2=A0 =C2=A0th=
is memo as a approach to provide better connectivity to end users<br>=C2=A0=
 =C2=A0by doing accurate measurement and comparison on IPv6/IPv4 performanc=
e<br>=C2=A0 =C2=A0on the network side other than client-side Happy Eyeballs=
 (HE)<br>=C2=A0 =C2=A0([RFC8305]).=C2=A0 It works independently with client=
&#39;s adoption of HE.<br><br>=C2=A0 =C2=A0REMOVE BEFORE PUBLICATION: The s=
ource of the document with test<br>=C2=A0 =C2=A0script is currently placed =
at GitHub [NHE-GitHub].=C2=A0 Comments and pull<br>=C2=A0 =C2=A0request are=
 welcome.<br><br><br><br><br>Please note that it may take a couple of minut=
es from the time of submission<br>until the htmlized version and diff are a=
vailable at <a href=3D"http://tools.ietf.org" target=3D"_blank">tools.ietf.=
org</a>.<br><br>The IETF Secretariat<u></u><u></u></p></div></div></div><p =
class=3D"MsoNormal" style=3D"margin-left:35.4pt">__________________________=
_____________________ v6ops mailing list <a href=3D"mailto:v6ops@ietf.org" =
target=3D"_blank">v6ops@ietf.org</a> <a href=3D"https://www.ietf.org/mailma=
n/listinfo/v6ops" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v=
6ops</a> <u></u><u></u></p></div><br>**************************************=
********<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href=3D"http://www.consulintel.es" target=3D"_blank">http://www.consulin=
tel.es</a><br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.<br>
<br>
</div>
</blockquote></div>

--000000000000418127057670ac7e--


From nobody Sat Sep 22 01:00:36 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9C8F130DD0 for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 01:00:33 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 MAtscernt8nk for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 01:00:32 -0700 (PDT)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 23825128CF2 for <v6ops@ietf.org>; Sat, 22 Sep 2018 01:00:32 -0700 (PDT)
Received: by mail-ot1-x335.google.com with SMTP id o13-v6so15271182otl.4 for <v6ops@ietf.org>; Sat, 22 Sep 2018 01:00:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=AUv3IMoOpKA5XfzAvuYUzjj+FRgRSN/j34XG7DCQDqU=; b=NSZkAbXkIEhJOEh0pEfvqZKGvMzPbUDJPAJ7QSMMc3LY4ICseCz3Sx93ZqCSel1sNB s4qK4WmClXxWiE0HqNzAN8eFdlfGe4CFgIrQFPWkAEL203+0rF9ejyFNAleg1HWjdtBv e29u0tKqLX/W4KFnhmKhMK9iWg8M4C3OdNXVfgZnP6snSBW5NAw++5ageoAPLPdVyNQd SNci4XfZsJeYmWw08LhI9ky2ciUHU3aFIbMLUVSyxLZwKcd4H6Qvl7+6Cq1ISSesdAYc d/fHYSO4r5Xb1/BH3+Mo4WyX+Yp4dRY8CYkugYctLLzJ358rv4Td+9kpN2kxtMl0gkPP zKsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=AUv3IMoOpKA5XfzAvuYUzjj+FRgRSN/j34XG7DCQDqU=; b=N2sB9LD9LGgzmag/wkauT9wlIxZts37EE85CgCHO2fzgPkTs00H0z+vR+8/CpCzf36 hemkWmPSaDjFLhsuwcZ51XpM+Ev1GVHrfLoEvkrC5osWFZHY8ADNN4tOWVCFcXMP9Ymf E3sA1w+44+KLTF+PklSOIx6X2juPZjDUhfdAZRdWZWdHr6QCoHkhCClu6Vv+0GR+Xejw 8s0IolZlnj6YpSjdKVNl076lqgRoH+nbJHC8rH6sXFTekHSGT2B+j8dDEkCWObpvxEsv 0CswS3voSbrMLBQ24UwVKKDBnRMiKopid1KTtV1Q+JMRW3kZFvBy4b+LuX3oiS22mVBn GHIQ==
X-Gm-Message-State: ABuFfojjbx0YyUtt/bgBkSsN5zSLxvCNifKfKbfraNCLaYeWOv3nhAs1 H88G4zj5B5NoPUwxun7zGOZm61FF
X-Google-Smtp-Source: ACcGV60AlUeMv4kl9lxU2JmyEmATe3z38Ozw5VQ/oXs52eTsjP9YWM+pldIsjdWwT2npdpJi1P/Mrw==
X-Received: by 2002:a9d:3407:: with SMTP id v7-v6mr867204otb.122.1537603231368;  Sat, 22 Sep 2018 01:00:31 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::107d? ([2600:8802:5600:1546::107d]) by smtp.gmail.com with ESMTPSA id q204-v6sm10833233oih.49.2018.09.22.01.00.30 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Sep 2018 01:00:30 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <ABDC4D65-E476-43D2-AB2C-3CE9B4BF1B37@gmail.com>
Date: Sat, 22 Sep 2018 01:00:29 -0700
To: V6 Ops List <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/SxrL6fCNom7e5F3SgbbiUh47Wmc>
Subject: [v6ops] Impending Draft Cut-off
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 22 Sep 2018 08:00:34 -0000

The Internet Draft submission cut-off  for IETF 103 is 30 days from now. =
If you plan to submit a draft, now would be the time to do it, so that =
we have an opportunity for people to read and comment on it.

https://datatracker.ietf.org/meeting/important-dates/



From nobody Sat Sep 22 01:13:22 2018
Return-Path: <prvs=1803e9c019=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE920128CF2 for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 01:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 WACP9MlagYQ0 for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 01:13:18 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89E69130DC4 for <v6ops@ietf.org>; Sat, 22 Sep 2018 01:13:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1537603995; x=1538208795; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type; bh=IxmiGq0iE0mC6wSOOv02Bm 1XOlsEa8ThXSiFZEMEa8E=; b=t6vevIlAoF1C4hYP0tqjE8VZGGUqToHTzV+szm mSsjuBUZhl+X3/wso+5Xe4XVfOG036EoEWQBDlICWKHfgHys5tEsrhqO0JmMNYma I4xPTT3Ed+xYGmrQ4lgj2tvNgzdEk1t93RdIT+ftb2GJ8YlXGRGe3CJzLS85lxoj RIM2U=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sat, 22 Sep 2018 10:13:15 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 22 Sep 2018 10:13:14 +0200
Received: from [10.10.10.128] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005886068.msg for <v6ops@ietf.org>; Sat, 22 Sep 2018 10:13:13 +0200
X-MDRemoteIP: 2001:470:1f09:495:48dd:a41d:5d36:f6f1
X-MDHelo: [10.10.10.128]
X-MDArrival-Date: Sat, 22 Sep 2018 10:13:13 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1803e9c019=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Sat, 22 Sep 2018 10:13:08 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Davey Song <songlinjian@gmail.com>
CC: <v6ops@ietf.org>
Message-ID: <6364DDAE-AA09-454F-AA33-DFC3DD0A4C3F@consulintel.es>
Thread-Topic: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <C49A8009-519D-4B4B-B193-E6BED05FE5CA@consulintel.es> <CAAObRXJNsmbp9AAwz8UVyZaCojXMV=6_7XCZpADVmeW-6N81ow@mail.gmail.com>
In-Reply-To: <CAAObRXJNsmbp9AAwz8UVyZaCojXMV=6_7XCZpADVmeW-6N81ow@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3620455988_1401996206"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ymmoJj7RiKb8P78YKGjeyAqqFek>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 22 Sep 2018 08:13:21 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3620455988_1401996206
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Hi Davey,

=20

My point is that in the document you mention =E2=80=9CNetwork-based Happy E=
yeballs (NHE) is proposed in this memo as a approach to provide better conn=
ectivity to end users by doing accurate measurement=E2=80=A6=E2=80=9D.

=20

If those measurements are done, I think the next logical step is also to no=
tify somehow the IPv4-fallbacks to the operator. Don=E2=80=99t you think so=
?


Regards,

Jordi

=20

=20

=20

De: Davey Song <songlinjian@gmail.com>
Fecha: s=C3=A1bado, 22 de septiembre de 2018, 9:26
Para: <jordi.palet@consulintel.es>
CC: <v6ops@ietf.org>
Asunto: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-netwo=
rk-happyeyeballs-00.txt

=20

Hi Jordi,

=20

Thanks for your support. I read your draft. I think we target different pro=
blems. NHE can avoid the operational issues but it is not the main purpose.=
 If you would like to improve NHE to do better performance measurement or o=
ther extension, the authors are open for suggestions.=20

=20

Btw, it is the vacation of Mid-Autumn day in China. Wish you all Happy Mid-=
Autumn day : )

=20

Best regards,

Davey

=20

On Fri, 21 Sep 2018 at 14:51, JORDI PALET MARTINEZ <jordi.palet@consulintel=
.es> wrote:

Hi,

=20

I like this document.

=20

In fact, looks to me, somehow, as an alternative approach to what I was try=
ing in:

=20

https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00

=20

However, I=E2=80=99m missing some way to actually alert the ISP about the f=
ailures.

=20

If you think that this makes sense, I=E2=80=99m happy to contribute to that=
, as I was already working in an update of my document and alternatives to =
using syslog.


Regards,

Jordi

=20

=20

=20

De: v6ops <v6ops-bounces@ietf.org> en nombre de Davey Song <songlinjian@gma=
il.com>
Fecha: viernes, 21 de septiembre de 2018, 8:32
Para: <v6ops@ietf.org>
Asunto: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-h=
appyeyeballs-00.txt

=20

Hi folks,

=20

I just submited a new draft intending to provide better connectivity from n=
etwork side function . Comments are welcome.

=20

Best regares,

Davey=20

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Fri, 21 Sep 2018 at 14:15
Subject: New Version Notification for draft-v6ops-xie-network-happyeyeballs=
-00.txt
To: Chongfeng Xie <xiechf.bri@chinatelecom.cn>, Linjian Song <songlinjian@g=
mail.com>




A new version of I-D, draft-v6ops-xie-network-happyeyeballs-00.txt
has been successfully submitted by Linjian Song and posted to the
IETF repository.

Name:           draft-v6ops-xie-network-happyeyeballs
Revision:       00
Title:          Network-side Happy Eyeballs based on accurate IPv6 measurem=
ent
Document date:  2018-09-20
Group:          Individual Submission
Pages:          9
URL:            https://www.ietf.org/internet-drafts/draft-v6ops-xie-networ=
k-happyeyeballs-00.txt
Status:         https://datatracker.ietf.org/doc/draft-v6ops-xie-network-ha=
ppyeyeballs/
Htmlized:       https://tools.ietf.org/html/draft-v6ops-xie-network-happyey=
eballs-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-v6ops-xie-netwo=
rk-happyeyeballs


Abstract:
   During the period of IPv6 transition, both ISP and ICP (Internet
   Content Provider) care about user's experience in dual-stack network.
   They hesitate to provide IPv6 to their users due to the fear of poor
   IPv6 performance.  Network-based Happy Eyeballs (NHE) is proposed in
   this memo as a approach to provide better connectivity to end users
   by doing accurate measurement and comparison on IPv6/IPv4 performance
   on the network side other than client-side Happy Eyeballs (HE)
   ([RFC8305]).  It works independently with client's adoption of HE.

   REMOVE BEFORE PUBLICATION: The source of the document with test
   script is currently placed at GitHub [NHE-GitHub].  Comments and pull
   request are welcome.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________ v6ops mailing list v6ops@ie=
tf.org https://www.ietf.org/mailman/listinfo/v6ops=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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.



**********************************************
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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.


--B_3620455988_1401996206
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta ht=
tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name=
=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DES link=3Dblue vlink=3Dpurple><div class=3DW=
ordSection1><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-la=
nguage:EN-US'>Hi Davey,<o:p></o:p></span></p><p class=3DMsoNormal><span lan=
g=3DEN-US style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-language:EN-US=
'>My point is that in the document you mention =E2=80=9CNetwork-based Happy=
 Eyeballs (NHE) is proposed in this memo as a approach to provide better co=
nnectivity to end users by doing accurate measurement=E2=80=A6=E2=80=9D.<o:=
p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-far=
east-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 lang=3DEN-US style=3D'mso-fareast-language:EN-US'>If those measurements ar=
e done, I think the next logical step is also to notify somehow the IPv4-fa=
llbacks to the operator. Don=E2=80=99t you think so?<o:p></o:p></span></p><=
div><p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt;color=
:black'><br>Regards,<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mar=
gin-bottom:12.0pt'><span lang=3DEN-US style=3D'font-size:10.5pt;color:black=
;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p><p class=3DMsoNorma=
l style=3D'margin-bottom:12.0pt'><span lang=3DEN-US style=3D'font-size:10.5=
pt;color:black;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p></di=
v><p class=3DMsoNormal><span lang=3DEN-US style=3D'mso-fareast-language:EN-=
US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US sty=
le=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div style=3D=
'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p c=
lass=3DMsoNormal style=3D'margin-left:35.4pt'><b><span style=3D'font-size:1=
2.0pt;color:black'>De: </span></b><span style=3D'font-size:12.0pt;color:bla=
ck'>Davey Song &lt;songlinjian@gmail.com&gt;<br><b>Fecha: </b>s=C3=A1bado, =
22 de septiembre de 2018, 9:26<br><b>Para: </b>&lt;jordi.palet@consulintel.=
es&gt;<br><b>CC: </b>&lt;v6ops@ietf.org&gt;<br><b>Asunto: </b>Re: [v6ops] F=
wd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.t=
xt<o:p></o:p></span></p></div><div><p class=3DMsoNormal style=3D'margin-lef=
t:35.4pt'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'mar=
gin-left:35.4pt'>Hi Jordi,<o:p></o:p></p><div><p class=3DMsoNormal style=3D=
'margin-left:35.4pt'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal s=
tyle=3D'margin-left:35.4pt'>Thanks for your support. I read your draft. I t=
hink we target different problems. NHE can avoid the operational issues but=
 it is not the main purpose. If you would like to improve NHE to do better =
performance measurement or other extension, the authors are open for sugges=
tions.&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-=
left:35.4pt'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'=
margin-left:35.4pt'>Btw, it is the vacation of Mid-Autumn day in China. Wis=
h you all Happy Mid-Autumn day : )<o:p></o:p></p></div><div><p class=3DMsoN=
ormal style=3D'margin-left:35.4pt'><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal style=3D'margin-left:35.4pt'>Best regards,<o:p></o:p></p></div=
><div><p class=3DMsoNormal style=3D'margin-left:35.4pt'>Davey<o:p></o:p></p=
></div></div><p class=3DMsoNormal style=3D'margin-left:35.4pt'><o:p>&nbsp;<=
/o:p></p><div><div><p class=3DMsoNormal style=3D'margin-left:35.4pt'>On Fri=
, 21 Sep 2018 at 14:51, JORDI PALET MARTINEZ &lt;<a href=3D"mailto:jordi.pa=
let@consulintel.es">jordi.palet@consulintel.es</a>&gt; wrote:<o:p></o:p></p=
></div><blockquote style=3D'border:none;border-left:solid #CCCCCC 1.0pt;pad=
ding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p cla=
ss=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;=
margin-left:35.4pt'><span lang=3DEN-US>Hi,</span><o:p></o:p></p><p class=3D=
MsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margi=
n-left:35.4pt'><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMs=
oNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-=
left:35.4pt'><span lang=3DEN-US>I like this document.</span><o:p></o:p></p>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span lang=3DEN-US>&nbsp;</span><o:p></o:p></=
p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:35.4pt'><span lang=3DEN-US>In fact, looks to me, someho=
w, as an alternative approach to what I was trying in:</span><o:p></o:p></p=
><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;margin-left:35.4pt'><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><=
p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:=
auto;margin-left:35.4pt'><span lang=3DEN-US><a href=3D"https://tools.ietf.o=
rg/html/draft-palet-v6ops-he-reporting-00" target=3D"_blank">https://tools.=
ietf.org/html/draft-palet-v6ops-he-reporting-00</a></span><o:p></o:p></p><p=
 class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto;margin-left:35.4pt'><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p c=
lass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o;margin-left:35.4pt'><span lang=3DEN-US>However, I=E2=80=99m missing some =
way to actually alert the ISP about the failures.</span><o:p></o:p></p><p c=
lass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o;margin-left:35.4pt'><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p cla=
ss=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;=
margin-left:35.4pt'><span lang=3DEN-US>If you think that this makes sense, =
I=E2=80=99m happy to contribute to that, as I was already working in an upd=
ate of my document and alternatives to using syslog.</span><o:p></o:p></p><=
div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom=
-alt:auto;margin-left:35.4pt'><span lang=3DEN-US style=3D'font-size:10.5pt;=
color:black'><br></span><span lang=3DES-TRAD style=3D'font-size:10.5pt;colo=
r:black'>Regards,</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-ma=
rgin-top-alt:auto;margin-bottom:12.0pt;margin-left:35.4pt'><span lang=3DES-=
TRAD style=3D'font-size:10.5pt;color:black'>Jordi</span><o:p></o:p></p><p c=
lass=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;marg=
in-left:35.4pt'><span lang=3DES-TRAD style=3D'font-size:10.5pt;color:black'=
>&nbsp;</span><o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span lang=3DE=
S-TRAD>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span lang=3DE=
S-TRAD>&nbsp;</span><o:p></o:p></p><div style=3D'border:none;border-top:sol=
id #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><b><s=
pan style=3D'font-size:12.0pt;color:black'>De: </span></b><span style=3D'fo=
nt-size:12.0pt;color:black'>v6ops &lt;<a href=3D"mailto:v6ops-bounces@ietf.=
org" target=3D"_blank">v6ops-bounces@ietf.org</a>&gt; en nombre de Davey So=
ng &lt;<a href=3D"mailto:songlinjian@gmail.com" target=3D"_blank">songlinji=
an@gmail.com</a>&gt;<br><b>Fecha: </b>viernes, 21 de septiembre de 2018, 8:=
32<br><b>Para: </b>&lt;<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">=
v6ops@ietf.org</a>&gt;<br><b>Asunto: </b>[v6ops] Fwd: New Version Notificat=
ion for draft-v6ops-xie-network-happyeyeballs-00.txt</span><o:p></o:p></p><=
/div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto;margin-left:70.8pt'>&nbsp;<o:p></o:p></p></div><div><p clas=
s=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
argin-left:70.8pt'>Hi folks,<o:p></o:p></p><div><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'>=
&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-to=
p-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'>I just submited a=
 new draft intending to provide better connectivity from network side funct=
ion . Comments are welcome.<o:p></o:p></p></div><div><p class=3DMsoNormal s=
tyle=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8=
pt'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margi=
n-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'>Best regares,=
<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:70=
.8pt'>Davey&nbsp;<o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso=
-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'>-------=
--- Forwarded message ---------<br>From: &lt;<a href=3D"mailto:internet-dra=
fts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;<br>Date: F=
ri, 21 Sep 2018 at 14:15<br>Subject: New Version Notification for draft-v6o=
ps-xie-network-happyeyeballs-00.txt<br>To: Chongfeng Xie &lt;<a href=3D"mai=
lto:xiechf.bri@chinatelecom.cn" target=3D"_blank">xiechf.bri@chinatelecom.c=
n</a>&gt;, Linjian Song &lt;<a href=3D"mailto:songlinjian@gmail.com" target=
=3D"_blank">songlinjian@gmail.com</a>&gt;<o:p></o:p></p></div><p class=3DMs=
oNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:7=
0.8pt'><br><br><br>A new version of I-D, draft-v6ops-xie-network-happyeyeba=
lls-00.txt<br>has been successfully submitted by Linjian Song and posted to=
 the<br>IETF repository.<br><br>Name:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;draft-v6ops-xie-network-happyeyeballs<br>Revision:&nbsp; &nbsp; &nbsp; &=
nbsp;00<br>Title:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Network-side Happy Eyeb=
alls based on accurate IPv6 measurement<br>Document date:&nbsp; 2018-09-20<=
br>Group:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Individual Submission<br>Pages:=
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 9<br>URL:&nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; <a href=3D"https://www.ietf.org/internet-drafts/draft-v6ops-xie-=
network-happyeyeballs-00.txt" target=3D"_blank">https://www.ietf.org/intern=
et-drafts/draft-v6ops-xie-network-happyeyeballs-00.txt</a><br>Status:&nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"https://datatracker.ietf.org/doc/dra=
ft-v6ops-xie-network-happyeyeballs/" target=3D"_blank">https://datatracker.=
ietf.org/doc/draft-v6ops-xie-network-happyeyeballs/</a><br>Htmlized:&nbsp; =
&nbsp; &nbsp; &nbsp;<a href=3D"https://tools.ietf.org/html/draft-v6ops-xie-=
network-happyeyeballs-00" target=3D"_blank">https://tools.ietf.org/html/dra=
ft-v6ops-xie-network-happyeyeballs-00</a><br>Htmlized:&nbsp; &nbsp; &nbsp; =
&nbsp;<a href=3D"https://datatracker.ietf.org/doc/html/draft-v6ops-xie-netw=
ork-happyeyeballs" target=3D"_blank">https://datatracker.ietf.org/doc/html/=
draft-v6ops-xie-network-happyeyeballs</a><br><br><br>Abstract:<br>&nbsp; &n=
bsp;During the period of IPv6 transition, both ISP and ICP (Internet<br>&nb=
sp; &nbsp;Content Provider) care about user's experience in dual-stack netw=
ork.<br>&nbsp; &nbsp;They hesitate to provide IPv6 to their users due to th=
e fear of poor<br>&nbsp; &nbsp;IPv6 performance.&nbsp; Network-based Happy =
Eyeballs (NHE) is proposed in<br>&nbsp; &nbsp;this memo as a approach to pr=
ovide better connectivity to end users<br>&nbsp; &nbsp;by doing accurate me=
asurement and comparison on IPv6/IPv4 performance<br>&nbsp; &nbsp;on the ne=
twork side other than client-side Happy Eyeballs (HE)<br>&nbsp; &nbsp;([RFC=
8305]).&nbsp; It works independently with client's adoption of HE.<br><br>&=
nbsp; &nbsp;REMOVE BEFORE PUBLICATION: The source of the document with test=
<br>&nbsp; &nbsp;script is currently placed at GitHub [NHE-GitHub].&nbsp; C=
omments and pull<br>&nbsp; &nbsp;request are welcome.<br><br><br><br><br>Pl=
ease note that it may take a couple of minutes from the time of submission<=
br>until the htmlized version and diff are available at <a href=3D"http://t=
ools.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br><br>The IETF Secret=
ariat<o:p></o:p></p></div></div></div><p class=3DMsoNormal style=3D'mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'>___________=
____________________________________ v6ops mailing list <a href=3D"mailto:v=
6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a> <a href=3D"https://www.=
ietf.org/mailman/listinfo/v6ops" target=3D"_blank">https://www.ietf.org/mai=
lman/listinfo/v6ops</a> <o:p></o:p></p></div><p class=3DMsoNormal style=3D'=
mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35=
.4pt'><br>**********************************************<br>IPv4 is over<br=
>Are you ready for the new Internet ?<br><a href=3D"http://www.consulintel.=
es" target=3D"_blank">http://www.consulintel.es</a><br>The IPv6 Company<br><br>This electronic message =
contains information which may be privileged or confidential. The informati=
on is intended to be for the exclusive use of the individual(s) named above=
 and further non-explicilty authorized disclosure, copying, distribution or=
 use of the contents of this information, even if partially, including atta=
ched files, is strictly prohibited and will be considered a criminal offens=
e. If you are not the intended recipient be aware that any disclosure, copy=
ing, distribution or use of the contents of this information, even if parti=
ally, including attached files, is strictly prohibited, will be considered =
a criminal offense, so you must reply to the original sender to inform abou=
t this communication and delete it.<o:p></o:p></p></div></blockquote></div>=
</div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.consulintel.es<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.<br>
<br>
</body></html>

--B_3620455988_1401996206--


From nobody Sat Sep 22 09:22:29 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A012130E17 for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 09:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level: 
X-Spam-Status: No, score=-1.201 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, HTML_MESSAGE=0.001, MIME_BOUND_DIGITS_15=0.798, SPF_PASS=-0.001] autolearn=no 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 0yQHurza-PUq for <v6ops@ietfa.amsl.com>; Sat, 22 Sep 2018 09:22:26 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 CF37D130E0C for <v6ops@ietf.org>; Sat, 22 Sep 2018 09:22:25 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id z13-v6so4823638qts.5 for <v6ops@ietf.org>; Sat, 22 Sep 2018 09:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hpgQRZg1Nf+wvGmWl+PvSMrhQR9RAp97BLdLMTSgzXE=; b=p3rFjM/Fl+jlI3szbAUwZyHs6q/+wUKmZc5TZe69FSd5+/o/3pGqBIOvrWZa6llsar UVrx7YxmKm+0jviMrGuPgXzqtetAsrlbfDoVVojvBCUDNqTrc4dMwmmhj9Z5hPPyCsHS 0uDomIA/6h4xeyhebFeHGjDfzsVeHh9U/bdGJJwM9uoe2xfKLp4Z/mXzwRSuzcRDJ/RA Ckv7ZbdaohkZ+N06RE2V8kYykKwgwEgkd3aEylxhLlc2GlIn998XdFecJGP6q/alNZwe JzvHo4Y9K1yF2PR6bAIRFs697yKIWsDmDQ9DXk7SU/hWoQa2vqSHjk7OtotYKfIsC0YQ 62cQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hpgQRZg1Nf+wvGmWl+PvSMrhQR9RAp97BLdLMTSgzXE=; b=HPiod3Sjr93W5OlSqfwQ4ElsfTRJj3BYQNRKdZ7UIT/2HXEs8zjxgoxYLNentH3Oyu pyRYIUWl4tqU7mGtuicwpLudmknPMk7N/ePc3YWzt0a5QINgw0ibekbTU8mvna+XNBUD nbCNxPon7AP9Fy58hnD3PINJTVGzlAOGEyA8UEaLu4xrK86RnYU0YKMb4jTN/OJ5QKl+ 980eMf6vDJvgi3yW/BhlDwwQNIqkREGVdcPvy5pnsLxzXuFXMF3o8nfhHMjCMINNDZSI X8WrjkW+7FNi+rgre6qS5FhXkhppChKEmPZBWelEyDGLmOrAB0q2uD7VC/8s2LgqDY5y 9tkw==
X-Gm-Message-State: ABuFfog0Ydrgl9xHTGN2igZYA2rEzpy71qdSgLcVBYCbLFPKBnLsbno2 6+79FUBZ8XyH8uY4UmVdVUjLjRldt6+QygIbwTOqENCXwtk=
X-Google-Smtp-Source: ACcGV61onPRwi129NXX5o7kKeZhkhLbFugiVWXzLEUP0g2qdQqbLAyZ5tqvVGxfGpfr3ZQQl9tnixP02zyVz4/G+E/I=
X-Received: by 2002:a0c:dc11:: with SMTP id s17-v6mr1847436qvk.24.1537633344850;  Sat, 22 Sep 2018 09:22:24 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <C49A8009-519D-4B4B-B193-E6BED05FE5CA@consulintel.es> <CAAObRXJNsmbp9AAwz8UVyZaCojXMV=6_7XCZpADVmeW-6N81ow@mail.gmail.com> <6364DDAE-AA09-454F-AA33-DFC3DD0A4C3F@consulintel.es>
In-Reply-To: <6364DDAE-AA09-454F-AA33-DFC3DD0A4C3F@consulintel.es>
From: Davey Song <songlinjian@gmail.com>
Date: Sun, 23 Sep 2018 00:22:05 +0800
Message-ID: <CAAObRX+ZGN=igiD+XfbjNyHDPD7r7r-yNaYMzoDTTBSANwyUsA@mail.gmail.com>
To: jordi.palet@consulintel.es
Cc: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005090790576782920"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/JfZfTiow_oP5zB8jV4N6ZX4fl70>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 22 Sep 2018 16:22:29 -0000

--0000000000005090790576782920
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Sure, helping ISP to record the fallback cases is additional gain from NHE
which adds more motivation for ISP to deploy it. If people like NHE and
encourage us to proceed, then we can discuss it after we move a step
forward.

Right now, people may be still doubt about the performance of NHE itself
(the accuracy and the cost of it ). We need some tests and data to
demonstrate the capacity. People may suspects that NHE may cause more
aggressive IPv4-fallback, so we need to determine a good threshold value
for NHE when comparing IPv6/IPv4 round-trip delay.  We need to know the
ratio of HE-enabled apps in top 1000 apps, and if NHE can help
None-HE-enabled Apps. Now it is unknown yet for me.

A good news recently is Apple release a ios version 12.1 which finally
support IPv6 in 4G LET data plane. And China telecom is planning for a
testing to find answers on above questions. If any ISP operators think NHE
is interesting, we can do some work together. Or if I missed any work
already done, please let me know. Thanks.

Best regards,
Davey

On Sat, 22 Sep 2018 at 16:13, JORDI PALET MARTINEZ <
jordi.palet@consulintel.es> wrote:

> Hi Davey,
>
>
>
> My point is that in the document you mention =E2=80=9CNetwork-based Happy=
 Eyeballs
> (NHE) is proposed in this memo as a approach to provide better connectivi=
ty
> to end users by doing accurate measurement=E2=80=A6=E2=80=9D.
>
>
>
> If those measurements are done, I think the next logical step is also to
> notify somehow the IPv4-fallbacks to the operator. Don=E2=80=99t you thin=
k so?
>
>
> Regards,
>
> Jordi
>
>
>
>
>
>
>
> *De: *Davey Song <songlinjian@gmail.com>
> *Fecha: *s=C3=A1bado, 22 de septiembre de 2018, 9:26
> *Para: *<jordi.palet@consulintel.es>
> *CC: *<v6ops@ietf.org>
> *Asunto: *Re: [v6ops] Fwd: New Version Notification for
> draft-v6ops-xie-network-happyeyeballs-00.txt
>
>
>
> Hi Jordi,
>
>
>
> Thanks for your support. I read your draft. I think we target different
> problems. NHE can avoid the operational issues but it is not the main
> purpose. If you would like to improve NHE to do better performance
> measurement or other extension, the authors are open for suggestions.
>
>
>
> Btw, it is the vacation of Mid-Autumn day in China. Wish you all Happy
> Mid-Autumn day : )
>
>
>
> Best regards,
>
> Davey
>
>
>
> On Fri, 21 Sep 2018 at 14:51, JORDI PALET MARTINEZ <
> jordi.palet@consulintel.es> wrote:
>
> Hi,
>
>
>
> I like this document.
>
>
>
> In fact, looks to me, somehow, as an alternative approach to what I was
> trying in:
>
>
>
> https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00
>
>
>
> However, I=E2=80=99m missing some way to actually alert the ISP about the=
 failures.
>
>
>
> If you think that this makes sense, I=E2=80=99m happy to contribute to th=
at, as I
> was already working in an update of my document and alternatives to using
> syslog.
>
>
> Regards,
>
> Jordi
>
>
>
>
>
>
>
> *De: *v6ops <v6ops-bounces@ietf.org> en nombre de Davey Song <
> songlinjian@gmail.com>
> *Fecha: *viernes, 21 de septiembre de 2018, 8:32
> *Para: *<v6ops@ietf.org>
> *Asunto: *[v6ops] Fwd: New Version Notification for
> draft-v6ops-xie-network-happyeyeballs-00.txt
>
>
>
> Hi folks,
>
>
>
> I just submited a new draft intending to provide better connectivity from
> network side function . Comments are welcome.
>
>
>
> Best regares,
>
> Davey
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Fri, 21 Sep 2018 at 14:15
> Subject: New Version Notification for
> draft-v6ops-xie-network-happyeyeballs-00.txt
> To: Chongfeng Xie <xiechf.bri@chinatelecom.cn>, Linjian Song <
> songlinjian@gmail.com>
>
>
>
>
> A new version of I-D, draft-v6ops-xie-network-happyeyeballs-00.txt
> has been successfully submitted by Linjian Song and posted to the
> IETF repository.
>
> Name:           draft-v6ops-xie-network-happyeyeballs
> Revision:       00
> Title:          Network-side Happy Eyeballs based on accurate IPv6
> measurement
> Document date:  2018-09-20
> Group:          Individual Submission
> Pages:          9
> URL:
> https://www.ietf.org/internet-drafts/draft-v6ops-xie-network-happyeyeball=
s-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-v6ops-xie-network-happyeyeballs/
> Htmlized:
> https://tools.ietf.org/html/draft-v6ops-xie-network-happyeyeballs-00
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-v6ops-xie-network-happyeyebal=
ls
>
>
> Abstract:
>    During the period of IPv6 transition, both ISP and ICP (Internet
>    Content Provider) care about user's experience in dual-stack network.
>    They hesitate to provide IPv6 to their users due to the fear of poor
>    IPv6 performance.  Network-based Happy Eyeballs (NHE) is proposed in
>    this memo as a approach to provide better connectivity to end users
>    by doing accurate measurement and comparison on IPv6/IPv4 performance
>    on the network side other than client-side Happy Eyeballs (HE)
>    ([RFC8305]).  It works independently with client's adoption of HE.
>
>    REMOVE BEFORE PUBLICATION: The source of the document with test
>    script is currently placed at GitHub [NHE-GitHub].  Comments and pull
>    request are welcome.
>
>
>
>
> 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.
>
> The IETF Secretariat
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>
>
> **********************************************
> 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
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
>
>
> **********************************************
> 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
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
>
>

--0000000000005090790576782920
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sure, helping ISP to record the fallback cases is addition=
al gain from NHE which adds more motivation for ISP to deploy it. If people=
 like NHE and encourage us to proceed, then we can discuss it after we move=
 a step forward.=C2=A0<div><br></div><div>Right now, people may be still do=
ubt about the performance of NHE itself (the accuracy and the cost of it ).=
 We need some tests and data to demonstrate the capacity. People may suspec=
ts that NHE may cause more aggressive IPv4-fallback, so we need to determin=
e a good threshold value for NHE when comparing IPv6/IPv4 round-trip delay.=
=C2=A0 We need to know the ratio of HE-enabled apps in top 1000 apps, and i=
f NHE can help None-HE-enabled Apps. Now it is unknown yet for me.</div><di=
v><br></div><div>A good news recently is Apple release a ios version 12.1 w=
hich finally support IPv6 in 4G LET data plane. And China telecom is planni=
ng for a testing to find answers on above questions. If any ISP operators t=
hink NHE is interesting, we can do some work together. Or if I missed any w=
ork already done, please let me know. Thanks.</div><div><div><br></div><div=
><div><div>Best regards,</div><div>Davey</div></div></div></div></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, 22 Sep 2018 at 16:13, JO=
RDI PALET MARTINEZ &lt;<a href=3D"mailto:jordi.palet@consulintel.es">jordi.=
palet@consulintel.es</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div lang=3D"ES" link=3D"blue" vlink=3D"purple"><div class=3D"m_-747129488=
6234365973WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Dave=
y,<u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u><=
/u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">My p=
oint is that in the document you mention =E2=80=9CNetwork-based Happy Eyeba=
lls (NHE) is proposed in this memo as a approach to provide better connecti=
vity to end users by doing accurate measurement=E2=80=A6=E2=80=9D.<u></u><u=
></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u=
></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">If those measur=
ements are done, I think the next logical step is also to notify somehow th=
e IPv4-fallbacks to the operator. Don=E2=80=99t you think so?<u></u><u></u>=
</span></p><div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-s=
ize:10.5pt;color:black"><br>Regards,<u></u><u></u></span></p><p class=3D"Ms=
oNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US" style=3D"font-=
size:10.5pt;color:black">Jordi<u></u><u></u></span></p><p class=3D"MsoNorma=
l" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.5pt;color:black"><u></u>=C2=A0<u></u></span></p></div><p class=3D"MsoNorm=
al"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNorm=
al"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p><div style=3D"borde=
r:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=
=3D"MsoNormal" style=3D"margin-left:35.4pt"><b><span style=3D"font-size:12.=
0pt;color:black">De: </span></b><span style=3D"font-size:12.0pt;color:black=
">Davey Song &lt;<a href=3D"mailto:songlinjian@gmail.com" target=3D"_blank"=
>songlinjian@gmail.com</a>&gt;<br><b>Fecha: </b>s=C3=A1bado, 22 de septiemb=
re de 2018, 9:26<br><b>Para: </b>&lt;<a href=3D"mailto:jordi.palet@consulin=
tel.es" target=3D"_blank">jordi.palet@consulintel.es</a>&gt;<br><b>CC: </b>=
&lt;<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a>&=
gt;<br><b>Asunto: </b>Re: [v6ops] Fwd: New Version Notification for draft-v=
6ops-xie-network-happyeyeballs-00.txt<u></u><u></u></span></p></div><div><p=
 class=3D"MsoNormal" style=3D"margin-left:35.4pt"><u></u>=C2=A0<u></u></p><=
/div><div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt">Hi Jordi,<u><=
/u><u></u></p><div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><u><=
/u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-left:=
35.4pt">Thanks for your support. I read your draft. I think we target diffe=
rent problems. NHE can avoid the operational issues but it is not the main =
purpose. If you would like to improve NHE to do better performance measurem=
ent or other extension, the authors are open for suggestions.=C2=A0<u></u><=
u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><u=
></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-lef=
t:35.4pt">Btw, it is the vacation of Mid-Autumn day in China. Wish you all =
Happy Mid-Autumn day : )<u></u><u></u></p></div><div><p class=3D"MsoNormal"=
 style=3D"margin-left:35.4pt"><u></u>=C2=A0<u></u></p></div><div><p class=
=3D"MsoNormal" style=3D"margin-left:35.4pt">Best regards,<u></u><u></u></p>=
</div><div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt">Davey<u></u>=
<u></u></p></div></div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt">=
<u></u>=C2=A0<u></u></p><div><div><p class=3D"MsoNormal" style=3D"margin-le=
ft:35.4pt">On Fri, 21 Sep 2018 at 14:51, JORDI PALET MARTINEZ &lt;<a href=
=3D"mailto:jordi.palet@consulintel.es" target=3D"_blank">jordi.palet@consul=
intel.es</a>&gt; wrote:<u></u><u></u></p></div><blockquote style=3D"border:=
none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:=
4.8pt;margin-right:0cm"><div><div><p class=3D"MsoNormal" style=3D"margin-le=
ft:35.4pt"><span lang=3D"EN-US">Hi,</span><u></u><u></u></p><p class=3D"Mso=
Normal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">=C2=A0</span><u><=
/u><u></u></p><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lan=
g=3D"EN-US">I like this document.</span><u></u><u></u></p><p class=3D"MsoNo=
rmal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">=C2=A0</span><u></u=
><u></u></p><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=
=3D"EN-US">In fact, looks to me, somehow, as an alternative approach to wha=
t I was trying in:</span><u></u><u></u></p><p class=3D"MsoNormal" style=3D"=
margin-left:35.4pt"><span lang=3D"EN-US">=C2=A0</span><u></u><u></u></p><p =
class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"><a hr=
ef=3D"https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00" target=
=3D"_blank">https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00</=
a></span><u></u><u></u></p><p class=3D"MsoNormal" style=3D"margin-left:35.4=
pt"><span lang=3D"EN-US">=C2=A0</span><u></u><u></u></p><p class=3D"MsoNorm=
al" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">However, I=E2=80=99m =
missing some way to actually alert the ISP about the failures.</span><u></u=
><u></u></p><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=
=3D"EN-US">=C2=A0</span><u></u><u></u></p><p class=3D"MsoNormal" style=3D"m=
argin-left:35.4pt"><span lang=3D"EN-US">If you think that this makes sense,=
 I=E2=80=99m happy to contribute to that, as I was already working in an up=
date of my document and alternatives to using syslog.</span><u></u><u></u><=
/p><div><p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"E=
N-US" style=3D"font-size:10.5pt;color:black"><br></span><span lang=3D"ES-TR=
AD" style=3D"font-size:10.5pt;color:black">Regards,</span><u></u><u></u></p=
><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;margin-left:35.4pt"><=
span lang=3D"ES-TRAD" style=3D"font-size:10.5pt;color:black">Jordi</span><u=
></u><u></u></p><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;margin=
-left:35.4pt"><span lang=3D"ES-TRAD" style=3D"font-size:10.5pt;color:black"=
>=C2=A0</span><u></u><u></u></p></div><p class=3D"MsoNormal" style=3D"margi=
n-left:35.4pt"><span lang=3D"ES-TRAD">=C2=A0</span><u></u><u></u></p><p cla=
ss=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"ES-TRAD">=C2=A0=
</span><u></u><u></u></p><div style=3D"border:none;border-top:solid #b5c4df=
 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal" style=3D"margin-le=
ft:70.8pt"><b><span style=3D"font-size:12.0pt;color:black">De: </span></b><=
span style=3D"font-size:12.0pt;color:black">v6ops &lt;<a href=3D"mailto:v6o=
ps-bounces@ietf.org" target=3D"_blank">v6ops-bounces@ietf.org</a>&gt; en no=
mbre de Davey Song &lt;<a href=3D"mailto:songlinjian@gmail.com" target=3D"_=
blank">songlinjian@gmail.com</a>&gt;<br><b>Fecha: </b>viernes, 21 de septie=
mbre de 2018, 8:32<br><b>Para: </b>&lt;<a href=3D"mailto:v6ops@ietf.org" ta=
rget=3D"_blank">v6ops@ietf.org</a>&gt;<br><b>Asunto: </b>[v6ops] Fwd: New V=
ersion Notification for draft-v6ops-xie-network-happyeyeballs-00.txt</span>=
<u></u><u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-left:70=
.8pt">=C2=A0<u></u><u></u></p></div><div><p class=3D"MsoNormal" style=3D"ma=
rgin-left:70.8pt">Hi folks,<u></u><u></u></p><div><p class=3D"MsoNormal" st=
yle=3D"margin-left:70.8pt">=C2=A0<u></u><u></u></p></div><div><p class=3D"M=
soNormal" style=3D"margin-left:70.8pt">I just submited a new draft intendin=
g to provide better connectivity from network side function . Comments are =
welcome.<u></u><u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin=
-left:70.8pt">=C2=A0<u></u><u></u></p></div><div><p class=3D"MsoNormal" sty=
le=3D"margin-left:70.8pt">Best regares,<u></u><u></u></p></div><div><p clas=
s=3D"MsoNormal" style=3D"margin-bottom:12.0pt;margin-left:70.8pt">Davey=C2=
=A0<u></u><u></u></p><div><div><p class=3D"MsoNormal" style=3D"margin-left:=
70.8pt">---------- Forwarded message ---------<br>From: &lt;<a href=3D"mail=
to:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>=
&gt;<br>Date: Fri, 21 Sep 2018 at 14:15<br>Subject: New Version Notificatio=
n for draft-v6ops-xie-network-happyeyeballs-00.txt<br>To: Chongfeng Xie &lt=
;<a href=3D"mailto:xiechf.bri@chinatelecom.cn" target=3D"_blank">xiechf.bri=
@chinatelecom.cn</a>&gt;, Linjian Song &lt;<a href=3D"mailto:songlinjian@gm=
ail.com" target=3D"_blank">songlinjian@gmail.com</a>&gt;<u></u><u></u></p><=
/div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt;margin-left:70.8p=
t"><br><br><br>A new version of I-D, draft-v6ops-xie-network-happyeyeballs-=
00.txt<br>has been successfully submitted by Linjian Song and posted to the=
<br>IETF repository.<br><br>Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0d=
raft-v6ops-xie-network-happyeyeballs<br>Revision:=C2=A0 =C2=A0 =C2=A0 =C2=
=A000<br>Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Network-side Happy Eyebal=
ls based on accurate IPv6 measurement<br>Document date:=C2=A0 2018-09-20<br=
>Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>Pages:=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 9<br>URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 <a href=3D"https://www.ietf.org/internet-drafts/draft-v6ops-xie-=
network-happyeyeballs-00.txt" target=3D"_blank">https://www.ietf.org/intern=
et-drafts/draft-v6ops-xie-network-happyeyeballs-00.txt</a><br>Status:=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org/doc/dra=
ft-v6ops-xie-network-happyeyeballs/" target=3D"_blank">https://datatracker.=
ietf.org/doc/draft-v6ops-xie-network-happyeyeballs/</a><br>Htmlized:=C2=A0 =
=C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/draft-v6ops-xie-=
network-happyeyeballs-00" target=3D"_blank">https://tools.ietf.org/html/dra=
ft-v6ops-xie-network-happyeyeballs-00</a><br>Htmlized:=C2=A0 =C2=A0 =C2=A0 =
=C2=A0<a href=3D"https://datatracker.ietf.org/doc/html/draft-v6ops-xie-netw=
ork-happyeyeballs" target=3D"_blank">https://datatracker.ietf.org/doc/html/=
draft-v6ops-xie-network-happyeyeballs</a><br><br><br>Abstract:<br>=C2=A0 =
=C2=A0During the period of IPv6 transition, both ISP and ICP (Internet<br>=
=C2=A0 =C2=A0Content Provider) care about user&#39;s experience in dual-sta=
ck network.<br>=C2=A0 =C2=A0They hesitate to provide IPv6 to their users du=
e to the fear of poor<br>=C2=A0 =C2=A0IPv6 performance.=C2=A0 Network-based=
 Happy Eyeballs (NHE) is proposed in<br>=C2=A0 =C2=A0this memo as a approac=
h to provide better connectivity to end users<br>=C2=A0 =C2=A0by doing accu=
rate measurement and comparison on IPv6/IPv4 performance<br>=C2=A0 =C2=A0on=
 the network side other than client-side Happy Eyeballs (HE)<br>=C2=A0 =C2=
=A0([RFC8305]).=C2=A0 It works independently with client&#39;s adoption of =
HE.<br><br>=C2=A0 =C2=A0REMOVE BEFORE PUBLICATION: The source of the docume=
nt with test<br>=C2=A0 =C2=A0script is currently placed at GitHub [NHE-GitH=
ub].=C2=A0 Comments and pull<br>=C2=A0 =C2=A0request are welcome.<br><br><b=
r><br><br>Please note that it may take a couple of minutes from the time of=
 submission<br>until the htmlized version and diff are available at <a href=
=3D"http://tools.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br><br>The=
 IETF Secretariat<u></u><u></u></p></div></div></div><p class=3D"MsoNormal"=
 style=3D"margin-left:70.8pt">_____________________________________________=
__ v6ops mailing list <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v=
6ops@ietf.org</a> <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a> <u></u><u>=
</u></p></div><p class=3D"MsoNormal" style=3D"margin-right:0cm;margin-botto=
m:12.0pt;margin-left:35.4pt"><br>******************************************=
****<br>IPv4 is over<br>Are you ready for the new Internet ?<br><a href=3D"=
http://www.consulintel.es" target=3D"_blank">http://www.consulintel.es</a><=
br>The IPv6 Company<br><br>This electronic message contains information whi=
ch may be privileged or confidential. The information is intended to be for=
 the exclusive use of the individual(s) named above and further non-explici=
lty authorized disclosure, copying, distribution or use of the contents of =
this information, even if partially, including attached files, is strictly =
prohibited and will be considered a criminal offense. If you are not the in=
tended recipient be aware that any disclosure, copying, distribution or use=
 of the contents of this information, even if partially, including attached=
 files, is strictly prohibited, will be considered a criminal offense, so y=
ou must reply to the original sender to inform about this communication and=
 delete it.<u></u><u></u></p></div></blockquote></div></div><br>***********=
***********************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href=3D"http://www.consulintel.es" target=3D"_blank">http://www.consulin=
tel.es</a><br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.<br>
<br>
</div>
</blockquote></div>

--0000000000005090790576782920--


From nobody Mon Sep 24 06:32:40 2018
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA5CE130EA6 for <v6ops@ietfa.amsl.com>; Mon, 24 Sep 2018 06:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 7xvD5FB_IjCe for <v6ops@ietfa.amsl.com>; Mon, 24 Sep 2018 06:32:36 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 B78AE12F1A2 for <v6ops@ietf.org>; Mon, 24 Sep 2018 06:32:36 -0700 (PDT)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w8ODTF2U006021 for <v6ops@ietf.org>; Mon, 24 Sep 2018 06:32:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=gc7vK2eveVN/zRtSPmzyF9UQj4zuM3xRA4gASf4Nk6M=; b=AkBi0ea9OSMbFI/uKlL+12SwT3P0pey4lnsbnToytEp8ahrOpThs4RKR+PyEL7sPx9+t Wp2JkPkkZwvfNL21rOg03p/XyfvCrckZM7qihMcKJrgPx9YIKsCjb5Ix7i7clIOMYcYf BkTZrhDVTCMJiGa4LeQ9SX9B3xxceLcZWi+4ibGT5amjzeUl+HnrDUpUh6RnKpC2mNW5 DPr1dO9EZeGe7smK12Tl5/nHtsajP42yVNtGbaCtYJ3wOLsAEnKm8Yr9VhE/XRwyK52j dsvRf4nqy8zkarTrcZ+hG9QSvnCwmmBnhRso4cHcCKujg45PIclamuKXBsqFmmSJPx1z gQ== 
Received: from nam02-cy1-obe.outbound.protection.outlook.com (mail-cys01nam02lp0053.outbound.protection.outlook.com [207.46.163.53]) by mx0b-00273201.pphosted.com with ESMTP id 2mnn69t8f5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <v6ops@ietf.org>; Mon, 24 Sep 2018 06:32:35 -0700
Received: from BYAPR05MB4245.namprd05.prod.outlook.com (20.176.252.26) by BYAPR05MB5271.namprd05.prod.outlook.com (20.177.231.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1164.19; Mon, 24 Sep 2018 13:32:32 +0000
Received: from BYAPR05MB4245.namprd05.prod.outlook.com ([fe80::75fa:69d:40a3:e580]) by BYAPR05MB4245.namprd05.prod.outlook.com ([fe80::75fa:69d:40a3:e580%3]) with mapi id 15.20.1164.017; Mon, 24 Sep 2018 13:32:33 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: draft-fioccola-v6ops-ipv6-alt-mark 
Thread-Index: AdRUCwaEybSqYHE5SW+LF8zdTmZi2Q==
Date: Mon, 24 Sep 2018 13:32:32 +0000
Message-ID: <BYAPR05MB4245FB0D50027E3F5E179D3EAE170@BYAPR05MB4245.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.500.58
dlp-reaction: no-action
x-originating-ip: [108.28.173.248]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB5271; 6:HQ4x7/6yOqflUcZ/GpPdrZg9bsgZlyJfXBzrFu9xCvcpbDXaWIvmK+Gt37URhJLGa/BvzuGlpMRd7VY3hLmdJvymGO+xNdAfgrtY2fjHpZToQrQIpC8MuDdOoBZ3ntJ3VmBGiSDRAXOoakohryraxDCX4RmqK1tZ8d0A/4343gzI1Cb+u3m3NAfCXHmaol66dwg3u8iXx6WC3ZznLCOVT9NPix0aC9axqdDtSQ+RTAT8hzk7S5iEwSq/AtwH+78WOIbGKBYlC3BXMtguE3AnV5fNMMw1UOFWIwzo31lIu5GF0lZeXaN3O97cfs25C9E5OuWlKRESJVOBly852vb4hnERPT6DbI4+tJPkz3grxyi11/FV+z48+8uh7M0osnMpGFGBtkW1UPsXpSJprLf0M0maYBJ7kNz+6+xhLk9LDmtoYeZwul7RyMwyJj/+rA6xOA5+F7q5ZsO44tvK6boDhw==; 5:mXtLTSEJXHAF2xWHwg19SxmZwH3Z6ywZqr4GDgmKpu8saq8P/xIz2e9nlaFORTBDoUUza1aN+6pIZ59+AgtjgVu4B6TYRf28LPk4L+gDHZXCYZj5dJCGpjBoJH1mHoRSs3GjokIqcq6oLHpYuvBK18Fc2QgkcmEU5iD2NKkiqLA=; 7:e5NfIXBnIRhWRg+kmnQwjX8rTQQyxGs67YR+tmC5pa/0F5v7kJLQJZCH7U0lntYjv435+AhlONfOWTahgUXPVNCIAEL22TrWa9apCNyXZbFvgozDknNhNOYA8YWF0KF5VrvTNK60EMnvo1YD8psOVafgmFu30zlta8EH9OoJcJ+AKn44hIkAGSPcy8pxVYK9QdsFOZJKYxnEaW6/pp0NahoNW9PiUR26zZCkwJJYlmpYE7zPSSdlOUCCsIiszb10
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: d5500f25-ee9a-40bc-c076-08d622222edf
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534165)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB5271; 
x-ms-traffictypediagnostic: BYAPR05MB5271:
x-microsoft-antispam-prvs: <BYAPR05MB527109CE5977A5C1BF961ED1AE170@BYAPR05MB5271.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231355)(944501410)(52105095)(6055026)(149066)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123564045)(20161123558120)(201708071742011)(7699051); SRVR:BYAPR05MB5271; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB5271; 
x-forefront-prvs: 0805EC9467
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(376002)(396003)(346002)(136003)(199004)(189003)(106356001)(97736004)(26005)(478600001)(7696005)(14454004)(6506007)(8676002)(81166006)(6116002)(558084003)(4743002)(2906002)(71190400001)(71200400001)(476003)(7736002)(8936002)(186003)(6436002)(53936002)(86362001)(316002)(33656002)(9686003)(3846002)(102836004)(5660300001)(74316002)(99286004)(55016002)(305945005)(81156014)(5640700003)(2900100001)(68736007)(2501003)(66066001)(5250100002)(105586002)(25786009)(486006)(2351001)(256004)(6916009); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB5271; H:BYAPR05MB4245.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: U3kpYbbP0nf1DfJzTAc0G5qWVuctr2j+QNws+mhraN10gDAtpMN97UeHzatqDc+o/Hoglbu+pXx08sB1lC6vPl4wztdFfvTcYA5JWvQX7DW02gqD8Ik04MQTjO+MMD4rGjda1uLCMnxvaafc469JfbjGfviFzVVq1B5cFR35dk4pw5EqtIr3Mvt7JPwCikEG+DTRtm9SnMOaKH8C/dJYt2xAps3Y/BuFCuvg5WNeIg9pH9gWw4avQwtinzp4LktsqNZjtOjs24PTFAZWnRSAtyvL/d5UXFv5Nb288lKp1v4jo24z7Usnj1irkSjdwkV59QbPYRiNLDHstXGD+a4PNXvuWp740ZcjgpiGdDMMCLQ=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: d5500f25-ee9a-40bc-c076-08d622222edf
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Sep 2018 13:32:32.8902 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB5271
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-24_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=444 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809240135
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/FlR51Z2ZAhT8qRdAb4o6b_-a3K4>
Subject: [v6ops] draft-fioccola-v6ops-ipv6-alt-mark
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Sep 2018 13:32:39 -0000

Folks,

Each week between now and IETF 103, we will review and discuss one draft wi=
th an eye towards progressing it.

This week, please review and comment on draft-fioccola-v6ops-ipv6-alt-mark.

                                                      Fred and Ron


From nobody Mon Sep 24 07:11:52 2018
Return-Path: <ietf.dmytro@shytyi.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F10D6130DF0 for <v6ops@ietfa.amsl.com>; Mon, 24 Sep 2018 07:11:50 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=shytyi.net
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 9de9W-2817fb for <v6ops@ietfa.amsl.com>; Mon, 24 Sep 2018 07:11:49 -0700 (PDT)
Received: from sender-of-o52.zoho.eu (sender-of-o52.zoho.eu [31.186.226.248]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6548130DC7 for <v6ops@ietf.org>; Mon, 24 Sep 2018 07:11:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1537798305;  s=hs; d=shytyi.net; i=ietf.dmytro@shytyi.net; h=Date:From:To:Cc:Message-Id:In-Reply-To:References:Subject:MIME-Version:Content-Type; l=21133; bh=ZhB3cbpCghSg7AcRmEfoJtihd4b+yg/UkKLAYtiUX10=; b=LN8LPxAdXxsx6ru5OceOBVQaoviaAWMcVRyd651Ryxt9ez1jg7L/tF0bjf8yO2uB KHFPVcEaz9eDx9wiNnQtqEBaGfY/MJQfbuQ8p7xF+HB8Gb40O/ON0jacpkDZlnNjfiV xGAyLXp0xPvM7U8RHp9r/vDSvb1kqiYFhM1hcZgU=
Received: from sender.zoho.eu (172.26.23.78 [172.26.23.78]) by mx.zoho.eu with SMTPS id 1537798305309411.27206200289936; Mon, 24 Sep 2018 16:11:45 +0200 (CEST)
Received: from mail.zoho.eu by mx.zoho.eu with SMTP id 1537798305237129.1170041697436; Mon, 24 Sep 2018 16:11:45 +0200 (CEST)
Date: Mon, 24 Sep 2018 16:11:45 +0200
From: Dmytro Shytyi <ietf.dmytro@shytyi.net>
To: "v6ops" <v6ops@ietf.org>
Cc: "Alexandre PETRESCU" <alexandre.petrescu@cea.fr>
Message-Id: <1660bebf5d1.11468ecdf27744.5532318214436203526@shytyi.net>
In-Reply-To: <162dab02960.c629492b49487.3795432881225509607@shytyi.net>
References: <162dab02960.c629492b49487.3795432881225509607@shytyi.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_76055_970497029.1537798305234"
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Dw3J2yqoFrOYF73h7_ldvrPYFts>
Subject: [v6ops] New version of the DANIR draft "draft-shytyi-v6ops-danir-02" is available!
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Sep 2018 14:11:51 -0000

------=_Part_76055_970497029.1537798305234
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dear v6opsers, We are happy to introduce the new version (v.02) of the DANI=
R draft. It describes the recommendations and setting that works entirely w=
ith DHCPv6-PD. Name:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0draft-s=
hytyi-v6ops-danir=C2=A0 Revision:=C2=A0=C2=A0=C2=A0=C2=A002=C2=A0 Title:=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0DHCPv6_PD, PDP and NDP Impleme=
ntation in IoT Router (DANIR)=C2=A0 Document date:=C2=A0=C2=A0=C2=A0=C2=A02=
018-09-24=C2=A0 Group:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Indiv=
idual Submission=C2=A0 Pages:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A018=C2=A0 URL: https://www.ietf.org/internet-drafts/draft-shytyi-v6ops-da=
nir-02.txt=C2=A0 Abstract:=C2=A0 This document provides a description of th=
e implementation of Dynamic=C2=A0 Host Configuration Protocol version 6 Pre=
fix Delegation, Neighbour=C2=A0 Discovery Protocol and of the use of the Pa=
cket Data Protocol in an=C2=A0 Internet of Things Router. This Internet of =
Things Router is=C2=A0 connected on a cellular network; it is a DHCPv6-PD C=
lient and it=C2=A0 requests a /56 pool of prefixes from the server; the DHC=
Pv6-PD server=C2=A0 is placed in the PGW and is a part of the cellular infr=
astructure.=C2=A0 After the pool of prefixes is delegated, the Internet of =
Things=C2=A0 Router derives sub-prefixes from the prefix pool; each one of =
these=C2=A0 sub-prefixes is aimed at one ingress interface.=C2=A0 After the=
 Internet of Things Router finishes the network prefix=C2=A0 assignment pro=
cedure, it advertises the network prefixes on the=C2=A0 ingress links by us=
ing the Neighbour Discovery protocol. Finally,=C2=A0 when Hosts receive the=
 sub-prefixes via Router Adverticement=C2=A0 messages, they configure the G=
lobal Unique Address with the Stateless=C2=A0 Address Auto-configuration pr=
otocol.=C2=A0 ______________ Dmytro SHYTYI
------=_Part_76055_970497029.1537798305234
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>=
<meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"></h=
ead><body ><div style=3D'font-size:10pt;font-family:Verdana,Arial,Helvetica=
,sans-serif;color:#00000;'><pre style=3D"box-sizing: border-box; overflow: =
auto; display: block; padding: 0px; margin: 0px 0px 10px; line-height: 1.42=
857; word-break: normal; word-wrap: normal; border: 0px none black; border-=
radius: 4px; text-decoration-style: initial; text-decoration-color: initial=
;" class=3D"wordwrap"><span class=3D"font" style=3D"font-family: &quot;time=
s new roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D=
"font-size: 16px">Dear v6opsers,

We are happy to introduce the new version (v.02) of the DANIR draft.
It describes the recommendations and setting that works entirely with DHCPv=
6-PD.</span></span><font color=3D"#333333" face=3D"Menlo, Monaco, Consolas,=
 Courier New, monospace"><span style=3D"white-space: pre-wrap; background-c=
olor: white;"><span class=3D"font" style=3D"font-family: &quot;times new ro=
man&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-si=
ze: 16px"><br></span></span></span></font></pre><div><span class=3D"highlig=
ht" style=3D""><span class=3D"colour" style=3D""><span class=3D"font" style=
=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;"><s=
pan class=3D"size" style=3D"font-size: 16px">Name:&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;draft-shytyi-v6ops-danir&nbsp;</span></span></span><=
/span><span class=3D"font" style=3D"font-family: &quot;times new roman&quot=
;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px=
"><br></span></span></div><div><span class=3D"highlight" style=3D""><span c=
lass=3D"colour" style=3D""><span class=3D"font" style=3D"font-family: &quot=
;times new roman&quot;, times, serif, sans-serif;"><span class=3D"size" sty=
le=3D"font-size: 16px">Revision:&nbsp;&nbsp;&nbsp;&nbsp;02</span></span><sp=
an><span class=3D"font" style=3D"font-family: &quot;times new roman&quot;, =
times, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">&=
nbsp;</span></span></span></span></span><span class=3D"font" style=3D"font-=
family: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=
=3D"size" style=3D"font-size: 16px"><br></span></span></div><div><span clas=
s=3D"highlight" style=3D""><span class=3D"colour" style=3D""><span class=3D=
"font" style=3D"font-family: &quot;times new roman&quot;, times, serif, san=
s-serif;"><span class=3D"size" style=3D"font-size: 16px">Title:&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DHCPv6_PD, PDP and NDP Implementation i=
n IoT Router (DANIR)</span></span><span><span class=3D"font" style=3D"font-=
family: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=
=3D"size" style=3D"font-size: 16px">&nbsp;</span></span></span></span></spa=
n><span class=3D"font" style=3D"font-family: &quot;times new roman&quot;, t=
imes, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px"><b=
r></span></span></div><div><span class=3D"highlight" style=3D""><span class=
=3D"colour" style=3D""><span class=3D"font" style=3D"font-family: &quot;tim=
es new roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=
=3D"font-size: 16px">Document date:&nbsp;&nbsp;&nbsp;&nbsp;2018-09-24</span=
></span><span><span class=3D"font" style=3D"font-family: &quot;times new ro=
man&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-si=
ze: 16px">&nbsp;</span></span></span></span></span><span class=3D"font" sty=
le=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;">=
<span class=3D"size" style=3D"font-size: 16px"><br></span></span></div><div=
><span class=3D"highlight" style=3D""><span class=3D"colour" style=3D""><sp=
an class=3D"font" style=3D"font-family: &quot;times new roman&quot;, times,=
 serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">Group:&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Individual Submission</span>=
</span><span><span class=3D"font" style=3D"font-family: &quot;times new rom=
an&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-siz=
e: 16px">&nbsp;</span></span></span></span></span><span class=3D"font" styl=
e=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;"><=
span class=3D"size" style=3D"font-size: 16px"><br></span></span></div><div>=
<span class=3D"highlight" style=3D""><span class=3D"colour" style=3D""><spa=
n class=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, =
serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">Pages:&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;18</span></span><span><span c=
lass=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, ser=
if, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">&nbsp;</spa=
n></span></span></span></span><span class=3D"font" style=3D"font-family: &q=
uot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"size" =
style=3D"font-size: 16px"><br></span></span></div><div><span class=3D"highl=
ight" style=3D""><span class=3D"colour" style=3D""><span class=3D"font" sty=
le=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;">=
<span class=3D"size" style=3D"font-size: 16px">URL: </span></span><a target=
=3D"_blank" href=3D"https://www.ietf.org/internet-drafts/draft-shytyi-v6ops=
-danir-02.txt"><span class=3D"font" style=3D"font-family: &quot;times new r=
oman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-s=
ize: 16px">https://www.ietf.org/internet-drafts/draft-shytyi-v6ops-danir-02=
.txt</span></span></a><span><span class=3D"font" style=3D"font-family: &quo=
t;times new roman&quot;, times, serif, sans-serif;"><span class=3D"size" st=
yle=3D"font-size: 16px">&nbsp;</span></span></span></span></span><span clas=
s=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, serif,=
 sans-serif;"><span class=3D"size" style=3D"font-size: 16px"><br></span></s=
pan></div><div><span class=3D"font" style=3D"font-family: &quot;times new r=
oman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-s=
ize: 16px"><br></span></span></div><div><span class=3D"highlight" style=3D"=
"><span class=3D"colour" style=3D""><span class=3D"font" style=3D"font-fami=
ly: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"=
size" style=3D"font-size: 16px">Abstract:</span></span><span><span class=3D=
"font" style=3D"font-family: &quot;times new roman&quot;, times, serif, san=
s-serif;"><span class=3D"size" style=3D"font-size: 16px">&nbsp;</span></spa=
n></span></span></span><span class=3D"font" style=3D"font-family: &quot;tim=
es new roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=
=3D"font-size: 16px"><br></span></span></div><div><span class=3D"highlight"=
 style=3D""><span class=3D"colour" style=3D""><span class=3D"font" style=3D=
"font-family: &quot;times new roman&quot;, times, serif, sans-serif;"><span=
 class=3D"size" style=3D"font-size: 16px">This document provides a descript=
ion of the implementation of Dynamic</span></span><span><span class=3D"font=
" style=3D"font-family: &quot;times new roman&quot;, times, serif, sans-ser=
if;"><span class=3D"size" style=3D"font-size: 16px">&nbsp;</span></span></s=
pan></span></span><span class=3D"font" style=3D"font-family: &quot;times ne=
w roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"fon=
t-size: 16px"><br></span></span></div><div><span class=3D"highlight" style=
=3D""><span class=3D"colour" style=3D""><span class=3D"font" style=3D"font-=
family: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=
=3D"size" style=3D"font-size: 16px">Host Configuration Protocol version 6 P=
refix Delegation, Neighbour</span></span><span><span class=3D"font" style=
=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;"><s=
pan class=3D"size" style=3D"font-size: 16px">&nbsp;</span></span></span></s=
pan></span><span class=3D"font" style=3D"font-family: &quot;times new roman=
&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-size:=
 16px"><br></span></span></div><div><span class=3D"highlight" style=3D""><s=
pan class=3D"colour" style=3D""><span class=3D"font" style=3D"font-family: =
&quot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"size=
" style=3D"font-size: 16px">Discovery Protocol and of the use of the Packet=
 Data Protocol in an</span></span><span><span class=3D"font" style=3D"font-=
family: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=
=3D"size" style=3D"font-size: 16px">&nbsp;</span></span></span></span></spa=
n><span class=3D"font" style=3D"font-family: &quot;times new roman&quot;, t=
imes, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px"><b=
r></span></span></div><div><span class=3D"highlight" style=3D""><span class=
=3D"colour" style=3D""><span class=3D"font" style=3D"font-family: &quot;tim=
es new roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=
=3D"font-size: 16px">Internet of Things Router. This Internet of Things Rou=
ter is</span></span><span><span class=3D"font" style=3D"font-family: &quot;=
times new roman&quot;, times, serif, sans-serif;"><span class=3D"size" styl=
e=3D"font-size: 16px">&nbsp;</span></span></span></span></span><span class=
=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, serif, =
sans-serif;"><span class=3D"size" style=3D"font-size: 16px"><br></span></sp=
an></div><div><span class=3D"highlight" style=3D""><span class=3D"colour" s=
tyle=3D""><span class=3D"font" style=3D"font-family: &quot;times new roman&=
quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-size: =
16px">connected on a cellular network; it is a DHCPv6-PD Client and it</spa=
n></span><span><span class=3D"font" style=3D"font-family: &quot;times new r=
oman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-s=
ize: 16px">&nbsp;</span></span></span></span></span><span class=3D"font" st=
yle=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;"=
><span class=3D"size" style=3D"font-size: 16px"><br></span></span></div><di=
v><span class=3D"highlight" style=3D""><span class=3D"colour" style=3D""><s=
pan class=3D"font" style=3D"font-family: &quot;times new roman&quot;, times=
, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">reques=
ts a /56 pool of prefixes from the server; the DHCPv6-PD server</span></spa=
n><span><span class=3D"font" style=3D"font-family: &quot;times new roman&qu=
ot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16=
px">&nbsp;</span></span></span></span></span><span class=3D"font" style=3D"=
font-family: &quot;times new roman&quot;, times, serif, sans-serif;"><span =
class=3D"size" style=3D"font-size: 16px"><br></span></span></div><div><span=
 class=3D"highlight" style=3D""><span class=3D"colour" style=3D""><span cla=
ss=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, serif=
, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">is placed in =
the PGW and is a part of the cellular infrastructure.</span></span><span><s=
pan class=3D"font" style=3D"font-family: &quot;times new roman&quot;, times=
, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">&nbsp;=
</span></span></span></span></span><span class=3D"font" style=3D"font-famil=
y: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"s=
ize" style=3D"font-size: 16px"><br></span></span></div><div><span class=3D"=
highlight" style=3D""><span class=3D"colour" style=3D""><span class=3D"font=
" style=3D"font-family: &quot;times new roman&quot;, times, serif, sans-ser=
if;"><span class=3D"size" style=3D"font-size: 16px">After the pool of prefi=
xes is delegated, the Internet of Things</span></span><span><span class=3D"=
font" style=3D"font-family: &quot;times new roman&quot;, times, serif, sans=
-serif;"><span class=3D"size" style=3D"font-size: 16px">&nbsp;</span></span=
></span></span></span><span class=3D"font" style=3D"font-family: &quot;time=
s new roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D=
"font-size: 16px"><br></span></span></div><div><span class=3D"highlight" st=
yle=3D""><span class=3D"colour" style=3D""><span class=3D"font" style=3D"fo=
nt-family: &quot;times new roman&quot;, times, serif, sans-serif;"><span cl=
ass=3D"size" style=3D"font-size: 16px">Router derives sub-prefixes from the=
 prefix pool; each one of these</span></span><span><span class=3D"font" sty=
le=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;">=
<span class=3D"size" style=3D"font-size: 16px">&nbsp;</span></span></span><=
/span></span><span class=3D"font" style=3D"font-family: &quot;times new rom=
an&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-siz=
e: 16px"><br></span></span></div><div><span class=3D"highlight" style=3D"">=
<span class=3D"colour" style=3D""><span class=3D"font" style=3D"font-family=
: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"si=
ze" style=3D"font-size: 16px">sub-prefixes is aimed at one ingress interfac=
e.</span></span><span><span class=3D"font" style=3D"font-family: &quot;time=
s new roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D=
"font-size: 16px">&nbsp;</span></span></span></span></span><span class=3D"f=
ont" style=3D"font-family: &quot;times new roman&quot;, times, serif, sans-=
serif;"><span class=3D"size" style=3D"font-size: 16px"><br></span></span></=
div><div><span class=3D"font" style=3D"font-family: &quot;times new roman&q=
uot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 1=
6px"><br></span></span></div><div><span class=3D"highlight" style=3D""><spa=
n class=3D"colour" style=3D""><span class=3D"font" style=3D"font-family: &q=
uot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"size" =
style=3D"font-size: 16px">After the Internet of Things Router finishes the =
network prefix</span></span><span><span class=3D"font" style=3D"font-family=
: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"si=
ze" style=3D"font-size: 16px">&nbsp;</span></span></span></span></span><spa=
n class=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, =
serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px"><br></sp=
an></span></div><div><span class=3D"highlight" style=3D""><span class=3D"co=
lour" style=3D""><span class=3D"font" style=3D"font-family: &quot;times new=
 roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font=
-size: 16px">assignment procedure, it advertises the network prefixes on th=
e</span></span><span><span class=3D"font" style=3D"font-family: &quot;times=
 new roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"=
font-size: 16px">&nbsp;</span></span></span></span></span><span class=3D"fo=
nt" style=3D"font-family: &quot;times new roman&quot;, times, serif, sans-s=
erif;"><span class=3D"size" style=3D"font-size: 16px"><br></span></span></d=
iv><div><span class=3D"highlight" style=3D""><span class=3D"colour" style=
=3D""><span class=3D"font" style=3D"font-family: &quot;times new roman&quot=
;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px=
">ingress links by using the Neighbour Discovery protocol. Finally,</span><=
/span><span><span class=3D"font" style=3D"font-family: &quot;times new roma=
n&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"font-size=
: 16px">&nbsp;</span></span></span></span></span><span class=3D"font" style=
=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;"><s=
pan class=3D"size" style=3D"font-size: 16px"><br></span></span></div><div><=
span class=3D"highlight" style=3D""><span class=3D"colour" style=3D""><span=
 class=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, s=
erif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">when Host=
s receive the sub-prefixes via Router Adverticement</span></span><span><spa=
n class=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, =
serif, sans-serif;"><span class=3D"size" style=3D"font-size: 16px">&nbsp;</=
span></span></span></span></span><span class=3D"font" style=3D"font-family:=
 &quot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"siz=
e" style=3D"font-size: 16px"><br></span></span></div><div><span class=3D"hi=
ghlight" style=3D""><span class=3D"colour" style=3D""><span class=3D"font" =
style=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif=
;"><span class=3D"size" style=3D"font-size: 16px">messages, they configure =
the Global Unique Address with the Stateless</span></span><span><span class=
=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, serif, =
sans-serif;"><span class=3D"size" style=3D"font-size: 16px">&nbsp;</span></=
span></span></span></span><span class=3D"font" style=3D"font-family: &quot;=
times new roman&quot;, times, serif, sans-serif;"><span class=3D"size" styl=
e=3D"font-size: 16px"><br></span></span></div><div><span class=3D"highlight=
" style=3D""><span class=3D"colour" style=3D""><span class=3D"font" style=
=3D"font-family: &quot;times new roman&quot;, times, serif, sans-serif;"><s=
pan class=3D"size" style=3D"font-size: 16px">Address Auto-configuration pro=
tocol.&nbsp;</span></span></span></span><span class=3D"font" style=3D"font-=
family: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=
=3D"size" style=3D"font-size: 16px"><br></span></span></div><div id=3D"Zm-_=
Id_-Sgn"><div><div><span class=3D"font" style=3D"font-family: &quot;times n=
ew roman&quot;, times, serif, sans-serif;"><span class=3D"size" style=3D"fo=
nt-size: 16px">______________</span><span class=3D"size" style=3D"font-size=
: 16px"><br></span></span></div><div><b><span class=3D"font" style=3D"font-=
family: &quot;times new roman&quot;, times, serif, sans-serif;"><span class=
=3D"size" style=3D"font-size: 16px">Dmytro SHYTYI</span></span></b><span cl=
ass=3D"font" style=3D"font-family: &quot;times new roman&quot;, times, seri=
f, sans-serif;"><span class=3D"size" style=3D"font-size: 16px"><br></span><=
/span></div></div></div><div><span class=3D"font" style=3D"font-family: &qu=
ot;times new roman&quot;, times, serif, sans-serif;"><span class=3D"size" s=
tyle=3D"font-size: 16px"><br></span></span></div><div><br></div></div><br><=
/body></html>
------=_Part_76055_970497029.1537798305234--




From nobody Mon Sep 24 08:10:24 2018
Return-Path: <tom@herbertland.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2405130DE6 for <v6ops@ietfa.amsl.com>; Mon, 24 Sep 2018 08:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 tq5BWm9gywgL for <v6ops@ietfa.amsl.com>; Mon, 24 Sep 2018 08:10:21 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 A1D0B130DE5 for <v6ops@ietf.org>; Mon, 24 Sep 2018 08:10:21 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id c25-v6so4040926qtp.6 for <v6ops@ietf.org>; Mon, 24 Sep 2018 08:10:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xv3unFNwaUY5IbUdj8HKV/7xM1rOnI+wHzXmS0Zm1H0=; b=dc7f9QLRKB27tjJLzCQW2tUXUjq43ax6sjGo7c3nxLYslmjdAsgig7eMPZEMIRnI9h L91Ew2f5ikq+4y1DskqvrWwaD2szNrds6tZrnebvcSkLpUzBgCJ4fK9J8ETF+1nfFp4g e1yl6bdZCrOrV+kcW+Bv1/QEii7z47+OVb+8nZhu9v0VC9h1EV4PTbsMH+zcRVeCkGNc qRUBUY6JHYQlOhXQY8s5bK1hRTYW1FxMGio6gdUAQnHQWsXTZe9JeHh+KMECIey95LDc p5vqTTi5KilwEPNR8wpAsfNoxcLXeK2ggPPJ9pzJ5nUdyNlGP0rbQava3hiES4AOSt6U vd8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xv3unFNwaUY5IbUdj8HKV/7xM1rOnI+wHzXmS0Zm1H0=; b=GyLF3hnHFgxTJwu/XIMp+AX38fgVgAHDKbgo3kvZL2RvNpoYmNdXVAsFLa2ZeKFklv F8V1AEkamXIr7C4UqtJoHWDafrIaGHO5B4RdBuqpQSIZ9mKGSPVaxiCDimzTBpYx1T52 eU8+oNZsZkWPMMU5o9Tu3YQX6lF/c+GNYJJBxLJDVcccFZz8m63lPgxK+vRKFTu+5aAC PKvUKGggHQZzRF61gE6ZdnksmhRNIEk7bKhsYrN4GWS9VQjP2WVmj2kiCPiLN1EnwZLj /IgTXdGT0C9DFjnCNDOiVbndjkOJR84oLueWDBxOhyPOVuoKY1hHfnBdak5OO2cUcOOD HT/Q==
X-Gm-Message-State: APzg51CkTcUEN7ndksAr7C2NldR7wqb3CzKfhk1bijeSetuiSdd3ibFc PWIa/sfbDz7tjfdkUdbE0YqX5EMBghLThWGEoxIVmbH12wM=
X-Google-Smtp-Source: ACcGV62EIF/Bn85K6sRf4/FtQYWqs2xLxUWA/9TlJsAqJjdc4HKH7Sxu5A7g73sMD0Te2sq2ajQLmQkOxDeAxQB7RTQ=
X-Received: by 2002:ac8:42dd:: with SMTP id g29-v6mr3169815qtm.162.1537801820527;  Mon, 24 Sep 2018 08:10:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac8:2a94:0:0:0:0:0 with HTTP; Mon, 24 Sep 2018 08:10:20 -0700 (PDT)
In-Reply-To: <BYAPR05MB4245FB0D50027E3F5E179D3EAE170@BYAPR05MB4245.namprd05.prod.outlook.com>
References: <BYAPR05MB4245FB0D50027E3F5E179D3EAE170@BYAPR05MB4245.namprd05.prod.outlook.com>
From: Tom Herbert <tom@herbertland.com>
Date: Mon, 24 Sep 2018 08:10:20 -0700
Message-ID: <CALx6S37hfaaKT_njqdzQvbwK41KkqU+L1qB6DJvF1YNpWekGuA@mail.gmail.com>
To: Ron Bonica <rbonica@juniper.net>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/JFW3NtG3Yd73EjkjbT2FB1oiAZw>
Subject: Re: [v6ops] draft-fioccola-v6ops-ipv6-alt-mark
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Sep 2018 15:10:24 -0000

Comments on the draft:

>From the draft: "Using a new EH assumes that ALL routers in the domain
support this type of headers, which complicates backward compatibility
of the technology."

Hop-by-Hop Options extension header is not new! What I think this
means to say is that a new Hop-by-Hop option would be used. Such an
option could be marked as ignore on unknown option so that legacy
devices don't need to support the option. The "backward compatibility"
problem alluded might be that some intermediate nodes could drop
packets with HBH options. That is a problem of non-conforming
implementations not the protocol, however there are some emerging
mitigations to resolve that issue.

  - RFC8200 allows HBH extension header to be completely ignored
  - RFC6434bis allow implementations to apply reasonable limits to
options to process
  - The use case of this draft is a limited domain, not the open Internet
  - Adding proper support for HBH options (or ignoring them) is
trivial to implement in software stacks (Linux, VPP)
  - Adding support in programmable network devices (P4, eBPF) is straightforward

>From the draft: "There is an advantage of using destination addresses
(DA) to encode the alternate marking method."

I think this would suffer from the same problem that using the flow
label does. Packets within a flow may have different destination
addresses when they transit the domain because of the marking, this
makes routing through ECMP and other steering inconsistent so that out
of order packets result.

>From the draft: "The flow label is an immutable field  recommended to
contain a pseudo-random value, however, often it has the default value
of zero."

"often" is a relative term. I believe all major host OSes not set the
flow label to non-zero by default, so often is becoming "less often"
as end hosts are updated.

"[RFC6436] and [RFC6437] open the door for IPv6 Flow Label to be used
in a controlled environment"

I don't see how they're opening the door to allow bits in the flow
label to be repurposed. The intent of these RFCs was to clarify
requirements including the requirement that forwarding nodes can't
modify a non-zero flow label (except for security reasons).

"In addition it is possible to mention
[I-D.krishnan-6man-header-reserved-bits] that tried to set aside 4
bits from the flow label field for future expansion."

That draft is from 2010 so it's really ancient history :-). IMO, the
ship has already sailed on flow label. It's deployed and being used in
packet steering. Trying to steal bits from it for other purposes is
infeasible at this point.

Tom








On Mon, Sep 24, 2018 at 6:32 AM, Ron Bonica <rbonica@juniper.net> wrote:
> Folks,
>
> Each week between now and IETF 103, we will review and discuss one draft with an eye towards progressing it.
>
> This week, please review and comment on draft-fioccola-v6ops-ipv6-alt-mark.
>
>                                                       Fred and Ron
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Mon Sep 24 11:14:58 2018
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2C7E130EFC; Mon, 24 Sep 2018 11:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.525
X-Spam-Level: 
X-Spam-Status: No, score=-0.525 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.146, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no 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 t1foYxnNdZp1; Mon, 24 Sep 2018 11:14:54 -0700 (PDT)
Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (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 5D319130E8B; Mon, 24 Sep 2018 11:14:54 -0700 (PDT)
Received: by mail-lj1-f176.google.com with SMTP id p89-v6so2987595ljb.3; Mon, 24 Sep 2018 11:14:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zcBO+tJLImc2WFepZpZXh0rAtt82jAxITUJ5SesR+i0=; b=TYOmjzuHAd29zhfO+Tyyd255OU6l3p/Fc1GNvhhVa4g3jPOxDPe9oXA4CjFKaXDSgl XsNDrbbMAlLtgXF06w04xh8wyFXfbVfMceZFv4p4zyTpqCAvS5WblAVA2OEpp6aQ2E5e 8deQDFBSH08NRghigmNSt4N3RoAHbigKUBc8+oRH6W52fw7vXzGKXMWSUX0hrK6r9n+8 mtwkLVcYKkzp1azwIENDx6bfCNFLhgUNgFOXtOlnuFdM0hsL7mCNLMmj7EbTeHmOvpRH Rl2Jx6U5c/V/jw8L2wb3R8nElWWuuAZR8dq/rvIkoXFGPO8WfFOTgo+Z+cpMNn2NolT2 UX1A==
X-Gm-Message-State: ABuFfojQKXwC5svtG9rrefChMJBxNWixN4ybqDfjvAy3bJTMJbsciU3d FrCoriyigeKHubsWeFiSccJVW7IXyza8u1LlazM=
X-Google-Smtp-Source: ACcGV60SuG4ZQvk4o8XRT4yR8w9zLzN6y6yuQFkfhcttl48qORNCaws1BVvqg0v1NWiKYuNXv6oHfFTEGOLzDknzVKY=
X-Received: by 2002:a2e:9dc7:: with SMTP id x7-v6mr18949ljj.142.1537812891742;  Mon, 24 Sep 2018 11:14:51 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com>
In-Reply-To: <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Mon, 24 Sep 2018 11:14:40 -0700
Message-ID: <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com>
To: Song Linjian <songlinjian@gmail.com>
Cc: v6ops@ietf.org, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000024b6290576a1f7e9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/l00WChf2RsJ_C-HkG2wC0k4NIN0>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Sep 2018 18:14:56 -0000

--00000000000024b6290576a1f7e9
Content-Type: text/plain; charset="UTF-8"

At Fri, 21 Sep 2018 14:31:50 +0800,
Davey Song <songlinjian@gmail.com> wrote:

> I just submited a new draft intending to provide better connectivity from
> network side function . Comments are welcome.

Some quick observations:

- I don't see why the intended status is Standards Track.  It seems to
  be a document about an operational practice rather than a new
  protocol feature.

- In general, I wouldn't be excited about placing such complicated
  functionality in the network rather than end hosts.  Sometimes it
  may be justified as a least evil option, but the current description
  of the draft didn't fully convince me

- I suspect the discussion on breaking DNSSEC is way too hand-waving.
  In my general understanding it's generally not accepted at dnsop to
  justify breaking DNSSEC just by saying "it's okay as validation at
  end hosts is not typical".  Especially if it really intends to be
  published as Standards Track I suspect some more detailed discussion
  with a stronger justification will be needed.

--
JINMEI, Tatuya

--00000000000024b6290576a1f7e9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">At Fri, 21 Sep 2018 14:31:50 +0800,<br>Da=
vey Song &lt;<a href=3D"mailto:songlinjian@gmail.com">songlinjian@gmail.com=
</a>&gt; wrote:<br><br>&gt; I just submited a new draft intending to provid=
e better connectivity from<br>&gt; network side function . Comments are wel=
come.<br><br>Some quick observations:<br><br>- I don&#39;t see why the inte=
nded status is Standards Track.=C2=A0 It seems to<br>=C2=A0 be a document a=
bout an operational practice rather than a new<br>=C2=A0 protocol feature.<=
br><br>- In general, I wouldn&#39;t be excited about placing such complicat=
ed<br>=C2=A0 functionality in the network rather than end hosts.=C2=A0 Some=
times it<br>=C2=A0 may be justified as a least evil option, but the current=
 description<br>=C2=A0 of the draft didn&#39;t fully convince me<br><br>- I=
 suspect the discussion on breaking DNSSEC is way too hand-waving.<br>=C2=
=A0 In my general understanding it&#39;s generally not accepted at dnsop to=
<br>=C2=A0 justify breaking DNSSEC just by saying &quot;it&#39;s okay as va=
lidation at<br>=C2=A0 end hosts is not typical&quot;.=C2=A0 Especially if i=
t really intends to be<br>=C2=A0 published as Standards Track I suspect som=
e more detailed discussion<br>=C2=A0 with a stronger justification will be =
needed.<br><br>--<br>JINMEI, Tatuya<br></div></div>

--00000000000024b6290576a1f7e9--


From nobody Mon Sep 24 16:31:12 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED7C130E60; Mon, 24 Sep 2018 16:31:06 -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, FREEMAIL_FROM=0.001, SPF_PASS=-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 AxL_C4u9nRXD; Mon, 24 Sep 2018 16:31:04 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 25B9313104E; Mon, 24 Sep 2018 16:31:04 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id k64-v6so51903oia.13; Mon, 24 Sep 2018 16:31:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=RmyfPwDL8s3uFd6cBlJGXDbzyAKPovzP01l4Vc5eghs=; b=GrtjgX3Sw9EgteXD/jNqHX2UnstEM/2wqqmSoUf9ovkMUnnIN5HXehNbr7mhy0ywuY 3bXRRGiMw/7gc9WG2WqKpZZc2QIEkC+kCwjF5PkORRTuz/zCUS+8UsmAWMnZ0BBwmpiv IclcKKvGhptMau+LOodl4AgD/UQtOQt2BB0YyIYXLqmDye5Pewr7jMhhYb3JSPSRR/k5 uainmsx/RXTCxajV/wAciuSc6Mo9oyBgZMSrm/ji+jhaYxWL/KlHm+WeEXaklF+JML12 ZYubQUMLL0eU6R0jBR0dca9tr3sqHlGgMTGuRu5rHf4yxqd5TzFw9HSgHkRTl8S0RBx1 Mciw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=RmyfPwDL8s3uFd6cBlJGXDbzyAKPovzP01l4Vc5eghs=; b=LdMd335zENMBRE6e0cbaS0jH6YDToqdBpjTxif3Tu7FfB/JzXUQcuosoL8PLfE9DdK 0E3U35s/e/IPfIQG/D73ZZjBYTKn+GHHTTGztxRw2or5I7p52BYvNcdcUpWl8Tu/btki twG1YAjN4ixTjm3txigFTDay2O33YJFojZpgH96AzGiTwPhF5UqvGnouKXCShKBHrK2S bnwqH1mN+7gzzBf3r5A+fbmFRxChnNb1d9s2/BNA/86E5MonYGSgwUpLFAE7uxjOwooW x2uyJukDiSnB1RW0A7+hzh/bDNAkSdZiTgK/l6zi7BORCcz3Exr6jC/wsWvV711+KXFB P8Yg==
X-Gm-Message-State: ABuFfojA0LaoLduz7GlmoMLIUHNTb1g5ul0uzlHuk4KiBTdnWF+JiRc3 4ugWFJ3E9/j/kituI7w+L5I=
X-Google-Smtp-Source: ACcGV626+T4HsjUt5HT0rRvQ19zmJNMjGEKDVqnEpJQMXXXs4ON5rlVb7rGqpvo4BihW2E6xFjhk1g==
X-Received: by 2002:aca:50c1:: with SMTP id e184-v6mr37318oib.264.1537831863418;  Mon, 24 Sep 2018 16:31:03 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::107d? ([2600:8802:5600:1546::107d]) by smtp.gmail.com with ESMTPSA id x23-v6sm229873oie.0.2018.09.24.16.31.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Sep 2018 16:31:02 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <9532441E-1CA5-4106-ACF7-926F857B8DBF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_0E203368-1FAF-453A-B71E-ADE7454546DD"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 24 Sep 2018 16:31:00 -0700
In-Reply-To: <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com>
Cc: Song Linjian <songlinjian@gmail.com>, v6ops@ietf.org, dnsop <dnsop@ietf.org>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lfy84OjfbU52H-zvKsxhbPHk9Ow>
Subject: Re: [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Sep 2018 23:31:07 -0000

--Apple-Mail=_0E203368-1FAF-453A-B71E-ADE7454546DD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Sep 24, 2018, at 11:14 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>=20
> At Fri, 21 Sep 2018 14:31:50 +0800,
> Davey Song <songlinjian@gmail.com> wrote:
>=20
> > I just submited a new draft intending to provide better connectivity =
from
> > network side function . Comments are welcome.
>=20
> Some quick observations:
>=20
> - I don't see why the intended status is Standards Track.  It seems to
>   be a document about an operational practice rather than a new
>   protocol feature.

I think we would have a charter problem as well. V6ops, per charter, can =
produce BCPs and informational documents.

> - In general, I wouldn't be excited about placing such complicated
>   functionality in the network rather than end hosts.  Sometimes it
>   may be justified as a least evil option, but the current description
>   of the draft didn't fully convince me
>=20
> - I suspect the discussion on breaking DNSSEC is way too hand-waving.
>   In my general understanding it's generally not accepted at dnsop to
>   justify breaking DNSSEC just by saying "it's okay as validation at
>   end hosts is not typical".  Especially if it really intends to be
>   published as Standards Track I suspect some more detailed discussion
>   with a stronger justification will be needed.
>=20
> --
> JINMEI, Tatuya
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_0E203368-1FAF-453A-B71E-ADE7454546DD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlupc7QACgkQEhdRnd2G
P+A4gQ/+ONitPdQyh7uj+0Cz7rzyMoHioeqDqWQBT9ZaOGHpL7C5Y+JcloWXZWwa
1LqdVMYBse2gQ5cvBEGztlKL1tu6HXEiNwNiLmjOEi7t24mscNFQ1d0E6DhkO1sX
nLe3eYZWb8DvFdWK0cZKYlOEZ0jJStkogxFMby14+K+Bq8aKrTGIbt3zc+rLlOGu
AxL7OQWlnDcj/EJoii2TWkdlqzkHis2kyhAgxJSw3sYBMjHi8Fd+Ny4VzcQ6dLff
9x4X0MEa9jzqez9f3P1la2V8C0wt0+RWcgwYtTwgyox71CCr7ASXA4Utc9GeEkkq
WGyu84xbHFsJGzqz0GDaIHAqAHuPlPY5AebtnJw1TA+FZezowRP5nrqJRfY3KdnZ
eptohFsvysokiD5qv2zWyIKNETUnIpS1u9KWSkRgKOhULYLmO7TadWXMhtOKPRon
fdp/x3oHU6drpNCHwUjo4x2rN90NyuybQie//S2opldwMP28zfdtQOGhOpri5Dio
Wt0fWWPLjjt4Eb0D3mXRJItdsCsLsLB5DgiWEaaC8w324DZOqBrghch0P3cIplOT
Y9iemJ5++lWzsU2q+BUFyoNQgmlcovqc/kZRNQMR20WCHQlNp2RsiWIB8Wf4jx8w
6uW8uP/Ta8oNl6/HL4z/kx9iyd+3cQcmqaegmWHlrXkuq6daT98=
=kvEP
-----END PGP SIGNATURE-----

--Apple-Mail=_0E203368-1FAF-453A-B71E-ADE7454546DD--


From nobody Mon Sep 24 19:30:25 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 585B21311FA; Mon, 24 Sep 2018 19:30:18 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 IUcmAlZB30wS; Mon, 24 Sep 2018 19:30:16 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 03E1A1311D0; Mon, 24 Sep 2018 19:30:16 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id a189-v6so3146127qkb.2; Mon, 24 Sep 2018 19:30:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GmAHUHxLJZ9Ovp/DdpGZ/3nMSRukQdRIBIdL31PTSsM=; b=Nob5Tcy6gIwCg3NVKVlzlAwyaDhgnB5+tdve1D8Tmatg7+4ESUCw25ztpS7WatodC9 lCHARXmWlYQqfvcx/nt2Y6DdKMiQ/HykXshRhewvqmBormow6IY/e7vIl32JtOO+wdXl gkgrxyhTIxYhxLYLRfXBj3KtqqgUiZWGA3oBbJicgAQyjexPRxIl1l1WaZfIMolLvHo+ e97oqNZIwnsh0bJ5wpC/vd+0pkdKlDe+YQspPZA3TOy+Kc+QvCQTuXLT+N6NViujZjvQ tSyc5LjWjU7yqkN5VWyCkU4BHJKmc7gXVMdJzLccOgWDAposhE7bIt2v6qkZr1JAHuc0 wQDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GmAHUHxLJZ9Ovp/DdpGZ/3nMSRukQdRIBIdL31PTSsM=; b=PkO799oSov7yLeTzYiGBwa/ujW/LiC1NRj3hkyEbAI5Q/tG0xvF3ePw8/XlJZLUjNB vVJIRB4okAzIvI6l+0mJEwDP1fDCOTX+NECnf5q9itbjMK8dpJ9xvpm36KxOIcnS4eC9 XuT0Zg4xNM42SgUTsnyocvl1DfWK5cj6tKebiBb6PFUk9Vuicm5L4HeTcvBdgIC1rig9 FJ5FVYk2JEm/L6AUwHhk7mZs32ZB8jjy4Lb/Oo1W6SULl6QijeD8bG/Q2b5kzxcgszom fBsoAwd02QZK9iOY55DZ5uFg0v5XG3euFs1QnKkYeS1pVdZJEMnNtFU9LBHquuXn6qlx sTzw==
X-Gm-Message-State: ABuFfogt5y3p53T5thw+e6AYClkmZRgS/Tqk4JkiASgpd4c0WtaSnE2E cwEexZzaeNk6TDShCjiO2kY/6aXO9KKXuRXWWhklvSS2
X-Google-Smtp-Source: ACcGV63FIeAlZ/szpr/V++zPLJT2D35RQbKpgQULobe/t/RotUtTx6Lf/Vu5ktyBrDM5gUJ1s8Wmrp4BCkTbxZdS07U=
X-Received: by 2002:a37:15e7:: with SMTP id 100-v6mr1132693qkv.151.1537842615066;  Mon, 24 Sep 2018 19:30:15 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com>
In-Reply-To: <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com>
From: Davey Song <songlinjian@gmail.com>
Date: Tue, 25 Sep 2018 10:30:05 +0800
Message-ID: <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Cc: v6ops@ietf.org, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000caa7750576a8e22c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8Ng2QjroI7bpRBVl2gIdUWlct6I>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Sep 2018 02:30:19 -0000

--000000000000caa7750576a8e22c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Jinmei,

Thanks for your comments. I once had same questions in my mind when this
draft is conceived. I reply inline.

Some quick observations:
>
> - I don't see why the intended status is Standards Track.  It seems to
>   be a document about an operational practice rather than a new
>   protocol feature.
>

I agree with your observation here if the draft intends to share
information and practice. It now goes with Standards Track because the
authors would like to provide a new HE feature(or a framework) on network
side as a peering funtion of client-side HE. I would like to see more
feadback on this issues.

- In general, I wouldn't be excited about placing such complicated
>   functionality in the network rather than end hosts.  Sometimes it
>   may be justified as a least evil option, but the current description
>   of the draft didn't fully convince me
>

Before I put down this draft, I talked with some CPs (content/app
providers) and ISPs, they have motivations and requirement on this.  One
example is Tencent, they are planning to deploy a complicated measurement
network to info their Apps (with a SDK ) which address family they should
try first (their apps use dns over http).  I'm told that Tencent think HE
implemented on each client is too complicated (they have comlicated apps)
and resource consuming. ISP's motivation is easy to understood, they always
try to improve their network connenctivity on both IPv4 and IPv6. I have no
more comment on your saying of evil option=EF=BC=9A=EF=BC=89 Any technology=
 can be used as
evil purpose I think.

- I suspect the discussion on breaking DNSSEC is way too hand-waving.
>   In my general understanding it's generally not accepted at dnsop to
>   justify breaking DNSSEC just by saying "it's okay as validation at
>   end hosts is not typical".  Especially if it really intends to be
>   published as Standards Track I suspect some more detailed discussion
>   with a stronger justification will be needed.
>

Sorry, I admit current txt on breaking DNSSEC is weak. Now it is put
into Security
Considerations as well as the issues on incoherency. I think one way to
avoid it as suggested in  Security Considerations is to artificially delay
the AAAA answers, other than omitting the AAAA record and its RRSIG

Best regards,
Davey

--000000000000caa7750576a8e22c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi Jinmei,<div><br></div=
><div>Thanks for your comments. I once had same questions in my mind when t=
his draft is conceived. I reply inline.=C2=A0</div><div><br></div><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr"><div dir=3D"ltr">Some quick observations:<br><br>- I don&#39;t se=
e why the intended status is Standards Track.=C2=A0 It seems to<br>=C2=A0 b=
e a document about an operational practice rather than a new<br>=C2=A0 prot=
ocol feature.<br></div></div></blockquote><div><br></div><div>I agree with =
your observation here if the draft intends to share information and practic=
e. It now goes with Standards Track because the authors would like to provi=
de a new HE feature(or a framework) on network side as a peering funtion of=
 client-side HE. I would like to see more feadback on this issues.=C2=A0</d=
iv><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr"><div dir=3D"ltr">- In general, I wouldn&#39;t be excited about pl=
acing such complicated<br>=C2=A0 functionality in the network rather than e=
nd hosts.=C2=A0 Sometimes it<br>=C2=A0 may be justified as a least evil opt=
ion, but the current description<br>=C2=A0 of the draft didn&#39;t fully co=
nvince me</div></div></blockquote><div><br></div><div>Before I put down thi=
s draft, I talked with some CPs (content/app providers) and ISPs, they have=
 motivations and requirement on this.=C2=A0 One example is Tencent, they ar=
e planning to deploy a complicated measurement network to info their Apps (=
with a SDK ) which address family they should try first (their apps use dns=
 over http).=C2=A0 I&#39;m told that Tencent think HE implemented on each c=
lient is too complicated (they have comlicated apps) and resource consuming=
. ISP&#39;s motivation is easy to understood, they always try to improve th=
eir network connenctivity on both IPv4 and IPv6. I have no more comment on =
your saying of evil option=EF=BC=9A=EF=BC=89 Any technology can be used as =
evil purpose I think.</div><div><br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">- I suspect the discussi=
on on breaking DNSSEC is way too hand-waving.<br>=C2=A0 In my general under=
standing it&#39;s generally not accepted at dnsop to<br>=C2=A0 justify brea=
king DNSSEC just by saying &quot;it&#39;s okay as validation at<br>=C2=A0 e=
nd hosts is not typical&quot;.=C2=A0 Especially if it really intends to be<=
br>=C2=A0 published as Standards Track I suspect some more detailed discuss=
ion<br>=C2=A0 with a stronger justification will be needed.<br></div></div>=
</blockquote><div>=C2=A0</div><div>Sorry, I admit current txt on breaking D=
NSSEC is weak. Now it is put into=C2=A0<span style=3D"color:rgb(0,0,0);font=
-size:13.3333px">Security Considerations as well as the issues on=C2=A0</sp=
an><span style=3D"color:rgb(0,0,0);font-size:13.3333px">incoherency. I thin=
k one way to avoid it as suggested in=C2=A0</span>=C2=A0<span style=3D"colo=
r:rgb(0,0,0);font-size:13.3333px">Security Considerations=C2=A0</span><span=
 style=3D"color:rgb(0,0,0);font-size:13.3333px">is to=C2=A0</span><span sty=
le=3D"color:rgb(0,0,0);font-size:13.3333px">artificially delay the AAAA ans=
wers, other than omitting the AAAA record and its RRSIG</span></div><div><b=
r></div><div>Best regards,</div><div>Davey=C2=A0</div></div></div></div></d=
iv>

--000000000000caa7750576a8e22c--


From nobody Tue Sep 25 00:20:22 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E09131234 for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 00:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 3Un-HMGPPTRH for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 00:20:18 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BDC8131232 for <v6ops@ietf.org>; Tue, 25 Sep 2018 00:20:18 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 0FF14438CC for <v6ops@ietf.org>; Tue, 25 Sep 2018 09:20:16 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 00D97438CB; Tue, 25 Sep 2018 09:20:16 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id E524720D2E; Tue, 25 Sep 2018 09:20:15 +0200 (CEST)
Date: Tue, 25 Sep 2018 09:20:15 +0200
From: Gert Doering <gert@space.net>
To: Davey Song <songlinjian@gmail.com>
Cc: ???????????? <jinmei@wide.ad.jp>, v6ops@ietf.org, dnsop <dnsop@ietf.org>
Message-ID: <20180925072015.GV11393@Space.Net>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4M0PUEbNdToDeVupXBfVzRXYBdY>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Sep 2018 07:20:21 -0000

Hi,

On Tue, Sep 25, 2018 at 10:30:05AM +0800, Davey Song wrote:
> Before I put down this draft, I talked with some CPs (content/app
> providers) and ISPs, they have motivations and requirement on this.  One
> example is Tencent, they are planning to deploy a complicated measurement
> network to info their Apps (with a SDK ) which address family they should
> try first (their apps use dns over http).  I'm told that Tencent think HE
> implemented on each client is too complicated (they have comlicated apps)
> and resource consuming. 

This hints at a general misunderstanding on how "The Internet" works.

Talking to the local ISP on "what would you recommend, IPv4 or IPv6?"
can give an indication, but if the server you're trying to talk to 
is on the other side of the world, the local ISP's preference for 
IPv4-vs-IPv6 might be the opposite of what actually works better to
reach said server.  There are many networks on the path...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Tue Sep 25 02:09:28 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB16713114A; Tue, 25 Sep 2018 02:09:26 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 QWRMvV6XOhCU; Tue, 25 Sep 2018 02:09:24 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 65F2D130F24; Tue, 25 Sep 2018 02:09:24 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id l16-v6so12026838qtq.10; Tue, 25 Sep 2018 02:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lASZSwvDTek2PBdiKxvcOvFKp1r/UdQ7Jsn1sijf2SQ=; b=hmRG/VvGVYFafdHO98vpLNiKoFP5Kkt1DBpJsNwWXaXEU3qCTloRHcv3vEXZC80HJJ OsMklCadW9HJ0JWfrAIXYuk6LWUWliCnV/s4fr3YsG+NS3H9pZ9pF+cCMPhDDIy6F3dQ rwn3zvy8O71Ho7QmkL7i//locmhuf2OdTdNLRT3WJWl4BJJjopAPG/ia49TMYXLoWgAW l0rWg+tq8YRywFeILaiXpWArZTLm+Rnx3N8LJ7Ya+yFDYseGjOj2OQm9htUQexRrnouf W8d+zzUW6FJBBNWSoZI+VOvbGewrDm8YnyXDNcN91ekGV3Olpa1SBrtqe5zjqDuvZjA5 JLUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lASZSwvDTek2PBdiKxvcOvFKp1r/UdQ7Jsn1sijf2SQ=; b=fkDOVy3x9kNxR/b6XX9vvt3PoRuu6ptaSaUXW+ux4N8SxKk0s1ZucD6kGad1K1c+QJ DCSWuKUsOHK8ug4arGRUBQlWvetcUZrejzhcjHvWLJ7sm5FoS/GAIRABrJzqHCcEsZ0U Wi0huQlKAvsqIn6Ms0rwTWKleTveEUX0wzXXVp2w6lK0Kj+x1Tl9IkXSHbPGrz460xkX vL3kxJMZmysmYyaehfP05ilZDsArdSKUIdc3k2Ljiw3qQmFBldmCrWxgr6yKEVq6u41+ rwT72Sb+8OrZ+hD6D7DppOZYzZ3j7jC1GSlnjakRA1qFEf+W5ir0ZPSBzKj+b7ruM8GZ whag==
X-Gm-Message-State: ABuFfoiR6b3DsXid8iw2upvpEQ3E6HbaCdwj7HnTsNCUxrsRd2irUO8i 9Kfv68S1OoKtjjnfxakvD88LRv6v+4uwet2b3Lw=
X-Google-Smtp-Source: ACcGV63OwysZDGkwbeukmolAyKoFOLR+B4qjsCaQE+4peJ8vmwKarE353qaY89YUFvND0W3mXnh/ne4lNzEePMEELBs=
X-Received: by 2002:ac8:3414:: with SMTP id u20-v6mr17402qtb.237.1537866563454;  Tue, 25 Sep 2018 02:09:23 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>
In-Reply-To: <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>
From: Davey Song <songlinjian@gmail.com>
Date: Tue, 25 Sep 2018 17:09:13 +0800
Message-ID: <CAAObRXKVVu3qkBGAdRzXaX1=qr498__Fg8hhqWPg3uEDFxm2Ow@mail.gmail.com>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Cc: v6ops@ietf.org, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003a0b390576ae7666"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/eQiWWNVnUTAUZ2mG_mvIWwDKFcU>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Sep 2018 09:09:27 -0000

--0000000000003a0b390576ae7666
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

To get to know the current status of HE , I did a simple test on my handy
devices visit top 20 website or open existing apps (currently only DNS). I
captured AAAA&A DNS query pairs (intervel less than 10s) and count HE query
pairs whoes interval less than 100ms. There is a prelimiary result:

1) My laptop with web browsers (Chrome, firfox, Sogou, QQ, 360). All
browers support HE in DNS in which  more than 90% AAAA&A query pairs are HE
query pairs.
2) My Andriod phone(V7.1.1).  262 AAAA&A query pairs out of  802 pairs . It
means only 32.6% DNS queries supported by HE. Not 32.6% Apps on my phone,
because some Apps may sent more DNS queries than others. I made a
statisitcs on interval of all AAAA& A pairs (statistics if no HE pairs
included), the average interval is 409ms (534ms), the median delay is
198ms(324ms), and the maximum is 7,135ms. If hostname resolution is not
support HE, the connection attampt will also be delayed accrodingly.
3) My ipad (V11.4.1).  1208 AAAA& A query pairs out of 1216 pairs. It means
more than 99% DNS queries supported by HE. It is true that IOS asynchronous
DNS API. But it is unkonwn on how many apps make connection asynchronously.
It will be investigated later.

In conlusion, HE is not widely supported at least in Android  platform.
Large companies can invest and implement it for their users. But it is not
fair for small Apps providers to endure such competitive disadvantage due
to IPv6 deployment.

- In general, I wouldn't be excited about placing such complicated
>>   functionality in the network rather than end hosts.  Sometimes it
>>   may be justified as a least evil option, but the current description
>>   of the draft didn't fully convince me
>>
>
> Before I put down this draft, I talked with some CPs (content/app
> providers) and ISPs, they have motivations and requirement on this.  One
> example is Tencent, they are planning to deploy a complicated measurement
> network to info their Apps (with a SDK ) which address family they should
> try first (their apps use dns over http).  I'm told that Tencent think HE
> implemented on each client is too complicated (they have comlicated apps)
> and resource consuming. ISP's motivation is easy to understood, they alwa=
ys
> try to improve their network connenctivity on both IPv4 and IPv6. I have =
no
> more comment on your saying of evil option=EF=BC=9A=EF=BC=89 Any technolo=
gy can be used as
> evil purpose I think.
>


Davey

--0000000000003a0b390576ae7666
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div class=3D"gmail_quote"><div>To get to know the current status of HE =
, I did a simple test on my handy devices visit top 20 website or open exis=
ting apps (currently only DNS). I captured AAAA&amp;A DNS query pairs (inte=
rvel less than 10s) and count HE query pairs whoes interval less than 100ms=
. There is a prelimiary result:</div><div><br></div><div>1) My laptop with =
web browsers (Chrome, firfox, Sogou, QQ, 360). All=C2=A0 browers support HE=
 in DNS in which=C2=A0 more than 90% AAAA&amp;A query pairs are HE query pa=
irs.</div><div>2) My Andriod phone(V7.1.1).=C2=A0 262 AAAA&amp;A query pair=
s=C2=A0out of=C2=A0 802 pairs=C2=A0. It means only 32.6% DNS queries suppor=
ted by HE. Not 32.6% Apps on my phone, because some Apps may sent more DNS =
queries than others. I made a statisitcs on interval of all AAAA&amp; A pai=
rs (statistics if no HE pairs included), the average interval is 409ms (534=
ms), the median delay is 198ms(324ms), and the maximum=C2=A0is 7,135ms. If =
hostname resolution is not support HE, the connection attampt will also be =
delayed accrodingly.=C2=A0</div><div>3) My ipad (V11.4.1).=C2=A0 1208 AAAA&=
amp; A query pairs out of 1216 pairs. It means more than 99% DNS queries su=
pported by HE. It is true that IOS=C2=A0<span style=3D"color:rgb(0,0,0);fon=
t-size:13.3333px">asynchronous DNS API. But it is unkonwn on how many apps =
make connection=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13.33=
33px">asynchronously. It will be investigated later.</span></div><div><br><=
/div><div>In conlusion, HE is not widely supported at least in Android=C2=
=A0 platform. Large companies can invest and implement it for their users. =
But it is not fair for small Apps providers to endure such competitive disa=
dvantage due to IPv6 deployment.</div><div><br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"l=
tr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"ltr"><div dir=3D"ltr">- In general, I wouldn&#39;t be exc=
ited about placing such complicated<br>=C2=A0 functionality in the network =
rather than end hosts.=C2=A0 Sometimes it<br>=C2=A0 may be justified as a l=
east evil option, but the current description<br>=C2=A0 of the draft didn&#=
39;t fully convince me</div></div></blockquote><div><br></div><div>Before I=
 put down this draft, I talked with some CPs (content/app providers) and IS=
Ps, they have motivations and requirement on this.=C2=A0 One example is Ten=
cent, they are planning to deploy a complicated measurement network to info=
 their Apps (with a SDK ) which address family they should try first (their=
 apps use dns over http).=C2=A0 I&#39;m told that Tencent think HE implemen=
ted on each client is too complicated (they have comlicated apps) and resou=
rce consuming. ISP&#39;s motivation is easy to understood, they always try =
to improve their network connenctivity on both IPv4 and IPv6. I have no mor=
e comment on your saying of evil option=EF=BC=9A=EF=BC=89 Any technology ca=
n be used as evil purpose I think.</div></div></div></div></div></blockquot=
e><div><br></div><div>=C2=A0</div><div>Davey=C2=A0</div></div></div></div><=
/div></div></div></div></div></div></div>

--0000000000003a0b390576ae7666--


From nobody Tue Sep 25 02:31:08 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741CB13125B; Tue, 25 Sep 2018 02:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 2PxzNppv6LVG; Tue, 25 Sep 2018 02:30:59 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 110F0131264; Tue, 25 Sep 2018 02:30:59 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id h22-v6so4607463qtr.13; Tue, 25 Sep 2018 02:30:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=59ikVPtR3mzfWb9E1m7MNobP18oJNbJTzDU3iiTj1ZQ=; b=XrK7BfMjFWKHINKdLqZcJESKXlzRj7XevK+uyKfFf+JacEsdOjuCIT6H0WDjRcw/Dp UNK865J+pwom/n8MZJiArmHFAOSxBf3aRg0L/+D8Ue+liJDf6r2l+OuyV2OHuDU4zyGA EzrdaMnvpCvMUwBfNxxedSd6c5IyXpqiRcrHHP1z5bmxSq+mBgF8lopowfGYFrZef8lv HQFNU7f0rmkrxC5EVG6vjxCQLiogfDI9A31kousrG4hJ116eXeTwkE4Qpvr7+SvR5DNN rYT7wonNdl1y78A13NJN74QnKq3S5cxVof/CV6nJADEgccidKwjk/yJwRPPoIQiuZXlN Fg6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=59ikVPtR3mzfWb9E1m7MNobP18oJNbJTzDU3iiTj1ZQ=; b=Mw9DbAaxeEJoN4E4GcpnMef5xLeysPtVWs17EsJCOao/bJH6OC3YoFzLIT8Z6prWuM JKMg9bfCiIHzP3uDqkL6ejAPsehnzm6l3sS16dfx6BJ33oECRsGnEMUmeuiUvDdXrMbf XeALmcsh0dXPzHFNp5EuAoQKU91pdnMrv1c51grukveBbcEQ0Lape5VahC8TLdIEvMO8 LT/S9lhZ7O3GG1r1aENi0IqyYFvw9mrbXEQK+p26HXfznQa87gB27y0l35PGIYHLUKqm enN9d44XaykfjkVi1CWNxt/rarWDHWI3SqSZ4AAOohJEPKJNAFHMjwRWN5AL3UEMXgXy oAyg==
X-Gm-Message-State: ABuFfojPYKYkFfrxW0/ZehSp/kn+bkz9+iInH9kNqfujBhvOW90YxNQ9 khhwb/kHg57+NTBFuG3D4gMeNWgMbvNFzQSiqqEEdA==
X-Google-Smtp-Source: ACcGV63eoUeGfO8PTNs2LCfdKXrmtZkBiKRCwFphfa2eyLZJwF76QhHsQFvCeesgLnHwvDd7gsl7m5HBn9RGFmh4Pvw=
X-Received: by 2002:a0c:ab15:: with SMTP id h21-v6mr105466qvb.96.1537867858183;  Tue, 25 Sep 2018 02:30:58 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net>
In-Reply-To: <20180925072015.GV11393@Space.Net>
From: Davey Song <songlinjian@gmail.com>
Date: Tue, 25 Sep 2018 17:30:48 +0800
Message-ID: <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com>
To: gert@space.net
Cc: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, v6ops@ietf.org,  dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000660a0c0576aec383"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gRPZ7SObtXeZt3hlNg9BXH0VF-M>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Sep 2018 09:31:00 -0000

--000000000000660a0c0576aec383
Content-Type: text/plain; charset="UTF-8"

>
> This hints at a general misunderstanding on how "The Internet" works.
>
> Talking to the local ISP on "what would you recommend, IPv4 or IPv6?"
> can give an indication, but if the server you're trying to talk to
> is on the other side of the world, the local ISP's preference for
> IPv4-vs-IPv6 might be the opposite of what actually works better to
> reach said server.  There are many networks on the path...
>
> Talking to far-end server need measurement on end-to-end path.So the
accurracy of end-to-end measurement is the key. There are acturally lots of
practice in the fields of NPM and APM. People can do it well.

Davey

--000000000000660a0c0576aec383
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
This hints at a general misunderstanding on how &quot;The Internet&quot; wo=
rks.<br>
<br>
Talking to the local ISP on &quot;what would you recommend, IPv4 or IPv6?&q=
uot;<br>
can give an indication, but if the server you&#39;re trying to talk to <br>
is on the other side of the world, the local ISP&#39;s preference for <br>
IPv4-vs-IPv6 might be the opposite of what actually works better to<br>
reach said server.=C2=A0 There are many networks on the path...<br><br></bl=
ockquote><div>Talking to far-end server need measurement on end-to-end path=
.So the accurracy of end-to-end measurement is the key. There are acturally=
 lots of practice in the fields of NPM and APM. People can do it well.=C2=
=A0<br></div><div><br></div><div>Davey=C2=A0=C2=A0</div></div></div>

--000000000000660a0c0576aec383--


From nobody Tue Sep 25 03:25:30 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1469131280; Tue, 25 Sep 2018 03:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 2bPSbiqeNQR2; Tue, 25 Sep 2018 03:25:19 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAC2613128B; Tue, 25 Sep 2018 03:25:19 -0700 (PDT)
Received: from astfgl.hanazo.no (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id B4B5CFECBEC7; Tue, 25 Sep 2018 10:25:18 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 762F5671DE7; Tue, 25 Sep 2018 12:25:16 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com>
Date: Tue, 25 Sep 2018 12:25:16 +0200
Cc: Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, V6 Ops List <v6ops@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com>
To: Davey Song <songlinjian@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/WZ8t3MtlBW9r4M0zvT1ip2i_tQI>
Subject: Re: [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Sep 2018 10:25:22 -0000

> This hints at a general misunderstanding on how "The Internet" works.
>=20
> Talking to the local ISP on "what would you recommend, IPv4 or IPv6?"
> can give an indication, but if the server you're trying to talk to=20
> is on the other side of the world, the local ISP's preference for=20
> IPv4-vs-IPv6 might be the opposite of what actually works better to
> reach said server.  There are many networks on the path...
>=20
> Talking to far-end server need measurement on end-to-end path..So the =
accurracy of end-to-end measurement is the key. There are acturally lots =
of practice in the fields of NPM and APM. People can do it well.=20

But in the general case the network cannot.
Think host multi-homing.

Ole=


From nobody Tue Sep 25 19:49:37 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B4F5130DEC; Tue, 25 Sep 2018 19:49:30 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 HlDrrl7mrZuk; Tue, 25 Sep 2018 19:49:26 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 4789512F1A6; Tue, 25 Sep 2018 19:49:26 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id x23-v6so15768956qtr.1; Tue, 25 Sep 2018 19:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8+XR/iqZdffMkNcRFjerGm/IweGUmuyhUanLxUnPf4c=; b=hIgOSAiaEqf5b0BLOLpKM+uniu3jOY29VGaRDFx7OB5IGd3MJRmZsL3NJkZ3JkUoyC lTs3RYH7p2ZuoZPrOq/7es5Mb71gOXo7875GGOdHaUBaLYTJsRXSdDOa0PxFg5R/olX7 upjE0D080g+YoZlZvqXUI43MGK4+wQDkREEwR5ElyDWicebKf2UV4auuqwtcuaui57f8 N1F1z1A62QgVYbnKXj5qZkqGtwMfVfJQeR/9a6lZDMdnX/MHU8dZqW/S7puegmApruLO x7b7C6YsRkrrpLCvrmvLL3MsPSQ1fSiqYitZ5c+YPsN1RgDSngsJffZEdwjmjB9VfsHn bRqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8+XR/iqZdffMkNcRFjerGm/IweGUmuyhUanLxUnPf4c=; b=RPNN2sywVfjJ4h5scBANkIjfVfjRAj3zzHyuciIQp37z2YCwQE3ASGj5hr98e1DIsx JO7pRr0bN8vNumSNaCyB5I0zcgj60nGk8bpV1/MUX0p/9CfbqQkAkGK7mQTTD7vkVXi+ yAO7pujUtZ23NG5cW5/zpifiC9rlXE5a7s6iq/7Mjgp25wCpdmN4MtJLzc0AyDO3bFEl JJmZ9iEs7CJ7GThX9uG5bJnSkIQ0EjxfNQnOpHPCeS1DNwSH4dIbNBhfKQe1HvlFZYS/ gzc6rWh5jI1lvlsw7pcutuoH4sRFgw5JaCgq4lZGq2yszVKPKh0Kh77mTimrUQMHxwrV tJDw==
X-Gm-Message-State: ABuFfohfGFCkzqhHFdl/36dTKYQnZHTamRRC29o584/3GTZ2b33cfecH /0lvebF+x4d2sLPh/0YQasqUcRrFVb0FnetAtiM=
X-Google-Smtp-Source: ACcGV63ntk7sAm8zivJDcHXSFvCZrfb3sYwMha4V4NcNyy8FG8HI6wg4VnHIgyLKjcAOLtKDhT2T/5m8+rVAFaghJIg=
X-Received: by 2002:ac8:85c:: with SMTP id x28-v6mr3078108qth.90.1537930165449;  Tue, 25 Sep 2018 19:49:25 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org>
In-Reply-To: <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org>
From: Davey Song <songlinjian@gmail.com>
Date: Wed, 26 Sep 2018 10:49:17 +0800
Message-ID: <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com>
To: otroan@employees.org
Cc: Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, v6ops@ietf.org,  =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary="0000000000003377ca0576bd4552"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3RaFty3KVLpnMNp74pTiYkfL7fA>
Subject: Re: [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 02:49:30 -0000

--0000000000003377ca0576bd4552
Content-Type: text/plain; charset="UTF-8"

>
> But in the general case the network cannot.
> Think host multi-homing.
>

Yes or no.

Generally speaking the races of IPv6 and IPv4 connections on both network
and client are going to be suffered by netowrk dynamics, including
Multi-homing,  route flaps, roaming, or other network falilures. Extremely,
a client can get a better IPv6 connection in one second (when IPv6 win the
race), and lose it in next second. In such case, more sophisticated
measurement should be done(on client or network) , for a longer period, on
statistics of RTT and Failure rate, or combinations of them. But in IMHO,
the assumption of HE is relatively stable network for short exchange
connections. The dynamics exits but relatively rare or no notable impact on
HE. So I see no such discussion in RFC8035.

Davey

--0000000000003377ca0576bd4552
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">But in the general case the network cannot.<br=
>
Think host multi-homing.<br></blockquote><div><br></div><div>Yes or no.=C2=
=A0</div><div><br></div><div>Generally speaking the races of IPv6 and IPv4 =
connections on both network and client are going to be suffered by netowrk =
dynamics, including Multi-homing,=C2=A0 route flaps,=C2=A0roaming, or other=
 network falilures. Extremely, a client can get a better IPv6 connection in=
 one second (when IPv6 win the race), and lose it in next second. In such c=
ase, more sophisticated measurement should be done(on client or network) , =
for a longer period, on statistics of RTT and Failure rate, or combinations=
 of them. But=C2=A0in IMHO, the assumption of HE is relatively stable netwo=
rk for short exchange connections. The dynamics exits but relatively rare o=
r no=C2=A0notable impact on HE. So I see no such discussion in RFC8035.</di=
v><div><br></div><div>Davey</div></div></div></div></div></div></div></div>

--0000000000003377ca0576bd4552--


From nobody Tue Sep 25 19:58:56 2018
Return-Path: <ggm@algebras.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEF50130DFE for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 19:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.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 9x1cCiPPlpmD for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 19:58:43 -0700 (PDT)
Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) (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 96D5512F1A6 for <v6ops@ietf.org>; Tue, 25 Sep 2018 19:58:43 -0700 (PDT)
Received: by mail-wr1-x444.google.com with SMTP id b11-v6so9117780wru.9 for <v6ops@ietf.org>; Tue, 25 Sep 2018 19:58:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ubMDddtEan7kF6ZNx6qqKlGT5AUsFm9DfU3QT89tOPM=; b=UcGYNQa0Xh6NwshTnuqpwC3Vlgfy0ShhOM4zkCtZ80l/vvRZ63qrMqn7vlB8mMmSva ZsgUo64h5/Hj1I3eRPz9Fd6FigsDUBZe81rYGwhN4W9AOWITZvYSFHaY99A/DQ/lO52q jhppoT0KFpBuCPd4XzTjeL+M63XSNao0qCzXazwrDYPeBLEF9Hh+Bps7hAmzwQnCihc0 s5AF9+pkfw/N30sinieA/WegXo+5e2//ks/deXu8P9pTTxM4ZdGsBvyeVrHwbbPVrnOT v9lyldVlNoWRsrn4zIhfIeIcFcyU7mQMC1uWu0Ug8wxXyjNhsLWK9XRaVB/1GrzaA5km Ts8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ubMDddtEan7kF6ZNx6qqKlGT5AUsFm9DfU3QT89tOPM=; b=rbEUBjeCTi7NQ6sMhJat1mcWAyR1Epde6pD37p7csRAI33xoC6L2Ow4O0Fy3R51qAF pB+WM5IspwbpBaheAdRE/VC+9D6m+5DIG8Ka8s4j03qvqtccpNOQD/Gs00z5cf1RJA7b 0rlAqsQrlqyYpfrGPU5xmWZnXj5PBpjDuaFGkgyy5pNL7Zwc5/4eF470RseJyVjW4pBt nssvtZdPRvYR9VNXwPeLKkLhSdilzUUHRxfEbWVdqIk98tdlxRmtrgUQy6KG1VuYXfxU sKcC0OA6tK3ymhqa3O8M7Xv1ewy9JEVvd0/J0bYdpa2amIE8f7US0HUAytsbUrmRwzyg vN4A==
X-Gm-Message-State: ABuFfojPRHRr5uHhTBGGFlbOI7a7VrUaFP9AmWls8N67NTJDlO/LR4GQ FEsqKEAP07J1W40wQ6Zn1+AXkWR2xGvC2pV/2TaAaA==
X-Google-Smtp-Source: ACcGV60P5piucyHp6ZGpPmKjINUkBN6R1IUezWZ0bphs0tAbvIEqmjJ3zMfWZQR3LH3iDirShAGuorm4ugRNYkaaHe8=
X-Received: by 2002:adf:ba12:: with SMTP id o18-v6mr3052547wrg.249.1537930722003;  Tue, 25 Sep 2018 19:58:42 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com>
In-Reply-To: <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 26 Sep 2018 12:58:30 +1000
Message-ID: <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com>
To: dnsop WG <dnsop@ietf.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/QyxCBRi2GjpZwd8WCUDBwNy6dsE>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 02:58:49 -0000

I have said before, but don't know if I still adhere to it, but
anyways, here's a question: How *long* do people think a biassing
mechanism like HE is a good idea?

 * is it a good idea *forever*

 * or is it a transition path mechanism which has an end-of-life?

 * how do we know, when its at end-of-life?

I used to love HE. I now have a sense, I'm more neutral. Maybe, we
actually don't want modified, better happy eyeballs, because we want
simpler, more deterministic network stack outcomes with less bias
hooks?

I barely register if I an on v4 any more. I assume I'm on 6 on many
networks. This is as an end-user. I guess if I am really an end user,
this belief I understand TCP and UDP is false, and I should stop
worrying (as an end user)
On Wed, Sep 26, 2018 at 12:49 PM Davey Song <songlinjian@gmail.com> wrote:
>>
>> But in the general case the network cannot.
>> Think host multi-homing.
>
>
> Yes or no.
>
> Generally speaking the races of IPv6 and IPv4 connections on both network=
 and client are going to be suffered by netowrk dynamics, including Multi-h=
oming,  route flaps, roaming, or other network falilures. Extremely, a clie=
nt can get a better IPv6 connection in one second (when IPv6 win the race),=
 and lose it in next second. In such case, more sophisticated measurement s=
hould be done(on client or network) , for a longer period, on statistics of=
 RTT and Failure rate, or combinations of them. But in IMHO, the assumption=
 of HE is relatively stable network for short exchange connections. The dyn=
amics exits but relatively rare or no notable impact on HE. So I see no suc=
h discussion in RFC8035.
>
> Davey
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Tue Sep 25 21:25:29 2018
Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3A71277C8; Tue, 25 Sep 2018 21:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=delong.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 0BsY6uS2kAGE; Tue, 25 Sep 2018 21:25:19 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 8082A12426A; Tue, 25 Sep 2018 21:25:18 -0700 (PDT)
Received: from kiev.delong.com (kiev.delong.com [IPv6:2620:0:930:0:0:0:200:5]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id w8Q4PGAC001374 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 25 Sep 2018 21:25:16 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com w8Q4PGAC001374
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1537935917; bh=mhMtBqZSYdMdaM3t0S79V+/VVWkKs5isUL1LXhCi50E=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=RXV0c4niI3ncu85DR3RCcg2Lw1EG6jyNSVLxr3GNaU8BFlRc1Bcfap/DEtBaAK5Tb olm8hF9citebvAq+VY6drtJRhjbeelrljv3Tg3SWSi9zhom9R3u9qDn4K2gktq63/O cnxEdplkrBVOB2ZxVYtjjUOB1oMx5stl+gB77btk=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com>
Date: Tue, 25 Sep 2018 21:25:16 -0700
Cc: dnsop WG <dnsop@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6F477B0-28DF-42C3-A8F6-F46BA2E0D119@delong.com>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.3445.9.1)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Tue, 25 Sep 2018 21:25:17 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UYkElnTqajzZ6EsuZZYl_7IURTE>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 04:25:22 -0000

It was never a good idea. It was a necessary evil (kind of like NAT in =
that regard) to expeditiously deal with a somewhat tenacious (at the =
time) problem which has since been given a significantly better =
solution, but so long as the workaround appears to be working, people =
are loathe to put in the effort of implementing the actual solution.

sigh=E2=80=A6 Human nature.

Owen


> On Sep 25, 2018, at 19:58 , George Michaelson <ggm@algebras.org> =
wrote:
>=20
> I have said before, but don't know if I still adhere to it, but
> anyways, here's a question: How *long* do people think a biassing
> mechanism like HE is a good idea?
>=20
> * is it a good idea *forever*
>=20
> * or is it a transition path mechanism which has an end-of-life?
>=20
> * how do we know, when its at end-of-life?
>=20
> I used to love HE. I now have a sense, I'm more neutral. Maybe, we
> actually don't want modified, better happy eyeballs, because we want
> simpler, more deterministic network stack outcomes with less bias
> hooks?
>=20
> I barely register if I an on v4 any more. I assume I'm on 6 on many
> networks. This is as an end-user. I guess if I am really an end user,
> this belief I understand TCP and UDP is false, and I should stop
> worrying (as an end user)
> On Wed, Sep 26, 2018 at 12:49 PM Davey Song <songlinjian@gmail.com> =
wrote:
>>>=20
>>> But in the general case the network cannot.
>>> Think host multi-homing.
>>=20
>>=20
>> Yes or no.
>>=20
>> Generally speaking the races of IPv6 and IPv4 connections on both =
network and client are going to be suffered by netowrk dynamics, =
including Multi-homing,  route flaps, roaming, or other network =
falilures. Extremely, a client can get a better IPv6 connection in one =
second (when IPv6 win the race), and lose it in next second. In such =
case, more sophisticated measurement should be done(on client or =
network) , for a longer period, on statistics of RTT and Failure rate, =
or combinations of them. But in IMHO, the assumption of HE is relatively =
stable network for short exchange connections. The dynamics exits but =
relatively rare or no notable impact on HE. So I see no such discussion =
in RFC8035.
>>=20
>> Davey
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Tue Sep 25 22:24:43 2018
Return-Path: <jabley@hopcount.ca>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 005AF130E08 for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 22:24:41 -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, RCVD_IN_DNSWL_NONE=-0.0001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 Wv0AQexy1W6S for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 22:24:38 -0700 (PDT)
Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com [IPv6:2a00:1450:4864:20::142]) (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 9F649130DC2 for <v6ops@ietf.org>; Tue, 25 Sep 2018 22:24:37 -0700 (PDT)
Received: by mail-lf1-x142.google.com with SMTP id l26-v6so22077674lfc.8 for <v6ops@ietf.org>; Tue, 25 Sep 2018 22:24:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=HYKHXevy9GU9/1KWRIc2KtFdZE6SeMChZtPpuP2GhaU=; b=GjGO4WHiRgEDVlRTIUfFgpBCCQUuCHKlnNeOYmJjMD+IRUSH4pU4eB4fMyliLreCxt 00y4I8/v4OOmVDteRt0tIG9oBQ6PywrWyXhf22M03jm+LpbRNUDJjwV9hmHN+CRUjLIu n0uyRcamjA9hEaFNsEHwDPc2SWT09zgKX6vu0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=HYKHXevy9GU9/1KWRIc2KtFdZE6SeMChZtPpuP2GhaU=; b=FxnAdwp7gblYj1qzNZxz4TTASn4sZYCwOmOEumcxufuBD34SRCexcxHVZU+EIp7L/r 48sdVhvchtd/yitK1AZqXCh92IkhYWPu1RU4laTWtMvRy/3DZNn8vM26Lc9zYdYNcge9 steF/71LR4FjfGpTloy+a0abPpmh8l7W5gjwULlKDM/wi92z60lYlwjjzlj1ukJh7uRb jBRDTASv75NuXuw4FcsXAZ2E6xQOOEUgKtDzpFhCVADqXr+AZs1V3W7MFC3y27Gt/7Tl bZfK4UGKkbnIMA+suvV3cLsBZVhdpfC0RXcbkhLzqxjZrVVW8thClMneCPJ4r3Z0iFJ2 uuGw==
X-Gm-Message-State: ABuFfogndcOk7Cd0X5WueDMyI7+l0xmLSmkK/2ONKQDGu2p2olj8EOOT jEyXRcvApazvivGTT8EPvuO33D+qpXksWSgZC0uzpw==
X-Google-Smtp-Source: ACcGV62uCPyLkf7wO+OfuSlJ+9vHl/tLQs2i110dWP/aGqBtEN2CQsBc9wQkR0FeTNE56BqIpFtckmvXtPsd0y4uftE=
X-Received: by 2002:a19:a2c1:: with SMTP id l184-v6mr2768861lfe.33.1537939475454;  Tue, 25 Sep 2018 22:24:35 -0700 (PDT)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Tue, 25 Sep 2018 22:24:34 -0700
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <F6F477B0-28DF-42C3-A8F6-F46BA2E0D119@delong.com>
In-Reply-To: <F6F477B0-28DF-42C3-A8F6-F46BA2E0D119@delong.com>
Date: Tue, 25 Sep 2018 22:24:34 -0700
Message-ID: <CAJhMdTMr7O0fKs3AVmi8MY91xT0JQZhLvYwtXvD9+ZbvK9QYPg@mail.gmail.com>
To: Owen DeLong <owen@delong.com>
Cc: George Michaelson <ggm@algebras.org>, dnsop WG <dnsop@ietf.org>,  "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/V7C4dMssBqJAtP2ZElPb58ctVNM>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 05:24:41 -0000

What better idea did you mean?

Being able to select a protocol based on what works best for the
end-user does not seem like a terrible end-state for the end-user,
short- or long-term.

> On Sep 25, 2018, at 21:25, Owen DeLong <owen@delong.com> wrote:
>
> It was never a good idea. It was a necessary evil (kind of like NAT in th=
at regard) to expeditiously deal with a somewhat tenacious (at the time) pr=
oblem which has since been given a significantly better solution, but so lo=
ng as the workaround appears to be working, people are loathe to put in the=
 effort of implementing the actual solution.
>
> sigh=E2=80=A6 Human nature.
>
> Owen
>
>
>> On Sep 25, 2018, at 19:58 , George Michaelson <ggm@algebras.org> wrote:
>>
>> I have said before, but don't know if I still adhere to it, but
>> anyways, here's a question: How *long* do people think a biassing
>> mechanism like HE is a good idea?
>>
>> * is it a good idea *forever*
>>
>> * or is it a transition path mechanism which has an end-of-life?
>>
>> * how do we know, when its at end-of-life?
>>
>> I used to love HE. I now have a sense, I'm more neutral. Maybe, we
>> actually don't want modified, better happy eyeballs, because we want
>> simpler, more deterministic network stack outcomes with less bias
>> hooks?
>>
>> I barely register if I an on v4 any more. I assume I'm on 6 on many
>> networks. This is as an end-user. I guess if I am really an end user,
>> this belief I understand TCP and UDP is false, and I should stop
>> worrying (as an end user)
>> On Wed, Sep 26, 2018 at 12:49 PM Davey Song <songlinjian@gmail.com> wrot=
e:
>>>>
>>>> But in the general case the network cannot.
>>>> Think host multi-homing.
>>>
>>>
>>> Yes or no.
>>>
>>> Generally speaking the races of IPv6 and IPv4 connections on both netwo=
rk and client are going to be suffered by netowrk dynamics, including Multi=
-homing,  route flaps, roaming, or other network falilures. Extremely, a cl=
ient can get a better IPv6 connection in one second (when IPv6 win the race=
), and lose it in next second. In such case, more sophisticated measurement=
 should be done(on client or network) , for a longer period, on statistics =
of RTT and Failure rate, or combinations of them. But in IMHO, the assumpti=
on of HE is relatively stable network for short exchange connections. The d=
ynamics exits but relatively rare or no notable impact on HE. So I see no s=
uch discussion in RFC8035.
>>>
>>> Davey
>>> _______________________________________________
>>> DNSOP mailing list
>>> DNSOP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Tue Sep 25 22:28:44 2018
Return-Path: <ggm@algebras.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED50A130DC2 for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 22:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.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 3Rh4gwNI6kLF for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 22:28:38 -0700 (PDT)
Received: from mail-wm1-x343.google.com (mail-wm1-x343.google.com [IPv6:2a00:1450:4864:20::343]) (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 307C0130E02 for <v6ops@ietf.org>; Tue, 25 Sep 2018 22:28:38 -0700 (PDT)
Received: by mail-wm1-x343.google.com with SMTP id o18-v6so792852wmc.0 for <v6ops@ietf.org>; Tue, 25 Sep 2018 22:28:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=VLaKytaKzzdFcy4GN19y+40//k265pjFW0mSiRg29/Q=; b=mGdMNp81C7JQaH6o35h5foFcr9g99uUmoDa8qEX+LKe/awOExc0RkohFo2pfAN0Apb k3rtu2WvLqW9lugFXlIN+2vnUjgl8h/YyymAmuQ384hju1GZ7VaZ65AESCdEERHEaiit 5jdmoNwzEGJBNrDJOp2OKsmcE4T0FNPmq4UXB+MRNH7v0WkrUBiqaxdm3q30Bhfvixod vrPwYoLr48SI7EzLKwSmZlLFhzpfjRhOycyXuoRvK+Wrrbttook5Tg+/xYjDmn/cmjyM b3i0KPiZhJajMG99iwq055JpQ7YhoMdFt5AGQtuk+QQ1iqIv/4LzEk1i7SZ5o/o3y7oX 8jkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=VLaKytaKzzdFcy4GN19y+40//k265pjFW0mSiRg29/Q=; b=VODSPa4va2UCR9HmcVOpUXSYrfygGMbsV88o0JP2YFcqMz5xvoK0GE3ztzI05l/Ijw mT6W5rK9gPjmScEHsdUnvVty6s5G0zC1/pTk11C3U7jikqD+HaZYPhTSSLAK7iH1sE8l ywS5utD/enutgN0u/nkNN2XESj2WC7z2dBlkRlbOoNptc24t/mouyZZoAS0n/iLwv84i Ttx7SbK0iMfloXhTnV3m34IwprbhsT5Zs0TtyWtEt6APeJe1hBk8keRUPgOtNNp+AAAP SOBTjhagzlHGhQKM3u1ImmLAItDfUBOoUiobOnXwFv0F1Uwv5ICZ/SQulf3MAb65n36H GTIA==
X-Gm-Message-State: ABuFfogL+j1TzshclCLWeFsZTU3fS4rnXzCTnVAsDDpxJHKVOK9XiKeb 5dPxHXRDAmCDILljl+eYeAtNZb7x0nxSCRzBOirWMg==
X-Google-Smtp-Source: ACcGV63IJi5aBBZfnEF3mNE0qKeRNIUQQm9zVlfTK5aJB7RndSapiCuxak6nK07hOBsyYnN8d+65z3Lbr9l6EGObAyc=
X-Received: by 2002:a1c:3314:: with SMTP id z20-v6mr2820424wmz.95.1537939716394;  Tue, 25 Sep 2018 22:28:36 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <F6F477B0-28DF-42C3-A8F6-F46BA2E0D119@delong.com> <CAJhMdTMr7O0fKs3AVmi8MY91xT0JQZhLvYwtXvD9+ZbvK9QYPg@mail.gmail.com>
In-Reply-To: <CAJhMdTMr7O0fKs3AVmi8MY91xT0JQZhLvYwtXvD9+ZbvK9QYPg@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 26 Sep 2018 15:28:24 +1000
Message-ID: <CAKr6gn06aOiGfTKqi2bzqmbXDLn3qn87niw8c6pBDmkT5vJCGg@mail.gmail.com>
To: dnsop WG <dnsop@ietf.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pXvdvqflNfcb8D-gEhWmKPk8e1g>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 05:28:42 -0000

I'm not speaking for Owen. I'm speaking for myself. I asked a
question. Is this really a long-term defensible thing to do? Do we
want HE forever?

run a race? thats fine. But, as the thread here notes, the
second-by-second conditions which leads one TCP to return SYN-ACK
before another can be volatile.

run a race, but bias the race towards the one you like? okaaaay.. But
once we're beyond a world where the V6 needs the bias, for anyone
stuck on the vestigial 4-is-better space, this means they incurred
*additional* connection penalty. wheres the control knob?

now we're talking about tuning the bias, weighting the sum, tumbling
the dice. I thought it was a crap shoot anyway...

-G
On Wed, Sep 26, 2018 at 3:24 PM Joe Abley <jabley@hopcount.ca> wrote:
>
> What better idea did you mean?
>
> Being able to select a protocol based on what works best for the
> end-user does not seem like a terrible end-state for the end-user,
> short- or long-term.
>
> > On Sep 25, 2018, at 21:25, Owen DeLong <owen@delong.com> wrote:
> >
> > It was never a good idea. It was a necessary evil (kind of like NAT in =
that regard) to expeditiously deal with a somewhat tenacious (at the time) =
problem which has since been given a significantly better solution, but so =
long as the workaround appears to be working, people are loathe to put in t=
he effort of implementing the actual solution.
> >
> > sigh=E2=80=A6 Human nature.
> >
> > Owen
> >
> >
> >> On Sep 25, 2018, at 19:58 , George Michaelson <ggm@algebras.org> wrote=
:
> >>
> >> I have said before, but don't know if I still adhere to it, but
> >> anyways, here's a question: How *long* do people think a biassing
> >> mechanism like HE is a good idea?
> >>
> >> * is it a good idea *forever*
> >>
> >> * or is it a transition path mechanism which has an end-of-life?
> >>
> >> * how do we know, when its at end-of-life?
> >>
> >> I used to love HE. I now have a sense, I'm more neutral. Maybe, we
> >> actually don't want modified, better happy eyeballs, because we want
> >> simpler, more deterministic network stack outcomes with less bias
> >> hooks?
> >>
> >> I barely register if I an on v4 any more. I assume I'm on 6 on many
> >> networks. This is as an end-user. I guess if I am really an end user,
> >> this belief I understand TCP and UDP is false, and I should stop
> >> worrying (as an end user)
> >> On Wed, Sep 26, 2018 at 12:49 PM Davey Song <songlinjian@gmail.com> wr=
ote:
> >>>>
> >>>> But in the general case the network cannot.
> >>>> Think host multi-homing.
> >>>
> >>>
> >>> Yes or no.
> >>>
> >>> Generally speaking the races of IPv6 and IPv4 connections on both net=
work and client are going to be suffered by netowrk dynamics, including Mul=
ti-homing,  route flaps, roaming, or other network falilures. Extremely, a =
client can get a better IPv6 connection in one second (when IPv6 win the ra=
ce), and lose it in next second. In such case, more sophisticated measureme=
nt should be done(on client or network) , for a longer period, on statistic=
s of RTT and Failure rate, or combinations of them. But in IMHO, the assump=
tion of HE is relatively stable network for short exchange connections. The=
 dynamics exits but relatively rare or no notable impact on HE. So I see no=
 such discussion in RFC8035.
> >>>
> >>> Davey
> >>> _______________________________________________
> >>> DNSOP mailing list
> >>> DNSOP@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/dnsop
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop


From nobody Tue Sep 25 22:43:47 2018
Return-Path: <jabley@hopcount.ca>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10439130E05 for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 22:43:46 -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, RCVD_IN_DNSWL_NONE=-0.0001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 zJp0A48691cG for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 22:43:43 -0700 (PDT)
Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (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 0B8E4130DC9 for <v6ops@ietf.org>; Tue, 25 Sep 2018 22:43:43 -0700 (PDT)
Received: by mail-lj1-x242.google.com with SMTP id 203-v6so23942119ljj.13 for <v6ops@ietf.org>; Tue, 25 Sep 2018 22:43:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google;  h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=qz24qd6jt9srLezpxAkqDeIeK2hXVUhF8H52lifYGZU=; b=PxhzQSQm/7TJQVQxkTAolx93CE42tHD5tLP4mjkirJr149Xq3zzR1CGQ4lA5IJX3dV yPcHvf+LzI3Y35erMtz9v1Q92MrfGXpsggbrYMaAEYwNkth7b2YramlG7vlPgYXaL2om N3zWBINeaR8oUWW77RGW49Vx+tUC6LBlctAR8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=qz24qd6jt9srLezpxAkqDeIeK2hXVUhF8H52lifYGZU=; b=T7QXvdbt++3+hBDBd/B8wTcBY5H49pCWBbAYHUhddv1O6wJ2zbcCGo/Tuk8kdNfQgA ke7YabH2/lYcRz6Z3kXEG3TOipj6gPpTimMYW2/i7fVjZf/TymCm3PmBgJ8Nh5RQIxEC CXbaQN2a2Bc6wKMGwMAbNfYJfnToRef6WZkBYWeWG1JWEWpShZTv4akkDwbTBfIchdv1 Dt/yDrVJIdzgotDXr5OO/aaL3GHotCCAJ1j+jvF9uIEjMcK4g4jF6wBuPqlxknqWa1a/ 0DXT1Sr8GP8Ry//JDu+OBTVO8eAmL8TVG02XT2ds6c9XCxhtn3EzK/2R75rqgweM9V3E fChg==
X-Gm-Message-State: ABuFfoj51lb/QE6vMrRxBzM7KIgQi1JqMGJtfZNkhfg9u6Slr/945i5B O5dgrJ0v9r4sqD5bD+mJ9KteLLCrqfyziIJ5qhQ23Q==
X-Google-Smtp-Source: ACcGV60NcaBfTDFf8W/PYoebYo7blm208yE/itTgA5WR58QCidHI5B9Y9K723rWs8m72C09L3yAlWPcD1VDzLAv2k7E=
X-Received: by 2002:a2e:9c4d:: with SMTP id t13-v6mr586030ljj.153.1537940620884;  Tue, 25 Sep 2018 22:43:40 -0700 (PDT)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Tue, 25 Sep 2018 22:43:40 -0700
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <F6F477B0-28DF-42C3-A8F6-F46BA2E0D119@delong.com> <CAJhMdTMr7O0fKs3AVmi8MY91xT0JQZhLvYwtXvD9+ZbvK9QYPg@mail.gmail.com> <CAKr6gn06aOiGfTKqi2bzqmbXDLn3qn87niw8c6pBDmkT5vJCGg@mail.gmail.com>
In-Reply-To: <CAKr6gn06aOiGfTKqi2bzqmbXDLn3qn87niw8c6pBDmkT5vJCGg@mail.gmail.com>
Date: Tue, 25 Sep 2018 22:43:40 -0700
Message-ID: <CAJhMdTPh29rnFuQKnSYcj1J4MtMRw6xqhUv=x0+9NAjZkq4ihw@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
Cc: dnsop WG <dnsop@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GidltOtK6D4XOYzF7x3tXcRzDfI>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 05:43:46 -0000

Having a predictable bias seems better than an unpredictable one.

> On Sep 25, 2018, at 22:28, George Michaelson <ggm@algebras.org> wrote:
>
> I'm not speaking for Owen. I'm speaking for myself. I asked a
> question. Is this really a long-term defensible thing to do? Do we
> want HE forever?
>
> run a race? thats fine. But, as the thread here notes, the
> second-by-second conditions which leads one TCP to return SYN-ACK
> before another can be volatile.
>
> run a race, but bias the race towards the one you like? okaaaay.. But
> once we're beyond a world where the V6 needs the bias, for anyone
> stuck on the vestigial 4-is-better space, this means they incurred
> *additional* connection penalty. wheres the control knob?
>
> now we're talking about tuning the bias, weighting the sum, tumbling
> the dice. I thought it was a crap shoot anyway...
>
> -G
>> On Wed, Sep 26, 2018 at 3:24 PM Joe Abley <jabley@hopcount.ca> wrote:
>>
>> What better idea did you mean?
>>
>> Being able to select a protocol based on what works best for the
>> end-user does not seem like a terrible end-state for the end-user,
>> short- or long-term.
>>
>>> On Sep 25, 2018, at 21:25, Owen DeLong <owen@delong.com> wrote:
>>>
>>> It was never a good idea. It was a necessary evil (kind of like NAT in =
that regard) to expeditiously deal with a somewhat tenacious (at the time) =
problem which has since been given a significantly better solution, but so =
long as the workaround appears to be working, people are loathe to put in t=
he effort of implementing the actual solution.
>>>
>>> sigh=E2=80=A6 Human nature.
>>>
>>> Owen
>>>
>>>
>>>> On Sep 25, 2018, at 19:58 , George Michaelson <ggm@algebras.org> wrote=
:
>>>>
>>>> I have said before, but don't know if I still adhere to it, but
>>>> anyways, here's a question: How *long* do people think a biassing
>>>> mechanism like HE is a good idea?
>>>>
>>>> * is it a good idea *forever*
>>>>
>>>> * or is it a transition path mechanism which has an end-of-life?
>>>>
>>>> * how do we know, when its at end-of-life?
>>>>
>>>> I used to love HE. I now have a sense, I'm more neutral. Maybe, we
>>>> actually don't want modified, better happy eyeballs, because we want
>>>> simpler, more deterministic network stack outcomes with less bias
>>>> hooks?
>>>>
>>>> I barely register if I an on v4 any more. I assume I'm on 6 on many
>>>> networks. This is as an end-user. I guess if I am really an end user,
>>>> this belief I understand TCP and UDP is false, and I should stop
>>>> worrying (as an end user)
>>>> On Wed, Sep 26, 2018 at 12:49 PM Davey Song <songlinjian@gmail.com> wr=
ote:
>>>>>>
>>>>>> But in the general case the network cannot.
>>>>>> Think host multi-homing.
>>>>>
>>>>>
>>>>> Yes or no.
>>>>>
>>>>> Generally speaking the races of IPv6 and IPv4 connections on both net=
work and client are going to be suffered by netowrk dynamics, including Mul=
ti-homing,  route flaps, roaming, or other network falilures. Extremely, a =
client can get a better IPv6 connection in one second (when IPv6 win the ra=
ce), and lose it in next second. In such case, more sophisticated measureme=
nt should be done(on client or network) , for a longer period, on statistic=
s of RTT and Failure rate, or combinations of them. But in IMHO, the assump=
tion of HE is relatively stable network for short exchange connections. The=
 dynamics exits but relatively rare or no notable impact on HE. So I see no=
 such discussion in RFC8035.
>>>>>
>>>>> Davey
>>>>> _______________________________________________
>>>>> DNSOP mailing list
>>>>> DNSOP@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dnsop
>>>>
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>> _______________________________________________
>>> DNSOP mailing list
>>> DNSOP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dnsop
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop


From nobody Tue Sep 25 23:10:33 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C156130DC9; Tue, 25 Sep 2018 23:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] 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 9yx9U7BVatMJ; Tue, 25 Sep 2018 23:10:12 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926FE126BED; Tue, 25 Sep 2018 23:10:12 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 1497EFECBEDF; Wed, 26 Sep 2018 06:10:12 +0000 (UTC)
Content-Type: multipart/alternative; boundary=Apple-Mail-44924CDD-E560-4FF7-B0C3-D5F04426F5F7
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (16A366)
In-Reply-To: <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com>
Date: Wed, 26 Sep 2018 08:10:02 +0200
Cc: Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, v6ops@ietf.org, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Transfer-Encoding: 7bit
Message-Id: <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com>
To: Davey Song <songlinjian@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/I_D4idGUVlSEzqZOQLtW5cA7Ca0>
Subject: Re: [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 06:10:14 -0000

--Apple-Mail-44924CDD-E560-4FF7-B0C3-D5F04426F5F7
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Davey,

If we=E2=80=99re discussing host based versus network based happy eyeballs, w=
ould it be naive to think that the network based HE would interfere with the=
 client=E2=80=99s HE?

A router knows very little about end to end properties of a connection. It c=
ould of course do those measurements by looking deeply into packets, but it w=
ould still be restricted to it=E2=80=99s own topological location. Compare t=
hat with the data available to an MP-TCP host stack.=20

And note I think HE can=E2=80=99t just be between v4 and v6, but between all=
 the candidate connections between source and destination.=20

Cheers,
Ole

On 26 Sep 2018, at 04:49, Davey Song <songlinjian@gmail.com> wrote:

>> But in the general case the network cannot.
>> Think host multi-homing.
>=20
> Yes or no.=20
>=20
> Generally speaking the races of IPv6 and IPv4 connections on both network a=
nd client are going to be suffered by netowrk dynamics, including Multi-homi=
ng,  route flaps, roaming, or other network falilures. Extremely, a client c=
an get a better IPv6 connection in one second (when IPv6 win the race), and l=
ose it in next second. In such case, more sophisticated measurement should b=
e done(on client or network) , for a longer period, on statistics of RTT and=
 Failure rate, or combinations of them. But in IMHO, the assumption of HE is=
 relatively stable network for short exchange connections. The dynamics exit=
s but relatively rare or no notable impact on HE. So I see no such discussio=
n in RFC8035.
>=20
> Davey

--Apple-Mail-44924CDD-E560-4FF7-B0C3-D5F04426F5F7
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">Dav=
ey,</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">If we=E2=80=99re discus=
sing host based versus network based happy eyeballs, would it be naive to th=
ink that the network based HE would interfere with the client=E2=80=99s HE?<=
/div><div dir=3D"ltr"><br></div><div dir=3D"ltr">A router knows very little a=
bout end to end properties of a connection. It could of course do those meas=
urements by looking deeply into packets, but it would still be restricted to=
 it=E2=80=99s own topological location. Compare that with the data available=
 to an MP-TCP host stack.&nbsp;</div><div dir=3D"ltr"><br></div><div dir=3D"=
ltr">And note I think HE can=E2=80=99t just be between v4 and v6, but betwee=
n all the candidate connections between source and destination.&nbsp;</div><=
div dir=3D"ltr"><br></div><div dir=3D"ltr">Cheers,</div><div dir=3D"ltr">Ole=
</div><div dir=3D"ltr"><br>On 26 Sep 2018, at 04:49, Davey Song &lt;<a href=3D=
"mailto:songlinjian@gmail.com">songlinjian@gmail.com</a>&gt; wrote:<br><br><=
/div><blockquote type=3D"cite"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D=
"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><d=
iv class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Bu=
t in the general case the network cannot.<br>
Think host multi-homing.<br></blockquote><div><br></div><div>Yes or no.&nbsp=
;</div><div><br></div><div>Generally speaking the races of IPv6 and IPv4 con=
nections on both network and client are going to be suffered by netowrk dyna=
mics, including Multi-homing,&nbsp; route flaps,&nbsp;roaming, or other netw=
ork falilures. Extremely, a client can get a better IPv6 connection in one s=
econd (when IPv6 win the race), and lose it in next second. In such case, mo=
re sophisticated measurement should be done(on client or network) , for a lo=
nger period, on statistics of RTT and Failure rate, or combinations of them.=
 But&nbsp;in IMHO, the assumption of HE is relatively stable network for sho=
rt exchange connections. The dynamics exits but relatively rare or no&nbsp;n=
otable impact on HE. So I see no such discussion in RFC8035.</div><div><br><=
/div><div>Davey</div></div></div></div></div></div></div></div>
</div></blockquote></body></html>=

--Apple-Mail-44924CDD-E560-4FF7-B0C3-D5F04426F5F7--


From nobody Tue Sep 25 23:23:54 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C59FC130E05; Tue, 25 Sep 2018 23:23:43 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 2BZ02h8ws_vb; Tue, 25 Sep 2018 23:23:41 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 1B7F5126BED; Tue, 25 Sep 2018 23:23:41 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id z8-v6so16078921qto.9; Tue, 25 Sep 2018 23:23:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jk9iceKH0eeyrtMwo3/aXGbbn8ypTUUTU8VmQpvHrxk=; b=Ot82eaX+DN8Hp5FQlLqKAAeaESDVq0dANox0+HPe3jeFEUd0GI2pzeDDlObh4H1gMD 6xoAnRmHAA239dJ2aO2l5D5J0W7l+ys7/y31zzNE8rdICVrXmfOJ9bWuuFPSn7gCfzeD KIrJz5e/nDz6B7gMNmW5hKMfjwLl00nTiwicRS5SOFRnRVYqrPjjUzOqOVAiIx5GRUHS /r0comnMYvR4v3ZCU71DXajxPf3LDps21nOuQLJJBvQuzv+KYTNwQbUAJWhhsJFQzRLZ 7JQBxs/WNqyoPPQdikEBiCVHcBODTNAL6yNd2wimnauewEkECZYBWxxdkh8rb3p10F2s VzzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jk9iceKH0eeyrtMwo3/aXGbbn8ypTUUTU8VmQpvHrxk=; b=DLHqClLqsyPYdDCvu2ef+eIUc/J+n7azs/Hc3va0apNIYj2JTv9G4AwW6+nLSQCJ/z 5uaE92JLKMuKbrZPTIhSpO3smRWAQdCTyGWliEiO0ac5+CSG///ZHNXEUnhX9P5knIi0 pudyyHGDHzbj/E7M9YSr3gI5eBh9phfw7ZC9JLtyDbD+Yy0kg9P984twbMgbIszEpfGd Bd7Sx3yhddX1WKLPqdGDRzpdzMvxrSdLrNMev1kdaQ0CMTfKYd74ysGg5QH3lv+0wfOo DdXfTo7kOhEzuoX/Gbkybqy88aXEfkE/3o5bhYqFgIep7s9L4e5cVmbxchFVIOM3sfuE KBzg==
X-Gm-Message-State: ABuFfogjXaX2OBcbhCuyfkC2ZRSBpsRwNzqR8RtQNZToymOuqzR3y2AC vBmYFuinEjkcjRbbpsSjnMuANOCdfAFZ0vQORInC378N
X-Google-Smtp-Source: ACcGV62vYwv2Q6rYbY+MS+fRw0HT5lkxjaCoAvklJB6cHMOZUnN4+Q79nwCd6qIZPFsoa7pwbBseFO1lYSwwvhpMdVY=
X-Received: by 2002:a0c:ef04:: with SMTP id t4-v6mr1320910qvr.24.1537943020159;  Tue, 25 Sep 2018 23:23:40 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <F6F477B0-28DF-42C3-A8F6-F46BA2E0D119@delong.com> <CAJhMdTMr7O0fKs3AVmi8MY91xT0JQZhLvYwtXvD9+ZbvK9QYPg@mail.gmail.com> <CAKr6gn06aOiGfTKqi2bzqmbXDLn3qn87niw8c6pBDmkT5vJCGg@mail.gmail.com>
In-Reply-To: <CAKr6gn06aOiGfTKqi2bzqmbXDLn3qn87niw8c6pBDmkT5vJCGg@mail.gmail.com>
From: Davey Song <songlinjian@gmail.com>
Date: Wed, 26 Sep 2018 14:23:30 +0800
Message-ID: <CAAObRXKV570=8tfxEacEtNE7zvMTiMMMEfYHH_yvgOK62cRhgA@mail.gmail.com>
To: George Michaelson <ggm@algebras.org>
Cc: dnsop <dnsop@ietf.org>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="00000000000066c87c0576c043d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1KgMuKAJrVXUA5virA4w5xFRjHA>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 06:23:44 -0000

--00000000000066c87c0576c043d6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi George,

Actually the idea of NHE is inspired partially by CDN stuff, which involve
lots of measurments
and route users to visit a best path against network dynamics.  It proves
to be a good practice
for morden Internet. No doubt. I'm wondering CDN is also breaking DNSSEC to
stub-resolver, right?

Davey

On Wed, 26 Sep 2018 at 13:28, George Michaelson <ggm@algebras.org> wrote:

> I'm not speaking for Owen. I'm speaking for myself. I asked a
> question. Is this really a long-term defensible thing to do? Do we
> want HE forever?
>
> run a race? thats fine. But, as the thread here notes, the
> second-by-second conditions which leads one TCP to return SYN-ACK
> before another can be volatile.
>
> run a race, but bias the race towards the one you like? okaaaay.. But
> once we're beyond a world where the V6 needs the bias, for anyone
> stuck on the vestigial 4-is-better space, this means they incurred
> *additional* connection penalty. wheres the control knob?
>
> now we're talking about tuning the bias, weighting the sum, tumbling
> the dice. I thought it was a crap shoot anyway...
>
> -G
> On Wed, Sep 26, 2018 at 3:24 PM Joe Abley <jabley@hopcount.ca> wrote:
> >
> > What better idea did you mean?
> >
> > Being able to select a protocol based on what works best for the
> > end-user does not seem like a terrible end-state for the end-user,
> > short- or long-term.
> >
> > > On Sep 25, 2018, at 21:25, Owen DeLong <owen@delong.com> wrote:
> > >
> > > It was never a good idea. It was a necessary evil (kind of like NAT i=
n
> that regard) to expeditiously deal with a somewhat tenacious (at the time=
)
> problem which has since been given a significantly better solution, but s=
o
> long as the workaround appears to be working, people are loathe to put in
> the effort of implementing the actual solution.
> > >
> > > sigh=E2=80=A6 Human nature.
> > >
> > > Owen
> > >
> > >
> > >> On Sep 25, 2018, at 19:58 , George Michaelson <ggm@algebras.org>
> wrote:
> > >>
> > >> I have said before, but don't know if I still adhere to it, but
> > >> anyways, here's a question: How *long* do people think a biassing
> > >> mechanism like HE is a good idea?
> > >>
> > >> * is it a good idea *forever*
> > >>
> > >> * or is it a transition path mechanism which has an end-of-life?
> > >>
> > >> * how do we know, when its at end-of-life?
> > >>
> > >> I used to love HE. I now have a sense, I'm more neutral. Maybe, we
> > >> actually don't want modified, better happy eyeballs, because we want
> > >> simpler, more deterministic network stack outcomes with less bias
> > >> hooks?
> > >>
> > >> I barely register if I an on v4 any more. I assume I'm on 6 on many
> > >> networks. This is as an end-user. I guess if I am really an end user=
,
> > >> this belief I understand TCP and UDP is false, and I should stop
> > >> worrying (as an end user)
> > >> On Wed, Sep 26, 2018 at 12:49 PM Davey Song <songlinjian@gmail.com>
> wrote:
> > >>>>
> > >>>> But in the general case the network cannot.
> > >>>> Think host multi-homing.
> > >>>
> > >>>
> > >>> Yes or no.
> > >>>
> > >>> Generally speaking the races of IPv6 and IPv4 connections on both
> network and client are going to be suffered by netowrk dynamics, includin=
g
> Multi-homing,  route flaps, roaming, or other network falilures. Extremel=
y,
> a client can get a better IPv6 connection in one second (when IPv6 win th=
e
> race), and lose it in next second. In such case, more sophisticated
> measurement should be done(on client or network) , for a longer period, o=
n
> statistics of RTT and Failure rate, or combinations of them. But in IMHO,
> the assumption of HE is relatively stable network for short exchange
> connections. The dynamics exits but relatively rare or no notable impact =
on
> HE. So I see no such discussion in RFC8035.
> > >>>
> > >>> Davey
> > >>> _______________________________________________
> > >>> DNSOP mailing list
> > >>> DNSOP@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/dnsop
> > >>
> > >> _______________________________________________
> > >> v6ops mailing list
> > >> v6ops@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/v6ops
> > >
> > > _______________________________________________
> > > DNSOP mailing list
> > > DNSOP@ietf.org
> > > https://www.ietf.org/mailman/listinfo/dnsop
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--00000000000066c87c0576c043d6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi George,=C2=A0<div><br></div><div>Actually the idea of N=
HE is inspired partially by CDN stuff, which involve lots of measurments <b=
r>and route users to visit a best path against network dynamics.=C2=A0 It p=
roves to be a good practice <br>for morden Internet.=C2=A0No doubt. I&#39;m=
 wondering CDN is also breaking DNSSEC to stub-resolver, right?</div><div><=
br></div><div>Davey</div><div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r">On Wed, 26 Sep 2018 at 13:28, George Michaelson &lt;<a href=3D"mailto:gg=
m@algebras.org">ggm@algebras.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">I&#39;m not speaking for Owen. I&#39;m speaking for myself. I=
 asked a<br>
question. Is this really a long-term defensible thing to do? Do we<br>
want HE forever?<br>
<br>
run a race? thats fine. But, as the thread here notes, the<br>
second-by-second conditions which leads one TCP to return SYN-ACK<br>
before another can be volatile.<br>
<br>
run a race, but bias the race towards the one you like? okaaaay.. But<br>
once we&#39;re beyond a world where the V6 needs the bias, for anyone<br>
stuck on the vestigial 4-is-better space, this means they incurred<br>
*additional* connection penalty. wheres the control knob?<br>
<br>
now we&#39;re talking about tuning the bias, weighting the sum, tumbling<br=
>
the dice. I thought it was a crap shoot anyway...<br>
<br>
-G<br>
On Wed, Sep 26, 2018 at 3:24 PM Joe Abley &lt;<a href=3D"mailto:jabley@hopc=
ount.ca" target=3D"_blank">jabley@hopcount.ca</a>&gt; wrote:<br>
&gt;<br>
&gt; What better idea did you mean?<br>
&gt;<br>
&gt; Being able to select a protocol based on what works best for the<br>
&gt; end-user does not seem like a terrible end-state for the end-user,<br>
&gt; short- or long-term.<br>
&gt;<br>
&gt; &gt; On Sep 25, 2018, at 21:25, Owen DeLong &lt;<a href=3D"mailto:owen=
@delong.com" target=3D"_blank">owen@delong.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; It was never a good idea. It was a necessary evil (kind of like N=
AT in that regard) to expeditiously deal with a somewhat tenacious (at the =
time) problem which has since been given a significantly better solution, b=
ut so long as the workaround appears to be working, people are loathe to pu=
t in the effort of implementing the actual solution.<br>
&gt; &gt;<br>
&gt; &gt; sigh=E2=80=A6 Human nature.<br>
&gt; &gt;<br>
&gt; &gt; Owen<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; On Sep 25, 2018, at 19:58 , George Michaelson &lt;<a href=3D"=
mailto:ggm@algebras.org" target=3D"_blank">ggm@algebras.org</a>&gt; wrote:<=
br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I have said before, but don&#39;t know if I still adhere to i=
t, but<br>
&gt; &gt;&gt; anyways, here&#39;s a question: How *long* do people think a =
biassing<br>
&gt; &gt;&gt; mechanism like HE is a good idea?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; * is it a good idea *forever*<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; * or is it a transition path mechanism which has an end-of-li=
fe?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; * how do we know, when its at end-of-life?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I used to love HE. I now have a sense, I&#39;m more neutral. =
Maybe, we<br>
&gt; &gt;&gt; actually don&#39;t want modified, better happy eyeballs, beca=
use we want<br>
&gt; &gt;&gt; simpler, more deterministic network stack outcomes with less =
bias<br>
&gt; &gt;&gt; hooks?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I barely register if I an on v4 any more. I assume I&#39;m on=
 6 on many<br>
&gt; &gt;&gt; networks. This is as an end-user. I guess if I am really an e=
nd user,<br>
&gt; &gt;&gt; this belief I understand TCP and UDP is false, and I should s=
top<br>
&gt; &gt;&gt; worrying (as an end user)<br>
&gt; &gt;&gt; On Wed, Sep 26, 2018 at 12:49 PM Davey Song &lt;<a href=3D"ma=
ilto:songlinjian@gmail.com" target=3D"_blank">songlinjian@gmail.com</a>&gt;=
 wrote:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; But in the general case the network cannot.<br>
&gt; &gt;&gt;&gt;&gt; Think host multi-homing.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Yes or no.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Generally speaking the races of IPv6 and IPv4 connections=
 on both network and client are going to be suffered by netowrk dynamics, i=
ncluding Multi-homing,=C2=A0 route flaps, roaming, or other network falilur=
es. Extremely, a client can get a better IPv6 connection in one second (whe=
n IPv6 win the race), and lose it in next second. In such case, more sophis=
ticated measurement should be done(on client or network) , for a longer per=
iod, on statistics of RTT and Failure rate, or combinations of them. But in=
 IMHO, the assumption of HE is relatively stable network for short exchange=
 connections. The dynamics exits but relatively rare or no notable impact o=
n HE. So I see no such discussion in RFC8035.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Davey<br>
&gt; &gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt; DNSOP mailing list<br>
&gt; &gt;&gt;&gt; <a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP=
@ietf.org</a><br>
&gt; &gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" r=
el=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/d=
nsop</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; v6ops mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@iet=
f.org</a><br>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6o=
ps</a><br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; DNSOP mailing list<br>
&gt; &gt; <a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.or=
g</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dnsop</a>=
<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a><br>
</blockquote></div></div></div>

--00000000000066c87c0576c043d6--


From nobody Tue Sep 25 23:36:23 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0D2130E11 for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 23:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable 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 FNSUKyoqxq-5 for <v6ops@ietfa.amsl.com>; Tue, 25 Sep 2018 23:36:12 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3683126BED for <v6ops@ietf.org>; Tue, 25 Sep 2018 23:36:11 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id BE8E6438CB for <v6ops@ietf.org>; Wed, 26 Sep 2018 08:36:09 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id AE03941B3E; Wed, 26 Sep 2018 08:36:09 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id A0491209E5; Wed, 26 Sep 2018 08:36:09 +0200 (CEST)
Date: Wed, 26 Sep 2018 08:36:09 +0200
From: Gert Doering <gert@space.net>
To: George Michaelson <ggm@algebras.org>
Cc: dnsop WG <dnsop@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
Message-ID: <20180926063609.GC11393@Space.Net>
References: <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <F6F477B0-28DF-42C3-A8F6-F46BA2E0D119@delong.com> <CAJhMdTMr7O0fKs3AVmi8MY91xT0JQZhLvYwtXvD9+ZbvK9QYPg@mail.gmail.com> <CAKr6gn06aOiGfTKqi2bzqmbXDLn3qn87niw8c6pBDmkT5vJCGg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKr6gn06aOiGfTKqi2bzqmbXDLn3qn87niw8c6pBDmkT5vJCGg@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/JCis3Wulle0a1xvkkPON--hkpwQ>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 06:36:15 -0000

Hi,

On Wed, Sep 26, 2018 at 03:28:24PM +1000, George Michaelson wrote:
> run a race, but bias the race towards the one you like? okaaaay.. But
> once we're beyond a world where the V6 needs the bias, for anyone
> stuck on the vestigial 4-is-better space, this means they incurred
> *additional* connection penalty. wheres the control knob?

We need a bias for one or the other protocol.  Otherwise you'll end up
flipflopping between v4 and v6 for subsequent connections if both are
equal (because the networks in beween just run v4 and v6 over the same
links, same devices, same peerings, ...) - and that is a major annoyance
when trying to troubleshoot things.  Like, web server access that 
"sometimes works and on reload brings an error" (because apache ACLs
are not in sync for v4 vs. v6).

In the long run, we want a single protocol, whichever it is.  Dual-stack
is dual-work.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Wed Sep 26 00:06:14 2018
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D382E130E27; Wed, 26 Sep 2018 00:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level: 
X-Spam-Status: No, score=-1.498 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 2ETeZtZoRiR8; Wed, 26 Sep 2018 00:05:54 -0700 (PDT)
Received: from mail-oi1-x241.google.com (mail-oi1-x241.google.com [IPv6:2607:f8b0:4864:20::241]) (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 0EB3E130E13; Wed, 26 Sep 2018 00:05:54 -0700 (PDT)
Received: by mail-oi1-x241.google.com with SMTP id n1-v6so3562131oic.4; Wed, 26 Sep 2018 00:05:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GIz/MDxKo158gydr1bGBShQWj+ImLkEvD1bYEcJxt6U=; b=l8Kj758J4UHGQJZ74no/kSuEraIOF9GkM0HpUMacpyl7ubEhqvZam9k1lfdXVClJn5 6dqdhj6cQs2MupiUHK+nvhz+zCtb4uDpi+nyqbQ1SJiuHhystJ7ieRrEVZ9lXC9WT6e9 xEz+62Z8s1s+iCxwHFgSWSgnEkgfXiPkdvP7z5wrT6Z0mZ63D2zSTB7g3fdH8VjxIEbH qisEPVpqgsSlOaSixkhLAjnRGPljmXUZiwgaM+KDLrQM+Mf7e4uyHqzn4Q/t7PZVpT8u oDC5UQ9WvE1wsIyD6EE6f7IAVya5bI2ncoN1Mngo5pDaJ0PmNQTuYHjqn0R3rtdXV5Eh yByA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GIz/MDxKo158gydr1bGBShQWj+ImLkEvD1bYEcJxt6U=; b=PGi2VQzRxdWJcK4cMj6gmEndc8hXQzxLkZ7aCyHH32Q+TcjsC92SX/rPIjpGlzHeGa i3Z2MKSdsuZnXWgygYHONLVKu/YSITKzWhp5JwJYXIqmBe04xDGGJGqkkc5tZMSO5dj7 zeSXwchRH0jJ1m2x/Mx78SqKexujKOBj7YMRjPa1Fo1Wp3Wv7fzkgrkT0rW6AwlKhX5U Dr5ngwZFdE4vhE5ZTNHNSXBTNXsXl/llZTwM03SlV8mpewKJ/QCknQWXPvkKhoUEkaxh f21mQ7zXtSj0yMjyQa9Rxh7cnVHXXwXdA9ZZuA2y57o0f8zmOP3j8rh80ADEP0K9hKve 9Aeg==
X-Gm-Message-State: ABuFfog2BKU0bJs3l07iAz+MAcUY2Nd0Y3dauBf8RC+pbK34SP4NIwBg 3DKpt74tLOL07Sfnbg3yCdVqBt5/6+nIbGdE8G8=
X-Google-Smtp-Source: ACcGV628KRz8Gp15YHzrlNpgJb1a6/eGt/fWHp9ZJMFH6svYFkskqStpcdQfmuQLPdTYlBJakTgkMJRT4/MNPHuObJw=
X-Received: by 2002:aca:e805:: with SMTP id f5-v6mr940324oih.38.1537945553309;  Wed, 26 Sep 2018 00:05:53 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org>
In-Reply-To: <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 26 Sep 2018 17:05:27 +1000
Message-ID: <CAO42Z2xrkV+qaue+CEBb0nq+3ocxsPhQLpQadkP+QPeHx9sMSA@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: songlinjian@gmail.com, dnsop@ietf.org, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>,  v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006397220576c0dae0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tMb95UbBuMMf1oa-0OKcvTlInlk>
Subject: Re: [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 07:05:56 -0000

--0000000000006397220576c0dae0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed., 26 Sep. 2018, 16:10 Ole Troan, <otroan@employees.org> wrote:

> Davey,
>
> If we=E2=80=99re discussing host based versus network based happy eyeball=
s, would
> it be naive to think that the network based HE would interfere with the
> client=E2=80=99s HE?
>
> A router knows very little about end to end properties of a connection. I=
t
> could of course do those measurements by looking deeply into packets, but
> it would still be restricted to it=E2=80=99s own topological location. Co=
mpare that
> with the data available to an MP-TCP host stack.
>
> And note I think HE can=E2=80=99t just be between v4 and v6, but between =
all the
> candidate connections between source and destination.
>

Yes, multipathing (+ encryption) has a lot of impacts on what is possible
to do and commonly done on the network today. A lot of those activities
would have to be shifted to the host.

Start at slide 63 -

http://www.users.on.net/~markachy/The_Rapid_Rise_of_the_MMHH.pdf

I can't seem to find it now, however I think Fred Baker wrote a draft a
number of years ago that observed that multi-addressing on a single
interface is also a form of multi-homing, meaning that it isn't a
requirement for a "multi-homed" host to have multiple interfaces attached
to multiple and different networks. That means most IPv4 hosts, and all
IPv6 hosts, by design, are potential multi-homed hosts.

Regards,
Mark.


> Cheers,
> Ole
>
> On 26 Sep 2018, at 04:49, Davey Song <songlinjian@gmail.com> wrote:
>
> But in the general case the network cannot.
>> Think host multi-homing.
>>
>
> Yes or no.
>
> Generally speaking the races of IPv6 and IPv4 connections on both network
> and client are going to be suffered by netowrk dynamics, including
> Multi-homing,  route flaps, roaming, or other network falilures. Extremel=
y,
> a client can get a better IPv6 connection in one second (when IPv6 win th=
e
> race), and lose it in next second. In such case, more sophisticated
> measurement should be done(on client or network) , for a longer period, o=
n
> statistics of RTT and Failure rate, or combinations of them. But in IMHO,
> the assumption of HE is relatively stable network for short exchange
> connections. The dynamics exits but relatively rare or no notable impact =
on
> HE. So I see no such discussion in RFC8035.
>
> Davey
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

--0000000000006397220576c0dae0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"auto"><div><br><br><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Wed., 26 Sep. 2018, 16:10 Ole Troan, &=
lt;<a href=3D"mailto:otroan@employees.org" target=3D"_blank">otroan@employe=
es.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">Davey,</div=
><div dir=3D"ltr"><br></div><div dir=3D"ltr">If we=E2=80=99re discussing ho=
st based versus network based happy eyeballs, would it be naive to think th=
at the network based HE would interfere with the client=E2=80=99s HE?</div>=
<div dir=3D"ltr"><br></div><div dir=3D"ltr">A router knows very little abou=
t end to end properties of a connection. It could of course do those measur=
ements by looking deeply into packets, but it would still be restricted to =
it=E2=80=99s own topological location. Compare that with the data available=
 to an MP-TCP host stack.=C2=A0</div><div dir=3D"ltr"><br></div><div dir=3D=
"ltr">And note I think HE can=E2=80=99t just be between v4 and v6, but betw=
een all the candidate connections between source and destination.=C2=A0</di=
v></div></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"au=
to">Yes, multipathing (+ encryption) has a lot of impacts on what is possib=
le to do and commonly done on the network today. A lot of those activities =
would have to be shifted to the host.</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">Start at slide 63 -</div><div dir=3D"auto"><br></div><div dir=
=3D"auto"><a href=3D"http://www.users.on.net/~markachy/The_Rapid_Rise_of_th=
e_MMHH.pdf">http://www.users.on.net/~markachy/The_Rapid_Rise_of_the_MMHH.pd=
f</a><br></div><div dir=3D"auto"><br></div><div>I can&#39;t seem to find it=
 now, however I think Fred Baker wrote a draft a number of years ago that o=
bserved that multi-addressing on a single interface is also a form of multi=
-homing, meaning that it isn&#39;t a requirement for a &quot;multi-homed&qu=
ot; host to have multiple interfaces attached to multiple and different net=
works. That means most IPv4 hosts, and all IPv6 hosts, by design, are poten=
tial multi-homed hosts.</div><div dir=3D"auto"><br></div><div>Regards,</div=
><div>Mark.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"auto"><div dir=3D"ltr"><br></div><div dir=3D"ltr">Cheers,</div><div dir=
=3D"ltr">Ole</div><div dir=3D"ltr"><br>On 26 Sep 2018, at 04:49, Davey Song=
 &lt;<a href=3D"mailto:songlinjian@gmail.com" rel=3D"noreferrer" target=3D"=
_blank">songlinjian@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=
=3D"cite"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">But in the general =
case the network cannot.<br>
Think host multi-homing.<br></blockquote><div><br></div><div>Yes or no.=C2=
=A0</div><div><br></div><div>Generally speaking the races of IPv6 and IPv4 =
connections on both network and client are going to be suffered by netowrk =
dynamics, including Multi-homing,=C2=A0 route flaps,=C2=A0roaming, or other=
 network falilures. Extremely, a client can get a better IPv6 connection in=
 one second (when IPv6 win the race), and lose it in next second. In such c=
ase, more sophisticated measurement should be done(on client or network) , =
for a longer period, on statistics of RTT and Failure rate, or combinations=
 of them. But=C2=A0in IMHO, the assumption of HE is relatively stable netwo=
rk for short exchange connections. The dynamics exits but relatively rare o=
r no=C2=A0notable impact on HE. So I see no such discussion in RFC8035.</di=
v><div><br></div><div>Davey</div></div></div></div></div></div></div></div>
</div></blockquote></div>_______________________________________________<br=
>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" rel=3D"noreferrer" target=3D"_blank">v6op=
s@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/v6ops</a=
><br>
</blockquote></div></div></div>
</div></div>

--0000000000006397220576c0dae0--


From nobody Wed Sep 26 00:15:05 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC82F130E18; Wed, 26 Sep 2018 00:14:54 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 FkubzeKqBKcN; Wed, 26 Sep 2018 00:14:53 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 1263F130DC8; Wed, 26 Sep 2018 00:14:53 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id l2-v6so16178485qtr.12; Wed, 26 Sep 2018 00:14:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q1+74/RE6aFIm5zuRfkVR7BmN2JB3WjaZ+s7W+zFr7E=; b=lTSWV9CDHyVQ79i2+LLMLKDL6yzj83D7PYa6FuF8Cn0kHViz5R0JB6RlzeGvLl5bhT 7wMudUDREUhG5wtoa+/0rqsbjHh44L94xAxDth0UDnFzHGtFI0i8NFaQpdboIC6dUtpc jy7QJXMV/k494mf4IZrHgWQMr/d/FmkJ8kWkkb11KJzbkT6IDqWCBflfxDFX9bd1B6nS Bi1kvv6FxUhOmrPEIVU3a6S2f19GOA0BfrBETOhxlLIQn+Z4djak6kzt60n3Kj16vhQC FdlObwZgztICEKOqDIe18yJH8SAKi2hqmuRCoJiVmXtAWa3k4L6A6OAA6jP9f60iR0wW iEJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q1+74/RE6aFIm5zuRfkVR7BmN2JB3WjaZ+s7W+zFr7E=; b=qLdSFg3X59JR03mu6J7KpwhvjalmfIMuplJG+d5U1M2o2ng9b2FA+ThxS67ytzLBJJ 9XJGHmRBjq/IwecvQ3BAXnjGvJ7cbq3ynVOXCwywjqLDr5hiwMrSU/ZsN16JrPCOeXdn OVAuCIFaJhdDqh5yMnIF3yGLUbp3fmQNr8AAGIZPcBkKQ+5LiFqesf3sVt+uajxq7/m1 DO2yN9OlfLREXIODWU9lW3TqWY7Ph8NtBX7LoLQ+lhaSsJTSyoxma20i21oB1As2Vf6N AjvXCY2Fg+PttwCmihv6KLbuijGNP6/4Wcq4mdPzziMz2JmEuhLUydAlm48a33/WMm5P kXWg==
X-Gm-Message-State: ABuFfoh/pfzvVZWxI0SIrFcP9goAUdvWAF83OKKUhbCUtbruzAjefXlr mDT19PwJmNYSfP/lm0HCsiQaN0UeIrK8dj/cassjm2qoc4chQQ==
X-Google-Smtp-Source: ACcGV62Wtt8AgRSaBjO/EB/aWzEaar7i9cfUjt31yuOM5QdBCf7iousbDKyvOhvttmgfYd85p1c/AFDhrgF85SymRns=
X-Received: by 2002:ac8:3414:: with SMTP id u20-v6mr3525720qtb.237.1537946092210;  Wed, 26 Sep 2018 00:14:52 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org>
In-Reply-To: <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org>
From: Davey Song <songlinjian@gmail.com>
Date: Wed, 26 Sep 2018 15:14:42 +0800
Message-ID: <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com>
To: otroan@employees.org
Cc: Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, v6ops@ietf.org,  =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary="000000000000828d160576c0fac4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CAhIx0k7vA0HxAU0-vSDjnXq52E>
Subject: Re: [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 07:14:55 -0000

--000000000000828d160576c0fac4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> If we=E2=80=99re discussing host based versus network based happy eyeball=
s, would
> it be naive to think that the network based HE would interfere with the
> client=E2=80=99s HE?
>

Currently this draft only considers IPv4/IPv6 racing situation. The general
address
racing is already done for all clients (rfc6724). As mentioned in the
draft, NHE can
work independenly(without interferance) with the adoption of Client-side
HE.
If client's already support HE, it will query A & AAAA at the same time. NH=
E
can
help reduce the unnecessary traffic emitted by HE client becuase the AAAA
record
will be omitted or delayed if IPv6 connectivity is poorer. I don't see any
interferance now.


> A router knows very little about end to end properties of a connection. I=
t
> could of course do those measurements by looking deeply into packets, but
> it would still be restricted to it=E2=80=99s own topological location.
>
It depends on how far you do the measurement to simulate the end users.
Some APM (application performance measurement) vendor like New Relic
provides sdk implementing on Apps to provide measurement data for analysis
and deliever a good performance monitoring and traffic engineering.
Some provide probes close to clients and edge.

I think maybe there is a crose-layer issues on this draft which should be
simple
 enough and aim IP layer issues. But right now lots of complected
application
layer complexities (like CDN, APM) are involved.


> Compare that with the data available to an MP-TCP host stack.
>

I think MP-TCP or other transmition protocol are based on stable,
high-performance ip layer.


> And note I think HE can=E2=80=99t just be between v4 and v6, but between =
all the
> candidate connections between source and destination.
>

HE(RFC8035) only focus on IP connection seletion right now accroding to the
problem statement:

   "Many communication protocols operating over the modern Internet use
   hostnames.  These often resolve to multiple IP addresses, each of
   which may have different performance and connectivity
   characteristics.  Since specific addresses or address families (IPv4
   or IPv6) may be blocked, broken, or sub-optimal on a network, clients
   that attempt multiple connections in parallel have a chance of
   establishing a connection more quickly.  This document specifies
   requirements for algorithms that reduce this user-visible delay and
   provides an example algorithm."


If there are other candidate connections, they also need a better IP
connectiviy as a bais I think.
NHE at least can give a indicaiton of poor connection for certain address
family (or address) .
It is potentially a low level routing founctions other than hight level
traffic scheduling tools.

Davey

--000000000000828d160576c0fac4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quot=
e"><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
dir=3D"auto"><div dir=3D"ltr">If we=E2=80=99re discussing host based versus=
 network based happy eyeballs, would it be naive to think that the network =
based HE would interfere with the client=E2=80=99s HE?</div></div></blockqu=
ote><div>=C2=A0</div><div>Currently this draft only considers IPv4/IPv6 rac=
ing situation. The general address <br>racing is already done for all clien=
ts (rfc6724). As mentioned in the draft, NHE can <br>work independenly(with=
out interferance) with the adoption of Client-side HE.=C2=A0 <br>If client&=
#39;s already support HE, it will query A &amp; AAAA at the same time.=C2=
=A0<span style=3D"color:rgb(0,0,0);font-size:13.3333px">NHE can <br>help re=
duce the unnecessary traffic</span><span style=3D"color:rgb(0,0,0);font-siz=
e:13.3333px">=C2=A0emitted by HE client becuase=C2=A0</span>the AAAA record=
 <br>will be omitted or delayed if IPv6 connectivity is poorer. I don&#39;t=
 see any interferance now.=C2=A0 =C2=A0 =C2=A0</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div dir=3D"l=
tr"></div><div dir=3D"ltr">A router knows very little about end to end prop=
erties of a connection. It could of course do those measurements by looking=
 deeply into packets, but it would still be restricted to it=E2=80=99s own =
topological location. </div></div></blockquote><div>It depends on how far y=
ou do the measurement to simulate the end users. <br>Some APM (application =
performance measurement) vendor like New Relic <br>provides sdk implementin=
g on Apps to provide measurement data for analysis <br>and deliever a good =
performance monitoring and traffic engineering. <br>Some provide probes clo=
se to clients and edge.=C2=A0</div><div><br></div><div>I think maybe there =
is a crose-layer issues on this draft which should be simple<br>=C2=A0enoug=
h and aim IP layer issues. But right now lots of complected application <br=
>layer complexities (like CDN, APM) are involved.=C2=A0 =C2=A0</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"a=
uto"><div dir=3D"ltr">Compare that with the data available to an MP-TCP hos=
t stack.=C2=A0</div></div></blockquote><div>=C2=A0</div><div>I think MP-TCP=
 or other transmition protocol are based on stable,<br>high-performance ip =
layer.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">And note I th=
ink HE can=E2=80=99t just be between v4 and v6, but between all the candida=
te connections between source and destination.=C2=A0</div></div></blockquot=
e><div><br></div><div>HE(RFC8035) only focus on IP connection seletion righ=
t now accroding to the <br>problem statement:</div><div><br></div><div><pre=
 class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin=
-bottom:0px;break-before:page;color:rgb(0,0,0)">   &quot;Many communication=
 protocols operating over the modern Internet use
   hostnames.  These often resolve to multiple IP addresses, each of
   which may have different performance and connectivity
   characteristics.  Since specific addresses or address families (IPv4
   or IPv6) may be blocked, broken, or sub-optimal on a network, clients
   that attempt multiple connections in parallel have a chance of
   establishing a connection more quickly.  This document specifies
   requirements for algorithms that reduce this user-visible delay and
   provides an example algorithm.&quot;</pre></div><div>=C2=A0</div><div>If=
 there are other candidate connections, they also need a better IP connecti=
viy as a bais I think. <br>NHE at least can give a indicaiton of poor conne=
ction for certain address family (or address) . <br>It is potentially a low=
 level routing founctions other than hight level traffic scheduling tools.<=
/div><div><br></div><div>Davey=C2=A0</div></div></div></div></div>

--000000000000828d160576c0fac4--


From nobody Wed Sep 26 00:28:47 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 986A8130E1E for <v6ops@ietfa.amsl.com>; Wed, 26 Sep 2018 00:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 4CCleLC2g1-h for <v6ops@ietfa.amsl.com>; Wed, 26 Sep 2018 00:28:43 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6A6C130E1A for <v6ops@ietf.org>; Wed, 26 Sep 2018 00:28:42 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 05F1D438D2 for <v6ops@ietf.org>; Wed, 26 Sep 2018 09:28:40 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id E6864438CF; Wed, 26 Sep 2018 09:28:39 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id D67FB20CB2; Wed, 26 Sep 2018 09:28:39 +0200 (CEST)
Date: Wed, 26 Sep 2018 09:28:39 +0200
From: Gert Doering <gert@space.net>
To: Davey Song <songlinjian@gmail.com>
Cc: otroan@employees.org, Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, v6ops@ietf.org, ???????????? <jinmei@wide.ad.jp>
Message-ID: <20180926072839.GD11393@Space.Net>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WOwsUXNV0YEGHQ+1"
Content-Disposition: inline
In-Reply-To: <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7ygu_OgTZZyV5Y0Ti-RnF_aMX3o>
Subject: Re: [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 07:28:46 -0000

--WOwsUXNV0YEGHQ+1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, Sep 26, 2018 at 03:14:42PM +0800, Davey Song wrote:
> NHE can
> help reduce the unnecessary traffic emitted by HE client becuase the AAAA
> record
> will be omitted or delayed if IPv6 connectivity is poorer. I don't see any
> interferance now.

I'm not sure how often I've heard the well-meaning suggestion "just do
not deliver DNS records of type <x> if <condition y>".

It was a bad idea at all times, and it is still a bad idea.  Never withhold
legitimate records.

[..]
> I think MP-TCP or other transmition protocol are based on stable,
> high-performance ip layer.

Read up again what MP-TCP does :-)

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Em=
mer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

--WOwsUXNV0YEGHQ+1
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEruB5jRHVM+CjiYD131bAZeTOf8UFAlurNSQACgkQ31bAZeTO
f8WpxA//WrU+4qOfz/luzGrlTfp2fIpBCUbVtP+lWMbHoyZuS1OQH+o7QvHJNcFW
xTt3RGpNkngUeNePxiJbDs6Mo6bivi2c4RHc3wpJ2kIZz0Mv1JmsIBYQUlsq+4e9
Cxo+E9BWCTJiRi2o0ycy1HEbmBZ/Es8RRVoN8HHwq1JepP2GRIfnlDqNLZwyXCMN
u1KLY5F/0dhtM85D+WqMrV+SPjq7d0J6euRriDh4KNtN4pr3OHCjrjvJbstk3cij
vV0gT93Opl14HikiSZRDLRaSxAOlrKvxYdvairWV54X3IyjqMEX4BDNXYc6+GJY2
IxR5Wp6e28Jy8m+HIhsZyoqmvaCHvHP09oHBahLmC15rwZM7lbYGO10uxJ9fsBpG
q7/o4Py0hpvtIGBirJsbmgQPP+V+2AfRN1HVYoHO7PW9xq4Fp0oZcZhSFxy1jpjs
c8lKFYrWYtljSCH785i+7ZrMtRKZ5+xZOG94YrhbxrkLTzJt5mt0HrpvKr6sai3I
gIjY0adNlk6ealbV79SktCvuTNwQgscAca/1MPlD5mSIpNQkL2SHdtgcUCFYLv05
5rxXWM5DCH8F7VoLljeKdVgog0DtFHze0RaYJMqNgYKvb6PqdEf86252xs3V54bo
c22D8n0ADY/SXs15Rrl+dOE+35kDktGQuCRgeKslp8JdthqwLeY=
=7Gfl
-----END PGP SIGNATURE-----

--WOwsUXNV0YEGHQ+1--


From nobody Wed Sep 26 00:56:46 2018
Return-Path: <xiechf.bri@chinatelecom.cn>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE063130E1B; Wed, 26 Sep 2018 00:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 76-SiIUj9ihc; Wed, 26 Sep 2018 00:56:41 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.223]) by ietfa.amsl.com (Postfix) with ESMTP id D7770130E1A; Wed, 26 Sep 2018 00:56:39 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.80:63737.1509675674
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.77 (unknown [172.18.0.80]) by chinatelecom.cn (HERMES) with SMTP id A48302800A1; Wed, 26 Sep 2018 15:56:17 +0800 (CST)
Received: from DANGMM9A10 ([219.142.69.77]) by App0022 with ESMTP id a487cae9-9147-43e5-9e2e-5945add1bab1 for ggm@algebras.org; Wed Sep 26 15:56:31 2018
X-filter-score: filter<0>
X-Real-From: xiechf.bri@chinatelecom.cn
X-Receive-IP: 219.142.69.77
X-MEDUSA-Status: 0
Date: Wed, 26 Sep 2018 15:56:15 +0800
From: "Chongfeng Xie" <xiechf.bri@chinatelecom.cn>
To: "George Michaelson" <ggm@algebras.org>,  "dnsop WG" <dnsop@ietf.org>
Cc: v6ops <v6ops@ietf.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com>,  <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com>,  <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com>,  <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>,  <20180925072015.GV11393@Space.Net>,  <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com>,  <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org>,  <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com>,  <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 8, 379[cn]
Mime-Version: 1.0
Message-ID: <201809261556142640046@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart461102808632_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/poBivF7O5orBpTDF-4KfdvIMFd0>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 07:56:45 -0000

This is a multi-part message in MIME format.

------=_001_NextPart461102808632_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCkknbSB3b3JraW5nIGluIENoaW5hIHRlbGVjb20uIEVuZCB1c2VycycgZXhwZXJpZW5jZSBp
cyB0aGUgdXBwZXJtb3N0IGltcG9ydGFudCBmb3IgdXMsIGVpdGhlciBpcyBvdmVyIElQdjQgb3Ig
SVB2Ni4gIFBlb3BsZSBoYXZlIGZlYXJzIG9uIElQdjYgdHJhbnNpdGlvbiBiZWNhdXNlIHRoZXkg
YXJlIG5vdCBzdXJlIG9mIElQdjYgcGVyZm9ybWFuY2UuIEFjdHVhbGx5IHdlIGhhdmUgcmVjZWl2
ZWQgdXNlcidzIGNvbXBsYWlucyB3aGVuIElQdjYgd2FzIGRlcGxveWVkLiBJUHY2LW9ubHkgaXMg
YXR0cmFjdGl2Ze+8jGJ1dCBpdCB3aWxsIHRha2UgbG9uZyB0aW1lLiAgSW4gdGhlIGVhcmx5IHN0
YWdlIG9mIGR1YWwtc3RhY2sgZGVwbG95bWVudCwgd2UgY2FuIG5vdCBleHBlY3QgdGhlIElQdjYg
aGFzIG1hdGNoZWQgcGVyZm9ybWFuY2Ugd2l0aCBJUHY0LiBNYW55IGNvdW50cmllcyBhbmQgcmVn
aW9ucyBzdGlsbCBpbiBlYXJseSBkZXZlbHBtZW50IHNob3duIGluIEFQTklDJ3MgZ2xvYmFsIElQ
djYgcGVyZm9ybWFuY2UgbW9uaXRvcmluZyAoc3RhdHMubGFicy5hcG5pYy5uZXQvdjZwZXJmKS4g
TkhFIGlzIGEgcHJvbWlzaW5nIHNvbHV0aW9uIHRvIGVuYWJsZSBuZXR3b3JrIG9wZXJhdG9yIHRv
IHByb3ZpZGUgdGhlaXIgY2xpZW50cyB3aXRoIGJldHRlciBjb25uZWN0aXZpdHkgaW4gZHVhbC1z
dGFjaywgd2hpY2ggd2lsbCBhbHNvIGJlIGhlbHBmdWwgdG8gU1AvQ1BzLiAgSW4gYWRkaXRpb24s
IElQdjYgc2l0dWF0aW9uIGluIG9uZSByZWdpb24gd2lsbCBwZXJzaXN0ZW50IGZvciBsb25nZXIg
cGVyaW9kIGNvbXBhcmVkIHRvIHRoZSBuZXR3b3JrIGR5bmFtaWNzLiBJdCB3aWxsIGJlIGVhc2ll
ciB0byBoYW5kbGUuDQpDaG9uZ2ZlbmcgWGllDQoNCg0KDQp4aWVjaGYuYnJpQGNoaW5hdGVsZWNv
bS5jbg0KIA0KRnJvbTogR2VvcmdlIE1pY2hhZWxzb24NCkRhdGU6IDIwMTgtMDktMjYgMTA6NTgN
ClRvOiBkbnNvcCBXRw0KQ0M6IDx2Nm9wc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbdjZvcHNd
IFtETlNPUF0gTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC12Nm9wcy14aWUtbmV0
d29yay1oYXBweWV5ZWJhbGxzLTAwLnR4dA0KSSBoYXZlIHNhaWQgYmVmb3JlLCBidXQgZG9uJ3Qg
a25vdyBpZiBJIHN0aWxsIGFkaGVyZSB0byBpdCwgYnV0DQphbnl3YXlzLCBoZXJlJ3MgYSBxdWVz
dGlvbjogSG93ICpsb25nKiBkbyBwZW9wbGUgdGhpbmsgYSBiaWFzc2luZw0KbWVjaGFuaXNtIGxp
a2UgSEUgaXMgYSBnb29kIGlkZWE/DQogDQoqIGlzIGl0IGEgZ29vZCBpZGVhICpmb3JldmVyKg0K
IA0KKiBvciBpcyBpdCBhIHRyYW5zaXRpb24gcGF0aCBtZWNoYW5pc20gd2hpY2ggaGFzIGFuIGVu
ZC1vZi1saWZlPw0KIA0KKiBob3cgZG8gd2Uga25vdywgd2hlbiBpdHMgYXQgZW5kLW9mLWxpZmU/
DQogDQpJIHVzZWQgdG8gbG92ZSBIRS4gSSBub3cgaGF2ZSBhIHNlbnNlLCBJJ20gbW9yZSBuZXV0
cmFsLiBNYXliZSwgd2UNCmFjdHVhbGx5IGRvbid0IHdhbnQgbW9kaWZpZWQsIGJldHRlciBoYXBw
eSBleWViYWxscywgYmVjYXVzZSB3ZSB3YW50DQpzaW1wbGVyLCBtb3JlIGRldGVybWluaXN0aWMg
bmV0d29yayBzdGFjayBvdXRjb21lcyB3aXRoIGxlc3MgYmlhcw0KaG9va3M/DQogDQpJIGJhcmVs
eSByZWdpc3RlciBpZiBJIGFuIG9uIHY0IGFueSBtb3JlLiBJIGFzc3VtZSBJJ20gb24gNiBvbiBt
YW55DQpuZXR3b3Jrcy4gVGhpcyBpcyBhcyBhbiBlbmQtdXNlci4gSSBndWVzcyBpZiBJIGFtIHJl
YWxseSBhbiBlbmQgdXNlciwNCnRoaXMgYmVsaWVmIEkgdW5kZXJzdGFuZCBUQ1AgYW5kIFVEUCBp
cyBmYWxzZSwgYW5kIEkgc2hvdWxkIHN0b3ANCndvcnJ5aW5nIChhcyBhbiBlbmQgdXNlcikNCk9u
IFdlZCwgU2VwIDI2LCAyMDE4IGF0IDEyOjQ5IFBNIERhdmV5IFNvbmcgPHNvbmdsaW5qaWFuQGdt
YWlsLmNvbT4gd3JvdGU6DQo+Pg0KPj4gQnV0IGluIHRoZSBnZW5lcmFsIGNhc2UgdGhlIG5ldHdv
cmsgY2Fubm90Lg0KPj4gVGhpbmsgaG9zdCBtdWx0aS1ob21pbmcuDQo+DQo+DQo+IFllcyBvciBu
by4NCj4NCj4gR2VuZXJhbGx5IHNwZWFraW5nIHRoZSByYWNlcyBvZiBJUHY2IGFuZCBJUHY0IGNv
bm5lY3Rpb25zIG9uIGJvdGggbmV0d29yayBhbmQgY2xpZW50IGFyZSBnb2luZyB0byBiZSBzdWZm
ZXJlZCBieSBuZXRvd3JrIGR5bmFtaWNzLCBpbmNsdWRpbmcgTXVsdGktaG9taW5nLCAgcm91dGUg
ZmxhcHMsIHJvYW1pbmcsIG9yIG90aGVyIG5ldHdvcmsgZmFsaWx1cmVzLiBFeHRyZW1lbHksIGEg
Y2xpZW50IGNhbiBnZXQgYSBiZXR0ZXIgSVB2NiBjb25uZWN0aW9uIGluIG9uZSBzZWNvbmQgKHdo
ZW4gSVB2NiB3aW4gdGhlIHJhY2UpLCBhbmQgbG9zZSBpdCBpbiBuZXh0IHNlY29uZC4gSW4gc3Vj
aCBjYXNlLCBtb3JlIHNvcGhpc3RpY2F0ZWQgbWVhc3VyZW1lbnQgc2hvdWxkIGJlIGRvbmUob24g
Y2xpZW50IG9yIG5ldHdvcmspICwgZm9yIGEgbG9uZ2VyIHBlcmlvZCwgb24gc3RhdGlzdGljcyBv
ZiBSVFQgYW5kIEZhaWx1cmUgcmF0ZSwgb3IgY29tYmluYXRpb25zIG9mIHRoZW0uIEJ1dCBpbiBJ
TUhPLCB0aGUgYXNzdW1wdGlvbiBvZiBIRSBpcyByZWxhdGl2ZWx5IHN0YWJsZSBuZXR3b3JrIGZv
ciBzaG9ydCBleGNoYW5nZSBjb25uZWN0aW9ucy4gVGhlIGR5bmFtaWNzIGV4aXRzIGJ1dCByZWxh
dGl2ZWx5IHJhcmUgb3Igbm8gbm90YWJsZSBpbXBhY3Qgb24gSEUuIFNvIEkgc2VlIG5vIHN1Y2gg
ZGlzY3Vzc2lvbiBpbiBSRkM4MDM1Lg0KPg0KPiBEYXZleQ0KPiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBETlNPUCBtYWlsaW5nIGxpc3QNCj4gRE5T
T1BAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbnNv
cA0KIA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnY2
b3BzIG1haWxpbmcgbGlzdA0KdjZvcHNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vdjZvcHMNCiANCg==

------=_001_NextPart461102808632_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3Dutf-8"><style>body { line-height: 1.5; }blockquote { margin-top: 0px; =
margin-bottom: 0px; margin-left: 0.5em; }body { font-size: 10.5pt; font-fa=
mily: 'Microsoft YaHei UI'; color: rgb(0, 0, 0); line-height: 1.5; }</styl=
e></head><body>=0A<div><span></span><br></div><div><br></div><div><span st=
yle=3D"font-family: &quot;" microsoft=3D"" yahei=3D"" ui'";=3D"" font-size=
:=3D"" 14px;=3D"" color:=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" background-colo=
r:=3D"" rgba(0,=3D"" font-weight:=3D"" normal;=3D"" font-style:=3D"" norma=
l;text-decoration:=3D"" none;'=3D"">I'm&nbsp;working&nbsp;in&nbsp;China&nb=
sp;telecom.&nbsp;End&nbsp;users'&nbsp;experience&nbsp;is&nbsp;the&nbsp;upp=
ermost&nbsp;important&nbsp;for&nbsp;us,&nbsp;either&nbsp;is&nbsp;over&nbsp=
;IPv4&nbsp;or&nbsp;IPv6.&nbsp;&nbsp;People&nbsp;have&nbsp;fears&nbsp;on&nb=
sp;IPv6&nbsp;transition&nbsp;because&nbsp;they&nbsp;are&nbsp;not&nbsp;sure=
&nbsp;of&nbsp;IPv6&nbsp;performance.&nbsp;Actually&nbsp;we&nbsp;have&nbsp;=
received&nbsp;user's&nbsp;complains&nbsp;when&nbsp;IPv6&nbsp;was&nbsp;depl=
oyed.&nbsp;IPv6-only&nbsp;is&nbsp;attractive=EF=BC=8Cbut&nbsp;it&nbsp;will=
&nbsp;take&nbsp;long&nbsp;time.&nbsp;&nbsp;In&nbsp;the&nbsp;early&nbsp;sta=
ge&nbsp;of&nbsp;dual-stack&nbsp;deployment,&nbsp;we&nbsp;can&nbsp;not&nbsp=
;expect&nbsp;the&nbsp;IPv6&nbsp;has&nbsp;matched&nbsp;performance&nbsp;wit=
h&nbsp;IPv4.&nbsp;Many&nbsp;countries&nbsp;and&nbsp;regions&nbsp;still&nbs=
p;in&nbsp;early&nbsp;develpment&nbsp;shown&nbsp;in&nbsp;APNIC's&nbsp;globa=
l&nbsp;IPv6&nbsp;performance&nbsp;monitoring&nbsp;(stats.labs.apnic.net/v6=
perf).&nbsp;NHE&nbsp;is&nbsp;a&nbsp;promising&nbsp;solution&nbsp;to&nbsp;e=
nable&nbsp;network&nbsp;operator&nbsp;to&nbsp;provide&nbsp;their&nbsp;clie=
nts&nbsp;with&nbsp;better&nbsp;connectivity&nbsp;in&nbsp;dual-stack,&nbsp;=
which&nbsp;will&nbsp;also&nbsp;be&nbsp;helpful&nbsp;to&nbsp;SP/CPs. &nbsp;=
In&nbsp;addition,&nbsp;IPv6&nbsp;situation&nbsp;in&nbsp;one&nbsp;region&nb=
sp;will&nbsp;persistent&nbsp;for&nbsp;longer&nbsp;period&nbsp;compared&nbs=
p;to&nbsp;the&nbsp;network&nbsp;dynamics.&nbsp;It&nbsp;will&nbsp;be&nbsp;e=
asier&nbsp;to&nbsp;handle.</span></div><div><span style=3D"font-family: &q=
uot;" microsoft=3D"" yahei=3D"" ui'";=3D"" font-size:=3D"" 14px;=3D"" colo=
r:=3D"" rgb(0,=3D"" 0,=3D"" 0);=3D"" background-color:=3D"" rgba(0,=3D"" f=
ont-weight:=3D"" normal;=3D"" font-style:=3D"" normal;text-decoration:=3D"=
" none;'=3D"">Chongfeng Xie</span></div>=0A<div><br></div><hr style=3D"wid=
th: 210px; height: 1px;" color=3D"#b5c4df" size=3D"1" align=3D"left">=0A<d=
iv><span><div style=3D"MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt=
"><div>xiechf.bri@chinatelecom.cn</div></div></span></div>=0A<blockquote s=
tyle=3D"margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em;"><div>&nb=
sp;</div><div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:=
3.0pt 0cm 0cm 0cm"><div style=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FO=
NT-SIZE: 12px;FONT-FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef; PADDI=
NG-BOTTOM: 8px; PADDING-TOP: 8px"><div><b>From:</b>&nbsp;<a href=3D"mailto=
:ggm@algebras.org">George Michaelson</a></div><div><b>Date:</b>&nbsp;2018-=
09-26&nbsp;10:58</div><div><b>To:</b>&nbsp;<a href=3D"mailto:dnsop@ietf.or=
g">dnsop WG</a></div><div><b>CC:</b>&nbsp;<a href=3D"mailto:v6ops@ietf.org=
">&lt;v6ops@ietf.org&gt;</a></div><div><b>Subject:</b>&nbsp;Re: [v6ops] [D=
NSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-0=
0.txt</div></div></div><div><div>I have said before, but don't know if I s=
till adhere to it, but</div>=0A<div>anyways, here's a question: How *long*=
 do people think a biassing</div>=0A<div>mechanism like HE is a good idea?=
</div>=0A<div>&nbsp;</div>=0A<div> * is it a good idea *forever*</div>=0A<=
div>&nbsp;</div>=0A<div> * or is it a transition path mechanism which has =
an end-of-life?</div>=0A<div>&nbsp;</div>=0A<div> * how do we know, when i=
ts at end-of-life?</div>=0A<div>&nbsp;</div>=0A<div>I used to love HE. I n=
ow have a sense, I'm more neutral. Maybe, we</div>=0A<div>actually don't w=
ant modified, better happy eyeballs, because we want</div>=0A<div>simpler,=
 more deterministic network stack outcomes with less bias</div>=0A<div>hoo=
ks?</div>=0A<div>&nbsp;</div>=0A<div>I barely register if I an on v4 any m=
ore. I assume I'm on 6 on many</div>=0A<div>networks. This is as an end-us=
er. I guess if I am really an end user,</div>=0A<div>this belief I underst=
and TCP and UDP is false, and I should stop</div>=0A<div>worrying (as an e=
nd user)</div>=0A<div>On Wed, Sep 26, 2018 at 12:49 PM Davey Song &lt;song=
linjian@gmail.com&gt; wrote:</div>=0A<div>&gt;&gt;</div>=0A<div>&gt;&gt; B=
ut in the general case the network cannot.</div>=0A<div>&gt;&gt; Think hos=
t multi-homing.</div>=0A<div>&gt;</div>=0A<div>&gt;</div>=0A<div>&gt; Yes =
or no.</div>=0A<div>&gt;</div>=0A<div>&gt; Generally speaking the races of=
 IPv6 and IPv4 connections on both network and client are going to be suff=
ered by netowrk dynamics, including Multi-homing,&nbsp; route flaps, roami=
ng, or other network falilures. Extremely, a client can get a better IPv6 =
connection in one second (when IPv6 win the race), and lose it in next sec=
ond. In such case, more sophisticated measurement should be done(on client=
 or network) , for a longer period, on statistics of RTT and Failure rate,=
 or combinations of them. But in IMHO, the assumption of HE is relatively =
stable network for short exchange connections. The dynamics exits but rela=
tively rare or no notable impact on HE. So I see no such discussion in RFC=
8035.</div>=0A<div>&gt;</div>=0A<div>&gt; Davey</div>=0A<div>&gt; ________=
_______________________________________</div>=0A<div>&gt; DNSOP mailing li=
st</div>=0A<div>&gt; DNSOP@ietf.org</div>=0A<div>&gt; https://www.ietf.org=
/mailman/listinfo/dnsop</div>=0A<div>&nbsp;</div>=0A<div>_________________=
______________________________</div>=0A<div>v6ops mailing list</div>=0A<di=
v>v6ops@ietf.org</div>=0A<div>https://www.ietf.org/mailman/listinfo/v6ops<=
/div>=0A<div>&nbsp;</div>=0A</div></blockquote>=0A</body></html>
------=_001_NextPart461102808632_=------


From nobody Wed Sep 26 01:01:32 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66FE7130E1E for <v6ops@ietfa.amsl.com>; Wed, 26 Sep 2018 01:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 DTfPTlO4ja7d for <v6ops@ietfa.amsl.com>; Wed, 26 Sep 2018 01:01:29 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DACD130DC2 for <v6ops@ietf.org>; Wed, 26 Sep 2018 01:01:28 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 30BC4438D0 for <v6ops@ietf.org>; Wed, 26 Sep 2018 10:01:27 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 1E83941B4B; Wed, 26 Sep 2018 10:01:27 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 19B7D20EB8; Wed, 26 Sep 2018 10:01:27 +0200 (CEST)
Date: Wed, 26 Sep 2018 10:01:27 +0200
From: Gert Doering <gert@space.net>
To: Chongfeng Xie <xiechf.bri@chinatelecom.cn>
Cc: George Michaelson <ggm@algebras.org>, dnsop WG <dnsop@ietf.org>, v6ops <v6ops@ietf.org>
Message-ID: <20180926080126.GF11393@Space.Net>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <201809261556142640046@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201809261556142640046@chinatelecom.cn>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ubZNciRiFDanPFAdm1aGz3wgPQY>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 08:01:31 -0000

Hi,

On Wed, Sep 26, 2018 at 03:56:15PM +0800, Chongfeng Xie wrote:
> In the early stage of dual-stack deployment, we can not expect the 
> IPv6 has matched performance with IPv4. 

This is true.  But "early stage of dual-stack deployment" was 15 years ago,
so this is not a valid excuse today.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


From nobody Wed Sep 26 02:28:05 2018
Return-Path: <pch-bCE2691D2@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 565B9130E0E; Wed, 26 Sep 2018 02:27:58 -0700 (PDT)
X-Quarantine-ID: <giNguRAerm2S>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 giNguRAerm2S; Wed, 26 Sep 2018 02:27:56 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 DB27E130DD0; Wed, 26 Sep 2018 02:27:55 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1g566p-0000GjC; Wed, 26 Sep 2018 11:27:51 +0200
Message-Id: <m1g566p-0000GjC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
Cc: George Michaelson <ggm@algebras.org>
Cc: dnsop WG <dnsop@ietf.org>
From: Philip Homburg <pch-v6ops-8@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> 
In-reply-to: Your message of "Wed, 26 Sep 2018 12:58:30 +1000 ." <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> 
Date: Wed, 26 Sep 2018 11:27:50 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/vLXWFzcazEfWLUdry8aL3giPUxk>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 09:27:58 -0000

In your letter dated Wed, 26 Sep 2018 12:58:30 +1000 you wrote:
>I have said before, but don't know if I still adhere to it, but
>anyways, here's a question: How *long* do people think a biassing
>mechanism like HE is a good idea?
>
>I used to love HE. I now have a sense, I'm more neutral. Maybe, we
>actually don't want modified, better happy eyeballs, because we want
>simpler, more deterministic network stack outcomes with less bias
>hooks?

In my own implementation of HE, I globally (i.e. across all processes) keep
track of the time it takes to establish a TCP connection for individual
addresses, and I compute values for IPv4 and IPv6.

Conceptually I like the idea that if you know (from past measurements) that 
it takes 100ms or less to establish a connection, you don't wait for a
couple of seconds for an attempt to fail. In addition, instead of trying
one address at a time, you can add a new connection attempt when the
previous one is still running.

All of this provides for a better user experience, at the cost of being
less deterministic and masking failures.

Note that in my implementation, I select the best address (giving a 30ms
preference to IPv6) wait for the expected time for the TCP connection
to complete and only if that timer expires, move to the next address.
So there is no race.


From nobody Wed Sep 26 03:58:27 2018
Return-Path: <dot@dotat.at>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 473BB130E81; Wed, 26 Sep 2018 03:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 VXD51YVE3B8X; Wed, 26 Sep 2018 03:58:13 -0700 (PDT)
Received: from ppsw-31.csi.cam.ac.uk (ppsw-31.csi.cam.ac.uk [131.111.8.131]) (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 ED030130E7F; Wed, 26 Sep 2018 03:58:12 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:57782) by ppsw-31.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1g57WB-000LwM-M6 (Exim 4.91) (return-path <dot@dotat.at>); Wed, 26 Sep 2018 11:58:07 +0100
Date: Wed, 26 Sep 2018 11:58:07 +0100
From: Tony Finch <dot@dotat.at>
To: Gert Doering <gert@space.net>
cc: Davey Song <songlinjian@gmail.com>, dnsop <dnsop@ietf.org>,  otroan@employees.org, v6ops@ietf.org
In-Reply-To: <20180926072839.GD11393@Space.Net>
Message-ID: <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/b4eD4WsiukxzbNkPVV9Mc34nKt4>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 10:58:15 -0000

Gert Doering <gert@space.net> wrote:
>
> I'm not sure how often I've heard the well-meaning suggestion "just do
> not deliver DNS records of type <x> if <condition y>".
>
> It was a bad idea at all times, and it is still a bad idea.  Never withhold
> legitimate records.

I think it's even worse in this case.

The point of happy eyeballs is to work around crappy or broken networks,
and this NHE idea sounds to me like making a huge effort to work around
broken or crappy networks rather than making the effort to fix them. It
seems misdirected to me.

If it's a third party network with crappy v6 connectivity, why not just
drop their v6 prefixes and let normal HE work as it should?

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
defend the right to speak, write, worship, associate, and vote freely


From nobody Wed Sep 26 06:44:12 2018
Return-Path: <bs7652@att.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34F93130E0C; Wed, 26 Sep 2018 06:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 wQPvJf361yGD; Wed, 26 Sep 2018 06:44:01 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 12952124BE5; Wed, 26 Sep 2018 06:44:00 -0700 (PDT)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w8QDbp98036217; Wed, 26 Sep 2018 09:43:53 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0083689.ppops.net-00191d01. with ESMTP id 2mr806wqax-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 26 Sep 2018 09:43:38 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w8QDgAju011360; Wed, 26 Sep 2018 09:42:10 -0400
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [135.47.91.179]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w8QDfwuY011021; Wed, 26 Sep 2018 09:42:01 -0400
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [127.0.0.1]) by zlp30484.vci.att.com (Service) with ESMTP id 377CC404C95A; Wed, 26 Sep 2018 13:41:58 +0000 (GMT)
Received: from GAALPA1MSGHUBAC.ITServices.sbc.com (unknown [130.8.218.152]) by zlp30484.vci.att.com (Service) with ESMTPS id 2307B4000376; Wed, 26 Sep 2018 13:41:58 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.98]) by GAALPA1MSGHUBAC.ITServices.sbc.com ([130.8.218.152]) with mapi id 14.03.0415.000; Wed, 26 Sep 2018 09:41:57 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Tony Finch'" <dot@dotat.at>, Gert Doering <gert@space.net>
CC: dnsop <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
Thread-Index: AQHUVYfwTxIu8Iu3YEmL4lW9mKfKqaUCeEGw
Date: Wed, 26 Sep 2018 13:41:56 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.61.166.248]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-26_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809260133
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ehHydYBj6P293ZwTZEYuHxeGc8I>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 13:44:03 -0000

> The point of happy eyeballs is to work around crappy or broken networks,

That's my recollection, too. And I'm really struggling to figure out which =
are the broken IPv6 networks NHE is trying to work around. The possible net=
works are: LAN, ISP/access, core/transit, and destination. I'm not aware of=
 issues with core/transit networks. I'm also not aware of major issues with=
 IPv6 broken at the destination (authoritative DNS servers supplying AAAA r=
ecords, but those IPv6 addresses aren't actually reachable over the Interne=
t or have incredibly slow IPv6 connectivity to the Internet).

My recollection is that the brokenness being worked around was primarily ca=
used by non-functioning IPv6 connections that were being advertised to host=
s, were provided AAAA addresses during DNS resolution (over IPv4), but didn=
't have actual IPv6 connectivity to The Internet. Teredo and 6to4 in CE rou=
ters and host OSs were primary causes of the problem, exacerbated by DNS re=
solvers (sitting on IPv4-only networks) providing AAAA records to DNS queri=
es over IPv4. The destination network was *not* the source of the broken IP=
v6. The problem was very, very local. HE wasn't in response to minor perfor=
mance differentials between IPv4 and IPv6 (to pick the one that worked bett=
er). It was about not waiting an entire 60 seconds (or more) for a 100% bro=
ken advertised IPv6 connection to fail before using IPv4.=20

Some questions I have are:
Why would an ISP choose to deploy partial or broken IPv6 + NHE, rather than=
 properly functioning IPv6? I would think we should be recommending deployi=
ng properly functioning IPv6 rather than broken IPv6 + NHE. I'm not aware o=
f a compelling reason at this stage of the game for non-IPv6 or partial-IPv=
6 ISPs to be providing AAAA to DNS queries over IPv4. Not providing AAAA ov=
er IPv4 DNS in this case is much easier than the proposed NHE.

As for CDN statements made in this thread: CDNs are in the business of opti=
mizing connections to their content. HE isn't about optimizing connections =
-- it's about more quickly reacting to the likelihood of outright brokennes=
s. But it sounds like NHE *is* about optimizing (where IPv6 isn't broken, b=
ut is just really slow)? I'm a bit confused about this.

I've done various IPv4/IPv6 latency tests from inside my home, over time.=20
Back when I had an ISP that was experimenting with IPv6 by having a single =
6rd BR in the center of the US and that ISP was having other "we don't know=
 what we're doing" issues, the IPv6 and general IP-connectivity performance=
 was pretty abysmal. Now that I have an ISP (for the past 6 years) that has=
 deployed a rock solid IPv6 solution (and I successfully got all the Teredo=
, 6to4, and ISATAP disabled on every device in my home), I have no problem.=
 Which suggests IPv6 issues related to poor IPv6 deployments in destination=
 networks isn't an issue for me. If it's an issue elsewhere in the world, p=
lease provide statistics -- I haven't seen any statistics presented by prop=
onents of NHE related to the severity of whichever problem they're trying t=
o solve. My experience suggests that ISPs who deploy IPv6 properly have no =
need for NHE.

It really sounds like the main thing NHE is trying to "solve" is "I'm an IS=
P who wants to deploy bad, partial, or broken IPv6 and need something that =
will keep my users from suffering too horribly from my ineptitude." I'm not=
 sure that's a compelling reason for an RFC. I also question whether such i=
nept ISPs would make use of NHE, even if it were available.
Barbara




From nobody Wed Sep 26 08:16:02 2018
Return-Path: <dot@dotat.at>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4A012008A; Wed, 26 Sep 2018 08:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 4xEhQNIVrbfB; Wed, 26 Sep 2018 08:15:58 -0700 (PDT)
Received: from ppsw-30.csi.cam.ac.uk (ppsw-30.csi.cam.ac.uk [131.111.8.130]) (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 44823130E30; Wed, 26 Sep 2018 08:15:57 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:50068) by ppsw-30.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1g5BXc-000nkC-fp (Exim 4.91) (return-path <dot@dotat.at>); Wed, 26 Sep 2018 16:15:52 +0100
Date: Wed, 26 Sep 2018 16:15:52 +0100
From: Tony Finch <dot@dotat.at>
To: "STARK, BARBARA H" <bs7652@att.com>
cc: Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com>
Message-ID: <alpine.DEB.2.20.1809261607110.3596@grey.csi.cam.ac.uk>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/G940PI0nCwxhMYgZebY3LWGkMQo>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 15:16:00 -0000

STARK, BARBARA H <bs7652@att.com> wrote:

> Why would an ISP choose to deploy partial or broken IPv6 + NHE, rather
> than properly functioning IPv6?

That was my initial reaction too :-) I think the actual idea is to work
around brokenness on third party networks, e.g. the ISP has working v6,
the web site has working v6, but there's bad connectivity between them.
(It doesn't help that there are some stupid peering wars going on between
tier 1 v6 providers, as mentioned in the v6 section of [1].)

The right fix, I think, is to get better peering or to filter broken
routes. It would seem to me to be better to implement the fix in the
network layer not the DNS layer, since it's a network problem not a DNS
problem.

[1] https://blog.apnic.net/2018/09/21/2018-national-internet-segments-reliability-report/

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
South Utsire, Forties, Cromarty: Westerly 5 to 7, perhaps gale 8 later, but
variable 4 for a time. Moderate or rough, occasionally very rough in South
Utsire. Drizzle, rain later. Moderate or good.


From nobody Wed Sep 26 08:38:15 2018
Return-Path: <tpauly@apple.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD403130EBD; Wed, 26 Sep 2018 08:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 3Qs68VrmwoD3; Wed, 26 Sep 2018 08:38:11 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) (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 83B83130EAB; Wed, 26 Sep 2018 08:38:11 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.22/8.16.0.22) with SMTP id w8QFQfsS001210; Wed, 26 Sep 2018 08:38:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : content-transfer-encoding : subject : date : references : to : in-reply-to : message-id; s=20180706; bh=/N9+McPudYu8cC/DXLPq8geHE9o+onSK9zwbx5Bgyuw=; b=I3Kni/Z8wpC07Z9ujKOF2/d70SW1kUgKOmz4bkfl7DtPIG5syPg9oRNRF+WdP4KPa+BF KUW7oZdIqPjMWSC0pp0MkRLqEA/WWHCaTOVWEIe+3A/qUKIw+jRKuHsSk3V0rIhGSQ0S cYqY22C6lJpz0qa+fyjXscuevtfU7xDnV2/ls7QftSk3i9cfZJaizFRPM6uRjwZVB3r0 nNua42Y/3V5cVQ+IDLABca5nfJ2MqlFp1w+KhaQnSZVJWt1Pag4UAIcNdPnO44Jaq8CT CVJKvZps8ICcnJMoMYGRzRRa4duEwnhVBQo2sIYGUrL3EryoL4toUFb5SDBisvqD9n8Z Hw== 
Received: from mr2-mtap-s03.rno.apple.com (mr2-mtap-s03.rno.apple.com [17.179.226.135]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2mnjdxh2ej-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Sep 2018 08:38:05 -0700
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by mr2-mtap-s03.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PFO00KN963EHA70@mr2-mtap-s03.rno.apple.com>; Wed, 26 Sep 2018 08:38:02 -0700 (PDT)
Received: from process_viserion-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PFO00B005GLBX00@nwk-mmpp-sz11.apple.com>; Wed, 26 Sep 2018 08:38:02 -0700 (PDT)
X-Va-A: 
X-Va-T-CD: 144617641ac748cde9c70ef99e507dfd
X-Va-E-CD: 8bc0b9c16ce221a945dc6496e27bf97d
X-Va-R-CD: 509f92fdfa9cd7b468cf80727b9f9984
X-Va-CD: 0
X-Va-ID: e184f48a-f6b1-47a5-818d-cdaef90e31a6
X-V-A: 
X-V-T-CD: 67cf6a6b67f967a4f6526e9ad78271ed
X-V-E-CD: 8bc0b9c16ce221a945dc6496e27bf97d
X-V-R-CD: 509f92fdfa9cd7b468cf80727b9f9984
X-V-CD: 0
X-V-ID: dda272d4-1025-4455-9335-3c7e622b6c31
Received: from process_milters-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PFO0000061YD900@nwk-mmpp-sz11.apple.com>; Wed, 26 Sep 2018 08:38:01 -0700 (PDT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-09-26_08:,, signatures=0
X-Proofpoint-Scanner-Instance: nwk-grpmailp-qapp14.corp.apple.com-10000_instance1
Received: from [17.234.44.107] (unknown [17.234.44.107]) by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PFO00EFS63DXQ40@nwk-mmpp-sz11.apple.com>; Wed, 26 Sep 2018 08:38:01 -0700 (PDT)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Content-transfer-encoding: quoted-printable
Date: Wed, 26 Sep 2018 08:37:52 -0700
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com> <alpine.DEB.2.20.1809261607110.3596@grey.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>, "STARK, BARBARA H" <bs7652@att.com>, dnsop <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Davey Song <songlinjian@gmail.com>
In-reply-to: <alpine.DEB.2.20.1809261607110.3596@grey.csi.cam.ac.uk>
Message-id: <697C1F5F-D17E-48E7-9EC0-C0E412362EDB@apple.com>
X-Mailer: Apple Mail (2.3445.100.36)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-26_08:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kkFK-LM6-kirMXy807AyMJAlGjw>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 15:38:14 -0000

+1 to the point that the proposal for NHE is essentially a mechanism for =
the ISP and/or content provider to work around a broken deployment that =
they should be in a position to fix themselves, or between one another =
as Tony describes.

The point of client-side Happy Eyeballs is to work around broken or =
suboptimal situations that the client has no control over. Following the =
analogy, the server or ISP should only employ a parallel mechanism in =
order to work around some problem it has no ability to fix =
otherwise=E2=80=94such as hiding IPv6 from clients with somehow broken =
IPv6 stacks. This isn't what the situation is like, however.

The part that remains interesting is suggestions for networks to collect =
more reports on the relative health of IPv4 and IPv6 connections, to =
help fix bugs and broken deployments. Focusing on these improvements =
rather than filtering DNS answers seems like it would be a more fruitful =
direction.

Best,
Tommy

> On Sep 26, 2018, at 8:15 AM, Tony Finch <dot@dotat.at> wrote:
>=20
> STARK, BARBARA H <bs7652@att.com> wrote:
>=20
>> Why would an ISP choose to deploy partial or broken IPv6 + NHE, =
rather
>> than properly functioning IPv6?
>=20
> That was my initial reaction too :-) I think the actual idea is to =
work
> around brokenness on third party networks, e.g. the ISP has working =
v6,
> the web site has working v6, but there's bad connectivity between =
them.
> (It doesn't help that there are some stupid peering wars going on =
between
> tier 1 v6 providers, as mentioned in the v6 section of [1].)
>=20
> The right fix, I think, is to get better peering or to filter broken
> routes. It would seem to me to be better to implement the fix in the
> network layer not the DNS layer, since it's a network problem not a =
DNS
> problem.
>=20
> [1] =
https://blog.apnic.net/2018/09/21/2018-national-internet-segments-reliabil=
ity-report/
>=20
> Tony.
> --=20
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> South Utsire, Forties, Cromarty: Westerly 5 to 7, perhaps gale 8 =
later, but
> variable 4 for a time. Moderate or rough, occasionally very rough in =
South
> Utsire. Drizzle, rain later. Moderate or good.
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Wed Sep 26 08:52:00 2018
Return-Path: <prvs=1807f66189=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B634E130EBA; Wed, 26 Sep 2018 08:51:52 -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
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 VeC8ZkAt7OY8; Wed, 26 Sep 2018 08:51:49 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E98FE130E19; Wed, 26 Sep 2018 08:51:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1537977107; x=1538581907; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=oibE6CQCHHOCC0ez39CAEhKMnDFrJUje4/abqpW6M6A=; b=i2mN0wcTOsR9y BYkojnbQz8nqQcEokOiaX5chnwFJB8b13rqA5JandII2zFiCxfzIsiTinBGzugBt ETlstEtqDi0bFKK/5OJ1Mvnmfi0T4CfmQA6qnJxggeeRTMOMyuElflpxniclu0by e3ZtcO00dbv3qvP+3d0wiFsYT3J0RM=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 26 Sep 2018 17:51:47 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 26 Sep 2018 17:51:47 +0200
Received: from [45.6.251.186] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005889253.msg; Wed, 26 Sep 2018 17:51:45 +0200
X-MDRemoteIP: 2001:13c7:7003:200:ac67:962a:35ef:c4d
X-MDHelo: [45.6.251.186]
X-MDArrival-Date: Wed, 26 Sep 2018 17:51:45 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1807f66189=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Wed, 26 Sep 2018 12:51:37 -0300
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "STARK, BARBARA H" <bs7652@att.com>, 'Tony Finch' <dot@dotat.at>, Gert Doering <gert@space.net>
CC: dnsop <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <C1CA71E7-C3FF-4F80-8EF6-D3A938F05FC8@consulintel.es>
Thread-Topic: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Py6Tc5VoNBH07cfZ3gOUbP5UG38>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 15:51:53 -0000

Hi Barbara,

In my experience, there are two ways IPv6 can be broken:
1) ICMPv6 being filtered, so PMTUD doesn't work.
2) IPv6 deployment issues (including having AAAA records with no or bad IPv=
6 connectivity).

HE only helps for 2).

But 2 can be caused in different points between the source and destination,=
 and in most of the cases is bad transit/peering more often than the LANs o=
r the ISP deploying IPv6 badly in its own network.

What is missing is that, unfortunately, many folks don't do the same level =
of monitoring on their IPv6 networks than IPv4 ones, or if the destination =
has AAAA, but they don't have IPv6 enabled, of course, they aren=E2=80=99t =
monitoring at all a non-existing IPv6 network.

Also, if the problem is caused by 1, is the ISP deploying IPv6, then one th=
at need to get some kind of alert from the customers about failing end-site=
s, and contact them or their transits ...

At the end they need to be able to cooperate resolving the problem.

There is an example about this. I've detected several years ago that 1&1 de=
ploys IPv6 to their customers, but even if I tried personally contacting th=
em they did nothing. I kept insisting for 3 years, but I already give up.

This means that thousands of web site with IPv6 aren't reachable for many c=
ustomers. Of course, because in this case is due to 1), you can't reach tho=
se web sites neither with IPv6 or IPv4 (unless you manually disable IPv6 in=
 the browser or OS).

Regards,
Jordi
=20
=20

=EF=BB=BF-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de "STARK, BARBARA H" <bs7652@=
att.com>
Fecha: mi=C3=A9rcoles, 26 de septiembre de 2018, 10:45
Para: 'Tony Finch' <dot@dotat.at>, Gert Doering <gert@space.net>
CC: dnsop <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Asunto: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-ne=
twork-happyeyeballs-00.txt

    > The point of happy eyeballs is to work around crappy or broken networ=
ks,
   =20
    That's my recollection, too. And I'm really struggling to figure out wh=
ich are the broken IPv6 networks NHE is trying to work around. The possible=
 networks are: LAN, ISP/access, core/transit, and destination. I'm not awar=
e of issues with core/transit networks. I'm also not aware of major issues =
with IPv6 broken at the destination (authoritative DNS servers supplying AA=
AA records, but those IPv6 addresses aren't actually reachable over the Int=
ernet or have incredibly slow IPv6 connectivity to the Internet).
   =20
    My recollection is that the brokenness being worked around was primaril=
y caused by non-functioning IPv6 connections that were being advertised to =
hosts, were provided AAAA addresses during DNS resolution (over IPv4), but =
didn't have actual IPv6 connectivity to The Internet. Teredo and 6to4 in CE=
 routers and host OSs were primary causes of the problem, exacerbated by DN=
S resolvers (sitting on IPv4-only networks) providing AAAA records to DNS q=
ueries over IPv4. The destination network was *not* the source of the broke=
n IPv6. The problem was very, very local. HE wasn't in response to minor pe=
rformance differentials between IPv4 and IPv6 (to pick the one that worked =
better). It was about not waiting an entire 60 seconds (or more) for a 100%=
 broken advertised IPv6 connection to fail before using IPv4.=20
   =20
    Some questions I have are:
    Why would an ISP choose to deploy partial or broken IPv6 + NHE, rather =
than properly functioning IPv6? I would think we should be recommending dep=
loying properly functioning IPv6 rather than broken IPv6 + NHE. I'm not awa=
re of a compelling reason at this stage of the game for non-IPv6 or partial=
-IPv6 ISPs to be providing AAAA to DNS queries over IPv4. Not providing AAA=
A over IPv4 DNS in this case is much easier than the proposed NHE.
   =20
    As for CDN statements made in this thread: CDNs are in the business of =
optimizing connections to their content. HE isn't about optimizing connecti=
ons -- it's about more quickly reacting to the likelihood of outright broke=
nness. But it sounds like NHE *is* about optimizing (where IPv6 isn't broke=
n, but is just really slow)? I'm a bit confused about this.
   =20
    I've done various IPv4/IPv6 latency tests from inside my home, over tim=
e.=20
    Back when I had an ISP that was experimenting with IPv6 by having a sin=
gle 6rd BR in the center of the US and that ISP was having other "we don't =
know what we're doing" issues, the IPv6 and general IP-connectivity perform=
ance was pretty abysmal. Now that I have an ISP (for the past 6 years) that=
 has deployed a rock solid IPv6 solution (and I successfully got all the Te=
redo, 6to4, and ISATAP disabled on every device in my home), I have no prob=
lem. Which suggests IPv6 issues related to poor IPv6 deployments in destina=
tion networks isn't an issue for me. If it's an issue elsewhere in the worl=
d, please provide statistics -- I haven't seen any statistics presented by =
proponents of NHE related to the severity of whichever problem they're tryi=
ng to solve. My experience suggests that ISPs who deploy IPv6 properly have=
 no need for NHE.
   =20
    It really sounds like the main thing NHE is trying to "solve" is "I'm a=
n ISP who wants to deploy bad, partial, or broken IPv6 and need something t=
hat will keep my users from suffering too horribly from my ineptitude." I'm=
 not sure that's a compelling reason for an RFC. I also question whether su=
ch inept ISPs would make use of NHE, even if it were available.
    Barbara
   =20
   =20
   =20
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Wed Sep 26 08:54:58 2018
Return-Path: <prvs=1807f66189=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC0D130E19; Wed, 26 Sep 2018 08:54:44 -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
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 kCpoACngnVT2; Wed, 26 Sep 2018 08:54:40 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CADAF130EBA; Wed, 26 Sep 2018 08:54:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1537977278; x=1538582078; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=H9jEzxqY J2MxLtw1VzfwjyVg2N99nHO4c04VS461zKE=; b=pRhbacRAq0jB88U1/avcgZrw Mmv6lZ8BjiP4+MIttPfbUhbDAUEmvQavw99S2gAKUn2JnCJdxONege0UFuYfEkOY 0xqsz70U+Zl8E2ehQbDtVw8ct+W8vM4Uc/htsNtSSCNmyl6A/LgFE3bwj9y+cOAs Saqwpidb/QBGVNEY0LE=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 26 Sep 2018 17:54:38 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 26 Sep 2018 17:54:37 +0200
Received: from [45.6.251.186] by mail.consulintel.es (MDaemon PRO v16.5.2)  with ESMTPA id md50005889256.msg; Wed, 26 Sep 2018 17:54:35 +0200
X-MDRemoteIP: 2001:13c7:7003:200:ac67:962a:35ef:c4d
X-MDHelo: [45.6.251.186]
X-MDArrival-Date: Wed, 26 Sep 2018 17:54:35 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1807f66189=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/10.10.2.180910
Date: Wed, 26 Sep 2018 12:54:33 -0300
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Tommy Pauly <tpauly@apple.com>, Tony Finch <dot@dotat.at>, "STARK, BARBARA H" <bs7652@att.com>, dnsop <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Davey Song <songlinjian@gmail.com>
Message-ID: <CA5C0B0E-F12F-4FC7-8A33-36CD3D0A9824@consulintel.es>
Thread-Topic: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com> <alpine.DEB.2.20.1809261607110.3596@grey.csi.cam.ac.uk> <697C1F5F-D17E-48E7-9EC0-C0E412362EDB@apple.com>
In-Reply-To: <697C1F5F-D17E-48E7-9EC0-C0E412362EDB@apple.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZwmyFqlrVp7C3yL5ECZx7e6rDuM>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 15:54:44 -0000

And this is what I tried to say several times:

We need to take advantage of HE and NHE, or other means, to "report" to the=
 ISPs about brokenness.

https://tools.ietf.org/html/draft-palet-v6ops-he-reporting-00

Regards,
Jordi
=20
=20

=EF=BB=BF-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Tommy Pauly <tpauly@apple.c=
om>
Fecha: mi=C3=A9rcoles, 26 de septiembre de 2018, 12:38
Para: Tony Finch <dot@dotat.at>, "STARK, BARBARA H" <bs7652@att.com>, dnsop=
 <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Davey Song <songlinji=
an@gmail.com>
Asunto: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-ne=
twork-happyeyeballs-00.txt

    +1 to the point that the proposal for NHE is essentially a mechanism fo=
r the ISP and/or content provider to work around a broken deployment that t=
hey should be in a position to fix themselves, or between one another as To=
ny describes.
   =20
    The point of client-side Happy Eyeballs is to work around broken or sub=
optimal situations that the client has no control over. Following the analo=
gy, the server or ISP should only employ a parallel mechanism in order to w=
ork around some problem it has no ability to fix otherwise=E2=80=94such as =
hiding IPv6 from clients with somehow broken IPv6 stacks. This isn't what t=
he situation is like, however.
   =20
    The part that remains interesting is suggestions for networks to collec=
t more reports on the relative health of IPv4 and IPv6 connections, to help=
 fix bugs and broken deployments. Focusing on these improvements rather tha=
n filtering DNS answers seems like it would be a more fruitful direction.
   =20
    Best,
    Tommy
   =20
    > On Sep 26, 2018, at 8:15 AM, Tony Finch <dot@dotat.at> wrote:
    >=20
    > STARK, BARBARA H <bs7652@att.com> wrote:
    >=20
    >> Why would an ISP choose to deploy partial or broken IPv6 + NHE, rath=
er
    >> than properly functioning IPv6?
    >=20
    > That was my initial reaction too :-) I think the actual idea is to wo=
rk
    > around brokenness on third party networks, e.g. the ISP has working v=
6,
    > the web site has working v6, but there's bad connectivity between the=
m.
    > (It doesn't help that there are some stupid peering wars going on bet=
ween
    > tier 1 v6 providers, as mentioned in the v6 section of [1].)
    >=20
    > The right fix, I think, is to get better peering or to filter broken
    > routes. It would seem to me to be better to implement the fix in the
    > network layer not the DNS layer, since it's a network problem not a D=
NS
    > problem.
    >=20
    > [1] https://blog.apnic.net/2018/09/21/2018-national-internet-segments=
-reliability-report/
    >=20
    > Tony.
    > --=20
    > f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
    > South Utsire, Forties, Cromarty: Westerly 5 to 7, perhaps gale 8 late=
r, but
    > variable 4 for a time. Moderate or rough, occasionally very rough in =
South
    > Utsire. Drizzle, rain later. Moderate or good.
    >=20
    > _______________________________________________
    > v6ops mailing list
    > v6ops@ietf.org
    > https://www.ietf.org/mailman/listinfo/v6ops
   =20
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Wed Sep 26 09:05:53 2018
Return-Path: <paul@redbarn.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EEA6130ED4; Wed, 26 Sep 2018 09:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 685bOBpscUqs; Wed, 26 Sep 2018 09:05:50 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77E9C130E19; Wed, 26 Sep 2018 09:05:50 -0700 (PDT)
Received: from [10.219.187.147] (unknown [88.128.82.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 5E956892C7; Wed, 26 Sep 2018 16:05:48 +0000 (UTC)
Message-ID: <5BABAE58.2070707@redbarn.org>
Date: Wed, 26 Sep 2018 09:05:44 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.25 (Windows/20180328)
MIME-Version: 1.0
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
CC: "STARK, BARBARA H" <bs7652@att.com>, 'Tony Finch' <dot@dotat.at>,  Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com> <C1CA71E7-C3FF-4F80-8EF6-D3A938F05FC8@consulintel.es>
In-Reply-To: <C1CA71E7-C3FF-4F80-8EF6-D3A938F05FC8@consulintel.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/de_n0vTAu3aGI351vA-wi3GIups>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 16:05:51 -0000

JORDI PALET MARTINEZ wrote:
> ...
>
> In my experience, there are two ways IPv6 can be broken:
> 1) ICMPv6 being filtered, so PMTUD doesn't work.

perhaps we can choose a flag day to turn on a new option in our ipv6 
stacks-- add an ipv6 option to all our syn and syn-ack packets, and/or 
require pmtud for all connections. anyone who filters, won't be on v6.

-- 
P Vixie


From nobody Wed Sep 26 10:27:56 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89743130DC7; Wed, 26 Sep 2018 10:27:46 -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, FREEMAIL_FROM=0.001, SPF_PASS=-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 1S3CZu7Iz7tT; Wed, 26 Sep 2018 10:27:44 -0700 (PDT)
Received: from mail-oi1-x242.google.com (mail-oi1-x242.google.com [IPv6:2607:f8b0:4864:20::242]) (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 25149126CC7; Wed, 26 Sep 2018 10:27:44 -0700 (PDT)
Received: by mail-oi1-x242.google.com with SMTP id u197-v6so4487584oif.5; Wed, 26 Sep 2018 10:27:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=jVS45iJ8MghPdrsuDRaWfUfQvxZZf5sILBVJoo5x+yg=; b=keVLSlKRIL1XMgM9TU5rIoOuRy2Ye/XW/q8XR3qbZQS1QdCAURCYqP2bl7wwmxE9TK Ve+P/Qyw2MoEQLkldpL0YNVJ+IKjwe/MlFp6Vban4E7FH/xN7hkKcJe5D4T/VHu2t9Bt HnYg+tDXxoMn+gcjIJX2V3Orc6yqkw1CWinxOKVKmanlchuJxdLhZuBqe9goZT9I/IqK s8dq2wykBZxAo1OBFZcFJ685jRxkjW0Ll8jlvhfe8Tf55JNeSaF+zKzb5xwmWvweOk02 y8J+M93B5A5RVykTZs182M0ZYhkTZF8zQjitfqbXSDj70nz2HpXltvcvw3WcTa2CIZPC mlzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=jVS45iJ8MghPdrsuDRaWfUfQvxZZf5sILBVJoo5x+yg=; b=nwgvh8bb8m2s6q1+K0UOAdIYh8ansi4RDJy5a6vGIn/9taAIKmWC/YWh9F34nYEkE0 bJ//cFSe8KOnWb78jbLXJXEQW31lGbTzZ4EFL2Ht8D65kcR/sIQjC3HzkPMeLGFtXKvH RpgwqznOZdZC9NdWAKEtlpjrGFIWouNE2IAC94mt1BfTjxZ7veQHPqXv2vqnoRB3OHXH YOmKjS5cE543CT5cpvnwCpHaF52yFA2mEDiY8yFhP4gZaZE4FieI26LnZF/FBePaigvm QyPwR9agU6ERT/Bk+hRzabGzaqT9ZKpVE2+vwMmkhrH4toGM/O2s1uvqJs+/CIgZ4iwo 4D9w==
X-Gm-Message-State: ABuFfohO29GnHfVx+iNxOtoLyEKlL8EDt8tEYGzjo+Rva+gIJ/Ge/0r6 hgJHzzdx47WeQ0M2bZtRoXS0sQVw
X-Google-Smtp-Source: ACcGV63SNxt0tGusjDl1+XCd9EPJ4M4vb+Lh6hzwzDiqKUmeNUc3o3sTlkASjDu04jb3d1H4bOZiRA==
X-Received: by 2002:aca:3507:: with SMTP id c7-v6mr1266686oia.46.1537982863350;  Wed, 26 Sep 2018 10:27:43 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1084? ([2600:8802:5600:1546::1084]) by smtp.gmail.com with ESMTPSA id q15-v6sm1973348otl.43.2018.09.26.10.27.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Sep 2018 10:27:42 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_799C5945-CF37-4015-90AF-C8D563B388A7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 26 Sep 2018 10:27:39 -0700
In-Reply-To: <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com>
Cc: dnsop WG <dnsop@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
To: George Michaelson <ggm@algebras.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/adfMTDX_TmN6nGopxf3zPUhMUlU>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 17:27:47 -0000

--Apple-Mail=_799C5945-CF37-4015-90AF-C8D563B388A7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Speaking for myself, I see HE as a mechanism whose usefulness as =
described (selecting between IPv4 and IPv6 addresses) will wane, but =
which applied in a different way may have value long term. The latter =
has to do with access from or to multi-addressed services and selecting =
the one that seems to work best most of the time - even if all of the =
addresses are IPv6 addresses (or, in the RFC 6555 timeframe, all of the =
addresses were IPv4 addresses). As IPv4 winds down, yes, HE as described =
will become anachronistic - there won't be a choice to make. It will =
become, as NAT64 will, a service that is more work to remove than it's =
worth, but eventually isn't implemented in new implementations and =
nobody notices. But in the more general sense of multihoming, it may =
have longer term value.

Again speaking for myself, if it's a technology with declining value, it =
seems to me to not be something to invest in long term. RFC 6555 =
addressed a very real and measurable problem - host applications could =
find themselves waiting longer than their users could bear to a =
connection to complete. RFC 8305 improved on that. Further investment =
needs, I think, to have the same kind of investigation a monetary =
investment needs - is there a real need being addressed, and does the =
investment address it?

I haven't drawn any conclusions, but that gives you an idea of the =
questions in my head.

> On Sep 25, 2018, at 7:58 PM, George Michaelson <ggm@algebras.org> =
wrote:
>=20
> I have said before, but don't know if I still adhere to it, but
> anyways, here's a question: How *long* do people think a biassing
> mechanism like HE is a good idea?
>=20
> * is it a good idea *forever*
>=20
> * or is it a transition path mechanism which has an end-of-life?
>=20
> * how do we know, when its at end-of-life?
>=20
> I used to love HE. I now have a sense, I'm more neutral. Maybe, we
> actually don't want modified, better happy eyeballs, because we want
> simpler, more deterministic network stack outcomes with less bias
> hooks?
>=20
> I barely register if I an on v4 any more. I assume I'm on 6 on many
> networks. This is as an end-user. I guess if I am really an end user,
> this belief I understand TCP and UDP is false, and I should stop
> worrying (as an end user)
> On Wed, Sep 26, 2018 at 12:49 PM Davey Song <songlinjian@gmail.com> =
wrote:
>>>=20
>>> But in the general case the network cannot.
>>> Think host multi-homing.
>>=20
>>=20
>> Yes or no.
>>=20
>> Generally speaking the races of IPv6 and IPv4 connections on both =
network and client are going to be suffered by netowrk dynamics, =
including Multi-homing,  route flaps, roaming, or other network =
falilures. Extremely, a client can get a better IPv6 connection in one =
second (when IPv6 win the race), and lose it in next second. In such =
case, more sophisticated measurement should be done(on client or =
network) , for a longer period, on statistics of RTT and Failure rate, =
or combinations of them. But in IMHO, the assumption of HE is relatively =
stable network for short exchange connections. The dynamics exits but =
relatively rare or no notable impact on HE. So I see no such discussion =
in RFC8035.
>>=20
>> Davey
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

=
--------------------------------------------------------------------------=
------
The fact that there is a highway to hell and a stairway to heaven is an =
interesting comment on projected traffic volume...


--Apple-Mail=_799C5945-CF37-4015-90AF-C8D563B388A7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlurwYsACgkQEhdRnd2G
P+BI7A//QJAO+HMAqB1dZGjzT6toOQeEmdEfVZM7vROOTpoqQDagiimQqgTAlZfA
FkhsGwh+uV3VuU5ZBzWzifNI3chPzGOuwjSjgYRadzQ9MUL61WntTU0ikpSjTSsk
UVy1JfsA0nL4efui7p3BJvmP0X5FqtYNSu1rx4T25ncDVVDowrjmeAcwqwZkKs3k
cBPbWQ17sxN6ZQtEaAZdFWNFvmCX262lGNU98ZIB8If5C7jdmPGDkj0rxGT/Y/iJ
3SpeO4TwqkBtzySam1HBLodG+usCfmNQ+fTiF7PIbGnpj0cRFY4ML6rHfbtP7KIw
m12H4LDiOLwprPaDYgnMneW25RrXd4/LIKCfojKvthmvckLM8XV6Rnhgp8/9FWs0
YADHJvrASUlI4VOuWnWA/ZG9TpaF/Yta4nOX+210mDviieKKmJkDBVaUXyvs2EsR
0DKrSL0Z7tT+m/n/6Mf1RGsw/p0SjUx100yp9vOA20WLK9V4V74F0/9iWnwd8I29
JEg53ORNC2F1ECfty5MduSCqsyXGKoARlXAfoU9s+b+dzpSQzeJQo9uFD+lyr7tU
kajG6vPvYjuhr6hPk3cD4laJ4eEFAGwYATow+IRJepSFffbD9eEKmOq59egar8jj
W0Kn6ZnCXRgTqGJJqqL98MHkXE60DEy17Fka1CoXvF0J7ycHUqE=
=sHuJ
-----END PGP SIGNATURE-----

--Apple-Mail=_799C5945-CF37-4015-90AF-C8D563B388A7--


From nobody Wed Sep 26 17:31:40 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF02F130DCE for <v6ops@ietfa.amsl.com>; Wed, 26 Sep 2018 17:31:38 -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, FREEMAIL_FROM=0.001, 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 upxjajRDkcsp for <v6ops@ietfa.amsl.com>; Wed, 26 Sep 2018 17:31:35 -0700 (PDT)
Received: from mail-oi1-x244.google.com (mail-oi1-x244.google.com [IPv6:2607:f8b0:4864:20::244]) (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 03CA7130DC4 for <v6ops@ietf.org>; Wed, 26 Sep 2018 17:31:34 -0700 (PDT)
Received: by mail-oi1-x244.google.com with SMTP id s69-v6so686725oie.10 for <v6ops@ietf.org>; Wed, 26 Sep 2018 17:31:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:subject:date:references:to:in-reply-to:message-id;  bh=SKQYmLR64k/AdTFNVzE7bVg+UZwqeKInznVgNOQM9Bk=; b=iPWsRHbyom/2Q25/JPXPLVc4X974YbAzft6BBob7bxTrmtaxZBs8ml5wA+Rq963irC B86BoP2NfhQJ/xMs7meD2RyJlWgpS9yro4E1nYYRGzwbqFpX3+wQemF0c6fhhh3zYcpY /NaZ3/pW/vC+fHYt0RNxkb8gO9tldnTypZxpjNQLxdB73ABznoEpLBThNWqhh38q08Ui mCkuOOk8WtzgRD3Er1KNlgrlyw3UT3Z7rc8YabIHrOqMEBVCnPYdhV1GUMiXgUuLNFEB iogisof5q1anv3C+vtutDEWsKg8A2acy1s1Ldkfrs3EEkKbOBQltySaNwUtIxRqjT17m h8ow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=SKQYmLR64k/AdTFNVzE7bVg+UZwqeKInznVgNOQM9Bk=; b=pNLwQWVFTPlf4k1QU26a0NWMnKs2eVO+3zuSc94xI+ekzb24NFkb8h0pwCZ4XcNVSb sn66gmDK4m7gvTfh3aU62ubBYwSeKu7NnSwPya6+eYEp6NThyR/2HDKF7wmWI9TvxVKd QJDMs21zfHTK08xZgm+3/zuBTDKf+nFem15/O9eTE1ik/oFMgTzlUt3hgjXNxq9QdtBY +gKAq9F65NGscpoJEiNFPV2gtaWLJIWLF3hJk9xi8FQiqmV/tecpNgfz2dC0hIzsAvuP DedlmaGCraP8eUJ2CYrBzVP9ksZAPB4vLKXVfw/AOj0ykY/x4XbLh6dNYP+lgjKWSPY2 KSjw==
X-Gm-Message-State: ABuFfogS7KbrjVdAtC5o9pGkQPuRU8fJ6mHMEBRSq50D33h6JecdwtRD wyu5lemZKly+0HFrPp9UzucwPj8n
X-Google-Smtp-Source: ACcGV603BcGJ8qiVZJoNAnGNKWToPAcaqO7sCO4J0/kPcWl4H15gvCMikeAVDe5bvHzVfXaEbUk9FA==
X-Received: by 2002:a54:4d9d:: with SMTP id y29-v6mr2015734oix.273.1538008293936;  Wed, 26 Sep 2018 17:31:33 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1084? ([2600:8802:5600:1546::1084]) by smtp.gmail.com with ESMTPSA id y63-v6sm219293oia.39.2018.09.26.17.31.32 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Sep 2018 17:31:33 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C6CD43D6-2B5B-4E7F-BD56-66D0907CDA45"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 26 Sep 2018 17:31:31 -0700
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com>
To: "<v6ops@ietf.org>" <v6ops@ietf.org>
In-Reply-To: <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com>
Message-Id: <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BRTHcdI_RmG8JfG4Yl7viEIKo8A>
Subject: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 Sep 2018 00:31:39 -0000

--Apple-Mail=_C6CD43D6-2B5B-4E7F-BD56-66D0907CDA45
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Sep 26, 2018, at 10:27 AM, Fred Baker <fredbaker.ietf@gmail.com> =
wrote:
> As IPv4 winds down, yes, HE as described will become anachronistic - =
there won't be a choice to make. It will become, as NAT64 will, a =
service that is more work to remove than it's worth, but eventually =
isn't implemented in new implementations and nobody notices.

This time I'm speaking as a co-chair of the working group. This is in =
part a question: if folks don't see things the way I do, I, and we, need =
to understand the various viewpoints. But it's also a statement of what =
I expect the next few years to look like.


As to the status of IPv6, let me comment on its history. I saw an =
article the other day whose headline announced that "IPv6 has failed; =
let's pick something else." RFC 2460 was published in 1998, but it =
didn't define IPv6 as a usable protocol. It needed IPv6-in-DNS, =
IPv6-in-DHCP, IPv6-in-your-favorite-routing-protocol, vendor =
implementation, working vendor implementation (oh, is that important?), =
random features like uRPF etc, ROAs and IRRs, and a long list of =
whatever else. ICANN didn't approve a policy for distribution of =
prefixes to RIRs, and the RIRs to networks, until 2006, per OECD. In =
2007, about 350 IPv6 prefixes were allocated by ARIN for testing =
purposes, and in 2009-2011 there was a "run on the bank" in Asia-Pacific =
as the result of a JPNIC study indicating that IPv4 depletion was a =
realistic scenario.

In other words, the development of the technologies implied by IPv6 took =
almost as long to develop as the technologies required to use IPv4 (and =
involved a few mis-steps). However, the impetus to use them was much =
lower - whenever a technology was unavailable to make IPv6 work, "well, =
you can always use IPv4". IPv6 didn't become "important" until "always" =
became untrue. That started in 2011, when the IPv4 address space =
available from the IANA (and eventually the RIRs) was depleted; it is =
becoming increasingly untrue as the cost of purchasing an IPv4 address =
spirals upward.

"Pick something else" - I have to wonder what "something else" might be =
in view. We have a number of research projects on the table, such as =
ICN/CCN/NBN, and they likely have their uses. But I don't see the =
architectural or business implications following through; if they were =
rationally available, they would have started a decade back, I suspect. =
So I see IPv6 deployment as the only rational option on the table.


What I am increasingly hearing from ISPs and other networks is that it =
is less expensive to deploy an IPv6-only network with (or without) an =
IPv4 overlay  than to deploy a dual stack network. There are a few =
networks that have drawn that conclusion; as more and more do, IPv4 will =
become less of a requirement.

I'm not sure what to expect next, and maybe people can inform me. One =
option would be two networks that implement IPv6 natively and IPv4 as an =
overlay service connect, meaning that the address of a 464XLAT PLAT (or =
whatever) from one carrier is an address in a different carrier for some =
part of one of their networks. Or, maybe, a network simply stops =
providing an IPv4 PLAT or other support for IPv4 as an overlay. Maybe =
they are running lw4o6 and it becomes necessary to do IPv4 routing =
inside that overlay, so that they want to charge for it as a service. =
The obviously implied next question is "when" - I'm guessing early 2020s =
or something like that.


So, what do I expect the next few years to look like? I see three broad =
classes of ISPs, IXPs, and networks at the edge: those that see IPv6 as =
the least expensive endpoint and drive to that end, those that have =
enough IPv4 for the moment and aren't thinking any further ahead than =
that, and those that are balanced on a knife's edge in between. We have =
those now. I expect to see a shifting balance, with different markets =
adopting different perspectives and changing over time. I see a slow but =
definitely discernible motion from "IPv4 works" to =
"https://www.youtube.com/watch?v=3D_y36fG2Oba0" "I suppose we ought to =
give it a try". One at a time, I hear operators say "I don't want to buy =
any more IPv4 addresses". The networks that are fixed in the "IPv4 =
laggard" camp tend to be networks that aren't faced with IPv4 address =
purchases and ask for a business justification that doesn't involve a =
monetary outlay.

Ron, Lee, and I asked for a change to the v6ops charter to discuss =
IPv6-only networking with that in view. What I want to see in v6ops is =
more of that - lets move IPv4 to an overlay service, and watch it become =
less relevant over time.

So I personally expect transition technologies of various kinds - lw4o6, =
464xlat, MAP-E, MAP-T, and so on - to remain important, but I expect =
that they will become the aftermarket more than the market. If cloud =
services are accessible by IPv6, I expect residential access to become =
IPv6 service to become larger and IPv4 to become smaller. If you want a =
picture of that, look at Trinidad and Tobago. As I understand it, there =
are some services (Google, Facebook, etc) that only offer IPv6 access =
there, so the "IPv6" picture is a picture of their market dominance. =
https://stats.labs.apnic.net/ipv6/CC?x=3D1&s=3D1&p=3D1&w=3D30&c=3DTT

I expect service providers to do as little with IPv4 as they can get =
away with, and for IPv4 to increasingly become ragged around the edges. =
There are still a variety of places where I would get tarred and =
feathered and sent home wearing a barrel for saying that, but the SNA =
people were of that opinion too - until APPN made SNA networks =
irrelevant and people started deploying IP-native applications.
=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_C6CD43D6-2B5B-4E7F-BD56-66D0907CDA45
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlusJOMACgkQEhdRnd2G
P+DH4RAAw5QDXxJ3MCHTlKUYYCHXQaT20vjS3tlARQKveFwooW3lx9siFaa0MmSb
cj9f/EhHAbu/smuJxT0QcJRQOtO8TW+SMfTZPxFs+BY76PJjoHF09KGgI0x9hwzW
YPPobE7YkST2kIaQKOJKo5sPPPAS5rSNg2vmQxZzvr7lFzUiUOTGsSPp7LwVntq7
ceMVaZDhpLYv5cnKX+Go1ngR4puj0NCUwP13rqk8BGT2+xCVDZ/qzZgjU4aSUO1p
aYyCZ4qpR7Uu/JQ3em6pRK5T1cD2NhG/g+HyXglYc49iwTdxruIFHfFQFZN1koWn
+GlJgNCui10eDRTll5t7jwK48WvjKvE6qtMh2SuJ3kL8n1eA6kIDVGtPCLqWoIad
3QyFrHgJFak+MqmOgI+TEN6vuANwCtAqtpoTGzWQkx5ddAqNbJQXYNo6f9RWQEEt
JRTEVeU9emew79CbfVvuSwQn1t5wxWetowYX2xWvRbHZStTDhQ/1BO7M/+0uhcHZ
OWKhKy3GrLsaOd25dKzy0b9TwVP20RXCc/Av/RuJN47UsbsfO2Tc4KZ63mcNKC7O
FaczMm8Jr98Z5s9VqAXGxrUt3qR66jop1xAuDc9wxYGFEhF3DmC6dtrOyT6p+4aP
uVyTYIB86rXNqgPuREvUd/dWqNdrmrRD3I9vr8E19KM7yBz7O0Q=
=mSYB
-----END PGP SIGNATURE-----

--Apple-Mail=_C6CD43D6-2B5B-4E7F-BD56-66D0907CDA45--


From nobody Wed Sep 26 20:09:59 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9C9130DDD; Wed, 26 Sep 2018 20:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 53ZX90bCirnN; Wed, 26 Sep 2018 20:09:49 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 6D6DA130DDB; Wed, 26 Sep 2018 20:09:49 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id k38-v6so1212532qtk.11; Wed, 26 Sep 2018 20:09:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qyJVoSe05wTVaLj2N+4yRQExYtljJMt7ZGoF14yKtt8=; b=bUykQUfwYI42iNDOVGKfPj/q4GdbLZIvttZ2un0smxO2jRvv2en+dGSsfF/wclHt/o PmPSF7i5vd+bwaO2IA2OwN0vGV95FdpqID9QAIpzlVaUuUF9wqvyqfps+iPX1cArwf7F ByzwqSczL3+0m3ORr8vXNX4W3JLzHSgB5Y+TSEwZZBupOIXCYQGDf2ZnAzYgxZwfpH9D MR5qxFZtJqiF1ExZSZIrer2ppNZ8q7PnW0dpKXso0trhyRJIZtkBL8mHFG2/Vz+8EKLi 8ssMYsqLm4eJ0MaMSE2dz9kl3Jn6x0Uk6iXjHzwHSpCH3jgoOPMdRW5EdRXahB/PCFss Q0CA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qyJVoSe05wTVaLj2N+4yRQExYtljJMt7ZGoF14yKtt8=; b=nxvF9ZNPpyw1qQ0QqPSgO8ruJqoAFpI5MbDorKCASFEgkPfLSD6lF/Q1ByzOe9cOCS be0sBB5JmOy4IRSjdaYcRMl0gtovJoDEHCIh2GlO/8pmhQ2NQDEV28Pw96pZOOiU2fZE MV7HBp1F4pIr7x/q4gJ08X9w/guLHuh+9cuRSErGK1HQQHdhJMmmJDy6yCMAiZG6M9EG 7/oA9KcYIxelYm1ErHLXlKNer+5Kq7ybuJNBwi/+gA9i0qq0/eRueG0A++LkAopDKmQF gTe7T48ly+jAA8CeuTZ2p0YsikqXZBIcsoyojEOxEsYe5bD2CVeaepEMBVvFi8jBgu4x hpLA==
X-Gm-Message-State: ABuFfojCEyBDaxZeQmuf2nlhXFVtWTRixRBp4JnuMPinr+sPy7ssDo7w IXhEK5HYReSL90DCtVTdHdHET8Wnf9zy+zBRhEZbYS0gVy4=
X-Google-Smtp-Source: ACcGV62mozT88eZAfPg+FN+Yzr7LiOzw0g3BTwDva97zdCi9NE93t3qirf4eTW5wT7n3myZL3UV5ymD7gYUbZ/SZfkE=
X-Received: by 2002:a0c:f9c5:: with SMTP id j5-v6mr6554877qvo.177.1538017788489;  Wed, 26 Sep 2018 20:09:48 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com>
From: Davey Song <songlinjian@gmail.com>
Date: Thu, 27 Sep 2018 11:09:39 +0800
Message-ID: <CAAObRX+QRy+asm2f+DRpbon-UjCHJw5wPHMbSRJUYX0E_m1ycA@mail.gmail.com>
To: bs7652@att.com
Cc: Tony Finch <dot@dotat.at>, Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f0f3a70576d1ab9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gfQKkMfO_ZjWS7W5s1xBsXnCHFw>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 Sep 2018 03:09:51 -0000

--000000000000f0f3a70576d1ab9d
Content-Type: text/plain; charset="UTF-8"

Hi Barbara,

Thanks for your comments and sharing. I need to note that NHE is not
competing with
Client-side HE or competing with deployment of fully functioning IPv6. The
background of
NHE is :

1) the dualstack is real. Client is facing the choice ipv4 or ipv6.
2) the poor or unpredictable IPv6 performance is real (
https://stats.labs.apnic.net/v6perf ).
3) Low adoption of Client-side HE is realy.

So the suffering of users is real in dualstack.

What we are trying to do is to make the dualstack less painful for users in
these regions.
We can not say "you are starving or poor becuase you are not rich". We can
not jump
directly to build a fully functioning IPv6 in one day (like roma city). I
feel so sad the region
I live failed to catch up the average level of IPv6 development. But it is
true the IPv6
development situation varies in different places.

Maybe your observation is true that local ISP is the major source of broken
IPv6. However,
though I'm not network operator, I had at least two observations of IPv6
failure caused
by far-end and midst. One case is a real user complaint from China telecom.
It proved
that user experinced long delay when Servfail is received when asking AAAA
for many times.
It is the problem of authoritative of that site.Another case is a real
routring problem of my office
which lasts for two days due to the middle transit (Hurricane Electric) not
acept my
company's prefix. There are other cases may introduced by my co-author who
have
more experince run ipv6 network.

Maybe you (and other guys) missed that the most important argument in this
draft is if HE is
not widely deployed, NHE can enable ISP to deloy it and gain.


> As for CDN statements made in this thread: CDNs are in the business of
> optimizing connections to their content. HE isn't about optimizing
> connections -- it's about more quickly reacting to the likelihood of
> outright brokenness. But it sounds like NHE *is* about optimizing (where
> IPv6 isn't broken, but is just really slow)? I'm a bit confused about this.
>

As to this question,  NHE does the same thing HE did racing the IPv6 and
IPv4 connections to avoid both broken and slow IPv6. But NHE does
optimizing as well in terms of stopping sending additional traffic if IPv6
connection is slow (not broken) , becuase AAAA record will not be recieved
or AAAA record is received too late (one promising direction for next
version of NHE draft).

Davey

--000000000000f0f3a70576d1ab9d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Barbar=
a,</div><div><br></div><div>Thanks for your comments and sharing. I need to=
 note that NHE is not competing with <br>Client-side HE or competing with d=
eployment of fully functioning IPv6. The background of <br>NHE is :</div><d=
iv><br></div><div dir=3D"ltr"><div>1) the dualstack is real. Client is faci=
ng the choice ipv4 or ipv6.</div><div>2) the poor or unpredictable IPv6 per=
formance is real (<a href=3D"https://stats.labs.apnic.net/v6perf">https://s=
tats.labs.apnic.net/v6perf</a> ). <br>3) Low adoption of Client-side HE is =
realy.=C2=A0</div><div><br></div><div>So the suffering of users=C2=A0is rea=
l in dualstack.=C2=A0</div><div><br></div><div>What we are trying to do is =
to make the dualstack less painful for users in these regions. <br>We can n=
ot say &quot;you are=C2=A0starving or poor becuase you are not rich&quot;. =
We can not jump <br>directly to build a fully functioning IPv6 in one day (=
like roma city). I feel so sad the region <br>I live failed to catch up the=
 average level of IPv6 development. But it is true the IPv6 <br>development=
 situation varies in different places.</div><div><br></div><div>Maybe your =
observation is true that local ISP is the major source of broken IPv6. Howe=
ver,=C2=A0<br>though I&#39;m not network operator, I had at least two obser=
vations of IPv6 failure caused <br>by far-end=C2=A0and midst. One case is a=
 real user complaint from China telecom. It proved <br>that user experinced=
=C2=A0long delay when Servfail is received when asking AAAA for many times.=
 <br>It is the problem of authoritative of that site.Another case is a real=
 routring problem of my office <br>which lasts for two days due to the midd=
le=C2=A0transit (Hurricane Electric) not acept my <br>company&#39;s prefix.=
 There are other cases may introduced by=C2=A0my co-author who have <br>mor=
e experince run ipv6 network.<br></div><div><br></div><div>Maybe you (and o=
ther guys) missed that the most important argument in this draft is if HE i=
s <br>not widely deployed, NHE can enable ISP to deloy it and gain.=C2=A0</=
div><div>=C2=A0</div><div><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">As for CDN statements made in this thread: CDNs=
 are in the business of optimizing connections to their content. HE isn&#39=
;t about optimizing connections -- it&#39;s about more quickly reacting to =
the likelihood of outright brokenness. But it sounds like NHE *is* about op=
timizing (where IPv6 isn&#39;t broken, but is just really slow)? I&#39;m a =
bit confused about this.<br></blockquote><div>=C2=A0</div><div>As to this q=
uestion,=C2=A0 NHE does the same thing HE did racing the IPv6 and IPv4 conn=
ections to avoid both broken and slow IPv6. But NHE does optimizing as well=
 in terms of stopping sending additional traffic if IPv6 connection is slow=
 (not broken) , becuase AAAA record will not be recieved or AAAA record is =
received too late (one promising direction for next version of NHE draft).<=
/div><div><br></div><div>Davey=C2=A0</div></div></div></div></div></div></d=
iv></div></div></div></div></div>

--000000000000f0f3a70576d1ab9d--


From nobody Wed Sep 26 20:29:06 2018
Return-Path: <songlinjian@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9BA8130DDD; Wed, 26 Sep 2018 20:28:55 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 eJtnfiW8MDCj; Wed, 26 Sep 2018 20:28:54 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 4D28B12F1AB; Wed, 26 Sep 2018 20:28:54 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id c126-v6so731578qkd.7; Wed, 26 Sep 2018 20:28:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JbNblA0XasfhxnRS36KIjnb9fd0OFvNOdrHUZZMMbGA=; b=GKMskJkGH4q5IzhWwqzAX2CgC0v6d/MJBsO+MGHpfrLrATAYOrw/lA/JtTPknF5aTP Obze57G3p6BlwMqq6UH9RTBIPw9QXuGos/sGzOxd6DoD7Pi+AS2xKENksyd5RyPS4a++ mp/lkZY5xom9pI7OrfSGp8VdTPcJyW/oxm+92N2wkZkm2xbDyGlsJJTaptx3PlHSF4+4 Ta0kPdud8QZ33Pl6BV4m2xxM5SYnimLAJ+DKqzU05fOkFswAwaxmfVSLODqobIUvFizd KF/p1QvQhTvlw1L7PqhvCkaLOFQO2FpUEXpxL1sjJhd2N/wzX9Bzxm8ARHkZm+g3dHVi Lb9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JbNblA0XasfhxnRS36KIjnb9fd0OFvNOdrHUZZMMbGA=; b=uLeOhuTxIW8aaKNsCmjF0YmU1CXaXNGp1UD7Fip6BSfR2wUH/EFdnQBLTCm9PbRw+X IlVw46s2qSPKcXbkfUUYIXOcwH1X6qagI/A8ZqzCJZ+H3WRmH9AGby4vRxoSCw/q+8lx Gh9IDYwd/OdSvs46+3E885EJzWOEYkPBo1nZ0UunBSXLVdyHv/2O4yKdh0I+pTLWTyOR u85I/5j15onX9Lh5RcLg2qXxKybilsozU4IiA+DdeXswAxLBebhx+F3WZ7t/PEwjIM2C 3yNpAuA54TrE146leFjRJluzBccpwBpxtiny7mgHiACiVUmJ0KxKL6pUyc3BlsxUDFCP iE2g==
X-Gm-Message-State: ABuFfojOX+gZ6vzRU/4tG2njikOH8SZw2wT0Wn7sRLLKtM3z6/r4TfgT mRpFuZNpXjihOa1Yx3ZiBRwSy6G14DtdH8Wi80M=
X-Google-Smtp-Source: ACcGV61isN/rGS64bJ3y/qbYqdT6mdk8qr+3Y4wW8I+7n7dNUiiCRpoJU+jIjzLDOAGkzMMWxN5cVEjh2y73nudMjfw=
X-Received: by 2002:a37:2ac7:: with SMTP id q68-v6mr6314150qkq.319.1538018933390;  Wed, 26 Sep 2018 20:28:53 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com> <alpine.DEB.2.20.1809261607110.3596@grey.csi.cam.ac.uk> <697C1F5F-D17E-48E7-9EC0-C0E412362EDB@apple.com>
In-Reply-To: <697C1F5F-D17E-48E7-9EC0-C0E412362EDB@apple.com>
From: Davey Song <songlinjian@gmail.com>
Date: Thu, 27 Sep 2018 11:28:45 +0800
Message-ID: <CAAObRXKeSuzhzWSaJwFPcjjDAHhgOERxkqe__5xY+NmE6S1MGw@mail.gmail.com>
To: tpauly@apple.com
Cc: Tony Finch <dot@dotat.at>, bs7652@att.com, dnsop <dnsop@ietf.org>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002ec1190576d1f091"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9GMc_f5mk548N52CGAAJ9i01p54>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 Sep 2018 03:28:56 -0000

--0000000000002ec1190576d1f091
Content-Type: text/plain; charset="UTF-8"

Hi Tommy,

Thanks for your suggestions.

On Wed, 26 Sep 2018 at 23:38, Tommy Pauly <tpauly@apple.com> wrote:

> +1 to the point that the proposal for NHE is essentially a mechanism for
> the ISP and/or content provider to work around a broken deployment that
> they should be in a position to fix themselves, or between one another as
> Tony describes.
>

 Fair enough. I think it is worth of doing it.

The part that remains interesting is suggestions for networks to collect
> more reports on the relative health of IPv4 and IPv6 connections, to help
> fix bugs and broken deployments. Focusing on these improvements rather than
> filtering DNS answers seems like it would be a more fruitful direction.
>

>From the feadback of this list, now I'm think of dividing NHE draft into
two pieces: One is network-side IPv6 measurment and failure reporting which
is in aim to provide information to workaround broken deployment in a
position to fix by ISP themselves. ISP can decide by themself to take
advantege of measurement information. It can be standard track or
informational.

Another one is Selectively delaying AAAA record other than filtering DNS
records. It served an experimental/informational case of ISP taking IPv6
mearement infromation as a feed to quickly and temporarily fix the problem
if operator think it is neccesary.

How does this sound ?

Davey

--0000000000002ec1190576d1f091
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Tommy,<div><br></div><div>Thanks for y=
our suggestions.=C2=A0=C2=A0<br><br><div class=3D"gmail_quote"><div dir=3D"=
ltr">On Wed, 26 Sep 2018 at 23:38, Tommy Pauly &lt;<a href=3D"mailto:tpauly=
@apple.com">tpauly@apple.com</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">+1 to the point that the proposal for NHE is es=
sentially a mechanism for the ISP and/or content provider to work around a =
broken deployment that they should be in a position to fix themselves, or b=
etween one another as Tony describes.<br></blockquote><div><br></div><div>=
=C2=A0Fair enough. I think it is worth of doing it.</div><div><br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">
The part that remains interesting is suggestions for networks to collect mo=
re reports on the relative health of IPv4 and IPv6 connections, to help fix=
 bugs and broken deployments. Focusing on these improvements rather than fi=
ltering DNS answers seems like it would be a more fruitful direction.<br></=
blockquote><div>=C2=A0</div><div>From the feadback of this list, now I&#39;=
m think of dividing NHE draft into two pieces: One is network-side IPv6 mea=
surment and failure reporting which is in aim to provide information to wor=
karound broken deployment in a position to fix by ISP themselves. ISP can d=
ecide by themself to take advantege of measurement information. It can be s=
tandard track or informational.=C2=A0=C2=A0</div><div><br></div><div>Anothe=
r one is Selectively delaying AAAA record other than filtering DNS records.=
 It served an experimental/informational case of ISP taking IPv6 mearement =
infromation as a feed to quickly and=C2=A0temporarily fix the problem if op=
erator think it is neccesary.=C2=A0</div><div><br></div><div>How does this =
sound ?</div><div><br></div><div>Davey</div></div></div></div></div>

--0000000000002ec1190576d1f091--


From nobody Thu Sep 27 05:10:38 2018
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D298130DF6 for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2018 05:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] 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 RRxraP-pyDGT for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2018 05:10:34 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [80.229.10.150]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2F27128CE4 for <v6ops@ietf.org>; Thu, 27 Sep 2018 05:10:34 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from macbook-pro.thehobsons.co.uk (MacBook-Pro.thehobsons.co.uk [192.168.137.117]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 6FB001BC37 for <v6ops@ietf.org>; Thu, 27 Sep 2018 12:10:26 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com>
Date: Thu, 27 Sep 2018 13:10:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA6CE403-EC8D-484C-AEB6-6D4A250ADB9D@thehobsons.co.uk>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com>
To: "<v6ops@ietf.org>" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lRwL35MThG3XExB7nFKY1u_5cHI>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 Sep 2018 12:10:37 -0000

Fred Baker <fredbaker.ietf@gmail.com> wrote:

> So, what do I expect the next few years to look like?

I largely agree with your predictions, contrary to the naysayers IPv6 is =
here to stay and while it's going to take a long time, it's going to =
become dominant.
As to timescales, I don't think we'll see the end of IPv4 for a long =
long long time - and having watched the lack of activity from my own ISP =
(who isn't exactly a dinosaur) I think early 2020s for IPv4 to be =
relegated to an overlay/tunnelled/whatever protocol for "most" networks =
is probably a bit optimistic.

And then I think back to last year when I was having a bit of a play =
with Azure at work, and I don't recall seeing any mention of IPv6 at all =
with that. Indeed, from what I could see, their model for providing =
service mobility relies on IPv4 and NAT. I imagine the same is true to =
some extend with all the large providers working with flexible pools of =
resources.
That sort of thing is going to be a drag on ditching IPv4.

On the upside, I've seen hosting providers where IPv6 is included and =
IPv4 is a paid for extra. Or even IPv6 only with NAT64 to reach the IPv4 =
internet https://ipv6onlyhosting.com/en-us/cms/

I think the key single point that's going to drag things out compared to =
how IPv4 killed off things like AppleTalk and IPX is that IPv4 offered a =
compelling advantage (global routing, ubiquitous support once it and =
"the internet" "took off") - while for many people, IPv6 is just "the =
same thing with added complexity".


From nobody Thu Sep 27 05:13:10 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39503130DFF for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2018 05:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 SDuC0JXCGQzZ for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2018 05:13:06 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C814128CE4 for <v6ops@ietf.org>; Thu, 27 Sep 2018 05:13:06 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 6FF9041CDB for <v6ops@ietf.org>; Thu, 27 Sep 2018 14:13:03 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 5CDA141CDA; Thu, 27 Sep 2018 14:13:03 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 594F937817; Thu, 27 Sep 2018 14:13:03 +0200 (CEST)
Date: Thu, 27 Sep 2018 14:13:03 +0200
From: Gert Doering <gert@space.net>
To: Davey Song <songlinjian@gmail.com>
Cc: bs7652@att.com, Tony Finch <dot@dotat.at>, Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, v6ops@ietf.org
Message-ID: <20180927121303.GO11393@Space.Net>
References: <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com> <CAAObRX+QRy+asm2f+DRpbon-UjCHJw5wPHMbSRJUYX0E_m1ycA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rSnsErh/zDv3QTX/"
Content-Disposition: inline
In-Reply-To: <CAAObRX+QRy+asm2f+DRpbon-UjCHJw5wPHMbSRJUYX0E_m1ycA@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uzgdueFmhCZTGNC7gDN6becA4YI>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 Sep 2018 12:13:08 -0000

--rSnsErh/zDv3QTX/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Thu, Sep 27, 2018 at 11:09:39AM +0800, Davey Song wrote:
> So the suffering of users is real in dualstack.

This is a misconception.

"A few applications are lazy, so performance for them is poor" is better
describing things.

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Em=
mer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

--rSnsErh/zDv3QTX/
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEruB5jRHVM+CjiYD131bAZeTOf8UFAlusyU4ACgkQ31bAZeTO
f8W/qw//cZpM6TgmEmbbv2DPSUDe479mt2UkeHBLQ8AP8zNtFH/WzfTdHhliCZnV
+QehuDxaZmp+zb6NbN9qmWXgWYqB3vvutgk0JmMvym99QmU2knx2bseAt8cMo106
kBfoU319FNsPKDHSK7pMPRuLbpWY+chmx76E/fWMl/KNpNXgp0Skm4P8bUa1fp3q
RtHO+aOilPfM/LSezSCp2nWbKN1Uw1dmmPTp89B5C+ThQDt1Y1MgdA5ifBOrAygS
qAtkncpRB2AZ8FXk1mSLCTdH02H9t/VaJZqMF8+lSr3PX120oFqqSYSEJ3GFaiI7
ZqsvA+3P7a+N5xEI8EwXnQ7fiSDJ5KXP7KHGtOLv6Su1YSkJaYh8Ioh6BxAEEtno
Xk9/LO4K3tg9jJ4AlDosSdvbr6AsaPyHqfEjtzvUspvSAjGqVhJi4lMKQfltJqmF
spPgslhHZHei5bfTHr3htqZ96iF/ltSrG7gQPxmJT7qnl/R74aj8y0yf3eTALy7z
NedvA0SZgUo8TV3oZNWBlkpyFVsb1j0OAw506HOYv5J2RiHQMuQVU786eQmxzN0M
YqAPMJp9gIw/4rxFR37wOpchRQBIErmLOhA+u3o7GyNjAcM+qX8vOe1/ALFd2yct
3HpRsoQd2jKxgdh7s8ddQ1kDo7AMu53r6xQ4ekodGHkKUXAZqjw=
=pxbm
-----END PGP SIGNATURE-----

--rSnsErh/zDv3QTX/--


From nobody Thu Sep 27 05:18:45 2018
Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98B96130DF6 for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2018 05:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 zFn_KZ5wVJmV for <v6ops@ietfa.amsl.com>; Thu, 27 Sep 2018 05:18:41 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50B3812F295 for <v6ops@ietf.org>; Thu, 27 Sep 2018 05:18:41 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 8407A41CDD for <v6ops@ietf.org>; Thu, 27 Sep 2018 14:18:39 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 770A541CDB; Thu, 27 Sep 2018 14:18:39 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 7421F37886; Thu, 27 Sep 2018 14:18:39 +0200 (CEST)
Date: Thu, 27 Sep 2018 14:18:39 +0200
From: Gert Doering <gert@space.net>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
Message-ID: <20180927121839.GP11393@Space.Net>
References: <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KqPT3xPY8JRFVQo/"
Content-Disposition: inline
In-Reply-To: <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.0 (2018-05-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LFrWSYnIfi0mOllsCtoMst_I-KQ>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 Sep 2018 12:18:44 -0000

--KqPT3xPY8JRFVQo/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, Sep 26, 2018 at 05:31:31PM -0700, Fred Baker wrote:
> ICANN didn't approve a policy for distribution of prefixes to RIRs, and=
=20
> the RIRs to networks, until 2006, per OECD.=20

First /35 handed out by the RIPE NCC was in August 1999.

(I agree with the general statement, but these numbers are just not right)

The formal "/12 to the RIRs" policy took a few years longer, so ICANN was
operating under a provisional "/23 (IIRC) to each RIR" policy at the time,
but nevertheless, these was a regular RIPE policy and the prefixes are
official and valid.

(I'm a bit sensitive on that topic, as a large part of the excuses why
people haven't deployed IPv6 is "because assignment/allocation policies
are not right!!!" - which just wasn't true for the majority of use cases
for well over 10 years now)

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Em=
mer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

--KqPT3xPY8JRFVQo/
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEruB5jRHVM+CjiYD131bAZeTOf8UFAlusyp4ACgkQ31bAZeTO
f8Vl+g/+M2Alxn0SLOMvmnTMzoN7TXT2ezwPWMvhzYKK4Di2xMeJzJS75UMkCVef
a3n0KVCK/TKR6WziTw0bcaX+E9XNozvUgD1eSIjzR4/gMuHBTq0vWEpdOXZtNlm0
gGdnuGMdP0u3uz7b/OINy43Tmi32Fy3ylZxSSp95dTHW4qrBS847LSqMsg9p3PId
d0HF9DUs4Qw2aPJDxcrjer/pY9mop9qe4MOf8YzRYeYRVq+orl/zu7BFm+eMShE7
AF+bwWOvwLEqwUmtlcP4RW/Sg3/CvUiJUwYBwAgay9EXDf1rnNBI4grRkrrrYLBb
yFWSTljH+Imt+ZTH/nXB0n6vCwZjSYpy8xuDX2HYjDYz+c3al4ruwgVmWJzt/ZA7
wnNDmHRo94uj3/3gc/l7wBTVqgraYi7TtE1dBE4cSrMKv4C00gTCbmRdkl6/tZHt
0OXUGogVo/HIvetyJmeiNcCmj1BTh2SkZrWloDubkfmafLGKsjwvoHHNEgHn3nqY
5B3N/Nd7XJKunCdQpcHtntvoLhNaX5Yd7PiDGkindCQ8QyhWf+o/DUQx+NgASnfk
05QHDZGI5RmsjbtnxrI35+1lxXkJnkpRiDj3tw0I3Xx3J+fCa7O1k4XIdbfhIqq4
WCu3k6Dx8HiGW0STi28+k42JitraXZOd7buG9rah2V7iUx1YaOQ=
=a/H9
-----END PGP SIGNATURE-----

--KqPT3xPY8JRFVQo/--


From nobody Fri Sep 28 08:49:51 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93FFD130E4E for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 08:49:48 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 uNIpZ9iq-t1U for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 08:49:47 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 0DDB5130E42 for <v6ops@ietf.org>; Fri, 28 Sep 2018 08:49:46 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id m23-v6so6510738otf.0 for <v6ops@ietf.org>; Fri, 28 Sep 2018 08:49:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zbTPkOzZdn+I/iZ86bxRZFwcIjIoEvFHuo0Nr1SuhXU=; b=YqusnrDt5MPCurHuh8wcfKljFQ6VEECdcfekZ5vOstOq8qFnAd+NjwIFoL6O4H+ZXL VFIV1VYIqvSnGAF9lRTiNy/4XVrnUfsgk9gRo35Z21SPzAPerRscPe9qyvRnA+IShp65 LerpbO3iVesczIcYv8gLr7cf8jzNKGKLcooUa70l4QCgo60l46kfEV5vgml9DR6Nlw07 Go9vdKSsp2qnvGrXNLW6wFRA6m8MDZg0y3Ff5zVZn0wo1vB5dQjqVI5Zl5QOJKB0bAPJ wDcWhfrpI9KY0oxPKRjTx9MZ7UnHZdtzi6/LT1oX2SCWrEyzVSdsLd+MwCZIQPDFynz5 Jq+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zbTPkOzZdn+I/iZ86bxRZFwcIjIoEvFHuo0Nr1SuhXU=; b=LDTiS7Kk3tIOZMN9h5lASo7+DCqYShsVT1d3SKbj3fBC0BCBIgBBPxki/GeBkQjGVh +jO9/x74kjI2bWOxjF+gQ5qgB4t8cYPlAlhPDId8O0i/bYIq+cYV+L99KVrL7qptjpxx hOiXF5k7HIvuRcjryLhyhbQwzC0jElqrUtEPj04nUjp6DQmu3s4DLOwR6aXTPkrD3BOo yxtDUNIAEESuvxqtnc2eoAybf53xkoyVcpHxVbRe5QMXPj/yWeDd8msdZWDBIs9uPdLq XrX2jicleTjUKu/mC3bAlT3WEFg/P8uYv/J03+BATyrOWvs6GhQjnofno9e+mk0yczex kw4Q==
X-Gm-Message-State: ABuFfoic+eHo9kA6fwt0yW5pO1L03rIq+DOVnYbnOyrIhBFPKlh6tXHc 1InzKS4y2kWCQAnTeqKxssk=
X-Google-Smtp-Source: ACcGV63D37r1qHpao5ryObcufI8OVy3ZL6TbMOgVjpkDNNCUZiArgqoS9sSE1kbm8k56ViVuwialLQ==
X-Received: by 2002:a9d:2a89:: with SMTP id e9-v6mr7833791otb.82.1538149786281;  Fri, 28 Sep 2018 08:49:46 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1008? ([2600:8802:5600:1546::1008]) by smtp.gmail.com with ESMTPSA id 33-v6sm1929039otw.29.2018.09.28.08.49.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Sep 2018 08:49:45 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <AE54D6F3-9D4B-4744-AF9E-3392E088FCD8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D6157DCA-DDE7-4703-A4F2-E79DD447C297"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 28 Sep 2018 08:49:43 -0700
In-Reply-To: <20180927121839.GP11393@Space.Net>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
To: Gert Doering <gert@space.net>
References: <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com> <20180927121839.GP11393@Space.Net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/WijDu1MabFEw1ok7K9Lm25uvseQ>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Sep 2018 15:49:49 -0000

--Apple-Mail=_D6157DCA-DDE7-4703-A4F2-E79DD447C297
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks for the correction. The OECD document I found the date in was =
probably referring to the /12 to the RIRs policy.

> On Sep 27, 2018, at 5:18 AM, Gert Doering <gert@space.net> wrote:
>=20
> Hi,
>=20
> On Wed, Sep 26, 2018 at 05:31:31PM -0700, Fred Baker wrote:
>> ICANN didn't approve a policy for distribution of prefixes to RIRs, =
and
>> the RIRs to networks, until 2006, per OECD.
>=20
> First /35 handed out by the RIPE NCC was in August 1999.
>=20
> (I agree with the general statement, but these numbers are just not =
right)
>=20
> The formal "/12 to the RIRs" policy took a few years longer, so ICANN =
was
> operating under a provisional "/23 (IIRC) to each RIR" policy at the =
time,
> but nevertheless, these was a regular RIPE policy and the prefixes are
> official and valid.
>=20
> (I'm a bit sensitive on that topic, as a large part of the excuses why
> people haven't deployed IPv6 is "because assignment/allocation =
policies
> are not right!!!" - which just wasn't true for the majority of use =
cases
> for well over 10 years now)
>=20
> Gert Doering
>        -- NetMaster
> --
> have you enabled IPv6 on something today...?
>=20
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, =
Michael Emmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. =
Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279


--Apple-Mail=_D6157DCA-DDE7-4703-A4F2-E79DD447C297
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluuTZcACgkQEhdRnd2G
P+BZ4Q//bMszz48mk7gu9EOtJnlT+MZ4C6DaRGhlGDqvfkpzQU75f6rfahlfoebc
Ervqpbp+0NCPqkIQcXM2al8/KcxrNHXGHIxeCNPMGSXxWxdYzqsk3UpqhrK91zwf
1GNbvuxwoacl6uPP/gtoTG8r/5aYJHjijIqV1PZ/f3MAYCxf3zQmqVwyvmLhJYmj
7OCpVl2hJrkQUZIz342KcrEicV/xHpx8jTGkfBhQnLBwHW4epWW93CLMU7k6lbtw
qH51E1fZBSJNPW0lCswbm+MQwka23ZhPE8/l4ITL050DhB9oFZjDsc9rIGmsm0aY
MCoBO35S9drV/M9xcv7EwUsGIzvyJ1wg/PGjOb4XLdlxlbUYqFPC6hubBBsg8CwJ
Aocel8dd4Y+VJOhhNMnZxOHUTsPvSkFdqeE+pNrHdYvPqbxFXK1nY5meuRII1wKG
Q+1Yp8q2j8Znh2VwNgYURrBQQSy+/yg7FhPQigCFzuG2kp9shOB5uySBjeWg14y/
/QUe6Wlq2iqV4iytV7i6ZSRU+oyU4cDcGsLf9IMecBEUwjUK1NWwtELTQLAofsJM
W00MSoriPo/0JCajK9tuA4VEnUCro1j6CVSEXtLvJlCWFzNHPj7id8Lm8dpdk5ze
v290l7+C1RM0MdLxlfLITzrg/7geGPtYmNJnWTYnonvYq8b0jzU=
=W2MR
-----END PGP SIGNATURE-----

--Apple-Mail=_D6157DCA-DDE7-4703-A4F2-E79DD447C297--


From nobody Fri Sep 28 10:01:27 2018
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAF3B130E77 for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 10:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level: 
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, 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 kBLUMNKWEADD for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 10:01:18 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 0C492130E59 for <v6ops@ietf.org>; Fri, 28 Sep 2018 10:01:17 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8SH1Fs1032692 for <v6ops@ietf.org>; Fri, 28 Sep 2018 19:01:15 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C3ECD206AF2 for <v6ops@ietf.org>; Fri, 28 Sep 2018 19:01:15 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B8AA8206AC2 for <v6ops@ietf.org>; Fri, 28 Sep 2018 19:01:15 +0200 (CEST)
Received: from [10.8.68.14] ([10.8.68.14]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w8SH1EIs006455 for <v6ops@ietf.org>; Fri, 28 Sep 2018 19:01:15 +0200
To: v6ops@ietf.org
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com>
Date: Fri, 28 Sep 2018 19:01:14 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/G9tMPQjiU0V64v245LWBYsrtkMY>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Sep 2018 17:01:26 -0000

For me it looks quite challenging to develop a meaningful vision in this
space.

On one hand, this Internet witnesses fast digital evolutions, and
disruptions, every other day. On another hand IPv6 overcoming IPv4 seems 
to advance very slowly. On a same timescale Windows leaped from 95 to 
10, while IP still steps from 4 to 6.

In that sense, I think IPv6 and IPv4 side by side as a double stack is
still a viable evolution in the next decades, although not very fancy.
The translation from one to another seems like an artificial path that
keeps reinventing itself but with no clear advantage of one translation
mechanism over another. These IPv4-IPv6 translation mechanisms are like
satisfaction for our needs of getting there faster.

(but I also speculated at a time that Twitter would disappear in its
infancy because finger existed - the reverse happened; I also speculated
that iPhone 4 would do _only_ IPv4 and iPhone 6 _only_ IPv6 - it did not
happen).

Le 27/09/2018 à 02:31, Fred Baker a écrit :
> On Sep 26, 2018, at 10:27 AM, Fred Baker <fredbaker.ietf@gmail.com>
> wrote:
>> As IPv4 winds down, yes, HE as described will become anachronistic
>> - there won't be a choice to make. It will become, as NAT64 will, a
>> service that is more work to remove than it's worth, but eventually
>> isn't implemented in new implementations and nobody notices.
> 
> This time I'm speaking as a co-chair of the working group. This is in
> part a question: if folks don't see things the way I do, I, and we,
> need to understand the various viewpoints. But it's also a statement
> of what I expect the next few years to look like.
> 
> 
> As to the status of IPv6, let me comment on its history. I saw an
> article the other day whose headline announced that "IPv6 has failed;
> let's pick something else." RFC 2460 was published in 1998, but it
> didn't define IPv6 as a usable protocol. It needed IPv6-in-DNS,
> IPv6-in-DHCP, IPv6-in-your-favorite-routing-protocol, vendor
> implementation, working vendor implementation (oh, is that
> important?), random features like uRPF etc, ROAs and IRRs, and a long
> list of whatever else. ICANN didn't approve a policy for distribution
> of prefixes to RIRs, and the RIRs to networks, until 2006, per OECD.
> In 2007, about 350 IPv6 prefixes were allocated by ARIN for testing
> purposes, and in 2009-2011 there was a "run on the bank" in
> Asia-Pacific as the result of a JPNIC study indicating that IPv4
> depletion was a realistic scenario.
> 
> In other words, the development of the technologies implied by IPv6
> took almost as long to develop as the technologies required to use
> IPv4 (and involved a few mis-steps). However, the impetus to use them
> was much lower - whenever a technology was unavailable to make IPv6
> work, "well, you can always use IPv4". IPv6 didn't become "important"
> until "always" became untrue. That started in 2011, when the IPv4
> address space available from the IANA (and eventually the RIRs) was
> depleted; it is becoming increasingly untrue as the cost of
> purchasing an IPv4 address spirals upward.

I would like to react to this.

We should reckon frankly what happened with this depletion.  It has been 
hugely advertised.  It is a few years now.

It depleted.  But it is still possible to get IPv4 as long as the unused 
space gets back.

We can talk about refuelling IPv4.

Maybe we need to wait for several cycles of depletion-refuelling in 
order to sense a stronger need of IPv6.

Alex

> 
> "Pick something else" - I have to wonder what "something else" might
> be in view. We have a number of research projects on the table, such
> as ICN/CCN/NBN, and they likely have their uses. But I don't see the
> architectural or business implications following through; if they
> were rationally available, they would have started a decade back, I
> suspect. So I see IPv6 deployment as the only rational option on the
> table.
> 
> 
> What I am increasingly hearing from ISPs and other networks is that
> it is less expensive to deploy an IPv6-only network with (or without)
> an IPv4 overlay  than to deploy a dual stack network. There are a few
> networks that have drawn that conclusion; as more and more do, IPv4
> will become less of a requirement.
> 
> I'm not sure what to expect next, and maybe people can inform me. One
> option would be two networks that implement IPv6 natively and IPv4 as
> an overlay service connect, meaning that the address of a 464XLAT
> PLAT (or whatever) from one carrier is an address in a different
> carrier for some part of one of their networks. Or, maybe, a network
> simply stops providing an IPv4 PLAT or other support for IPv4 as an
> overlay. Maybe they are running lw4o6 and it becomes necessary to do
> IPv4 routing inside that overlay, so that they want to charge for it
> as a service. The obviously implied next question is "when" - I'm
> guessing early 2020s or something like that.
> 
> 
> So, what do I expect the next few years to look like? I see three
> broad classes of ISPs, IXPs, and networks at the edge: those that see
> IPv6 as the least expensive endpoint and drive to that end, those
> that have enough IPv4 for the moment and aren't thinking any further
> ahead than that, and those that are balanced on a knife's edge in
> between. We have those now. I expect to see a shifting balance, with
> different markets adopting different perspectives and changing over
> time. I see a slow but definitely discernible motion from "IPv4
> works" to "https://www.youtube.com/watch?v=_y36fG2Oba0" "I suppose we
> ought to give it a try". One at a time, I hear operators say "I don't
> want to buy any more IPv4 addresses". The networks that are fixed in
> the "IPv4 laggard" camp tend to be networks that aren't faced with
> IPv4 address purchases and ask for a business justification that
> doesn't involve a monetary outlay.
> 
> Ron, Lee, and I asked for a change to the v6ops charter to discuss
> IPv6-only networking with that in view. What I want to see in v6ops
> is more of that - lets move IPv4 to an overlay service, and watch it
> become less relevant over time.
> 
> So I personally expect transition technologies of various kinds -
> lw4o6, 464xlat, MAP-E, MAP-T, and so on - to remain important, but I
> expect that they will become the aftermarket more than the market. If
> cloud services are accessible by IPv6, I expect residential access to
> become IPv6 service to become larger and IPv4 to become smaller. If
> you want a picture of that, look at Trinidad and Tobago. As I
> understand it, there are some services (Google, Facebook, etc) that
> only offer IPv6 access there, so the "IPv6" picture is a picture of
> their market dominance.
> https://stats.labs.apnic.net/ipv6/CC?x=1&s=1&p=1&w=30&c=TT
> 
> I expect service providers to do as little with IPv4 as they can get
> away with, and for IPv4 to increasingly become ragged around the
> edges. There are still a variety of places where I would get tarred
> and feathered and sent home wearing a barrel for saying that, but the
> SNA people were of that opinion too - until APPN made SNA networks
> irrelevant and people started deploying IP-native applications. 
> --------------------------------------------------------------------------------
>
> 
Victorious warriors win first and then go to war,
> Defeated warriors go to war first and then seek to win. Sun Tzu
> 
> 
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> 


From nobody Fri Sep 28 10:47:32 2018
Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19DC1130E77 for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 10:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.224
X-Spam-Level: 
X-Spam-Status: No, score=-1.224 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, T_MONEY_PERCENT=0.01] autolearn=no 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 lBQpu8rSAU8b for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 10:47:27 -0700 (PDT)
Received: from atl4mhob19.registeredsite.com (atl4mhob19.registeredsite.com [209.17.115.112]) (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 30E3E1274D0 for <v6ops@ietf.org>; Fri, 28 Sep 2018 10:47:27 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail01pod6.registeredsite.com [10.30.71.209]) by atl4mhob19.registeredsite.com (8.14.4/8.14.4) with ESMTP id w8SHlNlI022433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <v6ops@ietf.org>; Fri, 28 Sep 2018 13:47:23 -0400
Received: (qmail 8715 invoked by uid 0); 28 Sep 2018 17:47:23 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.103?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 28 Sep 2018 17:47:23 -0000
To: v6ops@ietf.org
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com> <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <96bb5ddb-95f9-2437-f0b2-b1274912bf3c@asgard.org>
Date: Fri, 28 Sep 2018 13:47:23 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MtECoGvPFt85AveUH9TuKODlQvM>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Sep 2018 17:47:30 -0000

On 09/28/2018 01:01 PM, Alexandre Petrescu wrote:
> For me it looks quite challenging to develop a meaningful vision in this
> space.
>
> On one hand, this Internet witnesses fast digital evolutions, and
> disruptions, every other day. On another hand IPv6 overcoming IPv4 
> seems to advance very slowly. On a same timescale Windows leaped from 
> 95 to 10, while IP still steps from 4 to 6.
Windows 95 was a significant rebuild over Windows 3.11.  Each of the 
next several versions were incremental upgrades, and all were both 
forward and backward compatible.

Meanwhile, lots of work had to go into making IPv6 deployable, and it 
didn't really start until 2011. In that time, Windows has evolved from 
Windows 7 to Windows 10 (skipping 9, so only two desktop upgrades).

>
> In that sense, I think IPv6 and IPv4 side by side as a double stack is
> still a viable evolution in the next decades, although not very fancy.
> The translation from one to another seems like an artificial path that
> keeps reinventing itself but with no clear advantage of one translation
> mechanism over another. These IPv4-IPv6 translation mechanisms are like
> satisfaction for our needs of getting there faster.

How does a network run dual-stack when it's out of IPv4 addresses?
If it buys addresses, why does it run dual-stack?
I guess you consider IPv6-only plus translation to be dual-stack?

Agreed, for now different people are choosing different mechanisms, and 
there isn't yet a clear winner.


>
> (but I also speculated at a time that Twitter would disappear in its
> infancy because finger existed - the reverse happened; I also speculated
> that iPhone 4 would do _only_ IPv4 and iPhone 6 _only_ IPv6 - it did not
> happen).
I haven't seen finger enabled on a system since 1992.


>>
>> In other words, the development of the technologies implied by IPv6
>> took almost as long to develop as the technologies required to use
>> IPv4 (and involved a few mis-steps). However, the impetus to use them
>> was much lower - whenever a technology was unavailable to make IPv6
>> work, "well, you can always use IPv4". IPv6 didn't become "important"
>> until "always" became untrue. That started in 2011, when the IPv4
>> address space available from the IANA (and eventually the RIRs) was
>> depleted; it is becoming increasingly untrue as the cost of
>> purchasing an IPv4 address spirals upward.
>
> I would like to react to this.
>
> We should reckon frankly what happened with this depletion.  It has 
> been hugely advertised.  It is a few years now.
>
> It depleted.  But it is still possible to get IPv4 as long as the 
> unused space gets back.
At about US$20 each.

>
> We can talk about refuelling IPv4.
>
> Maybe we need to wait for several cycles of depletion-refuelling in 
> order to sense a stronger need of IPv6.


Right now, the cloud and CDN companies are essentially all of the IPv4 
demand. In terms of number of addresses and dollars spent, they are more 
than 90% of the market. The CDNs are mostly okay in IPv6 support, even 
if they ingest over IPv4.
The cloud providers are in a pile of trouble. AWS is way ahead of anyone 
else for IPv6 support, and last I heard they're still buying IPv4 
addresses to make sure they have enough cushion. Azure can do a VM or a 
Load Balancer, but not both, which is more than Google Cloud can do 
(only LB). Oracle will allow you to open a ticket requesting IPv6, but 
unless it's a Service Cloud, they'll close the ticket with no action. 
Alibaba promises an IPv6-only cloud by 2025, but so far has nothing but 
dreams.

Something like seven years ago I predicted 500M IPv4 addresses in the 
market. About half have moved, but the market didn't really get moving 
until about 2015. It's important to note that large net blocks are 
valued by large companies: nobody wants to manage hundreds of /18s. 
Unless the US government/Department of Defense releases several /8s, the 
high end of the market is all but gone.
Yes, there may be thousands of /16s still available, for over a million 
USD each and rising.

2018 has seen an inflection in pricing. But of course, nobody knows what 
happens next. My concern is that instead of "permissionless innovation" 
the IPv4 Internet will require significant capital just to get connected.

We're also on track for 50% of the world to reach Google over IPv6 in 
two years. Several mobile networks are already IPv6-only internally, and 
several large landline ISPs are either there or on their way.


So, what do you advocate we wait and see? How long should we wait, and 
what are we looking for?
More importantly, once we see it, how much time will we have to do 
something about it, and will it be enough time?

Lee

>
> Alex
>
>>
>> "Pick something else" - I have to wonder what "something else" might
>> be in view. We have a number of research projects on the table, such
>> as ICN/CCN/NBN, and they likely have their uses. But I don't see the
>> architectural or business implications following through; if they
>> were rationally available, they would have started a decade back, I
>> suspect. So I see IPv6 deployment as the only rational option on the
>> table.
>>
>>
>> What I am increasingly hearing from ISPs and other networks is that
>> it is less expensive to deploy an IPv6-only network with (or without)
>> an IPv4 overlay  than to deploy a dual stack network. There are a few
>> networks that have drawn that conclusion; as more and more do, IPv4
>> will become less of a requirement.
>>
>> I'm not sure what to expect next, and maybe people can inform me. One
>> option would be two networks that implement IPv6 natively and IPv4 as
>> an overlay service connect, meaning that the address of a 464XLAT
>> PLAT (or whatever) from one carrier is an address in a different
>> carrier for some part of one of their networks. Or, maybe, a network
>> simply stops providing an IPv4 PLAT or other support for IPv4 as an
>> overlay. Maybe they are running lw4o6 and it becomes necessary to do
>> IPv4 routing inside that overlay, so that they want to charge for it
>> as a service. The obviously implied next question is "when" - I'm
>> guessing early 2020s or something like that.
>>
>>
>> So, what do I expect the next few years to look like? I see three
>> broad classes of ISPs, IXPs, and networks at the edge: those that see
>> IPv6 as the least expensive endpoint and drive to that end, those
>> that have enough IPv4 for the moment and aren't thinking any further
>> ahead than that, and those that are balanced on a knife's edge in
>> between. We have those now. I expect to see a shifting balance, with
>> different markets adopting different perspectives and changing over
>> time. I see a slow but definitely discernible motion from "IPv4
>> works" to "https://www.youtube.com/watch?v=_y36fG2Oba0" "I suppose we
>> ought to give it a try". One at a time, I hear operators say "I don't
>> want to buy any more IPv4 addresses". The networks that are fixed in
>> the "IPv4 laggard" camp tend to be networks that aren't faced with
>> IPv4 address purchases and ask for a business justification that
>> doesn't involve a monetary outlay.
>>
>> Ron, Lee, and I asked for a change to the v6ops charter to discuss
>> IPv6-only networking with that in view. What I want to see in v6ops
>> is more of that - lets move IPv4 to an overlay service, and watch it
>> become less relevant over time.
>>
>> So I personally expect transition technologies of various kinds -
>> lw4o6, 464xlat, MAP-E, MAP-T, and so on - to remain important, but I
>> expect that they will become the aftermarket more than the market. If
>> cloud services are accessible by IPv6, I expect residential access to
>> become IPv6 service to become larger and IPv4 to become smaller. If
>> you want a picture of that, look at Trinidad and Tobago. As I
>> understand it, there are some services (Google, Facebook, etc) that
>> only offer IPv6 access there, so the "IPv6" picture is a picture of
>> their market dominance.
>> https://stats.labs.apnic.net/ipv6/CC?x=1&s=1&p=1&w=30&c=TT
>>
>> I expect service providers to do as little with IPv4 as they can get
>> away with, and for IPv4 to increasingly become ragged around the
>> edges. There are still a variety of places where I would get tarred
>> and feathered and sent home wearing a barrel for saying that, but the
>> SNA people were of that opinion too - until APPN made SNA networks
>> irrelevant and people started deploying IP-native applications. 
>> -------------------------------------------------------------------------------- 
>>
>>
>>
> Victorious warriors win first and then go to war,
>> Defeated warriors go to war first and then seek to win. Sun Tzu
>>
>>
>>
>> _______________________________________________ v6ops mailing list 
>> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Fri Sep 28 11:26:33 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B265E130E77 for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 11:26:31 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 pm9HXPOUZHzV for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 11:26:29 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 BD49C130E6D for <v6ops@ietf.org>; Fri, 28 Sep 2018 11:26:29 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id o13-v6so6941523otl.4 for <v6ops@ietf.org>; Fri, 28 Sep 2018 11:26:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=1ceZMiHnRM2CFsyX5hzRVZBK/wgou/MWNpnQAbhQ9IE=; b=YXdDjx5AFVl0osPcXfS7FuC0K9x8aydlAiXvoMCVWmGGa1ZCxj+GN0VxyMK0ZZnISd wDA+nkTTBoiMzbNvJbIJ2vxxtn0RGgWx5Rw62FJMFzgTzK70ChWAM1h4SvN5ZG1jYJTa ecMo7TARwl3eDyw/X/tEgM3hM5iAtu+Wl9sqbEXyRL/1G2G8rEWOJ/ToCVzqGtZMezUx gkxDo6DyAVtEsGFDw74OOOrfIfUOt/IAFlGTerGLMkoYVIllqYAaN422Z2cFSj9xS5YW KxZrnjcVSKVOL3Z6IJBU/y+yHTZ+/6wVxNiaJtF4Emy4YrAy3jgWo79cCOzBljXcwX3g NjCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=1ceZMiHnRM2CFsyX5hzRVZBK/wgou/MWNpnQAbhQ9IE=; b=f1DD4+V8utKhnpEwgMdrA7s2EkG4rFYrGBJzoWDdFkfsREqRNLUJDFp3eITePkGbjg Ol158M+F76jf6ACQgm55a33HfwsoVgJO9f7HYUFE34aBLsOkrGLb6cFyvTBOX/4LZlzo C1Lo/J5zPBofTZ+VkeYB7Zc6+BkY538qnEEPKISRngRhflCMAsA98Ck06JaZrUaDZAIJ F7FT8OVe4+Geq3I8LbGy44aMqgI2XT2W7pZ86/xKuIp5khl/HyIn20fHAMe/1lQYpCvS n9S7DJ6kZd0jpNR/JdW0k/ICIh0tJ/GfQreNHwzq8FKXzjDobT68tyHOX6d8rQAxBcf7 LkzQ==
X-Gm-Message-State: ABuFfoi4T3JvesR5H8GBYKqQRJkOtP+9MBZGE/2v2P9TW7TolbFjZEke khZiyH2kfMFTef1vzAJRPQs=
X-Google-Smtp-Source: ACcGV62b4VBYgyoNwOFOxGRHhJasvn+56sL1Lpjsh7mRq1vCMqQrL7zFr1dICd9a3o1tRIawFuWT9A==
X-Received: by 2002:a9d:3226:: with SMTP id t38-v6mr10055085otc.303.1538159188996;  Fri, 28 Sep 2018 11:26:28 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1008? ([2600:8802:5600:1546::1008]) by smtp.gmail.com with ESMTPSA id m11-v6sm2073820otc.18.2018.09.28.11.26.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Sep 2018 11:26:27 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <AE7687A9-F28C-4DB2-AECD-709A7EB4C778@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1CD6628F-52F7-4A30-A963-BAF07565BEED"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 28 Sep 2018 11:26:25 -0700
In-Reply-To: <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com>
Cc: v6ops@ietf.org
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com> <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/NstPeB0kMSozIco_tvU56WQCDcc>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Sep 2018 18:26:32 -0000

--Apple-Mail=_1CD6628F-52F7-4A30-A963-BAF07565BEED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



On Sep 28, 2018, at 10:01 AM, Alexandre Petrescu =
<alexandre.petrescu@gmail.com> wrote:
> In that sense, I think IPv6 and IPv4 side by side as a double stack is
> still a viable evolution in the next decades, although not very fancy.

As I theorized the other day, I suspect that the IPv4 Internet becomes =
something strictly at the edge. It might very well be dual stack within =
the edge network, but it will come to a NAT of some kind before it =
leaves the premises. The ISPs run IPv6-only, and they serve residential =
and mobile customers/services using it. CLAT-PLAT translation means that =
the ISP doesn't have to think about it too much; lw4o6 tunnels become a =
network of their own that someone has to manage. As much as I dislike =
LISP, LISP might be a rational tunneling technology; it allows for the =
dynamic creation of tunnels whenever and wherever needed, which would be =
useful for enterprise connection to its hosting sites and business =
partners.

Also, I suspect that said aftermarket business becomes a PITA that =
people charge to support. Given the choice of a bill for one protocol or =
a bill for two separate protocols with some sort of PLAT or tunnel =
endpoint support built in, expect customers to stop asking about a =
business case and start asking about reducing their costs.

=
--------------------------------------------------------------------------=
------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
     Sun Tzu


--Apple-Mail=_1CD6628F-52F7-4A30-A963-BAF07565BEED
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluuclEACgkQEhdRnd2G
P+BEJA//dmdsyt+iwR9gsaLO43jVC1vV2roUyR6PvnNpkMQSzsGNiDDLGih9TFoC
n6qDfuqvQ+TRuonAf5NNysVUKMKaX0Y91KzrpYv3E543ykQUa0NedI+dRWevjGLv
e2Qwneb34DNFLc5VfYX10k4WNizoPiL4JJdLkWF4mJT1K8GaZs+99kGuJ4hJq0et
bxg8QV4G9Ovu2I6yFthR8eVgh1PYhim8xQhsKxiLuFJiWGSQSu09Wjb6jYkAPvxy
KGdMc+M0v4aQOZmnuQs/N79AczahgcaA2e4bsX1pVJThQBwGorWgTmD6ttOa+W9y
uKe9YWRf4KjptvuMVE1DQDaEAs5lus+aBTHhJ5qKRk+gJd1NYbPNyvAp6I9hiF+E
mi0UeZXPxe/t+3eJmBNBEe5tH1NUqhf9Y8/OoW4rpIzlGmH1U7LhQKavVqymlWzU
LswYr3hXa77jZLzl3SSAOC8KCpG/4k/EagdcAYlNdrPJi3x8ByH1fjSCPx2IoS2X
4Z4Z28PfHn8Tl+DarDVZpU8BZE/2zPZvaN6itMFY1iAehh4rPVxULWtof9ZlOyTU
dUThlFx8fHrEgjRrZoI7cvHHCReZutHQvhSADPTRGan6Q4vbY87X3jd5yIGJKCyc
BtqJbgBoVW3HV2NKBJBPgXhjVR0xnETYiG7hIcBcTn8rfYngH08=
=QGyE
-----END PGP SIGNATURE-----

--Apple-Mail=_1CD6628F-52F7-4A30-A963-BAF07565BEED--


From nobody Fri Sep 28 11:47:44 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE71130E3C for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 11:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 RDuDucT5mC_U for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 11:47:41 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AC1612958B for <v6ops@ietf.org>; Fri, 28 Sep 2018 11:47:40 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id DF45DFECBF09; Fri, 28 Sep 2018 18:47:39 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (16A366)
In-Reply-To: <AE7687A9-F28C-4DB2-AECD-709A7EB4C778@gmail.com>
Date: Fri, 28 Sep 2018 20:47:37 +0200
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A06CFC7A-DA95-4D06-8509-4B90C6D6D256@employees.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com> <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com> <AE7687A9-F28C-4DB2-AECD-709A7EB4C778@gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/M4BbRcAzDFyFXPGPrSboNT7QrRk>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Sep 2018 18:47:43 -0000

Fred,

> On 28 Sep 2018, at 20:26, Fred Baker <fredbaker.ietf@gmail.com> wrote:
>=20
> it. CLAT-PLAT translation means that the ISP doesn't have to think about i=
t too much; lw4o6 tunnels become a network of their own that someone has to m=
anage.

I don=E2=80=99t understand this statement.=20
You seem to imply that there should be less management with 464XLAT aka doub=
le translation than tunneling? Why do you believe that?

Ole=


From nobody Fri Sep 28 12:32:14 2018
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C0E2130EC6 for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 12:32:08 -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, FREEMAIL_FROM=0.001, SPF_PASS=-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 N5tFlnTAUDTM for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 12:32:06 -0700 (PDT)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::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 28C50130E9A for <v6ops@ietf.org>; Fri, 28 Sep 2018 12:32:06 -0700 (PDT)
Received: by mail-oi1-x229.google.com with SMTP id s69-v6so6369559oie.10 for <v6ops@ietf.org>; Fri, 28 Sep 2018 12:32:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=T3iOR1eZn10GRZY9P69KnSbXIxfle80NdhzE9HYC6VE=; b=LQ9tI1E6ecLvcSOAPQMWV9oTveJh2fMqAiXX8LaUESFLf7GtGCUidNyHr3lXybN9yH BLrlBgKakt3Ep4fUgustsR2pHfRklXbvo+m0oc6/nPXMSq7jG2NjOS/BE5rlkWhJIf1+ jvEyJyFZI7oSiWbq2U+x0YdrrjhOt4IOoXRrDcP5TMyiLbnsTm6V3RtN1K2ie3NV1vEn I6THAfJ+y3D0qghuQ/b+36eM7WalvypM9nFpHFZHmVFpUO2ir1KfcY4ScjuDDDg+s0iQ DedUglKHZV/NLk5QEF+vW9PqlEI6lGTgPzmTA1EB1AthWs1MU46+VKlGq3aoQGdz0ZjD yoaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=T3iOR1eZn10GRZY9P69KnSbXIxfle80NdhzE9HYC6VE=; b=RKiGvsmcNoQ1AwCyhXYMBRHGmr015RH5myhNy0wCbqPCL0BcwJPhEzn2bznImzpnqz 4fQrjMJCc/eIBfoCmPvwGUeWH3FfVdhWsqgNOvIL0m96pdmBgfwAlZPITTJ73bbdDqxA XTVY9DGlso4hG74erIdibQx/tWPBS34wr5ApuJkBmarY73ULj4uKWxLmOo81Gvgjbwpz EHRWtqbSVYLpNU4tfB4P0FHNPkpvkhO/02Yszz2cgBLL0wnY6IY8vuXe8L9T2e2UWpLZ Ly7Dwkj2pYNt1eoTb7/mzJ0SjPZ+ZhmQM8OAL8lEtX5typvj5vq/usf6wB6LQR4sobTY czow==
X-Gm-Message-State: ABuFfog5cZ0NuB/EwVE2n0CDnyyilQWHGWsmIO2Xqw/8KFAy8V2H/L2u a1DH29hDK4cVwHEIIzHbRLg=
X-Google-Smtp-Source: ACcGV61X68Rd1knr7pFTErbhcBisY7GJUjOYOZzA+V3wMWLVRyYa18JdMAe+4hTvpMEvFrZX2QS1xQ==
X-Received: by 2002:aca:754b:: with SMTP id q72-v6mr43326oic.13.1538163125478;  Fri, 28 Sep 2018 12:32:05 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::1008? ([2600:8802:5600:1546::1008]) by smtp.gmail.com with ESMTPSA id m7-v6sm2035377oia.32.2018.09.28.12.32.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Sep 2018 12:32:04 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <91A911BA-B85A-437E-AF51-D02EB5B51BC1@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_03FBB74E-E28C-4A03-AD3C-5674AB4C2937"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 28 Sep 2018 12:32:00 -0700
In-Reply-To: <A06CFC7A-DA95-4D06-8509-4B90C6D6D256@employees.org>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, v6ops@ietf.org
To: Ole Troan <otroan@employees.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com> <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com> <AE7687A9-F28C-4DB2-AECD-709A7EB4C778@gmail.com> <A06CFC7A-DA95-4D06-8509-4B90C6D6D256@employees.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/vjGSYupSPmjP1AQZ8mO2hSYTpnU>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Sep 2018 19:32:12 -0000

--Apple-Mail=_03FBB74E-E28C-4A03-AD3C-5674AB4C2937
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Sep 28, 2018, at 11:47 AM, Ole Troan <otroan@employees.org> wrote:
>=20
> Fred,
>=20
>> On 28 Sep 2018, at 20:26, Fred Baker <fredbaker.ietf@gmail.com> =
wrote:
>>=20
>> it. CLAT-PLAT translation means that the ISP doesn't have to think =
about it too much; lw4o6 tunnels become a network of their own that =
someone has to manage.
>=20
> I don=E2=80=99t understand this statement.
> You seem to imply that there should be less management with 464XLAT =
aka double translation than tunneling? Why do you believe that?

With translation, there are two translators. With a tunnel, there are =
two tunnel endpoints. I see the number two in both statements.

In addition, in both cases the connection gets to an IPv4 Internet. =
However, at some point, that network starts to break down. If, for =
example, it becomes a set of tunnels leading to each neighboring ISP, =
then there is routing somewhere in the lw4o6-or-whatever system to =
select the right neighboring ISP. If it's translation, then that routing =
can be accomplished using the IPv6 prefix plus some subset of the IPv4 =
address in question.

=
--------------------------------------------------------------------------=
------
The fact that there is a highway to hell and a stairway to heaven is an =
interesting comment on projected traffic volume...


--Apple-Mail=_03FBB74E-E28C-4A03-AD3C-5674AB4C2937
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAluugbAACgkQEhdRnd2G
P+BMuRAAgJ3A0Sm0wo+BBRnOaXb3sFv/pp7tAIEg4jYbVzthAgJ+Brg5Ppym128m
ljQZUyxX4wKZg2s+/KPplK+N5lXwEvTB/NR4Yy6CxV3UULNhOcifTW9z74mhP0nr
3Qd7NFMNi1bGcSycD7EJytgt9eHTNzbEtN2LV9epLMa1/R7Edd5rJPpbw/MVYt6j
q8AWWP0Xnks1TPLmPMrhfY/a95T4PEwgqD8cmxTgqA6YyMbuKcmObl7pBvpyLUx5
uQqx1UlPoG+wP0co9/T6o3tnrZbCNar9NXMjx6v026UKaLzCj+hu+1w4Ag7ja/GJ
OEOLEgqimWkg6pzgXTFoosJOCYfD1t5V1LCuce4w9Z2cV3cUkoCjKPWtTma9W6ZQ
N4/Cs5EkB7gni+xmKBOYdYAHVUIbJR878twE8H1h62y3Wz3phxYRPydXaJwMMxLp
Pr5kGtaG5bnTNi4zIJnFOChL4FJehBg2o2pg/ZwitbmPoTaQdhCvp9T4aTTPHiCZ
aM1uzi170AfSVi+y5nKYOUM4aG3zGtFst3/uomx21cqwyuOuUMfHseQkNRzhE9o5
EOxawl5DXURTPYPeCeaBzQBTGkqYekN1za2CISsteIh8m4WLETlwU6td3hQu7hwF
vFBhMazer2Yybkpun0bwYfIE4MxYBpftQqCGQ991uUcyVa8thdY=
=QAnF
-----END PGP SIGNATURE-----

--Apple-Mail=_03FBB74E-E28C-4A03-AD3C-5674AB4C2937--


From nobody Fri Sep 28 12:44:30 2018
Return-Path: <bs7652@att.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC2F8130E7B; Fri, 28 Sep 2018 12:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.611
X-Spam-Level: 
X-Spam-Status: No, score=-0.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 EV8tNRmdwfw0; Fri, 28 Sep 2018 12:44:17 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 1DE8F130E81; Fri, 28 Sep 2018 12:44:17 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w8SHQg6U013421; Fri, 28 Sep 2018 13:30:43 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049295.ppops.net-00191d01. with ESMTP id 2msrd30sq0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 28 Sep 2018 13:30:43 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w8SHUf4q006783; Fri, 28 Sep 2018 13:30:41 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [135.47.91.189]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w8SHUYY5006514; Fri, 28 Sep 2018 13:30:35 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [127.0.0.1]) by zlp30483.vci.att.com (Service) with ESMTP id 67E624014670; Fri, 28 Sep 2018 17:30:34 +0000 (GMT)
Received: from GAALPA1MSGHUBAA.ITServices.sbc.com (unknown [130.8.218.150]) by zlp30483.vci.att.com (Service) with ESMTPS id 4FCE64014665; Fri, 28 Sep 2018 17:30:34 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.98]) by GAALPA1MSGHUBAA.ITServices.sbc.com ([130.8.218.150]) with mapi id 14.03.0415.000; Fri, 28 Sep 2018 13:30:33 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Davey Song'" <songlinjian@gmail.com>
CC: Tony Finch <dot@dotat.at>, Gert Doering <gert@space.net>, dnsop <dnsop@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [DNSOP] [v6ops] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
Thread-Index: AQHUVg+R4y1RbA9fHkmerOAq110HuaUF2o+g
Date: Fri, 28 Sep 2018 17:30:33 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DED128D@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <2FEEAF29-E213-4DA3-8ECA-4EF51E170B50@employees.org> <CAAObRXJXv3iDg=k00FghuLQtSuogFD4FMr25krMSAXginAM5bg@mail.gmail.com> <20180926072839.GD11393@Space.Net> <alpine.DEB.2.20.1809261153450.3596@grey.csi.cam.ac.uk> <2D09D61DDFA73D4C884805CC7865E6114DECDB78@GAALPA1MSGUSRBF.ITServices.sbc.com> <CAAObRX+QRy+asm2f+DRpbon-UjCHJw5wPHMbSRJUYX0E_m1ycA@mail.gmail.com>
In-Reply-To: <CAAObRX+QRy+asm2f+DRpbon-UjCHJw5wPHMbSRJUYX0E_m1ycA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.240.78]
Content-Type: multipart/alternative; boundary="_000_2D09D61DDFA73D4C884805CC7865E6114DED128DGAALPA1MSGUSRBF_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-28_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809280173
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ANUA-o8hEFYFhMQnJjbsdC8hDZY>
Subject: Re: [v6ops] [DNSOP] New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Sep 2018 19:44:20 -0000

--_000_2D09D61DDFA73D4C884805CC7865E6114DED128DGAALPA1MSGUSRBF_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgRGF2ZXksDQpUaGFua3MgZm9yIHRoZSBpbmZvLiBUaGF04oCZcyBlbmxpZ2h0ZW5pbmcuDQpJ
IHdvdWxkIG5vdCBzdXBwb3J0IHRoaXMgYXMgZWl0aGVyIGEgc3RhbmRhcmQgb3IgYSBiZXN0IHBy
YWN0aWNlLiBUaGUgcHJvcG9zZWQgTkhFIG1lY2hhbmlzbSBhcHBlYXJzIHRvIGJlIGEgY2FwYWJp
bGl0eSBvbmx5IG9mIGludGVyZXN0IHRvIElTUHMgaW4gY291bnRyaWVzL3JlZ2lvbnMgd2hlcmUg
KGJlY2F1c2Ugb2YgaG93IHRoZXkgaGF2ZSBjaG9zZW4gdG8gc2V0IHVwIHRoZWlyIElQdjYgcGVl
cmluZykgdGhleSBhcmUgaW1wYWN0ZWQgYnkgdGhlIGFjdGlvbnMgb2Ygc3BlY2lmaWMgdHJhbnNp
dCBwcm92aWRlcnMgKGFuZCBvdGhlciBJU1BzKSBkb2luZyBiYWQgSVB2Ni1yZWxhdGVkIHRoaW5n
czsgYW5kIGhvc3RzIGFyZW7igJl0IGRvaW5nIEhFLiBJIHdvdWxkIGJlIGZpbmUgd2l0aCBzb21l
dGhpbmcgaW5mb3JtYXRpdmUgYWxvbmcgdGhlIGxpbmVzIG9mIOKAnGlmIGFuIElTUCBmaW5kcyBp
dHNlbGYgaW4gdGhpcyBzaXR1YXRpb24sIGhlcmUgaXMgYSB3b3JrLWFyb3VuZCB0aGV5IG1pZ2h0
IGNvbnNpZGVyIGRvaW5nLCBhcyBhIGxhc3QgcmVzb3J0IChhZnRlciBmdXRpbGVseSB0cnlpbmcg
dG8gZ2V0IHRoZSB1bmRlcmx5aW5nIGNhdXNlcyBmaXhlZCBvciB0cnlpbmcgdG8gZW5zdXJlIG11
bHRpcGxlIHRyYW5zaXQgcGF0aHMgYXJlIGF2YWlsYWJsZSnigJ0uIERlc2lnbmluZyBhIG5ldHdv
cmsgd2l0aCBhIHNpbmdsZSBwb2ludCBvZiBmYWlsdXJlIGlzIG5ldmVyIGEgZ29vZCBpZGVhLiBC
dXQgdGhlIHByZWZlcnJlZCBhcHByb2FjaCBzaG91bGQgYmUgdG8gcmVjb21tZW5kIGNvbm5lY3Rp
bmcgdG8gbXVsdGlwbGUgSVB2NiBwZWVycywgcmF0aGVyIHRoYW4gdXNpbmcgSVB2NCBhcyB0aGUg
YmFja3VwIHRvIGZhaWx1cmUgb2YgYSBzaW5nbGUgSVB2NiBwZWVyLg0KDQpUaGUgbWFwIG1ha2Vz
IHRoaXMgcHJvYmxlbSBsb29rIHZlcnkgcmVnaW9uYWwsIG5hdGlvbmFsLCBvciBldmVuIGNvbXBh
bnktc3BlY2lmaWMuIEkgZG9u4oCZdCB0aGluayBpdOKAmXMgYSBnb29kIGlkZWEgdG8gY3JlYXRl
IHN0YW5kYXJkcyBvciBiZXN0IHByYWN0aWNlcyBmb3Igd29yay1hcm91bmRzIHRvIHJlZ2lvbmFs
L25hdGlvbmFsL2NvbXBhbnktc3BlY2lmaWMgcHJvYmxlbXMuDQoNCkkgZGlkIHNlZSB0aGUgZW1h
aWwgZnJvbSBUb255IHBvaW50aW5nIHRvIHByb2JsZW1zIGluc2lkZSB0aGUgVVMgYW5kIEV1cm9w
ZS4gQnV0IHRoZXkgZG9u4oCZdCBzZWVtIGltcGFjdGZ1bCBlbm91Z2ggZm9yIElTUHMgaW4gdGhl
c2UgcmVnaW9ucyB0byBiZSB3YW50aW5nIHRvIGRvIHRoaXMgc29ydCBvZiB3b3JrLWFyb3VuZC4N
CkJhcmJhcmENCg0KRnJvbTogRGF2ZXkgU29uZyA8c29uZ2xpbmppYW5AZ21haWwuY29tPg0KU2Vu
dDogV2VkbmVzZGF5LCBTZXB0ZW1iZXIgMjYsIDIwMTggMTE6MTAgUE0NClRvOiBTVEFSSywgQkFS
QkFSQSBIIDxiczc2NTJAYXR0LmNvbT4NCkNjOiBUb255IEZpbmNoIDxkb3RAZG90YXQuYXQ+OyBH
ZXJ0IERvZXJpbmcgPGdlcnRAc3BhY2UubmV0PjsgZG5zb3AgPGRuc29wQGlldGYub3JnPjsgdjZv
cHNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbRE5TT1BdIFt2Nm9wc10gTmV3IFZlcnNpb24gTm90
aWZpY2F0aW9uIGZvciBkcmFmdC12Nm9wcy14aWUtbmV0d29yay1oYXBweWV5ZWJhbGxzLTAwLnR4
dA0KDQpIaSBCYXJiYXJhLA0KDQpUaGFua3MgZm9yIHlvdXIgY29tbWVudHMgYW5kIHNoYXJpbmcu
IEkgbmVlZCB0byBub3RlIHRoYXQgTkhFIGlzIG5vdCBjb21wZXRpbmcgd2l0aA0KQ2xpZW50LXNp
ZGUgSEUgb3IgY29tcGV0aW5nIHdpdGggZGVwbG95bWVudCBvZiBmdWxseSBmdW5jdGlvbmluZyBJ
UHY2LiBUaGUgYmFja2dyb3VuZCBvZg0KTkhFIGlzIDoNCg0KMSkgdGhlIGR1YWxzdGFjayBpcyBy
ZWFsLiBDbGllbnQgaXMgZmFjaW5nIHRoZSBjaG9pY2UgaXB2NCBvciBpcHY2Lg0KMikgdGhlIHBv
b3Igb3IgdW5wcmVkaWN0YWJsZSBJUHY2IHBlcmZvcm1hbmNlIGlzIHJlYWwgKGh0dHBzOi8vc3Rh
dHMubGFicy5hcG5pYy5uZXQvdjZwZXJmPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNv
bS92Mi91cmw/dT1odHRwcy0zQV9fc3RhdHMubGFicy5hcG5pYy5uZXRfdjZwZXJmJmQ9RHdNRmFR
JmM9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZyPUxvR3poQy04c2M4U1k4VHE0dnJmb2cmbT1VQ2xK
c0pzQ1hoaTBHOHpmR3R5ZC1qYzZ4bFZ5ZVAtcERmRDljdVU4OU9VJnM9Y2lVZGNwb3hWOEc2TV9n
NlJOWWdNXzNWekdmdDltYzJUVmxHbTNFUUt5MCZlPT4gKS4NCjMpIExvdyBhZG9wdGlvbiBvZiBD
bGllbnQtc2lkZSBIRSBpcyByZWFseS4NCg0KU28gdGhlIHN1ZmZlcmluZyBvZiB1c2VycyBpcyBy
ZWFsIGluIGR1YWxzdGFjay4NCg0KV2hhdCB3ZSBhcmUgdHJ5aW5nIHRvIGRvIGlzIHRvIG1ha2Ug
dGhlIGR1YWxzdGFjayBsZXNzIHBhaW5mdWwgZm9yIHVzZXJzIGluIHRoZXNlIHJlZ2lvbnMuDQpX
ZSBjYW4gbm90IHNheSAieW91IGFyZSBzdGFydmluZyBvciBwb29yIGJlY3Vhc2UgeW91IGFyZSBu
b3QgcmljaCIuIFdlIGNhbiBub3QganVtcA0KZGlyZWN0bHkgdG8gYnVpbGQgYSBmdWxseSBmdW5j
dGlvbmluZyBJUHY2IGluIG9uZSBkYXkgKGxpa2Ugcm9tYSBjaXR5KS4gSSBmZWVsIHNvIHNhZCB0
aGUgcmVnaW9uDQpJIGxpdmUgZmFpbGVkIHRvIGNhdGNoIHVwIHRoZSBhdmVyYWdlIGxldmVsIG9m
IElQdjYgZGV2ZWxvcG1lbnQuIEJ1dCBpdCBpcyB0cnVlIHRoZSBJUHY2DQpkZXZlbG9wbWVudCBz
aXR1YXRpb24gdmFyaWVzIGluIGRpZmZlcmVudCBwbGFjZXMuDQoNCk1heWJlIHlvdXIgb2JzZXJ2
YXRpb24gaXMgdHJ1ZSB0aGF0IGxvY2FsIElTUCBpcyB0aGUgbWFqb3Igc291cmNlIG9mIGJyb2tl
biBJUHY2LiBIb3dldmVyLA0KdGhvdWdoIEknbSBub3QgbmV0d29yayBvcGVyYXRvciwgSSBoYWQg
YXQgbGVhc3QgdHdvIG9ic2VydmF0aW9ucyBvZiBJUHY2IGZhaWx1cmUgY2F1c2VkDQpieSBmYXIt
ZW5kIGFuZCBtaWRzdC4gT25lIGNhc2UgaXMgYSByZWFsIHVzZXIgY29tcGxhaW50IGZyb20gQ2hp
bmEgdGVsZWNvbS4gSXQgcHJvdmVkDQp0aGF0IHVzZXIgZXhwZXJpbmNlZCBsb25nIGRlbGF5IHdo
ZW4gU2VydmZhaWwgaXMgcmVjZWl2ZWQgd2hlbiBhc2tpbmcgQUFBQSBmb3IgbWFueSB0aW1lcy4N
Ckl0IGlzIHRoZSBwcm9ibGVtIG9mIGF1dGhvcml0YXRpdmUgb2YgdGhhdCBzaXRlLkFub3RoZXIg
Y2FzZSBpcyBhIHJlYWwgcm91dHJpbmcgcHJvYmxlbSBvZiBteSBvZmZpY2UNCndoaWNoIGxhc3Rz
IGZvciB0d28gZGF5cyBkdWUgdG8gdGhlIG1pZGRsZSB0cmFuc2l0IChIdXJyaWNhbmUgRWxlY3Ry
aWMpIG5vdCBhY2VwdCBteQ0KY29tcGFueSdzIHByZWZpeC4gVGhlcmUgYXJlIG90aGVyIGNhc2Vz
IG1heSBpbnRyb2R1Y2VkIGJ5IG15IGNvLWF1dGhvciB3aG8gaGF2ZQ0KbW9yZSBleHBlcmluY2Ug
cnVuIGlwdjYgbmV0d29yay4NCg0KTWF5YmUgeW91IChhbmQgb3RoZXIgZ3V5cykgbWlzc2VkIHRo
YXQgdGhlIG1vc3QgaW1wb3J0YW50IGFyZ3VtZW50IGluIHRoaXMgZHJhZnQgaXMgaWYgSEUgaXMN
Cm5vdCB3aWRlbHkgZGVwbG95ZWQsIE5IRSBjYW4gZW5hYmxlIElTUCB0byBkZWxveSBpdCBhbmQg
Z2Fpbi4NCg0KQXMgZm9yIENETiBzdGF0ZW1lbnRzIG1hZGUgaW4gdGhpcyB0aHJlYWQ6IENETnMg
YXJlIGluIHRoZSBidXNpbmVzcyBvZiBvcHRpbWl6aW5nIGNvbm5lY3Rpb25zIHRvIHRoZWlyIGNv
bnRlbnQuIEhFIGlzbid0IGFib3V0IG9wdGltaXppbmcgY29ubmVjdGlvbnMgLS0gaXQncyBhYm91
dCBtb3JlIHF1aWNrbHkgcmVhY3RpbmcgdG8gdGhlIGxpa2VsaWhvb2Qgb2Ygb3V0cmlnaHQgYnJv
a2VubmVzcy4gQnV0IGl0IHNvdW5kcyBsaWtlIE5IRSAqaXMqIGFib3V0IG9wdGltaXppbmcgKHdo
ZXJlIElQdjYgaXNuJ3QgYnJva2VuLCBidXQgaXMganVzdCByZWFsbHkgc2xvdyk/IEknbSBhIGJp
dCBjb25mdXNlZCBhYm91dCB0aGlzLg0KDQpBcyB0byB0aGlzIHF1ZXN0aW9uLCAgTkhFIGRvZXMg
dGhlIHNhbWUgdGhpbmcgSEUgZGlkIHJhY2luZyB0aGUgSVB2NiBhbmQgSVB2NCBjb25uZWN0aW9u
cyB0byBhdm9pZCBib3RoIGJyb2tlbiBhbmQgc2xvdyBJUHY2LiBCdXQgTkhFIGRvZXMgb3B0aW1p
emluZyBhcyB3ZWxsIGluIHRlcm1zIG9mIHN0b3BwaW5nIHNlbmRpbmcgYWRkaXRpb25hbCB0cmFm
ZmljIGlmIElQdjYgY29ubmVjdGlvbiBpcyBzbG93IChub3QgYnJva2VuKSAsIGJlY3Vhc2UgQUFB
QSByZWNvcmQgd2lsbCBub3QgYmUgcmVjaWV2ZWQgb3IgQUFBQSByZWNvcmQgaXMgcmVjZWl2ZWQg
dG9vIGxhdGUgKG9uZSBwcm9taXNpbmcgZGlyZWN0aW9uIGZvciBuZXh0IHZlcnNpb24gb2YgTkhF
IGRyYWZ0KS4NCg0KRGF2ZXkNCg==

--_000_2D09D61DDFA73D4C884805CC7865E6114DED128DGAALPA1MSGUSRBF_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw
bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v
cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAx
LjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5I
aSBEYXZleSw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyBmb3Ig
dGhlIGluZm8uIFRoYXTigJlzIGVubGlnaHRlbmluZy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkkgd291bGQgbm90IHN1cHBvcnQgdGhpcyBhcyBlaXRoZXIgYSBzdGFuZGFy
ZCBvciBhIGJlc3QgcHJhY3RpY2UuIFRoZSBwcm9wb3NlZCBOSEUgbWVjaGFuaXNtIGFwcGVhcnMg
dG8gYmUgYSBjYXBhYmlsaXR5IG9ubHkgb2YgaW50ZXJlc3QgdG8gSVNQcyBpbiBjb3VudHJpZXMv
cmVnaW9ucyB3aGVyZSAoYmVjYXVzZSBvZiBob3cgdGhleSBoYXZlIGNob3NlbiB0byBzZXQgdXAg
dGhlaXIgSVB2NiBwZWVyaW5nKSB0aGV5DQogYXJlIGltcGFjdGVkIGJ5IHRoZSBhY3Rpb25zIG9m
IHNwZWNpZmljIHRyYW5zaXQgcHJvdmlkZXJzIChhbmQgb3RoZXIgSVNQcykgZG9pbmcgYmFkIElQ
djYtcmVsYXRlZCB0aGluZ3M7IGFuZCBob3N0cyBhcmVu4oCZdCBkb2luZyBIRS4gSSB3b3VsZCBi
ZSBmaW5lIHdpdGggc29tZXRoaW5nIGluZm9ybWF0aXZlIGFsb25nIHRoZSBsaW5lcyBvZiDigJxp
ZiBhbiBJU1AgZmluZHMgaXRzZWxmIGluIHRoaXMgc2l0dWF0aW9uLCBoZXJlIGlzIGEgd29yay1h
cm91bmQNCiB0aGV5IG1pZ2h0IGNvbnNpZGVyIGRvaW5nLCBhcyBhIGxhc3QgcmVzb3J0IChhZnRl
ciBmdXRpbGVseSB0cnlpbmcgdG8gZ2V0IHRoZSB1bmRlcmx5aW5nIGNhdXNlcyBmaXhlZCBvciB0
cnlpbmcgdG8gZW5zdXJlIG11bHRpcGxlIHRyYW5zaXQgcGF0aHMgYXJlIGF2YWlsYWJsZSnigJ0u
IERlc2lnbmluZyBhIG5ldHdvcmsgd2l0aCBhIHNpbmdsZSBwb2ludCBvZiBmYWlsdXJlIGlzIG5l
dmVyIGEgZ29vZCBpZGVhLiBCdXQgdGhlIHByZWZlcnJlZCBhcHByb2FjaA0KIHNob3VsZCBiZSB0
byByZWNvbW1lbmQgY29ubmVjdGluZyB0byBtdWx0aXBsZSBJUHY2IHBlZXJzLCByYXRoZXIgdGhh
biB1c2luZyBJUHY0IGFzIHRoZSBiYWNrdXAgdG8gZmFpbHVyZSBvZiBhIHNpbmdsZSBJUHY2IHBl
ZXIuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBtYXAgbWFrZXMgdGhpcyBwcm9ibGVtIGxv
b2sgdmVyeSByZWdpb25hbCwgbmF0aW9uYWwsIG9yIGV2ZW4gY29tcGFueS1zcGVjaWZpYy4gSSBk
b27igJl0IHRoaW5rIGl04oCZcyBhIGdvb2QgaWRlYSB0byBjcmVhdGUgc3RhbmRhcmRzIG9yIGJl
c3QgcHJhY3RpY2VzIGZvciB3b3JrLWFyb3VuZHMgdG8gcmVnaW9uYWwvbmF0aW9uYWwvY29tcGFu
eS1zcGVjaWZpYyBwcm9ibGVtcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBkaWQgc2VlIHRo
ZSBlbWFpbCBmcm9tIFRvbnkgcG9pbnRpbmcgdG8gcHJvYmxlbXMgaW5zaWRlIHRoZSBVUyBhbmQg
RXVyb3BlLiBCdXQgdGhleSBkb27igJl0IHNlZW0gaW1wYWN0ZnVsIGVub3VnaCBmb3IgSVNQcyBp
biB0aGVzZSByZWdpb25zIHRvIGJlIHdhbnRpbmcgdG8gZG8gdGhpcyBzb3J0IG9mIHdvcmstYXJv
dW5kLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmFyYmFyYTxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6
MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBEYXZleSBTb25nICZsdDtzb25nbGluamlh
bkBnbWFpbC5jb20mZ3Q7IDxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIFNlcHRlbWJlciAy
NiwgMjAxOCAxMToxMCBQTTxicj4NCjxiPlRvOjwvYj4gU1RBUkssIEJBUkJBUkEgSCAmbHQ7YnM3
NjUyQGF0dC5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBUb255IEZpbmNoICZsdDtkb3RAZG90YXQu
YXQmZ3Q7OyBHZXJ0IERvZXJpbmcgJmx0O2dlcnRAc3BhY2UubmV0Jmd0OzsgZG5zb3AgJmx0O2Ru
c29wQGlldGYub3JnJmd0OzsgdjZvcHNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6
IFtETlNPUF0gW3Y2b3BzXSBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXY2b3Bz
LXhpZS1uZXR3b3JrLWhhcHB5ZXllYmFsbHMtMDAudHh0PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBCYXJiYXJhLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MgZm9yIHlvdXIgY29tbWVudHMg
YW5kIHNoYXJpbmcuIEkgbmVlZCB0byBub3RlIHRoYXQgTkhFIGlzIG5vdCBjb21wZXRpbmcgd2l0
aA0KPGJyPg0KQ2xpZW50LXNpZGUgSEUgb3IgY29tcGV0aW5nIHdpdGggZGVwbG95bWVudCBvZiBm
dWxseSBmdW5jdGlvbmluZyBJUHY2LiBUaGUgYmFja2dyb3VuZCBvZg0KPGJyPg0KTkhFIGlzIDo8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjEpIHRoZSBkdWFsc3RhY2sgaXMgcmVhbC4gQ2xpZW50IGlzIGZhY2luZyB0aGUgY2hvaWNl
IGlwdjQgb3IgaXB2Ni48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjIpIHRoZSBwb29yIG9yIHVucHJlZGljdGFibGUgSVB2NiBwZXJmb3JtYW5jZSBp
cyByZWFsICg8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJs
P3U9aHR0cHMtM0FfX3N0YXRzLmxhYnMuYXBuaWMubmV0X3Y2cGVyZiZhbXA7ZD1Ed01GYVEmYW1w
O2M9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZhbXA7cj1Mb0d6aEMtOHNjOFNZOFRxNHZyZm9nJmFt
cDttPVVDbEpzSnNDWGhpMEc4emZHdHlkLWpjNnhsVnllUC1wRGZEOWN1VTg5T1UmYW1wO3M9Y2lV
ZGNwb3hWOEc2TV9nNlJOWWdNXzNWekdmdDltYzJUVmxHbTNFUUt5MCZhbXA7ZT0iPmh0dHBzOi8v
c3RhdHMubGFicy5hcG5pYy5uZXQvdjZwZXJmPC9hPg0KICkuIDxicj4NCjMpIExvdyBhZG9wdGlv
biBvZiBDbGllbnQtc2lkZSBIRSBpcyByZWFseS4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U28gdGhlIHN1ZmZlcmluZyBvZiB1c2Vy
cyZuYnNwO2lzIHJlYWwgaW4gZHVhbHN0YWNrLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaGF0IHdlIGFyZSB0cnlpbmcgdG8gZG8g
aXMgdG8gbWFrZSB0aGUgZHVhbHN0YWNrIGxlc3MgcGFpbmZ1bCBmb3IgdXNlcnMgaW4gdGhlc2Ug
cmVnaW9ucy4NCjxicj4NCldlIGNhbiBub3Qgc2F5ICZxdW90O3lvdSBhcmUmbmJzcDtzdGFydmlu
ZyBvciBwb29yIGJlY3Vhc2UgeW91IGFyZSBub3QgcmljaCZxdW90Oy4gV2UgY2FuIG5vdCBqdW1w
DQo8YnI+DQpkaXJlY3RseSB0byBidWlsZCBhIGZ1bGx5IGZ1bmN0aW9uaW5nIElQdjYgaW4gb25l
IGRheSAobGlrZSByb21hIGNpdHkpLiBJIGZlZWwgc28gc2FkIHRoZSByZWdpb24NCjxicj4NCkkg
bGl2ZSBmYWlsZWQgdG8gY2F0Y2ggdXAgdGhlIGF2ZXJhZ2UgbGV2ZWwgb2YgSVB2NiBkZXZlbG9w
bWVudC4gQnV0IGl0IGlzIHRydWUgdGhlIElQdjYNCjxicj4NCmRldmVsb3BtZW50IHNpdHVhdGlv
biB2YXJpZXMgaW4gZGlmZmVyZW50IHBsYWNlcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TWF5YmUgeW91ciBvYnNlcnZhdGlvbiBpcyB0cnVl
IHRoYXQgbG9jYWwgSVNQIGlzIHRoZSBtYWpvciBzb3VyY2Ugb2YgYnJva2VuIElQdjYuIEhvd2V2
ZXIsJm5ic3A7PGJyPg0KdGhvdWdoIEknbSBub3QgbmV0d29yayBvcGVyYXRvciwgSSBoYWQgYXQg
bGVhc3QgdHdvIG9ic2VydmF0aW9ucyBvZiBJUHY2IGZhaWx1cmUgY2F1c2VkDQo8YnI+DQpieSBm
YXItZW5kJm5ic3A7YW5kIG1pZHN0LiBPbmUgY2FzZSBpcyBhIHJlYWwgdXNlciBjb21wbGFpbnQg
ZnJvbSBDaGluYSB0ZWxlY29tLiBJdCBwcm92ZWQNCjxicj4NCnRoYXQgdXNlciBleHBlcmluY2Vk
Jm5ic3A7bG9uZyBkZWxheSB3aGVuIFNlcnZmYWlsIGlzIHJlY2VpdmVkIHdoZW4gYXNraW5nIEFB
QUEgZm9yIG1hbnkgdGltZXMuDQo8YnI+DQpJdCBpcyB0aGUgcHJvYmxlbSBvZiBhdXRob3JpdGF0
aXZlIG9mIHRoYXQgc2l0ZS5Bbm90aGVyIGNhc2UgaXMgYSByZWFsIHJvdXRyaW5nIHByb2JsZW0g
b2YgbXkgb2ZmaWNlDQo8YnI+DQp3aGljaCBsYXN0cyBmb3IgdHdvIGRheXMgZHVlIHRvIHRoZSBt
aWRkbGUmbmJzcDt0cmFuc2l0IChIdXJyaWNhbmUgRWxlY3RyaWMpIG5vdCBhY2VwdCBteQ0KPGJy
Pg0KY29tcGFueSdzIHByZWZpeC4gVGhlcmUgYXJlIG90aGVyIGNhc2VzIG1heSBpbnRyb2R1Y2Vk
IGJ5Jm5ic3A7bXkgY28tYXV0aG9yIHdobyBoYXZlIDxicj4NCm1vcmUgZXhwZXJpbmNlIHJ1biBp
cHY2IG5ldHdvcmsuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPk1heWJlIHlvdSAoYW5kIG90aGVyIGd1eXMpIG1pc3NlZCB0aGF0IHRoZSBtb3N0
IGltcG9ydGFudCBhcmd1bWVudCBpbiB0aGlzIGRyYWZ0IGlzIGlmIEhFIGlzDQo8YnI+DQpub3Qg
d2lkZWx5IGRlcGxveWVkLCBOSEUgY2FuIGVuYWJsZSBJU1AgdG8gZGVsb3kgaXQgYW5kIGdhaW4u
Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90
ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRk
aW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4i
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMgZm9yIENETiBzdGF0ZW1lbnRzIG1hZGUgaW4gdGhp
cyB0aHJlYWQ6IENETnMgYXJlIGluIHRoZSBidXNpbmVzcyBvZiBvcHRpbWl6aW5nIGNvbm5lY3Rp
b25zIHRvIHRoZWlyIGNvbnRlbnQuIEhFIGlzbid0IGFib3V0IG9wdGltaXppbmcgY29ubmVjdGlv
bnMgLS0gaXQncyBhYm91dCBtb3JlIHF1aWNrbHkgcmVhY3RpbmcgdG8gdGhlIGxpa2VsaWhvb2Qg
b2Ygb3V0cmlnaHQgYnJva2VubmVzcy4gQnV0IGl0IHNvdW5kcw0KIGxpa2UgTkhFICppcyogYWJv
dXQgb3B0aW1pemluZyAod2hlcmUgSVB2NiBpc24ndCBicm9rZW4sIGJ1dCBpcyBqdXN0IHJlYWxs
eSBzbG93KT8gSSdtIGEgYml0IGNvbmZ1c2VkIGFib3V0IHRoaXMuPG86cD48L286cD48L3A+DQo8
L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BcyB0byB0aGlzIHF1
ZXN0aW9uLCZuYnNwOyBOSEUgZG9lcyB0aGUgc2FtZSB0aGluZyBIRSBkaWQgcmFjaW5nIHRoZSBJ
UHY2IGFuZCBJUHY0IGNvbm5lY3Rpb25zIHRvIGF2b2lkIGJvdGggYnJva2VuIGFuZCBzbG93IElQ
djYuIEJ1dCBOSEUgZG9lcyBvcHRpbWl6aW5nIGFzIHdlbGwgaW4gdGVybXMgb2Ygc3RvcHBpbmcg
c2VuZGluZyBhZGRpdGlvbmFsIHRyYWZmaWMgaWYgSVB2NiBjb25uZWN0aW9uIGlzIHNsb3cgKG5v
dA0KIGJyb2tlbikgLCBiZWN1YXNlIEFBQUEgcmVjb3JkIHdpbGwgbm90IGJlIHJlY2lldmVkIG9y
IEFBQUEgcmVjb3JkIGlzIHJlY2VpdmVkIHRvbyBsYXRlIChvbmUgcHJvbWlzaW5nIGRpcmVjdGlv
biBmb3IgbmV4dCB2ZXJzaW9uIG9mIE5IRSBkcmFmdCkuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRhdmV5Jm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--_000_2D09D61DDFA73D4C884805CC7865E6114DED128DGAALPA1MSGUSRBF_--


From nobody Fri Sep 28 17:07:46 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7CF130DC1 for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 17:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level: 
X-Spam-Status: No, score=-1.989 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, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_MONEY_PERCENT=0.01] 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 IKZidAskkPKk for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 17:07:42 -0700 (PDT)
Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (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 3B1E6127148 for <v6ops@ietf.org>; Fri, 28 Sep 2018 17:07:42 -0700 (PDT)
Received: by mail-pg1-x544.google.com with SMTP id f18-v6so2017147pgv.3 for <v6ops@ietf.org>; Fri, 28 Sep 2018 17:07:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=F4eEfGHfybEngJf8RuIxUgvcHZnX0Oqw2n7ZjoGy1/M=; b=e20x4JcTE06Rjg/0MOlH7gIsukRpRaZH0bTqIuGAOS/nbmR/U6iUQTSe9Gl0V2MsFe JpOflMIruB8gx2rr9U6xUGF2ofKFyEIdXCKOPLqZwET1WiQql9gehvWccg62QOSlnfWF 7/AYWGK4yemGy5y5/Vtfv4HCCfqY3TfzjD+1HHnXgRjDRUA0CnuWMWzBbpB1cI/QxA3r oIA0KnYji8Je687JZYbHeyD92IbHMweEddAsTEr0iHji6ZCwQRELD7A/BjyDZgAA7NnH FKkeCiqNoW1YSax7BW4NUilpoZ5YP/rKNR3CU5v4JfUIi22NOg52LMZBjJgqhA/ugeIG RKdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=F4eEfGHfybEngJf8RuIxUgvcHZnX0Oqw2n7ZjoGy1/M=; b=Qis83Ws0OVgZt/khPif4NSBURr8sjPg8aCRSvNm5Xde1kvt7Ad6gGm2qumHP+/xy+b rp2/NCMxBmPia0kS1sJK5qsn+Gj0/0ohk5+vH75gglapTheQlxS4WNIj6Cpt/7ki3Llu lBxse1L4BMVmJ7ButFM3RJdggN8dEi+8nRFCf9SnS4/3w0HB/w0AUJVrogMmaSYesa4c Rk2QXeWKODRKHPEeOHbvXN0pemp8W7YuwG1Hfz1DiMYVHSEWptLnOXASuphnxiJ7c/RV kSlqKKCV+aWRBtxHd2KClRo1RyRWpJzU73iVQ7SYd5u9f53JWSb1rA0ZM/kU5SmoZ4m3 2U4g==
X-Gm-Message-State: ABuFfoh7KPBDQr4UGX85BmdZi5CrOomyDbDc8neb+pa0Ih9SY7kjVFjB Eq8W7KC9FW/s47CVtAWAJf/3TEKC
X-Google-Smtp-Source: ACcGV62LZr32E0gyzN14pH3TcNjl1+D3oR8nlkM8SSQs55yU5sZik0RwURLNzfjbDYXJ0YxmZYpl+w==
X-Received: by 2002:a63:745e:: with SMTP id e30-v6mr828482pgn.446.1538179661139;  Fri, 28 Sep 2018 17:07:41 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id 70-v6sm9513337pfz.27.2018.09.28.17.07.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Sep 2018 17:07:40 -0700 (PDT)
To: Lee Howard <lee@asgard.org>, v6ops@ietf.org
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com> <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com> <96bb5ddb-95f9-2437-f0b2-b1274912bf3c@asgard.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a0079342-4c46-b5e1-b24c-97ac1db0e92a@gmail.com>
Date: Sat, 29 Sep 2018 12:07:33 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <96bb5ddb-95f9-2437-f0b2-b1274912bf3c@asgard.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_jwlLaqVyimvqpjB7eYLyrYsiAw>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 29 Sep 2018 00:07:45 -0000

On 2018-09-29 05:47, Lee Howard wrote:
>=20
>=20
> On 09/28/2018 01:01 PM, Alexandre Petrescu wrote:
>> For me it looks quite challenging to develop a meaningful vision in th=
is
>> space.
>>
>> On one hand, this Internet witnesses fast digital evolutions, and
>> disruptions, every other day. On another hand IPv6 overcoming IPv4=20
>> seems to advance very slowly. On a same timescale Windows leaped from =

>> 95 to 10, while IP still steps from 4 to 6.
> Windows 95 was a significant rebuild over Windows 3.11.=C2=A0 Each of t=
he=20
> next several versions were incremental upgrades, and all were both=20
> forward and backward compatible.
>=20
> Meanwhile, lots of work had to go into making IPv6 deployable, and it=20
> didn't really start until 2011. In that time, Windows has evolved from =

> Windows 7 to Windows 10 (skipping 9, so only two desktop upgrades).
>=20
>>
>> In that sense, I think IPv6 and IPv4 side by side as a double stack is=

>> still a viable evolution in the next decades, although not very fancy.=

>> The translation from one to another seems like an artificial path that=

>> keeps reinventing itself but with no clear advantage of one translatio=
n
>> mechanism over another. These IPv4-IPv6 translation mechanisms are lik=
e
>> satisfaction for our needs of getting there faster.
>=20
> How does a network run dual-stack when it's out of IPv4 addresses?

I think it all depends on what you mean by "network". The network I'm
on right now has all the IPv4 addresses it can possibly need, and my lapt=
op
sees a full dual stack service. It doesn't seem to care that its IPv4
address is in 192.168.178.0/24. It also has no idea whether the upstream
link is dual stack or not. (My upstream, above the NAT, is dual stack,
but my laptop doesn't need to know that.)

OK, I'm belabouring the obvious, but I want to cement the notion that
today and for many years to come, most hosts need to see a dual stack
network for everything to more or less work. Nothing new there, I've
been saying so since 1994 in my first RFC. (Well, there's a bit new,
in that 464XLAT is now an alternative to tunnels as a way to simulate
a dual stack if you don't actually run one. My laptop wouldn't know or
care if the CE used 464XLAT.)

> If it buys addresses, why does it run dual-stack?
> I guess you consider IPv6-only plus translation to be dual-stack?

If it looks that way to the end host, yes. Dual-stack isn't a religion,
it's a coexistence technique. Although people insist on using the
T-word (transition), everything's been about coexistence all along,
and still is.

> Agreed, for now different people are choosing different mechanisms, and=
=20
> there isn't yet a clear winner.

And there doesn't need to be, as far as I can see.
=20
>>
>> (but I also speculated at a time that Twitter would disappear in its
>> infancy because finger existed - the reverse happened; I also speculat=
ed
>> that iPhone 4 would do _only_ IPv4 and iPhone 6 _only_ IPv6 - it did n=
ot
>> happen).
> I haven't seen finger enabled on a system since 1992.
>=20
>=20
>>>
>>> In other words, the development of the technologies implied by IPv6
>>> took almost as long to develop as the technologies required to use
>>> IPv4 (and involved a few mis-steps). However, the impetus to use them=

>>> was much lower - whenever a technology was unavailable to make IPv6
>>> work, "well, you can always use IPv4". IPv6 didn't become "important"=

>>> until "always" became untrue. That started in 2011, when the IPv4
>>> address space available from the IANA (and eventually the RIRs) was
>>> depleted; it is becoming increasingly untrue as the cost of
>>> purchasing an IPv4 address spirals upward.
>>
>> I would like to react to this.
>>
>> We should reckon frankly what happened with this depletion.=C2=A0 It h=
as=20
>> been hugely advertised.=C2=A0 It is a few years now.
>>
>> It depleted.=C2=A0 But it is still possible to get IPv4 as long as the=
=20
>> unused space gets back.
> At about US$20 each.
>=20
>>
>> We can talk about refuelling IPv4.
>>
>> Maybe we need to wait for several cycles of depletion-refuelling in=20
>> order to sense a stronger need of IPv6.
>=20
>=20
> Right now, the cloud and CDN companies are essentially all of the IPv4 =

> demand. In terms of number of addresses and dollars spent, they are mor=
e=20
> than 90% of the market. The CDNs are mostly okay in IPv6 support, even =

> if they ingest over IPv4.
> The cloud providers are in a pile of trouble. AWS is way ahead of anyon=
e=20
> else for IPv6 support, and last I heard they're still buying IPv4=20
> addresses to make sure they have enough cushion. Azure can do a VM or a=
=20
> Load Balancer, but not both, which is more than Google Cloud can do=20
> (only LB). Oracle will allow you to open a ticket requesting IPv6, but =

> unless it's a Service Cloud, they'll close the ticket with no action.=20
> Alibaba promises an IPv6-only cloud by 2025, but so far has nothing but=
=20
> dreams.
>=20
> Something like seven years ago I predicted 500M IPv4 addresses in the=20
> market. About half have moved, but the market didn't really get moving =

> until about 2015. It's important to note that large net blocks are=20
> valued by large companies: nobody wants to manage hundreds of /18s.=20
> Unless the US government/Department of Defense releases several /8s, th=
e=20
> high end of the market is all but gone.
> Yes, there may be thousands of /16s still available, for over a million=
=20
> USD each and rising.
>=20
> 2018 has seen an inflection in pricing. But of course, nobody knows wha=
t=20
> happens next. My concern is that instead of "permissionless innovation"=
=20
> the IPv4 Internet will require significant capital just to get connecte=
d.
>=20
> We're also on track for 50% of the world to reach Google over IPv6 in=20
> two years. Several mobile networks are already IPv6-only internally, an=
d=20
> several large landline ISPs are either there or on their way.
>=20
>=20
> So, what do you advocate we wait and see? How long should we wait, and =

> what are we looking for?
> More importantly, once we see it, how much time will we have to do=20
> something about it, and will it be enough time?

Obviously I (Brian) don't think we should wait and see. But we have to
clearly separate the separable problems. I won't try and do that right
here, except that it's very clear that moving cloud services to IPv6
is an utterly different problem from moving user LANs and end systems to
dual stack coexistence. I think we (v6ops) do need another round of probl=
em
analysis.

   Brian

>=20
> Lee
>=20
>>
>> Alex
>>
>>>
>>> "Pick something else" - I have to wonder what "something else" might
>>> be in view. We have a number of research projects on the table, such
>>> as ICN/CCN/NBN, and they likely have their uses. But I don't see the
>>> architectural or business implications following through; if they
>>> were rationally available, they would have started a decade back, I
>>> suspect. So I see IPv6 deployment as the only rational option on the
>>> table.
>>>
>>>
>>> What I am increasingly hearing from ISPs and other networks is that
>>> it is less expensive to deploy an IPv6-only network with (or without)=

>>> an IPv4 overlay=C2=A0 than to deploy a dual stack network. There are =
a few
>>> networks that have drawn that conclusion; as more and more do, IPv4
>>> will become less of a requirement.
>>>
>>> I'm not sure what to expect next, and maybe people can inform me. One=

>>> option would be two networks that implement IPv6 natively and IPv4 as=

>>> an overlay service connect, meaning that the address of a 464XLAT
>>> PLAT (or whatever) from one carrier is an address in a different
>>> carrier for some part of one of their networks. Or, maybe, a network
>>> simply stops providing an IPv4 PLAT or other support for IPv4 as an
>>> overlay. Maybe they are running lw4o6 and it becomes necessary to do
>>> IPv4 routing inside that overlay, so that they want to charge for it
>>> as a service. The obviously implied next question is "when" - I'm
>>> guessing early 2020s or something like that.
>>>
>>>
>>> So, what do I expect the next few years to look like? I see three
>>> broad classes of ISPs, IXPs, and networks at the edge: those that see=

>>> IPv6 as the least expensive endpoint and drive to that end, those
>>> that have enough IPv4 for the moment and aren't thinking any further
>>> ahead than that, and those that are balanced on a knife's edge in
>>> between. We have those now. I expect to see a shifting balance, with
>>> different markets adopting different perspectives and changing over
>>> time. I see a slow but definitely discernible motion from "IPv4
>>> works" to "https://www.youtube.com/watch?v=3D_y36fG2Oba0" "I suppose =
we
>>> ought to give it a try". One at a time, I hear operators say "I don't=

>>> want to buy any more IPv4 addresses". The networks that are fixed in
>>> the "IPv4 laggard" camp tend to be networks that aren't faced with
>>> IPv4 address purchases and ask for a business justification that
>>> doesn't involve a monetary outlay.
>>>
>>> Ron, Lee, and I asked for a change to the v6ops charter to discuss
>>> IPv6-only networking with that in view. What I want to see in v6ops
>>> is more of that - lets move IPv4 to an overlay service, and watch it
>>> become less relevant over time.
>>>
>>> So I personally expect transition technologies of various kinds -
>>> lw4o6, 464xlat, MAP-E, MAP-T, and so on - to remain important, but I
>>> expect that they will become the aftermarket more than the market. If=

>>> cloud services are accessible by IPv6, I expect residential access to=

>>> become IPv6 service to become larger and IPv4 to become smaller. If
>>> you want a picture of that, look at Trinidad and Tobago. As I
>>> understand it, there are some services (Google, Facebook, etc) that
>>> only offer IPv6 access there, so the "IPv6" picture is a picture of
>>> their market dominance.
>>> https://stats.labs.apnic.net/ipv6/CC?x=3D1&s=3D1&p=3D1&w=3D30&c=3DTT
>>>
>>> I expect service providers to do as little with IPv4 as they can get
>>> away with, and for IPv4 to increasingly become ragged around the
>>> edges. There are still a variety of places where I would get tarred
>>> and feathered and sent home wearing a barrel for saying that, but the=

>>> SNA people were of that opinion too - until APPN made SNA networks
>>> irrelevant and people started deploying IP-native applications.=20
>>> ---------------------------------------------------------------------=
-----------=20
>>>
>>>
>>>
>> Victorious warriors win first and then go to war,
>>> Defeated warriors go to war first and then seek to win. Sun Tzu
>>>
>>>
>>>
>>> _______________________________________________ v6ops mailing list=20
>>> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


From nobody Fri Sep 28 23:06:52 2018
Return-Path: <otroan@employees.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C42741271FF for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 23:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 59KOh2J5OCkY for <v6ops@ietfa.amsl.com>; Fri, 28 Sep 2018 23:06:49 -0700 (PDT)
Received: from bugle.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10E2F124C04 for <v6ops@ietf.org>; Fri, 28 Sep 2018 23:06:48 -0700 (PDT)
Received: from [192.168.10.187] (30.51-175-112.customer.lyse.net [51.175.112.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id 51F49FECBC64; Sat, 29 Sep 2018 06:06:45 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ole Troan <otroan@employees.org>
X-Mailer: iPhone Mail (16A366)
In-Reply-To: <91A911BA-B85A-437E-AF51-D02EB5B51BC1@gmail.com>
Date: Sat, 29 Sep 2018 08:06:42 +0200
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FC02368-6913-4FD7-804D-7AE536B9089F@employees.org>
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com> <20180925072015.GV11393@Space.Net> <CAAObRXKhS++5_cmvjTx3LY+ti6NbGj1NvtL6XeQGOvYuJKw0uw@mail.gmail.com> <3BDC24C2-6D51-4FF1-8A48-CAD4F8CEBF9C@employees.org> <CAAObRXJd3Ym_JezijzFVGGUj6hnkLd78dA-B_oug1gZ_-kbeAw@mail.gmail.com> <CAKr6gn0p0ayWimZ8kWCAfNhLnpaK3j9WOGOmNCMXMac=cLR1Tw@mail.gmail.com> <5167BC92-DAC7-4F40-8DD4-E4A0ECEAC4BD@gmail.com> <AC3405AC-14A8-4828-BD40-37170C1F654C@gmail.com> <3ecf8076-3056-94a5-1229-959cb2e38e6d@gmail.com> <AE7687A9-F28C-4DB2-AECD-709A7EB4C778@gmail.com> <A06CFC7A-DA95-4D06-8509-4B90C6D6D256@employees.org> <91A911BA-B85A-437E-AF51-D02EB5B51BC1@gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1YmHHGNjTZJeWr163cPBqMH1WVQ>
Subject: Re: [v6ops] Trajectory for "transition" mechanisms in our working group
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 29 Sep 2018 06:06:51 -0000

Fred,

> On 28 Sep 2018, at 21:32, Fred Baker <fredbaker.ietf@gmail.com> wrote:
>=20
>=20
>=20
>> On Sep 28, 2018, at 11:47 AM, Ole Troan <otroan@employees.org> wrote:
>>=20
>> Fred,
>>=20
>>> On 28 Sep 2018, at 20:26, Fred Baker <fredbaker.ietf@gmail.com> wrote:
>>>=20
>>> it. CLAT-PLAT translation means that the ISP doesn't have to think about=
 it too much; lw4o6 tunnels become a network of their own that someone has t=
o manage.
>>=20
>> I don=E2=80=99t understand this statement.
>> You seem to imply that there should be less management with 464XLAT aka d=
ouble translation than tunneling? Why do you believe that?
>=20
> With translation, there are two translators. With a tunnel, there are two t=
unnel endpoints. I see the number two in both statements.
>=20
> In addition, in both cases the connection gets to an IPv4 Internet. Howeve=
r, at some point, that network starts to break down. If, for example, it bec=
omes a set of tunnels leading to each neighboring ISP, then there is routing=
 somewhere in the lw4o6-or-whatever system to select the right neighboring I=
SP. If it's translation, then that routing can be accomplished using the IPv=
6 prefix plus some subset of the IPv4 address in question.

A future where IPv4 routing is injected into IPv6 routing. Didn=E2=80=99t we=
 drop that idea when deprecating auto-tunnels and IPv4 compatible addresses?=


It might be one future, but personally I doubt the =E2=80=9Cnetwork starts t=
o break down=E2=80=9D part.=20

Cheers=20
Ole


>=20
> --------------------------------------------------------------------------=
------
> The fact that there is a highway to hell and a stairway to heaven is an in=
teresting comment on projected traffic volume...
>=20


From nobody Sat Sep 29 02:38:53 2018
Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8CB130DE8 for <v6ops@ietfa.amsl.com>; Sat, 29 Sep 2018 02:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 0ihjuOg4BcGH for <v6ops@ietfa.amsl.com>; Sat, 29 Sep 2018 02:38:48 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FE4C130DC9 for <v6ops@ietf.org>; Sat, 29 Sep 2018 02:38:47 -0700 (PDT)
Received: from [192.168.0.104] (84-217-107-21.customers.ownit.se [84.217.107.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 24DAB867AF; Sat, 29 Sep 2018 11:38:29 +0200 (CEST)
From: Fernando Gont <fgont@si6networks.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ole Troan <otroan@employees.org>, George Michaelson <ggm@algebras.org>
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>
References: <9B8DB67F-DF22-4E5D-8EC5-90E79E3C86A2@gmail.com> <33af3d07-c1be-783a-e7a7-d1674c46b51d@asgard.org> <CAD6AjGQ_OBFGJb_C+mP_87nu7q_oXPrTvxhaV_=RcubeHtMy2Q@mail.gmail.com> <E345387F-6C1D-49D4-8B03-52D04498DDA5@lists.zabbadoz.net> <a9eeba1b-76dc-a69f-aabe-04fa4ddc3a4f@gmail.com> <e560c82c-085e-60fe-2076-70e3624696c0@asgard.org> <9142206A0C5BF24CB22755C8EC422E459CB46310@AZ-US1EXMB03.global.avaya.com> <76055AE4-FF87-47E1-988A-CDB7E157C6AD@delong.com> <9142206A0C5BF24CB22755C8EC422E459CB4644F@AZ-US1EXMB03.global.avaya.com> <CAN-Dau26+uOpa9+CSf5QGmbqbmW5UisM3zxitLv12pLWRmZ8rQ@mail.gmail.com> <f2d934cb-5075-fc1c-49d5-71d4613b3b9c@gmail.com> <CAKr6gn2UJiEr2B4O9z7niMxm46fHzmw26+g++H=7i49wYh8Khg@mail.gmail.com> <4645850B-9496-49F0-A284-09E01C0ED820@employees.org> <68a76cb2-911f-186d-dc78-7d6116dcb790@si6networks.com> <a0736784-77f7-5d09-f961-a5b4428e684e@gmail.com> <bcbdfd68-1331-4966-e4e0-c402bb6ad703@si6networks.com> <21e9805c-7c2e-3261-4bf6-04fb21f60f41@gmail.com>
Openpgp: preference=signencrypt
Autocrypt: addr=fgont@si6networks.com; prefer-encrypt=mutual; keydata= xsFNBE5so2gBEACzBQBLUy8nzgAzSZn6ViXT6TmZBFNYNqTpPRvTVtUqF6+tkI+IEd9N2E8p pXUXCd0W4dkxz6o7pagnK63m4QSueggvp881RVVHOF8oTSHOdnGxLfLeLNJFKE1FOutU3vod GK/wG/Fwzkv9MebdXpMlLV8nnJuAt66XGl/lU1JrNfrKO4SoYQi4TsB/waUQcygh7OR/PEO0 EttiU8kZUbZNv58WH+PAj/rdZCrgUSiGXiWUQQKShqKnJxLuAcTcg5YRwL8se/V6ciW0QR9i /sr52gSmLLbW5N3hAoO+nv1V/9SjJAUvzXu43k8sua/XlCXkqU7uLj41CRR72JeUZ4DQsYfP LfNPC98ZGTVxbWbFtLXxpzzDDT8i3uo7w1LJ2Ij/d5ezcARqw01HGljWWxnidUrjbTpxkJ9X EllcsH94mer728j/HKzC9OcTuz6WUBP3Crgl6Q47gY5ZIiF0lsmd9/wxbaq5NiJ+lGuBRZrD v0dQx9KmyI0/pH2AF8cW897/6ypvcyD/1/11CJcN+uAGIrklwJlVpRSbKbFtGC6In592lhu7 wnK8cgyP5cTU+vva9+g6P1wehi4bylXdlKc6mMphbtSA+T3WBNP557+mh3L62l4pGaEGidcZ DLYT2Ud18eAJmxU3HnM8P3iZZgeoK7oqgb53/eg96vkONXNIOwARAQABzSVGZXJuYW5kbyBH b250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20+wsGBBBMBAgArAhsjBQkSzAMABgsJCAcDAgYV CAIJCgsEFgIDAQIeAQIXgAUCTmylpQIZAQAKCRCuJQ1VHU50kv7wD/9fuNtTfxSLk3B3Hs3p ixTy8YXVjdkVwWlnJjFd7BOWmg7sI+LDhpjGfT6+ddOiwkumnvUZpObodj4ysH0i8c7P4C5t F9yu7WjklSlrB5Rth2CGChg5bKt541z2WHkFFxys9qBLmCSYDeKQkzLqhCjIUJizY2kOJ2GI MnSFDzJjhSFEh//oW830Y8fel1xnf/NVF+lBVtRMtMOfoWUqDjvP3sJ1G4zgkDCnF0CfncLx +hq2Mv26Uq9OTzvLH9aSQQ/f067BOkKAJKsfHdborX4E96ISTz57/4xECRSMr5dVsKVm4Y// uVIsb+L5z+a32FaiBZIAKDgnJO7Z8j6CV5e5yfuBTtX52Yi9HjYYqnYJGSDxYd6igD4bWu+7 xmJPHjkdqZgGV6dQIgiUfqkU+s5Cv350vK48CMaT/ZLo2BdsMhWsmaHmb+waePUMyq6E4E9x 9Js+EJb9ZiCfxS9exgieZQpet1L36IvhiwByvkQM009ywfa30JeMOltUtfLi5V06WQWsTzPL 5C+4cpkguSuAJVDTctjCA0moIeVDOpJ8WH9voQ4IeWapQnX35OIoj1jGJqqYdx65gc1ygbyx b8vw+pJ9E5GLse5TQnYifOWpXzX9053dtbwp/2OVhU4KLlzfCPCEsoTyfu9nIZxdI2PMwiL5 M85BfjX4NmwBLmPGoM7BTQRObKNoARAAqqXCkr250BchRDmi+05F5UQFgylUh10XTAJxBeaQ UNtdxZiZRm6jgomSrqeYtricM9t9K0qb4X2ZXmAMW8o8AYW3RrQHTjcBwMnAKzUIEXXWaLfG cid/ygmvWzIHgMDQKP+MUq1AGQrnvt/MRLvZLyczAV1RTXS58qNaxtaSpc3K/yrDozh/a4pu WcUsVvIkzyx43sqcwamDSBb6U8JFoZizuLXiARLLASgyHrrCedNIZdWSx0z0iHEpZIelA2ih AGLiSMtmtikVEyrJICgO81DkKNCbBbPg+7fi23V6M24+3syHk3IdQibTtBMxinIPyLFF0byJ aGm0fmjefhnmVJyCIl/FDkCHprVhTme57G2/WdoGnUvnT7mcwDRb8XY5nNRkOJsqqLPemKjz kx8mXdQbunXtX9bKyVgd1gIl+LLsxbdzRCch773UBVoortPdK3kMyLtZ4uMeDX3comjx+6VL bztUdJ1Zc9/njwVG8fgmQ+0Kj5+bzQfUY+MmX0HTXIx3B4R1I1a8QoOwi1N+iZNdewV5Zfq+ 29NlQLnVPjCRCKbaz9k6RJ2oIti55YUI6zSsL3lmlOXsRbXN5bRswFczkNSCJxJMlDiyAUIC WOay7ymzvgzPa+BY/mYn94vRaurDQ4/ljOfj6oqgfjts+dJev4Jj89vp8MQI3KJpZPEAEQEA AcLBZQQYAQIADwUCTmyjaAIbDAUJEswDAAAKCRCuJQ1VHU50km4xEACho45PZrUjY4Zl2opR DFNo5a6roTOPpgwO9PcBb3I5F8yX2Dnew+9OhgWXbBhAFq4DCx+9Gjs43Bn60qbZTDbLGJ/m 8N4PwEiq0e5MKceYcbetEdEUWhm5L6psU9ZZ82GR3UGxPXYe+oifEoJjOXQ39avf9S8p3yKP Diil0E79rn7LbJjMcgMLyjFg9SDoJ6pHLtniJoDhEAaSSgeV7Y745+gyMIdtQmrFHfqrFdjq D6G0HE+Z68ywc5KN67YxhvhBmSycs1ZSKAXv1zLDlXdmjHDHkU3xMcB+RkuiTba8yRFYwb/n j62CC4NhFTuIKOc4ta3dJsyXTGh/hO9UjWUnmAGfd0fnzTBZF8Qlnw/8ftx5lt4/O+eqY1EN RITScnPzXE/wMOlTtdkddQ+QN6xt6jyR2XtAIi7aAFHypIqA3lLI9hF9x+lj4UQ2yA9LqpoX 6URpPOd13JhAyDe47cwsP1u9Y+OBvQTVLSvw7Liu2b4KjqL4lx++VdBi7dXsjJ6kjIRjI6Lb WVpxe8LumMCuVDepTafBZ49gr7Fgc4F9ZSCo6ChgQNLn6WDzIkqFX+42KuHz90AHWhuW+KZR 1aJylERWeTcMCGUSBptd48KniWmD6kPKpzwoMkJtEXTuO2lVuborxzwuqOTNuYg9lWDl7zKt wPI9brGzquUHy4qRrA==
Message-ID: <7cb18f27-159a-ae2e-1ddf-0edbd8e40a4c@si6networks.com>
Date: Sat, 29 Sep 2018 06:11:47 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <21e9805c-7c2e-3261-4bf6-04fb21f60f41@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dWgPMLI3TxhQXzC5rekEv5WtxDw>
Subject: [v6ops] Thinking about problems in IPv6-only networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 29 Sep 2018 09:38:51 -0000

Hello, Brian,

On 09/04/2018 04:03 AM, Brian E Carpenter wrote:
[...]
>>
>>> Any node that emits IPv4 traffic when the bit
>>> is set is either a legacy host or a dual stack host that's not entered
>>> a v6-only mode. So that means it's a host worth checking as part of
>>> the v6-only test.
>>>
>>> **"Dual stack hosts that have a good reason to use IPv4, for example for
>>>    a specific IPv4 link-local service, can continue to do so.  This is
>>>    consistent with the SHOULD language in this document."
>>
>> But... is that IPv6 only? At the end of the day, it would seem that for
>> most home and enterprise networks, you will always have a reason for
>> doing some IPv4.. so I wonder when one would see this bit have practical
>> effect. -- most enterprise and home networks will normally do DNS-SD or
> 
> DNS-SD works for IPv6 too afaik

Appolgies if my comment was misleading/sloppy -- I meant, in general:
they do deal with devices that are IPv4-only.



>> LLMNR, and associated sevices. Also, think about e.g. printers that are
>> likely going to remain IPv4-only till they eventually beak and get replaced.
> 
> Indeed. This is a long-term play; I would expect that if the IPv6only bit is
> approved and deployed, it will become increasingly relevant as the legacy
> nodes slowly vanish. And at the end it will become irrelevant again.

Apologies if this has already been discussed, and I just missed it:

I envision two alternatives:

1) "the network/router knows better", and then reaction to the IPv6-only
flag is more of a MUST (well, could be a "SHOULD", but certainly not
with a clause that is expected to be common.. otherwise it's not an
"exception", but rather a rule :-) ). That way, the flag could
indeed disable IPv4 on the network.

2) "end hosts know better", and reaction to the flag becomes kind of a
"MAY". And I'm not sure to what extent the flag will have much of a
practical effect on networks. -- particularly when the hosts don't
really "know better" -- the best they can do is "keep trying"... whether
for actually getting an IPv4 address and/or for things like DNS-SD.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




